I am writing an audio plugin for FinalCutProX, and I am using the AudioProcessorValueTreeState.
FinalCut opens several instances of the plugin, to render the waveform previews in the timeline. But this triggers an assert in AudioProcessorValueTreeState.cpp:199:
What can be done, so that the AudioProcessorValueTreeState can be used in FinalCut and possibly other hosts we are not aware of?
The MessageManager is shared amongst all JUCE plugin instances, right?
This assert means, that the creation of a plugin instance is not thread safe, right?
Can this assert be changed into a lock, because creating a plugin instance is not time critical anyway?
EDIT: just confirming that changing the assert into
const MessageManagerLock mmLock;
works fine in FinalCutProX…