#LADIOCAST LOCAL UPDATE#
(…and four additional ?hotfixes.) This update has 40 improvements and fixes! ? New 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".6.2.2 (hotfix 6.2.2.3.4) June 2–7, 2022 This update has 60 improvements and fixes! 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. It does sound like a potential clocking problem though. Still experiencing the audio artifacts described above. I've now tried playing a 48k track on Logic running 48k. I've confirmed there are no audio artifacts when I play the same track directly from Logic to my headphones, without. 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. The ping time is 0ms and overall delay is staying pretty steady at about 20ms. I just tried running a local server and connecting to it via 127.0.0.1. 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. 2) The dropout intensity seems to be correlated with overall delay time. I think this helped, although it's hard to tell as the problem has not entirely gone away.
![ladiocast local ladiocast local](https://www.radioking.com/p/wp-content/uploads/2019/10/vdj-2.jpg)
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.
![ladiocast local ladiocast local](https://s3.amazonaws.com/archive.timmmmyboy.com/uploads/2011/03/Screen-shot-2011-03-22-at-8.24.49-AM.jpg)
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. 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. I have a follow up question though: I'm hoping to use a BCF2000 to control my Jamulus mix. 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.
#LADIOCAST LOCAL PRO#
It might be the very fact that I'm playing audio off Logic Pro (an audio program) that's causing these dropouts. The only other step is to change the cc controller. Once the Jamulus client is open using the -ctrlmidich 0 flag, everything works beautifully.
#LADIOCAST LOCAL MAC#
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.
![ladiocast local ladiocast local](https://i.altapps.net/img/ladiocast-bc9ac.jpeg)
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. It was not totally clean, with a few audible clicks during the 3 minute track, but not nearly as distracting as it was previously. Overall latency was about 40ms the whole time (ping time: 20ms). 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.