74MB discrepancy in size of multiplexed MPEG-2 file

[evilclive]

My home-made recording of The Valkyrie (a Wagner opera) consists of the following elememtal streams:

Valkyrie.m2v - MPEG-2 Video, VBR - 5,007,940KB
Valkyrie.mp2 - MP2 Audio, 256kbps - 467,567KB

When I multiplex them with TMPGEnc Plus 2.5.21, I get the file:

Valkyrie.mpg - 5,549,559KB

which is some 74,000KB larger than the sum of its parts.

Demultiplexing reveals the original two streams, plus something called a padding stream (number 0xBE), of negligible size when demultiplexed.

Am I right in guessing that this overhead is perfectly normal, and not worth worrying about?

[45tripp]

Am I right in guessing that this overhead is perfectly normal, and not worth worrying about?

yes

[evilclive]

What often seems to happen is, I record something that's slightly too large to archive to a DVD-R: say about 5 billion bytes. Rather than re-encoding it a second time (which would mean two lots of MPEG artifacts), I can just cut ten minutes of unimportant stuff out here and there.

So I demultiplex the file with PVAStrumento or ProjectX, and use MPEG2Schnitt to select the bits I want to keep. MPEG2Schnitt helpfully shows the combined size of the cuttings in the video and audio elemental streams, but doesn't show the overhead that will be required when the streams are multiplexed by IFOEdit or TMPGEnc Plus.

It's a little frustrating when I create a 4400MB cut (for a 4487MB DVD-R), wait several minutes for IFOEdit to do its work, and find the overhead is closer to 120MB.

Is there a utility, or a rule of thumb, to predict the size of the overhead?

[Boulder]

I use 4350 or 4375 megabytes for my calculations, and the results have always been just below the DVD+R disc size.

[AVIL]

Hi,

Try with other multiplexer i.e. Imago MPEG muxer

http://www.videohelp.com/tools/ImagoMPEG-Muxer

Its freeware, don't requires installation and does a good job.

Good luck