Audio initialization difference between template audio app and AudioPluginHost

[reuk]

Thanks for the additional info.

@Kraku

When I use only ‘internal’ nodes (no plugins anywhere), the crash disappears and the stability of switching between audio interface sample rates seems to produce less buggy results.

Is it possible that the crash is caused by an external plugin, in that case? If you inspect the stack trace at the point of the crash, is it in a specific plugin each time?

@Kraku

However, only the 44100 Hz sample rate seems to produce any output on Mac (Windows 10 seems to work fine). I tested this by routing audio interfaces audio inputs directly to its own outputs in AudioPluginHost. Every time I used 44100 Hz sample rate the sound passed without issues through my audio interface. If I changed the sample rate to anything else, I heard nothing from the speakers.

That’s more strange. Are the audio inputs and outputs both on the MOTU device, or are you using separate devices? It sounds like you’re using the MOTU for both input and output, is that correct?

Can you confirm that you see the same behaviour when building the AudioPluginHost from latest develop?

We pushed a fix for another issue with audio devices on macOS very recently. I don’t know whether it’s exactly the same issue, but perhaps it’s related:

Audio stops working after changing samplerate externally

Thanks for your patience on this issue, things have been quite hectic here lately! We pushed a change to the develop branch at the end of last week which should resolve an issue where audio devices were not restarted correctly after their samplerate was changed externally. I’m not completely sure that this is the same issue you’re seeing (it’s not limited to matching-pair devices), but the symptoms sound similar, i.e. the displayed samplerate is not updated and audio output ceases. Given this,…