A new Jamulus software version is available: 3.5.6. Here are the changes:
support sorting faders by channel name (#178)
enable/disable recording from command line, coded by pljones (#228)
add Audacity "list of files" writer to jam recorder, by pljones (#315)
make level meter LED black when off, by fleutot (#318)
added ukulele/bass ukulele instrument icons created by dos1 (#319)
avoid showing IP address if no name in the musician profile is given (#316)
show channel numbers if --ctrlmidich is used (#241, #95)
added check in acknowledge message, coded by atsampson (#302)
bug fix: on MacOS declare an activity to ensure the process doesn't get throttled
by OS level Nap, Sleep, and Thread Priority systems, coded by AronVietti (#23)
👍
4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to issue the server a SIGUSR2 signal. On Linux (and Mac?) you'd do that with kill -SIGUSR2 <pid> to turn off the recorder and then issue the same signal again to turn it back on. I don't know how you'd do that on Windows though.
BTW controlling server recording from the GUI will be possible in future release. Pljones is working on that.
Last edit: Gilgongo 2020-06-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you start a ver 3.5.6 server with gui, you now have control to start/stop recording via a tick box for "Enable jam recorder". That's great!
@Gilgongo, thanks for the info on SIGUSR2. It was just what I was looking for so that I can use ssh to control recording. I prefer that to a remote X session, as that's more prone to accidents!
A means to check if the server state (recording enabled / disabled) via command line would be nice to have.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good question - there's not a direct way as far as I know other than by looking in the logs:
Jun 25 18:56:56 oddjob jamulus[3396]: OnHandledSignal: 12
Jun 25 18:56:56 oddjob jamulus[3396]: Recording state disabled
Jun 25 18:57:26 oddjob jamulus[3396]: OnHandledSignal: 12
Jun 25 18:57:26 oddjob jamulus[3396]: Recording state enabled
So if you are unusre if it's recording or not prior to issuing the kill, then I guess you need to check the log history, or simply issue the kill and see which state it flips to?
BTW the next release of the client will show if the server is recording.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A new Jamulus software version is available: 3.5.6. Here are the changes:
support sorting faders by channel name (#178)
enable/disable recording from command line, coded by pljones (#228)
add Audacity "list of files" writer to jam recorder, by pljones (#315)
make level meter LED black when off, by fleutot (#318)
added ukulele/bass ukulele instrument icons created by dos1 (#319)
avoid showing IP address if no name in the musician profile is given (#316)
show channel numbers if --ctrlmidich is used (#241, #95)
added check in acknowledge message, coded by atsampson (#302)
bug fix: on MacOS declare an activity to ensure the process doesn't get throttled
by OS level Nap, Sleep, and Thread Priority systems, coded by AronVietti (#23)
How does the recording on/off from command line work?
You need to issue the server a SIGUSR2 signal. On Linux (and Mac?) you'd do that with
kill -SIGUSR2 <pid>
to turn off the recorder and then issue the same signal again to turn it back on. I don't know how you'd do that on Windows though.BTW controlling server recording from the GUI will be possible in future release. Pljones is working on that.
Last edit: Gilgongo 2020-06-14
If you start a ver 3.5.6 server with gui, you now have control to start/stop recording via a tick box for "Enable jam recorder". That's great!
@Gilgongo, thanks for the info on SIGUSR2. It was just what I was looking for so that I can use ssh to control recording. I prefer that to a remote X session, as that's more prone to accidents!
A means to check if the server state (recording enabled / disabled) via command line would be nice to have.
from the command line, how can i check if recording is on / off prior or after executing kill -SIGUSR2 pid?
Last edit: tigabeatz 2020-06-25
Good question - there's not a direct way as far as I know other than by looking in the logs:
Jun 25 18:56:56 oddjob jamulus[3396]: OnHandledSignal: 12
Jun 25 18:56:56 oddjob jamulus[3396]: Recording state disabled
Jun 25 18:57:26 oddjob jamulus[3396]: OnHandledSignal: 12
Jun 25 18:57:26 oddjob jamulus[3396]: Recording state enabled
So if you are unusre if it's recording or not prior to issuing the kill, then I guess you need to check the log history, or simply issue the kill and see which state it flips to?
BTW the next release of the client will show if the server is recording.
thanks, :-) this is cool. better wait, then parsing logs. :-)
Last edit: tigabeatz 2020-06-25
hihi,
just want to ask a somple question! how can we add a welcome message for the jamming mysicians on a private server?
Hi Win - You can do that using the
-w
option on the command line. See the docs on that here:https://github.com/corrados/jamulus/wiki/Command-Line-Options