PDA

View Full Version : Bitrate vs Output avi size


Nozomi
25th November 2001, 07:30
I have the following 2CD profile for Nandub v1.0RC2.
I used it with "Enemy at the Gate" and the output avi size is always 1.04G for bitrate setting between 1250Kbps to 1450Kbps while encoding with the same first pass stats file. Any idea why? There is no reason to increase the bitrate without affecting the output avi size, am I hitting a bug? Frameserving method: DVD2AVI176 -> Avisynth (crop & resize) -> Nandub...

VirtualDub.audio.SetSource(1);
VirtualDub.audio.SetMode(0);
VirtualDub.audio.SetInterleave(1,500,1,0,0);
VirtualDub.audio.SetClipMode(1,1);
VirtualDub.audio.SetConversion(0,0,0,0,0);
VirtualDub.audio.SetVolume();
VirtualDub.audio.SetCompression();
VirtualDub.audio2.SetSource(1);
VirtualDub.audio2.SetMode(0);
VirtualDub.audio2.SetInterleave(1,500,1,0,0);
VirtualDub.audio2.SetClipMode(1,1);
VirtualDub.audio2.SetConversion(0,0,0,0,0);
VirtualDub.audio2.SetVolume();
VirtualDub.audio2.SetCompression();
VirtualDub.video.SetDepth(24,24);
VirtualDub.video.SetMode(1);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetRange(0,0);
VirtualDub.video.SetDivX(1300,10);
VirtualDub.video.SetQualityControl(1,0,0,0);
VirtualDub.video.SetMotionDetection(8,10,300,300);
VirtualDub.video.SetCrispness(30,0);
VirtualDub.video.SpaceKF(24);
VirtualDub.video.InternalSCD(100);
VirtualDub.video.SetMinKBPS(320);
VirtualDub.video.SetCurveFile("");
VirtualDub.video.SetCurveMcFactor(25);
VirtualDub.video.SetCurveCompression(10,3);
VirtualDub.video.SetCurveFilter(270,6000);
VirtualDub.video.SetCurveCredits(0,150);
VirtualDub.video.SetLumaCorrectionAmp(1,10,30);
VirtualDub.video.SetCurveRedist(0);
// VirtualDub.video.CalcCurveCompression();
VirtualDub.video.SetCompLevelsMain(2,16);
VirtualDub.video.SetCompLevelsA(300,3,16);
VirtualDub.video.SetCompLevelsB(300,4,16);
VirtualDub.video.SetCompLevelsC(300,5,16);
VirtualDub.video.SetCompLevelsD(300,6,16);
VirtualDub.video.SetCompLevelsE(300,7,16);
VirtualDub.video.SetCompLevelK(4,31);
VirtualDub.video.SetBitsReservoir(0,35,40,100,45,0);
VirtualDub.video.SetLowBrCorrection(0,0);
VirtualDub.video.NoAVIOutput(0);
VirtualDub.video.GenStats("",0);
VirtualDub.video.SetEncodingControl("");
VirtualDub.video.filters.Clear();
VirtualDub.subset.Delete();
VirtualDub.brc.Set( 0, 695 );
VirtualDub.brc.Set( 1, 2 );
VirtualDub.brc.Set( 2, 0 );
VirtualDub.brc.Set( 3, 0 );
VirtualDub.brc.Set( 4, 0 );

