VLM with VLC 0.8.2-test2

[rossmac]

I am testing the VLM server with the VLC 0.8.2-test2 release on a Windows XP SP 2 server.

I have installed VLM as an ntservice with the following command line:

c:\program files\videolan\vlc>vlc --extraintf ntservice --ntservice-install --ntservice-name "VLM Server 6" --ntservice-extraintf telnet --ntservice-options "--vlm-conf c:\satin.cfg"

The service is setup successfully on the Windows XP SP2 server machine, and after starting the service and opening a telnet session to the service a 'show' command indicates that the VLM configuration file has been automatically loaded.

The results of the show command are as follows:

Password:
Welcome, Master
> show
show
media : ( 0 broadcast - 1 vod )
satin
type : vod
enabled : yes
instances
schedule
>

A VOD object has been setup automatically.

The configuration file, which is automatically loaded, contains the following content:

new satin vod enabled
setup satin input c:\satin.mp3

Ok, now here are the observed problems:

i. Even though the VLM configuation file has been read in, the Satin
object does not want to play from a VLC client using the following
URL rtsp://192.168.1.99/satin

ii. If the path to the VLM configuration file is somewhat longer, e.g.
c:\program files\videolan\vlc\satin.cfg, the configuration file does not
load at all using the command line shown above (with appropriate
modifications for longer path to the configuration file)

/Ross

[rptl]

in item i have tested vlm with mmsh + broadcast and works great.

BUT you are missing --rtsp-host host:port in your command line!

about item ii

try use --vlm-conf like:

vlc --vlm-conf "c:\path\to your\vlm.cfg"

i hope this help

[rossmac]

With regard to item i. You are correct when I added the --rtsp-host option within the ntservice-options string as follows, everything started working:

c:\program files\videolan\vlc>vlc --extraintf ntservice --ntservice-install --ntservice-name "VLM Server 6" --ntservice-extraintf telnet --ntservice-options "--vlm-conf c:\satin.cfg --rtsp-host 192.168.1.99"

The problem with your second suggestion is that I am installing VLM as an NT service (successfully I should add), and most parameters have to be passed to the NT service through the 'catch all'

--ntservice-options "--vlm-conf c:\satin.cfg --rtsp-host 192.168.1.99"

parameter. I don't think the above parameter can take nested quotes.

I did try using the above parameter with single quotes inside the required double quotes, without much success.

/Ross

[rptl]

pay attention again in yours "" !!!!!! you are missing syntax!!

--ntservice-options --vlm-conf "c:\satin.cfg" --rtsp-host 192.168.1.99

you have to put "" only if you have parameters with spaces, like path name, marq-marquee, etc.

[rossmac]

In the following parameter:

--ntservice-options "--vlm-conf c:\satin.cfg --rtsp-host 192.168.1.99"

everything between the quotes is a string (with blanks) that pertains to the

--ntservice-options

parameter.

In other words the general syntax of --ntservice-options is

--ntservice-options "<string>"

Multiple standard parameters with blanks between parameters can be passed to the ntservice using a string which consists of a series of standard VLC command line parameters, so the syntax I published above is correct and the ntservice version of vlm launches successfully with a "vlm-conf" and a "rtsp-host" parameter, so on this one I am correct on the use of double quotes.

That is what leads to the need for double quotes within double quotes.

Double quotes around a string with a blank such as a path name can be used inside a larger string which is the input the "ntservice-options" parameter string.

However, I am not sure that nested quotes is acceptable to the command line interpreter.


/Ross

[Guest]

Escaping quotes work?

"--stuff=\"blah\""