Bug in VLM (VLC 0.8.2-test1)

[rossmac]

I am loading an MP3 file into VLM as a VOD object, in order to create a music server.

I start VLM as follows on Windows XP SP2.

c:\>vlc --intf telnet --rtsp-host 192.168.1.99

VLM starts successfully. I then telnet to VLM from a client machine using
putty and log into VLM - No problem.

If I place the mp3 file in the same directory with VLC and load the following configuration file:

new satin vod enabled
setup satin input satin.mp3

The song plays fine using VLC on a client machine with RTSP as the access method.

However if I move all the music to a subdirectory of VLC
c:\program files\videolan\vlc\moodyblues\satin.mp3

and I try to load the configuration file as follows:

new satin vod enabled
setup satin input c:\program files\videolan\vlc\moodyblues\satin.mp3

I get the following result in the telnet output

Password:
Welcome, Master
> show
show
media : ( 0 broadcast - 0 vod )
schedule
> load satin.cfg
load : error while loading file
> show
show
media : ( 0 broadcast - 1 vod )
satin
type : vod
enabled : yes
instances
schedule

Despite the reported error while loading the configuration file, a show command reports that the vod object exists.

When I try to play the object from a VLC client on another machine using RTSP the object will not play.

THE ONLY DIFFERENCE BETWEEN THE TWO CONFIGURATION FILES IS THE FULY DEFINED PATH TO THE MP3 FILE.

I don't think VLM is processing a fully defined path within a configuration
file on Windows XP SP2 correctly.

/Ross

[dionoea]

could you try loading the configuration file manualy line by line and see if it gives an error message ?

[rossmac]

Here is the error message I received when I performed the setup step by step - manually.

Password:
Welcome, Master
> show
show
media : ( 0 broadcast - 0 vod )
schedule
> new satin vod enabled

> setup satin input c:\program files\videolan\vlc\moodyblues\satin.mp3
setup : Wrong properties syntax

/Ross

[dionoea]

what about :

Code: Select all

setup satin input "c:\program files\videolan\vlc\moodyblues\satin.mp3"

(must be the space in "program files" which messes every thing up)

[rossmac]

Here is the resolution to the issue:

Password:
Welcome, Master
> show
show
media : ( 0 broadcast - 0 vod )
schedule
> new satin vod enabled

> setup satin input c:\"program files"\videolan\vlc\moodyblues\satin.mp3

I used double quotes around "program files".

However, the syntax I originally used was standard windows syntax
(ok, putting a blank in the middle of a directory name may be brain damaged, but go tell Bill about it), so ....

I think you need to update your command line parser to deal with the Microsoft silliness.

/Ross

[dionoea]

our command line parser assumes that commands are issued this way :
setup <name> <command1> <value1> <command2> <value2> ... <commandn> <valuen>

the seperator between commands and values is a space. So i guess we won't be able (or want) to change that behavior. Quoting the whole file location seems like a good alternative to me. Besides, its pretty standard to do so when using shell commands in linux for example.

[rossmac]

ok, point taken about the parser.

Is there a log file for VLM on the server?

I've looked for the usual suspects *.log, *.txt, *log*, but nothing stands out
as a log file.

/Ross

[rossmac]

In my posting above (see the copy of the posting below), I indicated
the correct syntax to load a configuration file with a fully defined path to a VOD object into VLM on a Windows XP SP2 server.

Unfortunately, after further testing I discovered that while the configuration file described below will load successfully, the object in question will NOT play, unless the object is in the same directory, with the VLC code.

On Windows XP SP2 this directory is:

c:\program files\videolan\vlc.

/Ross

Here is the post I am referring to:

Here is the resolution to the issue:

Password:
Welcome, Master
> show
show
media : ( 0 broadcast - 0 vod )
schedule
> new satin vod enabled

> setup satin input c:\"program files"\videolan\vlc\moodyblues\satin.mp3

I used double quotes around "program files".

[dionoea]

Is there a log file for VLM on the server?

I've looked for the usual suspects *.log, *.txt, *log*, but nothing stands out
as a log file.

no ... not yet ... but it is in our (at least mine) todo list for 0.8.3