I'm new to Jamulus. I'm running version 3.6.1 on a MacOS Big Sur 11.0.1 (the most recent OS). My microphone setup works fine with many apps. but won't connect to Jamulus. The problem may be the Security & Privacy settings (Security & Privacy > Microphone) where Jamulus is not listed as an app that can access the microphone. Any ideas?
Thank you for the quick response, and yes, it seems to be a permissions problem. If Jamulus appeared as an option in System Preferences/Security & Privacy/Privacy it would be simple to grant it permission. But it doesn’t show up, and I can’t see a way to get the Mac to see it. Screenshot attached. I tried re-installing Jamulus but that didn’t help.
Oh OK. Not sure what's going on then assuming Jamulus is all installed OK. There was some speculation that Big Sur might cause problems but so far I don't think anyone's tested it apart from you!
Vielen dank, Herr Fischer! Back to a clean compile, as usual. Make is now happy on Jesse through Stretch for my systems. I will update on Git as well, and post there in future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Jamulus documentation says that the server makes a mix (addition?) of the voices from each musician., the mix is sent to each musician.
How can the mix (made by the server) may take into account the individual settings of faders of each musician ?
How the server can take into account the different ping + process time different for each musician: Let us suppose a beat (like a metronome click) is transmitted by the server, each musician receives it , each one after some particular delay, he plays a note on it, and send it to the server with process and transmit time.
How iis made the correction (if any)? Does it mean that the overall delay depends on the worst ?What takes time ? DAC ? build of UDP ? Within the server ? the clients ?
Thank you for any help to understand Jamulus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there is no correction. The only correction that happens is in your head when your brain slowly adapts to the latency and make you play earlier relative the beat.
Jamulus works exactly as if you is standing far from each other. Since the body already can cope with that it works!
I wonder if Volker knew this or it just was a touch of luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there is no correction. The only correction that happens is in your head when your brain slowly adapts to the latency and make you play earlier relative the beat.
Jamulus works exactly as if you is standing far from each other. Since the body already can cope with that it works!
I wonder if Volker knew this or it just was a touch of luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Yves,
To answer your other questions;
- The server makes an individual mix for each client, it knows the settings of your faders.
- As Mats said there is no compensation, see below.
- The processing time in the client and server is small and is covered up by the buffering. The big differences come from the communications quality and time. Poor quality means added buffering, the communications time adds... well time.
Note that this is all not as bad as it may sound. As sound has a transmission time in air of about 3milliseconds/meter even playing in small groups we are always dealing with compensating delays of 10 to 20 milliseconds in a live performance. Our minds are used to doing this. In a big orchestra on a big stage, for example, the delays between performers at the outer edges of the orchestra can be consequential, 15 meters would mean 45ms.
Using Jamulus I have found that delays below 60ms are workable, delays below 30ms not noticeable at all after a short time playing. What is very important is that you listen to the sound coming back from the server and not what you are sending to the server, i.e. NOT direct monitoring.
In a live performance we use visual clues to help compensate and play together. With Jamulus you don't have those visual clues so it takes a little longer, but after a while you compensate automatically and don't notice it at all.
Last edit: DonC 2020-11-22
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.6.1. Here are the changes:
added menu entry "Set All Faders to New Client Level" (#622)
isolate a channel from the group temporarily with shift-click-drag (#695)
on shift-click the pan reset to 0 L/R (#707)
support multiple custom central server addresses (#698)
the Jamulus server now has a different icon, created by geheimerEichkater (#700)
support two rows for the mixer panel (#720)
changed RYG indicator lights with colour-blind compensation, created by geheimerEichkater (#57)
saving and loading mixer settings is now possible during an active connection and a
mixer settings file can be loaded with drag'n'drop (#706)
menu entry Clear All Stored Solo Settings is now enabled during an active connection
bug fix: the fader group property was not correctly loaded from the ini file
I'm new to Jamulus. I'm running version 3.6.1 on a MacOS Big Sur 11.0.1 (the most recent OS). My microphone setup works fine with many apps. but won't connect to Jamulus. The problem may be the Security & Privacy settings (Security & Privacy > Microphone) where Jamulus is not listed as an app that can access the microphone. Any ideas?
Hi Stanis - if this is a permissions problem (sound like it) then you can try this:
https://sourceforge.net/p/llcon/discussion/533517/thread/acf118ed81/#de20
Thank you for the quick response, and yes, it seems to be a permissions problem. If Jamulus appeared as an option in System Preferences/Security & Privacy/Privacy it would be simple to grant it permission. But it doesn’t show up, and I can’t see a way to get the Mac to see it. Screenshot attached. I tried re-installing Jamulus but that didn’t help.
On Dec 8, 2020, at 2:53 PM, Gilgongo gilgongojones@users.sourceforge.net wrote:
Hi Stanis - if this is a permissions problem (sound like it) then you can try this:
https://sourceforge.net/p/llcon/discussion/533517/thread/acf118ed81/#de20 https://sourceforge.net/p/llcon/discussion/533517/thread/acf118ed81/#de20
New Jamulus Release 3.6.1 https://sourceforge.net/p/llcon/discussion/software/thread/487c151a57/?limit=100#835c/0af3/37ea
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/llcon/discussion/software/ https://sourceforge.net/p/llcon/discussion/software/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ https://sourceforge.net/auth/subscriptions/
Oh OK. Not sure what's going on then assuming Jamulus is all installed OK. There was some speculation that Big Sur might cause problems but so far I don't think anyone's tested it apart from you!
https://github.com/corrados/jamulus/issues/749
Make of the new release is failing on my Debian 9 Linode. It succeeds as usual on a Debian 8 server, instance, and on another Debian 9 client machine.
Working from git clone, my re-compile as follows is failing.
qmake "CONFIG+=NOSOUND" Jamulus.pro
make clean
make
throws this error:
--begin example--
src/serverlist.cpp: In member function ‘void CServerListManager::CentralServerRegisterServer(const CHostAddress&, const CHostAddress&, const CServerCoreInfo&, QString)’:
src/serverlist.cpp:315:18: error: ‘QVersionNumber’ has not been declared
QVersionNumber::compare ( QVersionNumber::fromString ( strMinServerVersion ), QVersionNumber::fromString ( strVersion ) ) > 0 )
^~~~~~~~~~~~~~
src/serverlist.cpp:315:44: error: ‘QVersionNumber’ has not been declared
QVersionNumber::compare ( QVersionNumber::fromString ( strMinServerVersion ), QVersionNumber::fromString ( strVersion ) ) > 0 )
^~~~~~~~~~~~~~
src/serverlist.cpp:315:96: error: ‘QVersionNumber’ has not been declared
mber::compare ( QVersionNumber::fromString ( strMinServerVersion ), QVersionNumber::fromString ( strVersion ) ) > 0 )
^~~~~~~~~~~~~~
Makefile:2251: recipe for target 'serverlist.o' failed
make: *** [serverlist.o] Error 1
--end example-----------
I re-installed the dependencies with apt and re-tried: no joy.
Thanks for any light you can shed and please forgive me if this is not the correct location to post this. Should I be on github issues??
Thanks for reporting. I have created a Github Issue for it: https://github.com/corrados/jamulus/issues/736
I have just added a fix to your problem to the Git repo: https://github.com/corrados/jamulus/commit/8dc5bb16a171adc6a1fb80a00c2895d5763e0298. Are you able to check out the latest Git code on master and try out if it now compiles fine for you?
Vielen dank, Herr Fischer! Back to a clean compile, as usual. Make is now happy on Jesse through Stretch for my systems. I will update on Git as well, and post there in future.
Hi,
The new icons don't appear after compilation of Jamulus 3.6.1 !
Thank you for help
Thank you Volker for your prompt answers.
I visited https://github.com/corrados/jamulus/comm ... but I did not
find the "Git code on master" I'm supposed to try out ...unless I don't
understand what it means!
https://github.com/corrados/jamulus/commit/8dc5bb16a171adc6a1fb80a00c2895d5763e0298.
What kind of fix have you done? Is it included in version 3.6.1 (for
Unbuntu)?
https://github.com/corrados/jamulus/commit/8dc5bb16a171adc6a1fb80a00c2895d5763e0298.
Le 22/11/2020 à 09:30, Volker Fischer a écrit :
Hi,
I tried again https://github.com/corrados/jamulus/comm ...
https://github.com/corrados/jamulus/commit/8dc5bb16a171adc6a1fb80a00c2895d5763e0298.and
signed in, and I compiled release 3.6.1 (with Ubuntu 20.04) without
problems. Apparently the fix was not necessary with Ubuntu
Thank you all
Le 22/11/2020 à 15:42, yves moreau a écrit :
The Jamulus documentation says that the server makes a mix (addition?) of the voices from each musician., the mix is sent to each musician.
How can the mix (made by the server) may take into account the individual settings of faders of each musician ?
How the server can take into account the different ping + process time different for each musician: Let us suppose a beat (like a metronome click) is transmitted by the server, each musician receives it , each one after some particular delay, he plays a note on it, and send it to the server with process and transmit time.
How iis made the correction (if any)? Does it mean that the overall delay depends on the worst ?What takes time ? DAC ? build of UDP ? Within the server ? the clients ?
Thank you for any help to understand Jamulus
there is no correction. The only correction that happens is in your head when your brain slowly adapts to the latency and make you play earlier relative the beat.
Jamulus works exactly as if you is standing far from each other. Since the body already can cope with that it works!
I wonder if Volker knew this or it just was a touch of luck.
there is no correction. The only correction that happens is in your head when your brain slowly adapts to the latency and make you play earlier relative the beat.
Jamulus works exactly as if you is standing far from each other. Since the body already can cope with that it works!
I wonder if Volker knew this or it just was a touch of luck.
Hi Yves,
To answer your other questions;
- The server makes an individual mix for each client, it knows the settings of your faders.
- As Mats said there is no compensation, see below.
- The processing time in the client and server is small and is covered up by the buffering. The big differences come from the communications quality and time. Poor quality means added buffering, the communications time adds... well time.
Note that this is all not as bad as it may sound. As sound has a transmission time in air of about 3milliseconds/meter even playing in small groups we are always dealing with compensating delays of 10 to 20 milliseconds in a live performance. Our minds are used to doing this. In a big orchestra on a big stage, for example, the delays between performers at the outer edges of the orchestra can be consequential, 15 meters would mean 45ms.
Using Jamulus I have found that delays below 60ms are workable, delays below 30ms not noticeable at all after a short time playing. What is very important is that you listen to the sound coming back from the server and not what you are sending to the server, i.e. NOT direct monitoring.
In a live performance we use visual clues to help compensate and play together. With Jamulus you don't have those visual clues so it takes a little longer, but after a while you compensate automatically and don't notice it at all.
Last edit: DonC 2020-11-22
Anyone els that cannot open the disk image file (.dmg) on a Mac? Can't install the new version.
Solved! The dots in the version number make that the Mac does not see the file extension as ".dmg". Perhaps change the file name on Soundforge?