Ok i have looked at divx forums.. but that calc dont seem to want to work for my computer.. it always crashes and well that just aint acceptable.. (in other words.. i cant trust it when it crashes all the time).. Ive noticed that the way GN calcs it that if i use that figure and do my normal task of encoding the credits and or intros at significantly lower bitrates(to give headroom for the audio file).. i sometimes get about 30mb off target.. and other times.. if, lets say the dvd movie all needs to be at the higher bitrate (ie. old movies that have titles and credits in the movie action) then i tend to get oversized. The way the new algorithms work, im thinking that, maybe they are more variable than what you imput as a target. I often find that windows explorers properties on the movie are off.. (lower than expected)...I think this has to do with the amount of I-frames that the new process seems to add to the content of a movie. Since a calc can not predict this value, im starting to think that doing guestimation is the best way. So as of right now i use gordian knot to figure it out... and depending on what i think it will use, input the value.(which im wrong most of the time.)
I have made about 150 divx backups about 10 are 5.1 all using gordian knot and never once have they been undersized or oversized 1 cd rips are always 700MB and two cd's are always 1.36 GB, only thing when splitting 2cd rips sometimes I get a 699/701 or 700/701, etc, but they are always spot on, and 80 min cd's fit 702 mb anyway
Yep, It can also depend on the encoding application you use too. I mostly use MPEGmediator for DivX, XviD and WMV9 VCM 2pass encodes. And work everything out with a calculator! Encodes are always 'smack on' using both 700 and 800MB CD-Rs! Cheers
webpage: download: This calculator is accurate and, if not you can even configure it to change the algorythm! It's still under developement, so you may have downloaded an unstable version. The last one is stable. I use it everyday.
--------------------- "In 1959, we had 50 disks, each 24" in diameter, continuously spinning at a speed of 1200RPM, capable of storing 6MB of data (a staggering 12MB if your company opted for the double-capacity versions). The size of this thing? 400-sq ft space required,
The newest version (CLZM 1.7.2) is save! But it can't write to the registry as the older versions. If you have one of those older versions (1.7.0 or 1.7.1): Don't use them! They are very buggy, so please get the new CLZM! [ This message was edited by claude.m on 2003-09-19 ]