dingo
18th December 2002, 00:25
Fitcd doc (v1.1.0: November, 12th 2002)
- Removed CCE-optimizing because it's obsolete.
??? Can anyone have some information about this ?
Before the author of Fitcd said this:
- If you use the CCE:
Check 'Optimize for CCE'. This is only activated when the resolution-
rounder is set to 32 (or 16). It resizes the destination's Y-size
2 pixel smaller, because CCE has a bug with the motion-vectors
exceeding the resolution-boundaries.
E.g. if you want macroblock-optimization and a destination-size
of 448x320, which is exactly 560 macroblocks: resize to 448x318,
because otherwise CCE would code the black macroblocks above and
below your film-resolution, too. 448x352=616 macroblocks would be
coded.
The bug with the motion-vectors has been corrected ? since wich version ?
Thanks
Bye
- Removed CCE-optimizing because it's obsolete.
??? Can anyone have some information about this ?
Before the author of Fitcd said this:
- If you use the CCE:
Check 'Optimize for CCE'. This is only activated when the resolution-
rounder is set to 32 (or 16). It resizes the destination's Y-size
2 pixel smaller, because CCE has a bug with the motion-vectors
exceeding the resolution-boundaries.
E.g. if you want macroblock-optimization and a destination-size
of 448x320, which is exactly 560 macroblocks: resize to 448x318,
because otherwise CCE would code the black macroblocks above and
below your film-resolution, too. 448x352=616 macroblocks would be
coded.
The bug with the motion-vectors has been corrected ? since wich version ?
Thanks
Bye