BartM

Did you add the -T or --multithreading at the server run line in the service file te enable multiple vCPU's. In the install documentation on the wiki it is not listed, but because you have 6 cores you have to tell jamulus to use them.

Ron, Check the name of your server unit file. When you followed the wiki the unit file will be jamulus.service and not jamulus-server.service. The name behind "kill -s SIGUSR2" should match the name of the unitfile that conrols the server. You can also can use the server unit file to send the Signal to the process without an extra sytemctl service for the toggle. Use: systemclt kill -s SIGUSR2 jamulus or systemclt kill -s SIGUSR2 jamulus-server Depends on the name of the unit file If you have your...

Ron, Check the name of your server unit file. When you followed the wiki the unit file will be jamulus.service and not jamulus-server.service. The name behind "kill -s SUGUSR2" should match the name of the unitfile that conrols the server. You can also can use the server unit file to send the Signal to the process without an extra sytemctl service for the toggle. Use: systemclt kill -s SIGUSR2 jamulus or systemclt kill -s SIGUSR2 jamulus-server Depends on the name of the unit file If you have your...

Ron, Check the name of your server unit file. When you followed the wiki the unit file will be jamulus.service and not jamulus-server.service. The name behind "kill -s SUGUSR2" should match the name of the unitfile that conrols the server. You can also can use the server unit file to send the Signal to the process without an extra sytemctl service for the toggle. Use: systemclt kill -s SUGUSR2 jamulus or systemclt kill -s SUGUSR2 jamulus-server Depends on the name of the unit file If you have your...

For more info on the ProtectHome= parameter see man 5 systemd.exec

Check your jamulus service unit file, if there is a ProtectHome= true setting in the unit file (/etc/systemd/sytem/jamulus.service} change it to false or read-ony. If the value is true all files under /home are not accessable to the process. In thia case, where your tekst file is in the /home directory the read-only setting would be sufficient. The proces is able to read the file. See also https://sourceforge.net/p/llcon/discussion/server/thread/a3b144ca08/#4b35 here server recordings could not be...

Check your jamulus service unit file, if there is a ProtectHome= true setting in the unit file (/etc/systemd/sytem/jamulus.service} change it to false or readony. If the value is true all files under /home are not accessable to the process. In thia case, where your tekst file is in the /home directory the readonly setting would be sufficient. The proces is able to read the file. See also https://sourceforge.net/p/llcon/discussion/server/thread/a3b144ca08/#4b35 here server recordings could not be...

Scott, Nice to hear that the problem is fixed, also note the jamulus option --norecord, this disables the recording after starting jamulus server, so it won't start recording when the first user connects. You firsthave have to send a SIGUSR2 to the server to enable recording. This way everyone can first connect and setup and you can start recording when everybody is ready, The next SIGUSR2 signal will stop the recording. It's a toggle action.