[MPlayer-dev-eng] Re: UPDATED: A RTSP/ RTP streaming patch for "mplayer"
Ross Finlayson
finlayson at live.com
Mon Aug 5 20:09:31 CEST 2002
>so, you could emulate old rtp:// behaviour, for people using both live.com
>libs for rtsp and rtp:// for DVB ?
>
>i mean you shouldn't degrade the functionality at all
When the LIVE.COM code is being used, I don't want to allow people to
continue to say "rtp://...", because, as I've noted, it's a hack that can't
work for arbitary RTP streams.
However, I do want to make sure that the *functionality* of "rtp://..." -
for receiving/playing DVB streams - is still present. I believe that DVB
streams (which are MPEG-2 Transport Streams, right?) can be received using
a SDP file of the form
v=0
m=video <port> RTP/AVP 33
c=IN IP4 <address>/255
(Replace <port> with the stream's UDP port number, and <address> with the
IP multicast address (or, if the stream is unicast, the IP address of the
sender).)
Alternatively, if the DVB server supports RTSP, the user can just use a
"rtsp://..." URL.
Trouble is, I currently have no way of testing this. Can anyone point me
at a DVB stream that I can test? (If it's a multicast stream on the public
MBone, that's OK; I am able to connect to the MBone.)
Ross.
More information about the MPlayer-dev-eng
mailing list