tinlyer

I've tried a few more things. 1) I closed everything except Jamulus on my computer (including Ladiocast/Soundflower, which I had been using for audio routing), and played the track from my phone directly into the computer microphone. It was definitely a lot better. Overall latency was about 40ms the whole time (ping time: 20ms). It was not totally clean, with a few audible clicks during the 3 minute track, but not nearly as distracting as it was previously. I will try tomorrow to connect an audio...

Just to clarify - the "--ctrlmidich 0" flag should be added when starting the Jamulus server, or something else? Update: this flag should be added when starting the Jamulus client from terminal. For anyone trying this in the future: I ended up using an app called Midi Studio on the iPad, and then using the Audio Midi Setup on Mac to discover the iPad as a device. Once the Jamulus client is open using the --ctrlmidich 0 flag, everything works beautifully. The only other step is to change the cc controller...

Thanks, BTDT. It might be the very fact that I'm playing audio off Logic Pro (an audio program) that's causing these dropouts.

Just to clarify - the "--ctrlmidich 0" flag should be added when starting the Jamulus server, or something else? Update: I realized that yes, it is during the server start script. I have a follow up question though: I'm hoping to use a BCF2000 to control my Jamulus mix. I am using a Mac. Can someone explain in a bit more detail how one is supposed to connect the output of my MIDI controller to the input of Jamulus MIDI in Mac's MIDI studio? As far as I can tell, Jamulus is not a device that appears...

Just to clarify - the "--ctrlmidich 0" flag should be added when starting the Jamulus server, or something else? If it's when the server is being started, then how does Jamulus know which client's mix to control with the connected MIDI controller? Or does this setting just enable all clients to connect their own MIDI controllers? I'm hoping to use a BCF2000 to control my mix.

Learned a few more things: 1) The Ladiocast virtual mixer I'm using has its own sample rate settings (I've now updated to 48kHz. I think this helped, although it's hard to tell as the problem has not entirely gone away. 2) The dropout intensity seems to be correlated with overall delay time. I guess there's not much I can do about that, is there? If ping time is around 20ms, is it expected that overall delay time would be 35-65ms as I'm experiencing? Is there anything I can do to lower this overall...

Thanks for the suggestion. I just tried running a local server and connecting to it via 127.0.0.1. The ping time is 0ms and overall delay is staying pretty steady at about 20ms. Jitter buffer is auto-set at 2 and 2. Empirically, there may be slightly fewer audio artifacts now and I'll sometimes go about a minute without any, but they are definitely still happening from time to time. I've confirmed there are no audio artifacts when I play the same track directly from Logic to my headphones, without...

Thanks for the hint. I've now tried playing a 48k track on Logic running 48k. Still experiencing the audio artifacts described above. It does sound like a potential clocking problem though. I wonder if there is something I need to pay attention to when using Soundflower and Ladiocast, which is the method I'm using to pipe Logic output into Jamulus input. The other possibly related evidence is that sometimes but not always, the local jitter buffer size seems to increase and the system shows an "x"...