Any way to get detailed log/stat/debug for 2nd pass ?

[jugm]

Hi

Need some help with Nandub. I'm shooting for two 700mb CDs backup (512x216, 253122 frames, 2:55:57). I need about 200mb for sound and rest 1200-1300 Meg for video. For some reason I always end up with 1000 Meg AVI file(to be exact 1030..1040 Meg). All I want is to feed 200 more Megs to NanDub but he seems rejecting this generous gift from me ! :confused:

What I've tried to force Nandub use more space :

- In bitrate calc set audio size to 50 meg assuming to get back 200 meg larger AVI (increased bitrate that is)
- Increased Gauge to min 55%, max 100% AND decreased DRF to min 2x, max 4x

But Nandub ignored both changes judging from result AVI size (same 10xx Mb) :mad:

So are there any way to tell how and what has happened on 2nd pass ? Could Nandub use more bits at some scene or may be I better do more agressive settings ? But from what I read DRF min=2, max=4 is kinda agressive even for 2 CD ? Only thing I set a bit low is Low-pass=4000. Video is rather noisy as are action scenes and I thought to save some bits. I can post .vcfs if neccesary. But most settings are from doom9's guides.

-- jugm

[jrmillerUT]

Hi jugm,

Question... are you using GKnot to generate avs files and analyze? I don't mean to encode with it but generate ecf files and do compress tests? Some movies are soo compressible that a 2cd rip at xxxx resolution is actually the full first pass, eg DRF=2 at 6000k/s. There is no way to make that movie occupy more space at the given resolution if thats the case. Also is that 1040megs w or w/o audio? vcf's would really help, also what movie is it? I'd say try upping the resolution just a little bit and see if that helps...

a good example is Snatch, with ac3 and full res it doesn't fit 2cd's fully. Maybe you have the extreme rare case that you could maybe try a 1 cd rip of a 3 hr long movie? :)


James

[jrmillerUT]

ooops forgot to answer main q'... in nandub on your second pass... enter a diff stats file name (to save the new one) in the "collect in field" above the "encode using"... will generate a stats file based on the 2nd pass

read this

http://members.tripod.de/de_koepi/nandub_options_explained.html

[jugm]

Movie is "A Bridge Too Far". I think you pointed me in right direction. I had both "collect in" and "encode using" set to the same .stats file I use to encode. May be it was overwritten or something. I'll try redo .stats and make those files different.

I do not use GKnot for compress test. I only checked bits/pixel value in GKnot's calculator (was something like 0.27 or 0.25 but certainly above 0.2 and below 0.3).

[jrmillerUT]

sometimes you have to go even higher than .3 depending on the movie... Starship troopers is a good example. I have to go redo the first 4 Escaflowne epi's i'm doing cause they are all 20mb undersized and encoded at a constant DRF 2 :)

[LotionBoy]

jugm,

do a compressibility test or load your stat file into GKnot and see what that tells you. It will very quickly tell you if your target size is reachable.

LotionBoy

[jugm]

@LotionBoy

Will do that GKnot compressibility test. I guess first thing I need is a good stats file as old one could have been overwritten earlier. My 1-st pass is running now... And it shows "projected file size" 900-1000 Mb. Also in that blue graph stat bitrate value changes from ~600 to ~1200. Does it mean that I would get ~1000 Mb file if I encode with DRF=2 and bitrate=6000 ?

And another one... Cyan "motion" curve never reaches mid of blue bars. It looks very "low". May be max at 1/2 or 1/3 of the blue bars. May it be that motion detector doesn't work well (bad settings?) or its normal ? Any way to read absolute "motion" value from that cyan graph ?

--jugm