Gej
20th April 2003, 18:30
A quick official word about the MV files and DivX 5.0.4:
Due to some decision difference between 1st pass and nth pass (due to Psychovisual enhancements decision, different quantization decision or Interlace decision), the motion estimation may need to be different on some blocks, so MV file could not be used during the nth pass, enabling MV reuse during nth pass may cause strange artifacts. The Beta period help us to put light on this issue, the 5.0.4 Release carry a workaround: MV reuse is internally disabled; MV files are not wrote nor read. This may cause a little slowdown during nth pass, but will avoid any kind of visual artifacts.
We are working on fixing this issue, but the whole MV reuse concept suffers some major drawback in a mutli-pass environment where encoder can (and will) make different decision during each passes.
Due to some decision difference between 1st pass and nth pass (due to Psychovisual enhancements decision, different quantization decision or Interlace decision), the motion estimation may need to be different on some blocks, so MV file could not be used during the nth pass, enabling MV reuse during nth pass may cause strange artifacts. The Beta period help us to put light on this issue, the 5.0.4 Release carry a workaround: MV reuse is internally disabled; MV files are not wrote nor read. This may cause a little slowdown during nth pass, but will avoid any kind of visual artifacts.
We are working on fixing this issue, but the whole MV reuse concept suffers some major drawback in a mutli-pass environment where encoder can (and will) make different decision during each passes.