PDA

View Full Version : VOB overhead size?


unixfs
16th November 2002, 23:11
Hi,
is there a formula to calculate with a good approximation the size of
VOB overhead respect to the plain system stream?

In all the encodings I made it seemed to vary between 5 and 9%, and this variability always leaves the movie over- or under-sized.

Another question: is it possible to make mode2 (2352 bytes/sector) udf images, to gain the extra 100 MB of disk space? Would the resulting image be still dvd compliant?

Thanks very much.

FamousPerson
18th November 2002, 17:11
In response to your first question, I've found that authoring adds about 110 MB overhead. Basic menus and even subtitles are negligible.

My calculator may help you out (http://www.vanhouwelingen.com/marcvh/cceguesser/cceguesser.zip)

With regard to your second question, I have no idea, but my guess would be no...

slk001
18th November 2002, 20:18
My navigational overhead runs about 2.5-3% for a full DVD (ie, for a 4,450,000,000 byte video plus audio, I get about a 110,000,000 byte overhead hit).

For a complient DVD, the pack size is fixed at 2048 bytes (which is one DVD sector), so the answer to your second question is "no".

zyzzle77
21st November 2002, 03:54
Is it possible to eliminate this approx 100,000,000 byte overhead and still get a playable DVD? Why do we need 40-50 megs just for the prv2 stream? What does this seemingly wasted filler space accomplish?

FamousPerson
21st November 2002, 14:16
I doubt it - not if you want a compliant DVD.

What's a prv2 stream?

slk001
21st November 2002, 16:14
What's a prv2 stream?

It's Private Stream 2, which is the navigational data. I don't remember the exact number, but a DVD has significantly better error correction ability than that of an audio CD. A 2-3% overhead for that alone, is acceptable. Better to suffer through the increases in file size that to have corrupted data show on the television.

FamousPerson
21st November 2002, 16:30
Originally posted by slk001
It's Private Stream 2, which is the navigational data.

Ahh... I see. Thanks.