For all I know I used only MB plugin interface to tune the noise gate, as you can see in my video.
Do you refer to these sliders are remotes?
Did not touch them. As well as on a second laptop where issue reproduced from the scratch without anything taken from the first one, and also without touching these sliders.
As for Reaper I do not even have a slightest guess where these remotes can be, and reproduced the issue from the scratch as well starting with an empty project using MB interface only as shown in a second video. I doubt I could enable something automation related automatically there.
Anyway, that’s an interesting insight, thanks.
To retrieve the plugin state, the host issues a call into the plugin, asking for the data.
MG2 does not add the patchname to the data, so that is why that is not updated, when the host restores the plugin state, and still displays the confusing “default”. The rest of the data is restored however.
Suspected it to work that way, nice to get a confirmation.
Custom_Gate: A hard midi startgate and retrigger blocker - #6 by Paul
Wow. Looks very promising. Somewhat reminds me of classic debouncing problem on embedded devices.