fedge
20th September 2003, 00:24
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.)
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.)