Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
my question: can you change system control port and system socket dynamically or do you need 2 different .ini files for 2 different Snowmix'es to run at the same time? Basically it's this part:
system control port 9999
system socket /tmp/mixer1
You seem to have CSS turned off.
Please don't fill out this field.
Dynamically change the control port number after Snowmix has started listening on the port? No that is not possible, but if you can come with a good usage case or explain why this would be advantageous, I might add it to version 0.4.4. So far I haven't been able to come up with a good reason for this.
Dynamically change the system socket after it has been defined? No that is not possible, but if you can come with a good usage case or explain why this would be advantageous, I might add it to version 0.4.4. So far I haven't been able to come up with a good reason for this.
That said, in version 0.4.3 the command system output reset was added to be able to disconnect and close an existing system socket connection. It is then the responsibility of the connecting process/pipeline to reconnect upon need.
If you want to change the port dynamically, you can use netcat
$ mkfifo backpipe
$ nc 127.0.0.1 9999 0<backpipe | nc -l 127.0.0.1 9998 >backpipe
Here Snowmix listen on port 9999 and netcat listen on port 9998. This way you can take as many input on port 9999 you want and one input on port 9998. If you want more inputs on 9998, you have to find another tool or write a simple tcp server.
Similar method with a named pipe or fifo can be used to dynamically change the system socket.
yet another solution for the dynamically changing the control port is this
$ ssh -L9998:127.0.0.1:9999 127.0.0.1
This solution allows you to connect as many times you want to port 9999 and port 9998 and ssh can log in without password using keys instead.