I believe I've tried most of them, but always seem to be off a few 100 K. Which isn't that big a deal but when I encode say 7 eps of a show at a 100 megs and they end up being 705 megs in total, I can't burn all of them as I planned. So, I'm looking for an calculator that allows input of minutes and seconds, and allows indicating size in Kbytes not megs. Or could someone tell me how avi overhead is calculated and I would make something myself in excel or something.
>Or could someone tell me how avi overhead is calculated can't tell you that, but in the meantime you could use gordian knot just for this. enter the number of frames and the type of the audio-track and it will give you the overhead in kbytes.
Could somebody code an OGM calculator? Is there a "true" formula? Right now I'm only guessing what could be the correct size for the video stream. OGM overhead is a bit different from AVI overhead. Best regards, JimiK
@JimiK, I use my own formula with GordionKnot v0.27, I use XviD for the Video and vorbis for the Audio, both mixed use Cyrius's ogmuxer. Here is "my" formula : From the "Bitrate" tag, 1. choose the "DivX 5" 2. input your .d2v 3. input the vorbis audio (I usually use quality 0.250 ~96kbps) use the "Select" button to input your .ogg manually. 4. add about 4MB to the value inserted from step 3. 5. disable "calculate frame overhead" 6. use the video size in KB for the XviD's 2-pass int size. 7. mux the .avi + .ogg use the oggmuxer 8. it will hit 699MB perfectly, you still have around 1 - 2.5MB for your launcher, cover and artworks, etc. Goodluck! :)
Hi ookzDVD, so you say that the overhead is always about 4mb? I'm not at home and I don't know when I'll do my next rip, but I'll certainly test this. But I'm using 2 audio streams + substreams. Do you think your formula should still be valid? Best regards, JimiK
Thanks for the hint, but it's too big for me (and I wouldn't install the .net package. Yes I know there was already a discussion about that). I know it's not a simple OGM calculator, but more powerful. I think I'll try to code a simple Java proggy that calculates the overhead, using your guess. Best regards, JimiK