I’ve been trying to get my app working nicely through the Juce Audio Manager on Mac, and seeing some unexpected behaviour. Maybe you can help!
Basically, it seems that wrt the juce_AudioManager class instance I first need to call initialise(), and then subsequently call setAudioDeviceSetup() to get my device running at the rate I want with the block size and channels I want; I can’t seem to avoid that second call.
Anyways, this results in the underlying core audio device stopping/starting automatically under the hood twice (this happens every time that initialise or setAudioDeviceSetup is called), leading to delays at the start and some odd clicks and pops. It’d be nice to be able to avoid that call to setAudioDeviceSetup …
Additionally, I’d like to be able to totally delay the device from starting at all until some later point when I call a “start” method on the manager. I really don’t want to see those callbacks until I’m ready… I can’t quite figure-out how to do that with the API as it currently stands…
I guess that to have the app do what I want, I could drop down myself to Core Audio, but I dare say this is just down to my missing-out on some information somewhere in the Juce audio manager API.
With best wishes,