VST - Knobs to DAW's automation-crazy cpu peaks

[zoobooboozoo]

I'm interested in midi learn funcitons(currently checking out fsms and osms that around the internet).
But until my Qs about that...

I want to make my knobs/sliders etc. labeled in the DAW's automation dropmenu.
So the user can pick "Cutoff" in his midi/synth track's automatoin menu for example.

how?

[KG_is_back]

To send and receive automation the schematic uses the Preset manager. Then to the preset manager each knob/slider sends/receives its data via preset parameter primitive. "Dissect"some of the stock knobs/sliders to see it. The parameter prim also receives various parameters like "name" of the parameter, and also whether the knob can be automated (most likely some of these data can be edited in module properties of the knob).

[zoobooboozoo]

Works great, Ill start tagging my controls.

A problem:
Tried numerous midi learn knobs made by users of fs/sm and I'm having the same problems with all of them:
When I turn the knob controlling the cutoff with my mouse everything works fine, but when I do it via midi(either after midi learn with my midi controller or with the automation in my DAW) I get spikes of 30-50% cpu and pop and click noises. just checked and it happens with the stock knobs too... happens more-the more rapid and big the change in value is. there's a zipper at the end of the floats run where it enters the DSP code module of the actual filter...

[KG_is_back]

The problem might be, that there are too much MIDI massages coming in and they produce way too much triggers. Use trigger limiter - it should reduce trigger speed to maximum of 100triggers/second. It will however not work when gui is closed (triggers will be blocked. Still, check if that solves the problem and if it does, there are ways to make it work for closed gui too.

[zoobooboozoo]

Sorry, not exactly sure where to place it. should it be before the interact output?

[KG_is_back]

Right in the midi CC module after midi CC primitive. It is within module "preset" in default knobs.

[zoobooboozoo]

Hey. I used the redraw limiter(no "trigger limiter" could be found) and now midi control is simply not working...

[Perfect Human Interface]

Redraw limiter only passes triggers, so pass the values through a trigger blocker as well on the same outputs/inputs.

[zoobooboozoo]

It seems to solve the problem with stock knobs.
Ill keep testing with other knobs and different situations.

The problem is (as KG said) that when the window of the plugin in the daw is not active the automation/midi control doesn't work. what are the possible workarounds?

[zoobooboozoo]

Hey, is there any alternative solution that enable the automation even if the vst window is closed?