Hi there,
We are noticing a regression in AudioDeviceManager at least on macOS, introduced in
this commit by @reuk (JUCE 8.0.9). Basically the XML-to-audio config routine doesn’t discriminate anymore between “<<none>> selected in the device list (on purpose)”, and “the info is unavailable, just pick one”.
Steps to reproduce:
- start
AudioPluginHost - Set input device to
<<none>> - Quit, restart
=> Input device is set to something different. Before 8.0.9 it was remembering <<none>>
Let us know how we can help.
