What convention is used to name the WAV files recorded at the server?
- mostly I see something like ____-142_183_170_x_22141-798869-1
- rarely Robert_Lead_Ten-174_88_131_x_22175-797106-1
Is the -nnn_nnn_nnn the last 3 parts of the client's IP address?
Is the x_nnnnn the IP port number?
That leaves the variable length number followed by -n. What are those?
Why does a file exceptionally get the human friendly client name, not always? That would be very helpful in selecting files to download when a full session is unwanted.
Audacity and Reaper seem to behave differently in naming tracks on importing the files via the respective project files written by the server:
- Audacity takes the filename
- Reaper prepends the client name to the file name
Advantage: Reaper!
Why? Is that simply a feature of Reaper not supported by Audacity? If so, then if the server could prepend the client name to the file name then humans and Audacity would be happier.
Last edit: VE3MEO 2021-01-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe the filenames include a date and time stamp, as well as a portion of the IP address. If you have Recording enabled on the server BEFORE musicians join, the audio files will not have their Jamulus names - if you wait to enable Recording AFTER they've joined, or you restart recording AFTER they've joined, then the audio files will have their Jamulus names.
What convention is used to name the WAV files recorded at the server?
- mostly I see something like ____-142_183_170_x_22141-798869-1
- rarely Robert_Lead_Ten-174_88_131_x_22175-797106-1
Is the -nnn_nnn_nnn the last 3 parts of the client's IP address?
Is the x_nnnnn the IP port number?
That leaves the variable length number followed by -n. What are those?
Why does a file exceptionally get the human friendly client name, not always? That would be very helpful in selecting files to download when a full session is unwanted.
Audacity and Reaper seem to behave differently in naming tracks on importing the files via the respective project files written by the server:
- Audacity takes the filename
- Reaper prepends the client name to the file name
Advantage: Reaper!
Why? Is that simply a feature of Reaper not supported by Audacity? If so, then if the server could prepend the client name to the file name then humans and Audacity would be happier.
Last edit: VE3MEO 2021-01-07
I believe the filenames include a date and time stamp, as well as a portion of the IP address. If you have Recording enabled on the server BEFORE musicians join, the audio files will not have their Jamulus names - if you wait to enable Recording AFTER they've joined, or you restart recording AFTER they've joined, then the audio files will have their Jamulus names.
More on starting/stopping Recording here...
https://docs.google.com/document/d/1smcvsxdaaViPQvGMQHmah_6BQeqowhmGSFMHfnlY2FI/edit#