DVD-RB free size calculations

[techreactor]

How does DVD-RB calculate the source DVD size and then the compression ratios based on that ????

My source DVD is 4440 MB which I want to put thru DVD-RB.

It calculates a compression ratio of 99.5% means my source is 0.5 % (22 MB) above the DVD5 size. Which means that DVD-RB recognizes DVD5 size = 4418 MB and allocates the compression ratio/ bitrates based on this size only.

I always burn upto 4480 MB on my DVD and want DVD-RB to acknowledge that anything above 4480 MB only, should be compressed. I dont want to loose those bitrate calculations for the additional 62 MB's available, but not recognized.

Can I specify this in the INI using any parameter, can it be achieved in any way ???

[blutach]

Read the help file. Put a TargetSectors=2265000 line in the options section of the rebuilder.ini file.

Regards

[techreactor]

Read the help file. Put a TargetSectors=2265000 line in the options section of the rebuilder.ini file.

Regards

That was already present before I clicked the "Prepare" button.

And you are not getting my point Blu, Target sectors in so that DVD-RB can fill up that much space. What I am talking is the initial calculations (prepare) done by DVD-RB, in which it takes up the source size/destinationsize and then calculates the bitrates etc.

How DVD-RB is deciding on the final size is my question, it is considering 4418 MB as its target size during the prepare stage while doing the calculations, irrespective of the Targetsectors conf.

[blutach]

My understanding is that the default value is 4.32Gb

Regards

[techreactor]

My understanding is that the default value is 4.32Gb

Regards

Thats 4424 MB which is close to my calculations (4418 MB). Is there a way to increase it to 4480 MB ???.

[blutach]

Read my earlier post! Or use RBOpt.

Regards

[techreactor]

Read my earlier post! Or use RBOpt.

Regards

The targetsectors method doesnt work for the "prepare" stage, it works with the "encode" stage.

Which means that the bitrate calculations will be done based on 4.32 GB and the "encode" stage will try to fill up 4.38 GB on those wrong calculations/bitrate only.

@JDobbs, isnt this something to think about!!!!!

[blutach]

RBOpt operates after prepare and compute new BRs for each segment (or globally). Try it.

Regards

[jdobbs]

The targetsectors method doesnt work for the "prepare" stage, it works with the "encode" stage.

Which means that the bitrate calculations will be done based on 4.32 GB and the "encode" stage will try to fill up 4.38 GB on those wrong calculations/bitrate only.

@JDobbs, isnt this something to think about!!!!!

TargetSectors is used during the PREPARE phase to determine the output sizing. The encodes (ENCODE phase) are all done based upon the calculations done during PREPARE.

I would highly recommend, however, that everyone use the default value because:

1. Almost all discs have weaknesses in the outer edges that are more likely to cause errors.

2. Encoders are not completely accurate, and when you increase the size you will sometimes oversize -- that wastes a lot of time.

3. The amount you recover if you go from 4.32GB to 4.37GB (right to the edge) is negligible. It isn't enough space to make a detectable difference in video quality.

[techreactor]

TargetSectors is used during the PREPARE phase to determine the output sizing. The encodes (ENCODE phase) are all done based upon the calculations done during PREPARE.

I wonder, why it didnt work for me then, need to check again, thanks.

[jdobbs]

Make sure you haven't also set one of the encoder specific TargetSector settings as it will override the standard one. For example if you have TargetSectors=2236400 in the INI, but you also have HCTargetSectors=2260000, when you select HC your target changes to 2260000.