Parameter value output events after loading a state

[mwilliamson-fourier]

Hello!

From some testing of CLAP plugins, it seems like there are (at least) two cases when the process() call will emit parameter value output events:

1. When the user changes a parameter value, for instance by turning a dial in the UI
2. When a state is loaded using load on clap_plugin_state

It's useful in the plugin host to be able to disambiguate these two cases, for instance to determine whether or not the plugin host needs to persist a new state (typically yes in case (1), no in case (2) since the plugin host has just provided said state).

What's the expected way of doing so using CLAP? I thought perhaps that plugins should set the CLAP_EVENT_DONT_RECORD flag on any output events resulting from a state load, but it doesn't seem like CLAP plugins tend to do this.

Alternatively, I thought perhaps there might be a pair of events that indicate the start and end of a sequence of events resulting from a state load, but I didn't see any to that effect.

Any guidance on the expected behaviour of plugins according to the spec would be much appreciated.

Thanks!

[baconpaul]

There is a pair of events from a gesture wrapping case 1. Maybe that could be a guide?

the problem with that is: badly written plugins may skip them and then your host will look buggy, I guess

[mwilliamson-fourier]

Thanks for the suggestion. I believe the gesture events aren't mandatory, so even well-written plugins may skip them (for instance, it seems reasonable that a plugin might not use them for binary toggles).