[MPlayer-users] Re: Mplayer as a Client for VideoLAN server

[Rett Walters]

Ross Finlayson (finlayson at live.com) wrote:
>
>
>>The output is attached below - It looks like I need to create an SDP file
>>and use it
>>instead - since videolan doesn't provide SDP information. I think the
>>network is
>>unreachable message is a mis-nomer
>
>No, it's not.  The problem really is that the network is unreachable -
>because the IP address in your URL is not real!

I disagree, 234.5.6.7 is a valid multicast IP/group address that can be used on IP
networks.  What led me to use this is that this is the multicast IP/group address I
told videolan server to send the data out to, and 1234 is the port #.  Xine and the
Videolan client both take this info as is and work, so I believe the information is
correct.  Multicast IP addresses fall in the Class D IP ranges as defined by the
IETF, and are 224.x.x.x-239.x.x.x.  Since I am doing this on a private net with no
routers, this should work fine.

>>I tried with both mplayer -V rtsp://234.5.6.7:1234 and mplayer -V
>>rtsp://@234.5.6.7:1234
>
>The version with "@" is wrong.  However, the problem is that
>         234.5.6.7
>is an unused IP (i.e., unrouted) address.  Where did you get that URL -
>it's not valid!  (Also, I wouldn't be surprised if the port number "1234"
>is bogus also.)

See above....

>>AFAIK, videolan uses more or less standards complaint MPEG2-TS wrapped in
>>UDP packets sent as either multicast or unicast.
>
>Yes, but does its server support RTSP?  I.e., what made you think that
>"rtsp://234.5.6.7:1234" is a valid URL for playing that stream?
>
See above.  I don't know that it supports "RTSP" but it does say that it uses RTP to
send the stream.  Other video streaming devices such as those from Vbrick systems
work in a similar fashion.

Rett