Is there anyway to run VLC as a service and have the http already enabled when Windows loads?
I am running Windows 2003.
VLC as a Service
Forum rules
Please post only Windows specific questions in this forum category. If you don't know where to post, please read the different forums' rules. Thanks.
Please post only Windows specific questions in this forum category. If you don't know where to post, please read the different forums' rules. Thanks.
VLC As a Service
As of VLC 0.8.2, the following command line would start VLC as a service
C:\"Program Files"\VideoLAN\VLC\vlc.exe --ntservice-install --ntservice-name 'VLC' --ntservice-extraintf telnet --ntservice-options "--vlm-conf c:\satin.cfg" --rtsp-host 192.168.1.99
The VLM configuration parameter is (was) only necessary in order to automatically load a VLM configuation file with a list of VOD objects.
The entire --vlm-conf parameter is being passed as a string to the nt service manager for use as a parameter of the service.
VOD objects can also be music files (.mp3 files). At the time, the VLM configuration file had to be at the disk root directory "c:\".
In the above example the control interface is telnet which is used to manually install or delete VOD objects. The Telnet control interface listens on port 4212.
In 0.8.2 the telnet control interface worked, but the HTTP control interface did not.
A VLC client can listen to or view the VOD objects that are active within VLM using rtsp.
In 0.8.5 the following command line MAY also work.
C:\"Program Files"\VideoLAN\VLC\vlc.exe --ntservice-install --ntservice-name 'VLC' --ntservice-extraintf http --ntservice-options "--vlm-conf c:\satin.cfg" --rtsp-host 192.168.1.99
I believe the http control interface will listen on port 8081 in 0.8.5
In order to listen to (or view) a VOD object from a VLC client use following options:
file --> open network stream --> select the RTSP option -->
enter the url as rtsp://192.168.1.99/"object name"
objects are either loaded automatically, as above, or manually via the HTTP or Telnet command interface.
In 0.8.5 I cannot get the eqivalent functionality to work through the GUI even though it is advertised as a feature.
/Ross
C:\"Program Files"\VideoLAN\VLC\vlc.exe --ntservice-install --ntservice-name 'VLC' --ntservice-extraintf telnet --ntservice-options "--vlm-conf c:\satin.cfg" --rtsp-host 192.168.1.99
The VLM configuration parameter is (was) only necessary in order to automatically load a VLM configuation file with a list of VOD objects.
The entire --vlm-conf parameter is being passed as a string to the nt service manager for use as a parameter of the service.
VOD objects can also be music files (.mp3 files). At the time, the VLM configuration file had to be at the disk root directory "c:\".
In the above example the control interface is telnet which is used to manually install or delete VOD objects. The Telnet control interface listens on port 4212.
In 0.8.2 the telnet control interface worked, but the HTTP control interface did not.
A VLC client can listen to or view the VOD objects that are active within VLM using rtsp.
In 0.8.5 the following command line MAY also work.
C:\"Program Files"\VideoLAN\VLC\vlc.exe --ntservice-install --ntservice-name 'VLC' --ntservice-extraintf http --ntservice-options "--vlm-conf c:\satin.cfg" --rtsp-host 192.168.1.99
I believe the http control interface will listen on port 8081 in 0.8.5
In order to listen to (or view) a VOD object from a VLC client use following options:
file --> open network stream --> select the RTSP option -->
enter the url as rtsp://192.168.1.99/"object name"
objects are either loaded automatically, as above, or manually via the HTTP or Telnet command interface.
In 0.8.5 I cannot get the eqivalent functionality to work through the GUI even though it is advertised as a feature.
/Ross
Return to “VLC media player for Windows Troubleshooting”
Who is online
Users browsing this forum: No registered users and 59 guests