FredBender
31st January 2004, 13:38
Hi,
I encoded a movie with 591,952 "kbytes" as target size and it came out 603,056,769 bytes (Matroska) which would be
603,057 kbytes (1 kbyte = 1,000 byte) -> 11,105 kbytes too high
588,923 Kbytes (1 Kbyte = 1,024 byte) -> 3,029 Kbytes too low
So is it actually kbytes or Kbytes you have to specify?
And another question: should the XviD (no audio) be encoded to Matroska or AVI? I notice opening Matroska Files with VirtualDubMod takes a little time, and I need to open it in order to mux the audio in.
BTW I just saw an error message stating "Warning: Nothing To Output, BFrame Decoder Lag" in the first frame, is that something to worry about?
When converting the film from Matroska to AVI, the AVI ends up at 605,272,064 bytes
605,272 kbytes -> 13,320 kbytes too high
591,086 Kbytes -> 866 Kbytes too low
It seems XviD is measuring in KBytes and takes the AVI overhead into consideration. Can anyone confirm this? I don't want to draw my conclusions from just one single encode.
I'm new to XviD and Matroska, sorry if this has been asked before, I could not find anything about it.
TIA
EDIT: Assuming target size in XviD is measured in Kbytes = 1,024 Bytes do these formulas for calculating the target size make sense?
when audio encoding is already done:
target size = (700 * 1,024) - ((audio in bytes) / 1,024)
700 * 1,024 = 716,800 is the capacity of a CDR in Kbyte
/ 1,024 converts the audio filesize from byte to Kbyte
Note that by "1,024" I mean "1024" i.e. 2^10
when audio encoding has not yet been done:
target size = (700 * 1,024) - (seconds * (audio in kbit/s) / 8.192)
/ 8.192 converts the audio rate from kbit/s to Kbyte/s
Note that by "8.192" I mean "8192/1000" i.e. a rational number between 8 and 9.
Do you agree with these formulas?
I encoded a movie with 591,952 "kbytes" as target size and it came out 603,056,769 bytes (Matroska) which would be
603,057 kbytes (1 kbyte = 1,000 byte) -> 11,105 kbytes too high
588,923 Kbytes (1 Kbyte = 1,024 byte) -> 3,029 Kbytes too low
So is it actually kbytes or Kbytes you have to specify?
And another question: should the XviD (no audio) be encoded to Matroska or AVI? I notice opening Matroska Files with VirtualDubMod takes a little time, and I need to open it in order to mux the audio in.
BTW I just saw an error message stating "Warning: Nothing To Output, BFrame Decoder Lag" in the first frame, is that something to worry about?
When converting the film from Matroska to AVI, the AVI ends up at 605,272,064 bytes
605,272 kbytes -> 13,320 kbytes too high
591,086 Kbytes -> 866 Kbytes too low
It seems XviD is measuring in KBytes and takes the AVI overhead into consideration. Can anyone confirm this? I don't want to draw my conclusions from just one single encode.
I'm new to XviD and Matroska, sorry if this has been asked before, I could not find anything about it.
TIA
EDIT: Assuming target size in XviD is measured in Kbytes = 1,024 Bytes do these formulas for calculating the target size make sense?
when audio encoding is already done:
target size = (700 * 1,024) - ((audio in bytes) / 1,024)
700 * 1,024 = 716,800 is the capacity of a CDR in Kbyte
/ 1,024 converts the audio filesize from byte to Kbyte
Note that by "1,024" I mean "1024" i.e. 2^10
when audio encoding has not yet been done:
target size = (700 * 1,024) - (seconds * (audio in kbit/s) / 8.192)
/ 8.192 converts the audio rate from kbit/s to Kbyte/s
Note that by "8.192" I mean "8192/1000" i.e. a rational number between 8 and 9.
Do you agree with these formulas?