Timo Sivula

Done! https://github.com/corrados/jamulus/issues/575

Our Jamulus band is spread all around Europe and we struggle finding a good server, that would provide decent latency for all. This problem should be possible to be solved by Jamulus with an algorithm based on just a few criteria: 1. No one in the band SHOULD have more than 40 ms latency 2. The drummer SHOULD have the lowest latency 3. Of the servers fulfilling 1 and 2 the one with the lowest sum of or lowest average latency for the whole band SHOULD be selected. The implementation could be a button...

Indeed, that was the problem. Once I commented that line out it started working.

My server runs as a service in Lubutu 18.04 /etc/systemd/system/jamulus.service: [Unit] Description=Jamulus-Server After=network.target [Service] Type=simple User=jamulus Group=jamulus NoNewPrivileges=true ProtectSystem=true ProtectHome=true Nice=-20 IOSchedulingClass=realtime IOSchedulingPriority=0 ExecStart=/usr/local/bin/Jamulus -F -s -n -e jamulusrock.fischvolk.de:22424 -o "Orvas;Kokkola;73" -w "I like 30 to 36 degrees" -R "/home/jamulus" Restart=on-failure RestartSec=30 StandardOutput=journal...

How does the recording on/off from command line work?

Thanks, this was better than the original.

Some time ago someone here in the forum published a script that updated Jamulus on linux by pulling the next version from the web, compiled it and installed it. I can not find it anymore. Could someone point me to the script?

The server I use for my band only, is not registered to the central server. This way it is not visible to anyone and to connect it you need to know the IP of the server. I suggest anyone who wants to keep their server for them selves, to unregister from the central server.