From: Pinckney, Thomas <pinckney@vi...> - 2002-03-27 21:07:02
I'm not set up here to test this, but reading the code in
xine-lib-0.9.8/src/input/input_rtp.c from the 0.9.8 release I notice some
suspect looking behavior. Specifically, line 275 in the incoming packet read
loop where apparently the first 64 bits of the packet are cleared (but not
skipped). Assuming this is an RTP packet this means we're blanking the fixed
part of the RTP header (and usually there is only the fixed portion so we
don't normally have to worry about the optional headers).
My question is doesn't this result in 64 bits of zero at the start of every
packet's worth of data? Do the higher level demux or decode plugins somehow
not care about this? Or is this simply a bug?