MPEG file size?

[Batman]

I downloaded a movie in mpeg file format, which was I believe, and original divx avi that was later converted to mpeg using TMPGEnC. The filesize is remarkable, and the quality is impressive. It uses the standard 1100kbps CBR of TMPGEnc.

It is a dvd rip. All this, and it takes only a mere 800 mb of hard disk space (Yes the movie is complete it includes the credits). However, I have estimated that If I were to convert a divx 534 mb file to mpeg the resulting mpeg file would exceed 2 GB in file size.

Any ideas on how to solve this apparent "anamoly"? Thanks

[setarip]

"I downloaded a movie in mpeg file format, which was I believe, and original divx avi that was later converted to mpeg using TMPGEnC"

You can confirm your speculation by loading the file into a hex editor and reading the header information (which may occupy as much as the first 1K bytes).

"I have estimated that If I were to convert a divx 534 mb file to mpeg the resulting mpeg file would exceed 2 GB in file size."

Your estimate is high, by at least a factor of two. A 534Mb Divx-compressed .AVI would typically be converted by TMPGEnc to an MPEG1 or MPEG1-VideoCD of anywhere from 800Mbs to 1Gig...

[Batman]

Thank you Setarip

I conjectured the file would was converted to mpeg using TMPGEnc because the "encoded by EMC^2" logo that precedes the feature,it is atypical of TMPGEnc conversions.

May you please explain why small 65 mb files produce such large mpeg sizes?

I would assume you are correct in your analysis of mpeg file size. I based my calculations on this:

65 mb (avi)---199 mb mpeg file
y=534/65 (avi)--199 mb x y
mpeg file size: 8.2 x199mb=1.6 GB

Is the above calculation reasonable?
Since these are hypothetical cacluations, there is the possibility that it is flawed. Sorry, my 2 GB reference was way off.

[setarip]

"May you please explain why small 65 mb files produce such large mpeg sizes?"

That's probably far too small a file to use for extrapolating a meaningful .AVI:.MPEG1 ratio. There is a certain amount of fixed overhead required for ALL MPEG1s, regardless of size. Once you get above approximately 300Mb, this ceases to be a significant factor in the final size comparisons. Based on creating perhaps 400 .MPEG1s from .AVIs, I feel comfortable in stating that the typical ratio is 1:2 .AVI : .MPEG1.

"EMC^2"

This has nothing to do with TMPGEnc. It is someone's "handle/moniker/screenname" and is a version of Albert Einstein's famous equation "E=MC squared" ;>}

[Batman]

Thanks.

In the above post you mention:

"There is a certain amount of fixed overhead required for ALL MPEG1s, regardless of size. "

Suppose if I were to resolve the 534 mb file (using Virtualdub) into smaller divisions would the file size change? For example, would the sum of 10 "53.4 mb" files converted to mpeg produce the same total size as a 534 mb file converted to mpeg format?

Yeah, Einstein was a genius. He made numerous contributions to science, one of which is the popular equation "E=mc^2" where m is the mass defect in kilograms and c^2 is the speed light (3.00x10^8 m/s) squared.

[setarip]

"Suppose if I were to resolve the 534 mb file (using Virtualdub) into smaller divisions would the file size change? For example, would the sum of 10 "53.4 mb" files converted to mpeg produce the same total size as a 534 mb file converted to mpeg format?"

There's no reason to limit yourself to the hypothetical, is there?

[Batman]

I know. However, I posess an archaic PC. The reason being, my PC is old and directly converting a movie to mpeg would take 136 hours. The TMPGEnc process is unstable. Hence, I figured resolving the movie into smaller components would be more manageable.

Is there any way to encode a file to mpeg, and then stop in the middle, and then resume from that point onwards at a later time?

Thanks