[Live-devel] RFC 2250 Q

[Ross Finlayson]

>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>	boundary="----_=_NextPart_001_01C74C50.B5ECF64E"
>
>Does the Live555 Media server follow RFC 2250 to transport video?

Yes, but note that this RFC is only for MPEG-1 or 2 Video RTP 
streams.  Transport of other kinds of stream - including MPEG-4, 
H.263+ and H.264 - is defined using other RFCs (but we support those 
also).

To implement RFC 2250, we use the "MPEG1or2VideoRTPSource/Sink" 
classes (for Video Elementary Streams), the 
"MPEG1or2AudioRTPSource/Sink" classes (for Audio Elementary Streams), 
and the "SimpleRTPSource/Sink" classes (for Transport Streams).

Note also the numerous demo applications that use these classes.
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.live555.com/pipermail/live-devel/attachments/20070210/d661824a/attachment.html