Fit to 4.37GB

[HaJ-B]

Hello everbody!
I have noticed that the final file size is 4.29GB when i'm using DVD-RB.
Is there any way to rip files that be equal to 4.37GB? I just don't want to lose these 100MB.
When using the PREVIEW/EDIT button and moving it to 4.37GB the redistribution is getting lost.
Thanks in advance.

[blutach]

Make your target sectors larger. See hidden settings in the help file.

Regards

[HaJ-B]

"You should always leave a some room for error." (Help file).
What does it mean?
Additionally, it mentions the max size is around 2267500 sectors. Didn't try it, but I guess it'll be about 4.35GB, right?

[jikchung]

As I understand it, you leave room for error for two reasons. One is encoder accuracy, the closer you target the limit of your disc capacity the more risk you'll end up oversize. The other has to do with the disc itself, you can run into errors at the very edge of the disc (at least this used to be the case).

[gizzin]

In my experiences, I use 2260000, and 2250000. Sometimes when I use 2260000 I get closer to 4.37 but sometimes it oversizes it slightly. If you use 2250000, I usually get around 4.35,4.36. But this mostly depends on the source and encoder you are using. I'd say try 2250000 see how that works for you. Running into errors at the end of disc is a thing of the past. I'm pretty sure most people now aday can afford to buy 1st class media (yuden).

[blutach]

My targetsectors for HC is 2264000 - it is nearly always about 4.37Gb (except when it adjusts average bitrate down, in which case it end up a bit lower).

Regards

[jdobbs]

Just remember (here comes my caveat)... when you change the value and your encode comes out too large or the end of your movie is garbled -- it's your choice that caused it, not DVD-RB.

My personal opinion is that you can't tell the difference in quality between 4.3GB and 4.7GB -- so why take the chance of having to reencode.

[Wombler]

Just remember (here comes my caveat)... when you change the value and your encode comes out too large or the end of your movie is garbled -- it's your choice that caused it, not DVD-RB.

My personal opinion is that you can't tell the difference in quality between 4.3GB and 4.7GB -- so why take the chance of having to reencode.

You beat me to it and I agree entirely with that.

The smaller size also pre-empts potential problems with lesser quality media.

People are always pushing things to the limit without considering the consequences.

IMHO the default size is a sensible compromise and only experienced users that are fully aware of the potential problems should even consider altering it.


Wombler

[HaJ-B]

Thank you all.
In the meanwhile I have made two encodes with TargetSectors=2281500, and it turned up just fine.
I think I'll just leave this set like that until I'll get an oversized encode...
What you say?

(BTW: Using ProCoder 3, Mastering quality)

[jarthel]

you can't really predict final size until everything is done. I have been assuming (since 2001) that the various final sizes mentioned by software like dvd-rb, big3 method, gknot and others are just estimate.

and this is especially true if you used avs filters.

[hallway]

My personal opinion is that you can't tell the difference in quality between 4.3GB and 4.7GB -- so why take the chance of having to reencode. People believe they can see/tell a difference though.

[Sophocles]

I have to agree with those that say there is no discernible difference between 4.3 and 4.37. Like many I prefer a little wiggle room to account for anomalies. My preferred size is about 4.32 GHz which is where RB finishes most of my discs.



Edit: meant 4.37.

[HaJ-B]

Anyway, you can always disable One Click Mode and see in the preview window the final size right after the preparation phase. If it's more then 4.7, just reset the hidden settings, and prepare again.

[jikchung]

The preview window is an estimation, you still run the risk of being oversize.

[jdobbs]

That is a true statement. Most of the time the estimate is very close, but an estimate is no more than an estimate. The encoder is told to encode to a specific size -- but sometimes it goes over or under. Usually the over/under sizing of all the segments balance each other out, but rarely you get one that just doesn't size right.