Query on target sector formula - 1.01 Final

[blutach]

Thanks much for the final release.

The help file (Hidden settings) says the DVDRB's default is 2236400 and the maximum sectors for a DVD-5 is around 2267500.

I equate this maximum to be 4428.7Mb (at 2048 bytes per sector).

A +R DVD-5 is 4482Mb.

Can someone please explain the discrepency?

Regards

[Carpo]

its better to be just under than just over - most of my encodes come out at 4.32 - but sometimes they are bit bigger and if you use 32k padding this can aslo make it slighlty larger than dvd-rbs default setting.

Plus some dvd players have problems with reading a disc on the outside egde - so im guessing dvd-rb has been set to this size for compatibility reasons (although i could be wrong, i usually am :sly: )

Also you can change the sector setting yourself by adding an entry in the ini file (not too sure if you knew that ;) but i thought i would mention it anyway) so you can always change it so you use up the full amount of the disc

[blutach]

Thanks Carpo - I did know that and use it (TargetSectors=nnnn) but it is a bit variable. I too have encodes that come out at 4.32Gb at the default.

But my question goes to how to define the correct number of sectors. They just don't seem to multiply correctly using the numbers in my first post.

(Note FYI: Per the changelog, 32k padding is gone in 1.01 Pro - except if you use the hidden setting to enable it).

Regards

[wmansir]

This has been the case since TargetSectors was introduced as an option. I think jdobbs mentioned in another thread on the subject that the discrepancy is likely due to some unaccounted for muxing overhead.

The basic formula I use is: Default Sectors (2236400)/ Default size (4.32GB) X Target Size(in GB) = Target Sectors

[blutach]

Thanks wmansir :)

Regards

[jdobbs]

The default was set to that size because there is variability between encoders and the accuracy of encoders. Also you will find that many discs (yes, even the good ones) are prone to errors when you write close to the edge, this "buffer" prevents problems and gives the encoders room to breath. I added the "TargetSectors" variable (along with CCETargetSectors, HCTargetSectors, QuEncTargetSectors, NoEncodeTargetSectors, ProCoderTargetSectors, and ReJigTargetSectors) for those who like to push to the edge -- but I have also warned that the quality improvements are negligible and you risk occasionally oversizing.

By the way, TargetSectors= is the default size, but it will be overridden if one of the encoder specific settings is set and you are using that encoder.

Note to Carpo: You are right.

[blutach]

Thanks everyone - I have actually found varying the target through RBopt's global options to be pretty accurate. Also that formula of wmansir's worked a dandy last night.

Regards

[Carpo]

Note to Carpo: You are right.

beginners luck :devil: