CCE 2.7 File Size Calculation VS. FitCD

[greedy]

Quick question:

I noticed that in CCE 2.7 the automatic file size calculation is different than that of FitCD's (v1.24) when using the same average bitrate.

Example:
95min, 0 sec movie with 224kbps audio:

FitCD: Avg. bitrate - 2065kbps (1,471,321,124B)
CCE: Avg. bitrate - 2065kbps (1,497,509,635B)

So, is CCE just being conservative?

Plug in a value of 2065kbps into FitCD and see the value it gives... (ie. 1,471,321,124B)
Now, plug that value (1,471,321,124B) into CCE and see that it re-calculates the average bitrate to 2028kbps.

Would this be the best way to go about it? (Using the SIZE FitCD gives and putting it into CCE, bypassing the bitrate FitCD gives all together; I say the size cause FitCD has calculated overhead already) I know this sounds minute, but it would be unfortunate to come out with video file that is 30MB too large or too small.

Thanks.

[Matthew]

I don't know the answer to your question, but a while back I tried to do some overhead calculations and found that video overhead varied according to bitrate distribution. Hence coming up with a correct overhead figure is difficult.

[Boulder]

I've based all my calculations on the assumption that a DVD can hold 4350MB of data, so there's 130MB overhead (4480MB total disc size). It appears to be quite correct as the discs usually have some 10-20MB left after authoring, be it 2 movies or several episodes per disc.