Hello, I’m having a very weird behaviour that shows only on Bitwig 4.4.6 on Windows. Same version of Bitwig on Ubuntu 22.04.1 does not have this problem. I’m using the GenericAudioProcessorEditor to display the few Choice and Int parameters necessary to customize the plugin’s behaviour. I’m only using latest core JUCE 7.0.4 modules.
(The plugin in question is GitHub - YPares/arpligner: A multi-track & polyphonic arpeggiator plugin that takes both chords and arp patterns as live MIDI data. It’s a MIDI-effect plugin only. Code is open)
The behaviour is that my plugin AudioParameterChoice params are always reset to their default value [1] after reloading my project in Bitwig, or after deactivating/reactivating the plugin. What is weird is that the only AudioParameterInt I have is properly restored to its latest known value. After some VSCode debugger session, I noticed that setStateInformation is called with the correct values (and parameters’ values seem to be set correctly at that point) when the plugin restarts, but for some reason the Choice parameters change back to their default values immediately after (even before I open the GUI).
I still cannot pinpoint whether the problem comes from my code, JUCE or Bitwig. I tried to remain as much as possible “by the book” (ie. stuck closely to JUCE tutos) in my development and I don’t think I really did anything fancy (besides using a Singleton class that’s needed for multi-instance communication, but that’s another unrelated part of the project, it has nothing to do with the parameters).
Anybody experienced this behaviour? I searched through the forum and did not find quite the same behaviour. I read that setCurrentProgram being called after setStateInformation can (or could in the past) lead to that kind of problems, but my debugging session showed me that setCurrentProgram (which is empty anyway in my case) is never even called when the plugin reloads.
[1] The value I set for them when using addParameter, in my AudioProcessor constructor
=>