[XviD-devel] Extra padding after FrameCodeI/P
Christoph Lampert
xvid-devel@xvid.org
Mon, 13 Jan 2003 15:16:40 +0100 (CET)
Hi,
at the end of encoder_encode() there are 32 extra bits
0xFFFF, 0xFFFF written to bitstream. That's that for?
Just to remove the risk of a bitstream-reader reading
undefined/out-of-bounds memory? There has to be a better
way, e.g. the encoding application simply allocing more mem.
4 extra bytes per frame is wasteful at very low bitrates, and
also it's against MPEG-4 standard.
gruel