[x264-devel] Behaviour of Annex B encoding: bug or not?

[Jason Garrett-Glaser]

> It's only because x264 generates more complete session information, which
> includes several near-zero multi-byte integer parameters that result in
> escape-required patterns of traffic, that we are seeing the problem.
> It doesn't occur when the units talk to each other.

This is unrelated.  Simply due to random chance, statistically,
escaping bytes will be needed about once every 4 million bytes of
data--ignoring headers.

> I guess my approach should be not to alter x264 (since it's doing the right
> thing) but rather to add a flag in the ekiga/opal software so that, if it's
> dealing with buggy hardware, it calls the x264 library as usual to generate
> the NALs but then strips out the emulation prevention bytes before putting
> the packet on the wire.

That seems like doing a lot of extra CPU work for no reason.

Dark Shikari