Non-parameter state in JUCE plugin

[rbuskov]

I have head several people say the same - but also people who seem to have success with using updateHostDisplay() - for example:

How can i set a certain parameter not Automatable?

Yeah… personally I don’t use the APVST for non-automatable paramater-like data at all. That is, I immediately stopped doing it once I figured that there are hosts which ignore the non-automatable flag (I’m looking at you, Reaper!). It’s ridiculous how quirky all of this is. While JUCE does a good job in general abstracting the individual plugin format quirks away and applying some specific workarounds for extra quirky hosts, I hope that at some point the industry will adopt a new and better thou…

UpdateHostDisplay withNonParameterStateChanged sometimes ignored by Reaper

Did you check that with the latest Reaper release? We were under the impression that this has been fixed from the Reaper side recently.

Text Parameter

The wrapper (plugin API abstraction) is an AudioProcessorListener. When a parameter is changed, the audioProcessorParameterChanged() callback is called and the wrapper communicates that to the host. Same for updateHostDisplay() which calls audioProcessorChanged() with the appropriate ChangeDetails flags. Try first if updateHostDisplay() works for you, it did for me, but I know there were reports that some hosts didn’t respond to updateHostDisplay(), so people added fake parameters to trigger …

Did you identify issues in any particular DAWs before deciding on the “dummy parameter” approach?