When the available space for recording audio files at the server is reached, Jamulus server ploughs on ahead with the Reaper and Audacity project files and attempts to create new files for newly connected clients. The results are truncated files for clients online at the time storage ran out and empty files for subsequent connections. The project files are filled with half-truths.
Audacity attempts to load all the files listed but reports errors.
Reaper gets the start times and durations of every connection, loads all the files without reporting errors but loops the available audio for a track that spans the truncation until its connection duration is filled. After the truncation point, the mix can be quite hilarious when there are multiple clients.
I would suggest an enhancement that monitors available space, stops recording when it reaches zero or some non-zero threshold, and closes the project files. I guess the corollary is that Jamulus server should not auto-start recording when there is no space available. And the recording warning banner should now warn that automatic recording is suspended for lack of space (or better words to that effect).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi VE3,
Are you using the latest server version?
It seems to me that recently some changes were made for the disk full case when recording.
But it may, of course, not have fixed the case you have.
If you are not running the latest, I would update and see if things are better.
Don
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When the available space for recording audio files at the server is reached, Jamulus server ploughs on ahead with the Reaper and Audacity project files and attempts to create new files for newly connected clients. The results are truncated files for clients online at the time storage ran out and empty files for subsequent connections. The project files are filled with half-truths.
Audacity attempts to load all the files listed but reports errors.
Reaper gets the start times and durations of every connection, loads all the files without reporting errors but loops the available audio for a track that spans the truncation until its connection duration is filled. After the truncation point, the mix can be quite hilarious when there are multiple clients.
I would suggest an enhancement that monitors available space, stops recording when it reaches zero or some non-zero threshold, and closes the project files. I guess the corollary is that Jamulus server should not auto-start recording when there is no space available. And the recording warning banner should now warn that automatic recording is suspended for lack of space (or better words to that effect).
Hi VE3,
Are you using the latest server version?
It seems to me that recently some changes were made for the disk full case when recording.
But it may, of course, not have fixed the case you have.
If you are not running the latest, I would update and see if things are better.
Don
I am using a public server managed by someone else. Jamulus Explorer shows its version is 3.6.2git.
Well, that is the latest version.
I guess the best way forward is to announce the problem here:
https://github.com/corrados/jamulus/issues