The convolver based plugins were using dpf states in an incorrect way, where it was only handled internally and never through the host or UI. As such, there is no need to enable states on these plugins at all.
Updated DPF again while at it, why not.
Worth noting that on LV2 and CLAP, parameter changes happen during realtime audio, so the way you setup the code is for sure going to trigger xruns.
Would be preferred to change these to properly use states, if you want to get rid of xruns. The downside is that most hosts are not able to show these on a generic UI, and thus we would need to rely on the custom GUI to be able to change/set these. The plugin DSP side only by itself cannot set them.
Could be a future thing too, in case you want to tag a new release sooner rather than later.
The convolver based plugins were using dpf states in an incorrect way, where it was only handled internally and never through the host or UI. As such, there is no need to enable states on these plugins at all.
Updated DPF again while at it, why not.
Worth noting that on LV2 and CLAP, parameter changes happen during realtime audio, so the way you setup the code is for sure going to trigger xruns. Would be preferred to change these to properly use states, if you want to get rid of xruns. The downside is that most hosts are not able to show these on a generic UI, and thus we would need to rely on the custom GUI to be able to change/set these. The plugin DSP side only by itself cannot set them.
Could be a future thing too, in case you want to tag a new release sooner rather than later.