Number of passes (sorry to ask this)

[raddygast]

I am sure this has been asked a gajillion times. But with CCE SP, what would be the optimal default settings? DVD-RB seems to want to use VBR Bias 25, Quality Prec 16, and Passes set to 2. Is it worth bumping this up to 3 (because I really don't want to go to 4).

All I want is an end result that is better quality than using deep analysis with Quality Enhancement Mode on in Shrink. Because with those options on, Shrink takes only maybe 45 minutes less than DVD-RB.

[jdobbs]

Two for most, three for tough ones. Anything more shows negligible improvements.

As for your second question, if using CCE the answer is absolutely. The more difficult the encode the more difference you will see. Anyone who argues that needs glasses.

There are rare instances, where the original disc was encoded at a much higher rate than was necessary, in which you may be better off with DVD Shrink. But is is exceptionally rare. The reason is because of the limitations inherent in within-the-compressed-domain encoding (used by several one click encoders, including DVD-RB's ReJig support).

To its credit, though, DVD Shrink is fast, rock solid, and has more features than you can shake a stick at!

The reason I wrote DVD-RB was to get the best picture possible, with a heavy emphasis on using the highest quality encoders (like CCE, QuEnc, ProCoder, and now HC).

[raddygast]

Thanks for your response. I'm really grateful that you did write RB.

I just wanted to clarify though, that 2 passes in DVD-RB's VBR Passes Setting basically means the creation of a .vaf file and then one fine-tuning pass on top of that? So really, conceptually we should think of it as one pass.

I'm really not sure what .vaf creation really is -- does it re-encode in an optimistic way, then the passes on top of that sort of fine-tuning the bitrate distribution and make sure the resultant file is small enough so that the whole movie will fit a DVD-5? Sort of like what deep analysis does in Shrink?

[jdobbs]

No. Actually CCE has distorted the reality with their pass numbering terminology. When the .VAF is created you are actually doing a full encoding pass just like every other one. The "second" pass is in fact the second pass (like it is called with every other encoder).

The real fact of VBR is that you can get all the information you need in the first pass to determine where bits are needed. The second pass is to allocate it based upon what you found. Everything beyond that is insignificant tweaking and each additional pass has less-and-less impact. CCE's manual itself says anything above 4 is not noticable -- but if someone has the time and wants to take it to the limit -- why not?

When you reencode from scratch and use multipass VBR you are determining the output size and can be very accurate (just like the original authors).

[richarddd]

Originally posted by jdobbs
Two for most, three for tough ones. Anything more shows negligible improvements.
Just to be very clear, set RB to two (or three)?

As you say, "CCE has distorted the reality with their pass numbering terminology" so I want to make sure.

[Fishman0919]

Set it to 2, TWO, 1+1, II and forget about it .... LMAO sorry haven't gone to bed yet hehe :scared:

[richarddd]

Sleep well :D