Skeleton Key/CCEAQM Enabled, undersized

[TheSeeker]

I'm using DVDRB 1.05 pro, cce sp 2.70, dgdecode that comes with dvdrb, avisynth 2.55.

I DID preprocess with DVDRemake to get rid of all extras and the resulting dvd folder was 5.15 gb. when I ran it through dvdrb in cce mode and cceaqm enabled the result was a 4.03 gb dvd folder. Im guessing this is because the cceaqm option made the movie that much more compressible and that the size prediction didn't take that into account. Or my preprocessing just messed it up. Im not sure. Jdobbs, I know well your stance on preprocessing, but in your opinion is this normal behavior? Should I just up the target sectors when using cceaqm?

[Rockas]

My guess is that you should try a backup without pre-processing ;)

[TheSeeker]

I plan on doing that. But the segment editor that comes with DVDRB never seems to show all extras to be blanked out. For example, in skeleton key the extras are like this:

vts 2 - 158mb
vts 3 - 878mb
vts 4 - 750mb
vts 5 - 738mb
vts 6 - 260mb

but the dvdrb segment editor shows it something like this:

vts 2 - 89mb
vts 3 - 475mb
vts 4 - 375mb
vts 5 - 410mb
vts 6 - 150mb

Im just wondering if Im doing something wrong? Why doesn't the segment editor show the full extra vts's? Its almost like it's only showing half of the actual content in the vts.

In DVDRB's input settings window, it shows that all extra vts's add up to approx. 2,722 mb of content. When I blank every single extra segment that comes up in the segment editor however, it says I only recovered 1,561mb. Am I doing something wrong here? This is the only reason I use any 3rd party software at all to do preprocessing, otherwise I would be doing everything with DVDRB.

[SpazzHH]

Try reading this (http://forum.doom9.org/showthread.php?p=482090#post482090) thread for the hidden settings. Or even the help file that comes with RB. :rolleyes:

[TheSeeker]

Try reading this (http://forum.doom9.org/showthread.php?p=482090#post482090) thread for the hidden settings. Or even the help file that comes with RB. :rolleyes:

Hmm... I fail to see how that answers my question about cceaqm and its effect on target size prediction. Or my question about the segment editor. If you will actually take the time to read my posts, I wasn't asking HOW to up the target sectors, I was asking if that was the only solution to my issue. I already knew how to up the target sectors settings. gawd. A couple of months joined to this forum and you think you can talk down to anyone with a question. Take your condescension somewhere else and make way for someone that can actually help me.

How cute, you actually thought you knew something...

[Rockas]

I think SpazzHH was refering this:

VTS Minimium Size Re-Encode Threshold

vts_min_size=n
That means that if you put something like under [Options] section:
vts_min_size=1

All the VTSs will be shown on the Preview/Editor

[ilpippo80]

@TheSeeker
You're doing nothing wrong, the segment editor shows only the size calculated for the output, which is a dvd5, so it's normal that it's about the half of the original one...

[jdobbs]

I'm not positive about AQM in one pass mode (I assume you did a one-pass since you mentioned prediction). I'll have to look and see if is applied during the Phase I predictions. That's a good point.... but I wonder what the affect would be when it has so many "scene changes" (samples) during a prediction... that's one for the brainiacs to consider...

[TheSeeker]

@TheSeeker
You're doing nothing wrong, the segment editor shows only the size calculated for the output, which is a dvd5, so it's normal that it's about the half of the original one...


Thank you, thats all I needed to know. I didn't know that it showed the approx. resulting size instead of the original size, thanks much.