I am starting a VLM module with the Telnet interface and an RTSP server using the following command line on a Windows XP SP2 server system.
c:\program files\videolan\vlc>vlc --intf telnet --rtsp-host 192.168.1.99
The VLM module starts successfully.
I then Telnet to the VLM module at 192.168.1.99 and load a configuration file as a VOD object. The configuration file is a follows:
new MoodyBlues vod enabled
setup MoodyBlues input MoodyBlues.m3u
The load command within VLM works without problem and the 'show' command via the Telnet interface indicates a VOD object named MoodyBlues is loaded.
I then start VLC on a client system. The client system is also Windows XP SP2. The VLC client is using the wxWindows interface.
I select the 'open network stream' option, and I select the RTSP option. The following URL is entered:
rtsp://192.168.1.99/MoodyBlues
A port scan reports that something, presumably RTSP, is listening on TCP Port 554 on 192.168.1.99
I check the stream output box on the VLC client, and select the 'play locally' option Caching on the client side is set to 1200 msec.
The following error message is generated in the "view messages" box on the VLC client.
livedotcom error: describeURL failed (connect() failed: Unknown error)
main error: no suitable access module for `rtsp://'
livedotcom error: PLAY failed No RTSP session is currently in progress
main error: no suitable access module for
`rtsp://192.168.1.99/MoodyBlues'
What are the above error messages telling me?
I also noticed that CPU usage on the VLM server reaches nearly 100% while the VLM server is running after loading the VOD object.
I am using VLC 0.8.1 on both the client and server machines.
/Ross