punshon

It's a pretty old thread but it is good you mentioned it. The known-working hardware page is a lot harder to find now, and harder for us to edit too. The Blue Yeti (and the smaller Yeti Nano) can have their local monitoring turned off by running alsamixer and toggling the control (i think it was with the 'm' key) The Yeti Nano actually has a (hidden) hardware switch for it - you hold down the 'pattern' button for 5 seconds. So both microphones are completely good on linux , with headphones plugged...

Hi Ben, Your latency is caused by the audio buffer size. You are using 256 samples per buffer (that is the 10.7 ms setting). That's why you have the extra 30ms delay. You will need to get it to 128 samples per buffer (the 5.33 ms setting). The XRUN message (the chopped up sound) are caused by your computer not being able to process the audio quickly enough, from your USB audio interface. If you are using a USB hub, get rid of it. Even try a different USB cable. Check the CPU usage on your computer....

Hi Shesakillatwo, Can you roll back to 3.5.6 and tell me if you still see the problem ? John

Hi Scott, I addressed this in my video, Jamulus Tech Essentials 1 https://archive.org/details/jlp_jamulus_tech_essentials_1 The short answer is that for analog audio, low latency is easy. But for digital audio, low latency requires the audio interface to really work hard. Most onboard audio isn't capable of doing it. Kind regards, John

Somewhere in the documentation you will read the "Number 1 rule of Jamulus, don't listen to your local signal - only listen to your signal as it comes back from the server". With the Blue Yeti microphone, by default the local signal (the input to the microphone) comes directly out of the headphone jack. Blue calls this "zero-latency" monitoring. Unfortunately, if you hear your signal with zero latency, and the rest of your band with 40ms latency, then you won't be able to do a good job of playing...

Hi Cyprian, Please try it with no port mapping configured in your router. What is the name of your server?

Alex is right about the Blue Yeti. I am pretty sure I added it to the recommended hardware page, but with a couple of notes: 1 - it works great on mac (there is a checkbox to turn off local monitoring) 2 - it works ok on windows with ASIO4all. a bit more latency than on mac. you can turn off the local monitoring if you go deep into the settings 3 - latency on linux is good but i did not find any way to turn off the local monitoring.

Hi Carl, in termal, type this line and then press the ENTER key: cd /Applications/Jamulus.app/Contents/MacOS/ and then, type this line and then press the ENTER key: ./Jamulus -s