Jamulus documentation recommends 1.5 GHz CPU speed or more. (https://jamulus.io/wiki/Hardware-Setup) You may find you need to overclock your RPi 3. I find Raspbian fine on the RPi 4, at 1.5 GHz.
The message ends asking me if I want to open the ASIO driver setups. 'Yes' shows me another question "Are you done with your ASIO driver settings of device Realtek ASIO?" It does not show me a driver settings dialog or anything else. 'Yes' now closes the message and Jamulus dies. I agree, something else has grabbed the ASIO driver and changed that setting. But which something?
I have nearly the same message after loading Jamulus 3.6.0 today. It seems to think I have an ASIO driver but it is set to the wrong sample rate! I know I have an ASIO driver. I have been running Jamulus since June (v 3.4.3)! So how do I identify / locate the driver to correct the sample rate? [The bit about a device with a hardware switch rings no bells at all.]
I have nearly the same message after loading Jamulus 3.6.0 today. It seems to think I have an ASIO driver but it is set to the wrong sample rate! I know I have an ASIO driver. I have been running Jamulus since June (v 3.4.3)! So how do I identify / locate the driver to correct the sample rate?
I was in your position - I knew nothing about linux. I took the plain vanilla approach. Browse to the download page. The big green button downloaded the latest version for my OS (linux Rasbpbian). I read the instructions (README.md) and went for it. The instructions have moved since the README file was updated. So look at https://jamulus.io/wiki/Installation-for-Linux instead. Worked like a charm. My biggest problem was setting up a microphone. I needed to learn that inputs come in two kinds: 'microphone'...
Just the same as the first one: ping + 20 ms
… but this fixed it. On the Advanced tab in QJackCtl Settings (the one that says ‘Please do not touch these settings unless you know what you are doing.’!), I changed Output Device and Input Device from (default) to hw:CODEC (i.e. Behringer UCA-202). Much better now. It was a solution to another problem (QJackCtl cannot connect to client as server) but it has fixed this one too.
Thanks, but I changed the buffers from 1,024 to 128 this morning, That’s not my problem. RPi version remains a possibility.