using the mapping assistant, the ai knob has been properly mapped
The function works on the mixer volume and pan, the issue is with inserts and instruments. I am only using the included cubase plugins…..
the AI function does not work when hovering on any knob or fader in the instrument or plugin. The knob only works when the quick controls of the plugin/instrument are displayed on top. then hovering only any of those 8 controls the knob works. but only for those 8, and only when hovering on those 8 in the top row.
Any thoughts or help would be greatly appreciated.
This shouldn’t be the case, at least I don’t see this issue here. The AI knob properly attaches to whichever control of a plugin has the focus AND is set to have this property.
Yes.
Not sure about this, Martin. I have to note that NOT every single quick control as assigned in the remote control editor, supports this functionality. I’ll provide an example:
Take Retrologue, and inspect how the AI knob behaves when we focus on “Osc 1 Fine” and “Osc 1 Coarse”. No matter how you’ve setup these in the remote control editor, the “Osc 1 Coarse” won’t respond, while “Osc 1 Fine” will. Even if you delete the “Osc 1 Fine” it will still work. The AI functionality is per plugin parameter, independently of whether it is even in the qc matrix.
We can find more info here: MIDI Remote mapping to "AI Knob" does not work with non-Steinberg VST instruments - #10 by m.c
By the way, I must say that AI knob is an extremely useful feature, and I don’t get why many VST devs don’t implement this. Many hardware synths (I have a Fantom here and an MPC) with touchscreen, implement this. User can focus on a parameter and then choose whether to continue using the touchscreen to alter the parameter OR a dedicated hardware knob. I always prefer the latter, it’s just so much more accurate. Steinberg implemented the AI knob and I really feel disappointed not seeing many (or any at all) devs following this.
Doesn’t that defeat the purpose of the AI knob existing? If all it does is map to QC, you could just map the desired parameters to QC instead and assign controllers to those.
Does that mean now Nektar is the only one that has a proper AI knob implementation that changes whoever parameter you’re pointing at regardless of what it is?
For the AI Knob to work on VST3 plugins, the plugin developer has to introduce support for the IParameterFinder function available on the VST3 SDK. AFAIK, Eventide has been one of the latest companies to add support for it, now that the new Yamaha CC1 is available and also includes an AI Knob.