manono
25th November 2001, 09:39
Hi-I'm not too good at reading those things, but what's the resolution? That movie is quite compressible, and you may have maxed out the file size already and all DRFs may already be 2. That movie can easily be done for 1 CD. If you still want 2 CDs, perhaps use a higher resolution, and Precise Bicubic Resize. Maybe open the .stats file in GKnot at your current resolution and bit rate and audio file size (if it's figured in), and I'll bet that Video Size/First Pass Size is greater than 100%, which will prove you can't increase the file size. There's no bug.

Nozomi
25th November 2001, 13:01
Originally posted by manono

Hi-I'm not too good at reading those things, but what's the resolution? That movie is quite compressible, and you may have maxed out the file size already and all DRFs may already be 2. That movie can easily be done for 1 CD. If you still want 2 CDs, perhaps use a higher resolution, and Precise Bicubic Resize. Maybe open the .stats file in GKnot at your current resolution and bit rate and audio file size (if it's figured in), and I'll bet that Video Size/First Pass Size is greater than 100%, which will prove you can't increase the file size. There's no bug.

MPEG Layer-3,162 kBit/s, 48,000 Hz, Stereo
Resolution = 720 x 304, 24bitsĦA188568 FramesĦA23.976fpsĦA142KB/SecĦADIVXMPG4 V3
Total AVI File Size = 1.07GB

I will check with GKnot...

manono
25th November 2001, 15:17
Wow-high resolution. I may be wrong, then. You might need realSpiderman or rmatei to decipher that thing to tell you what's wrong.

Nozomi
25th November 2001, 15:27
You're right...

Gordian Knot reported:
Video Size / First Pass Size = 72.5%
All frames already at DRF Level 2

manono
25th November 2001, 17:19
Hi Nozomi-I hate to prove myself wrong, when you've already said I'm right, but I may be missing something. When you run through the movie after loading the .stats file and check the DRFs, they'll always say 2, because, of course, that's what the first pass does. If your Video Size/First Pass Size is 72.5% (and that's with a bit rate of 1250-1450?), although that'll produce an excellent quality movie, you aren't at maximum file size. So I'm not sure why you had your original problem. I wouldn't worry about it too much though, if I were you. I love that movie although, as perhaps you know, it's not too historically accurate.

FxOverlord
25th November 2001, 18:51
Since u have a 1.07GB first pass with 72.5% b/p why not try putting it on 1CD. It is obvious that this film is quite compressable and remember that 720 x ... is a VERY high resolution. So perhaps u could do a 1CD 640 x ...

Nozomi
9th December 2001, 11:13
Originally posted by manono

... If your Video Size/First Pass Size is 72.5% (and that's with a bit rate of 1250-1450?), ...

Wait the second, do I need to have Bitrate -> Avi File Size set to "2 CDs" before I load the Nandub Stats File in GKnot? Since everyone just mention loading the Stats files but not setting to 2 CDs...

I found Vido Size/First Pass Size = 145.5% after setting it to 2 CDs, the above 72.5% is for 1 CD only. So maybe that explain why I can no longer increase the 2nd pass output size.

manono
9th December 2001, 22:49
Hi Nozomi-Boy-that was a long time between posts. So I wasn't wrong after all. Originally you had said you were doing it for 2 CDs, and then you came back later and said Video Size/First Pass Size was 72.5% without saying that you had changed to 1 CD (or had kept the default 700 MB setting). You can set bit rate to whatever you want before you load the stats file, but I preset it at my intended final size, so that Video Size/First Pass Size actually means something. In your case, intending to make a 2 CD copy of the movie, you load the stats file (with file size preset for 2 CD=1400 MB), see it's 145.5%, adjust bit rate for 1 CD=700 MB, see it's 72.5%, and do the second pass for 1 CD. That's how I'd do it anyway. 72.5% is very high quality. Of course, Enemy At The Gates was done a long time ago, I'm sure. Kind of hard to screw up with that movie, it's so easy.

Nozomi
10th December 2001, 02:59
Hi Manono, this is the first time I encountered cannot reach the final avi size - usually, it should be the other way around :) Beside, this is also the first time I use Gordian Knot because Doom9 said that it is not very useful some times ago...

I've a full study on GKnot yesterday because I would like to make sure I did everything correct before go ahead with Pearl Harbour, this time a 3 hrs.+ movie. Then I did EAG all over again with GKnot, it actually reported 1257K is actually the maximum bitrate I can use with this movie and the final avi size is around 1.2G - please note that I already increased the resolution as well this time to actually higher than the DVD source!

manono
10th December 2001, 05:56
Hi Nozomi-There's someone around here (Steady? I forget) who recommends 800*xxx for movies and setting monitor resolution at 800x600, so the vid card doesn't need to rescale, and the result is a better picture (something like that-it was kind of over my head). I'm glad Enemy worked out for you.

Have fun with Pearl Harbor. About 2/3 of the movie is on 1 disc and the remainder on the other. Pretty screwy if you ask me. Probably easiest to do it for 3 CDs, or else you have a lot of extra work with joining and cutting.

Nozomi
16th December 2001, 07:05
Originally posted by manono
Have fun with Pearl Harbor. About 2/3 of the movie is on 1 disc and the remainder on the other. Pretty screwy if you ask me. Probably easiest to do it for 3 CDs, or else you have a lot of extra work with joining and cutting.

Hi, I just done Pearl Harbour at exactly 2.1G for 3 x 700M CDs.

I also tried Enemy in higher resolution - the result is playback become very machine horse power demanding, not good at all!