Log in

View Full Version : Targeting the size to 4.37Gt saled


Hatchet
8th March 2007, 07:12
Hi!

I was wondering if is there some formula how to make those changes to the rebuilder.ini file that will
result final output size close to 4.37Gt? I know threre is threats about this already but those didn't do it for me :confused:

So is there some formula like if the original size is:

example

5.25Gt the CCETargetSectors value should be = ?
6.25Gt the CCETargetSectors value should be = ?
And so on....

I've just tryed that first example (5.25Gt)with settings:

"CCETargetSectors=2255000" and what I got was 4.26Gt :rolleyes:

:thanks: for advance ..... please do dont say "die noob" to me :lol:

stereo
8th March 2007, 07:56
Hi Hatchet

I can only speak from my own experiences, and your result of CCETargetSectors=2255000 = 4.26 doesn't sound normal. Anyways here's what I got:

CCETargetSectors=2250000 gives me 4.35, 4,36, or 4.37 95% of the time

CCETargetSectors=2240000 gives me 4.33 or 4.34 95% percent of the time

This is what jdobbs wrote to me sometime ago:

Here's the calculations associated with target sectors that will accurately predict the output size (assuming encoder perfection).

(TargetSectors x 2048) x 1.015 = Output_Size

DVD sectors are always 2048 bytes long. The .015 adjustment represents the overhead (NAVPACKS, Packet headers, etc.) associated with packetizing the video/audio for DVD.

So the default value of 2236400 would result in:

(2236400 x 2048) x 1.015 = 4,648,849,408 = 4.329GB

The result usually falls between 4.32GB - 4.33GB.

I hope this helps you.

Hatchet
8th March 2007, 09:21
Hi Hatchet

I can only speak from my own experiences, and your result of CCETargetSectors=2255000 = 4.26 doesn't sound normal.

Hmm, so I'm doing something wrong maybe ... :(
CCE settings was 6 passess for this one if it matters?

stereo
8th March 2007, 11:14
No, 6 passes shouldn't matter (I used to do 5(6), now I do 3(4)). If you were doing OPV or 2 pass it could probably matter.

I acknowledge your frustration, but think of it this way: Most likely you won't be able to tell the difference between 4.26 and 4.37 in terms of video quality. And furthermore, 4.26 holds the advantage that it won't matter as much if the outer edges of the disc are scratched.

I'm sorry if this doesn't help you much. Maybe one of the other guys will be able to help you.

jdobbs
8th March 2007, 13:07
Also remember... when CCE encodes and determines it has reached the best level of quality with the current quantization matrix -- it won't add bits just to make the sizing larger (to meet the specified bitrate). This situation is called "encoder saturation". It happens sometimes when you remove a lot of video, use a fairly high bitrate, or do a "Movie-Only" encode. The result can be undersizing. Of course that isn't actually a bad thing -- because it indicates you are hitting "top quality".

If you set "CCEAQM=1" in the "[Options]" area of your REBUILDER.INI file it may help some -- as the quantization matrices get adjusted and the likelihood of saturation becomes less probable.

Hatchet
9th March 2007, 09:30
Also remember... when CCE encodes and determines it has reached the best level of quality with the current quantization matrix -- it won't add bits just to make the sizing larger (to meet the specified bitrate). This situation is called "encoder saturation". It happens sometimes when you remove a lot of video, us a fairly high bitrate, or do a "Movie-Only" encode. The result can be undersizing. Of course that isn't actually a bad thing -- because it indicates you are hitting "top quality".

If you set "CCEAQM=1" in the "[Options]" area of your REBUILDER.INI file it may help some -- as the quantization matrices get adjusted and the likelihood of saturation becomes less probable.

Thanks for this :D I finally got the result what I wanted :cool:
Output size is now 4.36Gt and overal bitrate 5650 :w00t: