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>>
This change was initially merged in response to this issue:
That issue was caused by setting IS_MIDI_EFFECT TRUE during development, so it’s unlikely to affect end users. That being the case, we’ve decided to revert the change, since the previous behaviour is more in line with the documentation.
this commit by @reuk (JUCE 8.0.9). Basically the XML-to-audio config routine doesn’t discriminate anymore between “