From: Mike M. <mel...@pc...> - 2003-06-27 01:00:23
|
On Thu, 26 Jun 2003, Pamel wrote: > Currently if a codec decides that a frame has to little movement to encode, > it returns an frame that has a byte sequence indicating that there is no > change in that frame. Then on decode the codec can output a duplicate > frame. This is idiocy. Its a throwback from old codec API's that no one > has bothered get rid of. If a codec doesn't want to code any change, it > should be able to simply not produce that frame. Fortunately, the developers of the Quicktime format were being absolutely visionary when they incorporated variable framerates and edit lists into the format. Works around this problem nicely. There are other general-purpose multimedia formats besides AVI and Matroska. > Another issue is the 2-pass encoding method. Codecs will output dummy > frames while creating a log file to use on the next pass. Why should it > have to output anything? Why does the application have to perform two > separate encodes? I give up. Why does an application have to perform two separate encodes? -- -Mike Melanson |