just one question regading the MP4V-ES payload (implemented in
MPEG4ESVideoRTPSource.cpp), it works very nice for every RFC 3016
compatible MPEG4 video source we have tried. This is a quite simple
payload because of the visual stream being mapped directly onto RTP
packets with no special header. But the cpp file says on line 25
//##### NOTE: INCOMPLETE!!! #####.
In what way is this payload implementation incomplete? Do you only
mean some marginal sanity checks or similar or is anything essential
missing from the implementation?
It's been a while since I wrote this code, so I can't remember why I
added the "INCOMPLETE" comment. But I suspect that one reason is
that we don't recognize all of the optional SDP parameters that are
possible for such streams.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
