Is there a program change key command? Or how would I do a MIDI message = prev/next program change (preset). ?
And is there a way to batch process third party plugins, to import their presets (save) into the media bay, so now I can do prev/next presets with a MIDI controller?
Hi,
You can show Program Change as a Controller Lane in the Key Editor. There is no MIDI Message Prev/Next Program. You have to insert the exact Program Change value/number.
Ok, that would explain why they didn’t add it to the Machine Mk3 midi remote script.
So cubase doesn’t have any message/hotkey for presets? You have to click with the mouse to change presets?
Another question: The “AI Knob” feature (that’s a wild name for volatile link) is great, but it doesn’t work on third party plugins?
It does work on some 3rd party VST plugins. The developer has to enable the feature in their plugin.
Hi,
Yes, there are Preset > Next and Preset > Previous commands. You can assign a Key Command or MIDI Remote.
It was introduced around 15 years ago. Originally, it was a dedicated controller for Steinberg and Yamaha hardware devices. AI is an acronym for Advanced Integration in this case.
This has been discussed many times already. It’s up to the plug-in developer side to enable/implement this option or not. It’s very easy for developers to do so for VST3 plug-ins.
It’s not written in stone. Since “AI” means something else now, there’s no reason not to change it.
This is why I was asking for a hard volatile link. Someone told me, “we already have that. It’s the AI knob in the MIDI Remote.” Um, excuse me but if it only works for some things then no we don’t “have it”.
The difference is you have to physically touch the control or move it with your mouse, for it to be linked up with the ‘volatile link’. This way you don’t need to bother with third party developers, because their parameters get registered as the ‘last tweaked’. No one needs to run around asking each plugin dev to help set something up; which will end up with being ignored, and if they do it, will probably be like a two year wait.
If you want something done right you got to do it yourself.
Wait, that’s “Track Preset”. Is it the same as this box?
Cause I’m trying it out and it’s just going to random presets from unrelated folders, that I didn’t navigate to, for it to go to the next preset.
How do I use a hotkey and MIDI controller to navigate the media bay list?
Let me guess, you can’t do it. In 2026 you can only use a mouse with presets in cubase. I wouldn’t be surprised as they can’t even do a basic ass auto-size columns to fit, or put a basic metadata tag on a .wav file. Things that were invented before I was even born.
Hi,
Yes, Steinberg has it. The technology is there. It’s up to the plug-in vendor to implement it.
No, this is not it. This is the plug-in preset.
Does the Preset Next/Previous work here?
Those options didn’t appear for me when I searched for the word “preset”. Only “track preset”
But I closed and opened the Preset parent folder and there they were. So ya they exist, my fault sorry.
I put them on some buttons. Works beautifully.
I’ll probaby move them somewhere else to reserve those four buttons above the AI knob for automation things.
The three different browser sections on the stock plugins messes with me. And that the names don’t line up when you use one preset section, it doesn’t change the other one.
Not sure yet which preset type I like the best. But close enough, I’ll be happy with that. Thanks for the help. 
Another huge reason to have “volatile link” instead of "mouse hover (last tweaked parameter is hard linked to that knob), is your mouse is free to do anything else in the daw. The parameter can be automated or moved at will on your midi controller, and you can do other things while the link remains active.
With this AI Knob you have to keep the mouse hovered for it to work. That’s no good. And when jamming you don’t want to have to carefully position your mouse over a tiny knob.
It reminds me of other programs when some dipshit computer programmers thought it was a good idea to nudge the right sided scroll bar a few pixels into the program, away from the edge of the screen “to prevent misclicks” making it ten times worse than it was before. Instead of just plopping the mouse on the edge to grab the scroll bar, now we have to have pixel-perfect mouse cursor position to carefully hover it over the inset scrollbar. Get outta here with that. 
Here, this is a perfect example of what I’m talking about. He’s listening to his effect and using the AI Knob to move it up and down. But he keeps having to go back and forth from the bypass button, then hover his mouse over the mix knob. Instead of just tweak the mix knob and it would be linked to the controller.
Not really. You can assign a button on your controller to Lock the AI knob to the currently selected parameter. This way you can freely move around and it will still work.
Yes.This is why I have designed an extension here:
Still, I do understand that this can get complicated for musicians with no programming background, totally expected. But then, a vendor of a controller who does share MIDI Remote implementations, could easily include it.
Ah, that’s good thanks.
I will have a look at that soon, that looks good. The link history looks useful too.
How do I do that?
The only thing I’m seeing in MIDI Remote is “Value at mouse pointer in lock state” and it isn’t doing anything.
My script is just an example. Ideally one should embed the code segments to the script already in use. Otherwise, you can still use the script but have to provide a virtual midi input port and set a knob and button of your controller to send their messages to this virtual port (for example by using Bome MIDI Translator or other utilities to translate the port and MIDI CC). It can get cumbersome.
