The VideoLAN Forums

Hello:

I have a home audio streaming system that runs vlc on a server with two different processes, each with a different playlist. I then chose the channel I want to hear by connecting to different IP addresses on the same server on port 8080 from client machine running vlc. I also use 9090 to query currently playing track info from the CLI as well.

Since an upgrade to 3.0.1 version of VLC, this no longer works properly. It seems that the new version of VLC automatically binds to all Interfaces, regardless of how the command line is structured.

Here are my two commands (executed from a bash script):

Stream channel 1 (binds to 192.168.0.14):

nohup vlc -I dummy --extraintf=http --http-host 192.168.0.14 --http-port 9090 --http-password '******' -Z /srv/export/multimedia/audiomix/00-playlist-easy.m3u --sout '#standard{access=http,mux=ogg,dst=192.168.0.14:8080}' --sout-keep &

Stream Channel 2 (binds to 192.168.0.23):

nohup vlc -I dummy --extraintf=http --http-host 192.168.0.23 --http-port 9090 --http-password '******' -Z /srv/export/multimedia/audiomix/00-playlist-hard.m3u --sout '#standard{access=http,mux=ogg,dst=192.168.0.23:8080}' --sout-keep &

SInce 3.0.1 it seems that the first command binds to all interfaces on ports 9090 and 8080, therefore preventing the second stream from working at all, although the process still starts.

Is there some additional command line switch needed now to make this work like before, or is there a new way of doing things in 3.0?

I am using Archlinux, and the latest packaged version of VLC is 3.0.1, compiled on March 6, 2018. Reverting back to the previous Vlc 2.2.8 package restores the expected behavior.

Thanks,

Rett Walters

Both .0.14 and 0.23 are on the same machine? Same interface?

Yes, same physical interface. .14 is "primary" ip, .23 is secondary IP. This configuration can be accomplished with the "ip" command set.

Here is the output from "ip addr" on the machine:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:8e:e4:d7 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.14/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet 192.168.0.23/24 brd 192.168.0.255 scope global secondary eth0
valid_lft forever preferred_lft forever
inet 192.168.0.24/24 brd 192.168.0.255 scope global secondary eth0
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe8e:e4d7/64 scope link
valid_lft forever preferred_lft forever

This is the only way I could get this to work before 3.0.1.

Thanks,

Rett Walters

Hi -

I guess that since I haven't seen any further response to this change in behavior, it's by design. If this the case, what is the proper way of running multiple instances of VLC to have multiple audio streams on the same server?

Thanks,

Rett Walters

There is a bug in the parsing right now, so you need to prepend // in the http-host IP field.

Thanks - that helps with 3.0.2, but just as a note - the 3.0.3 build in the arch repos segfaults with prepending // or without it. Apparently something else is going on with this version.

Rett

Scratch that - this works for the http control interface only binding to a specific interface and port, but the --sout '#standard{access=http,mux=ogg,dst=//192.168.0.14:8080}' component still binds to all interfaces on port 8080, not just the one specified (192.168.0.14 in this case).

But it does look like I can change the port to something other than 8080 on the second process on the sout module to get the same functionality.

Thanks,

Rett

Uh. It's exactly the same for streaming and interface.