When I have a given MIDI track set to output to, say, a virtual instrument that does not support MIDI Learn for which I definitely want to bind more than 8 quick controls, my best option is to create a MIDI Remote page for the given controller device I want to use, let’s say an Akai MIDIMIX.
Now, if I click to another instrument that DOES support MIDI Learn, suddenly the fact that the page specifically made for that other instrument is still loaded obscures all the MIDI Learned controls for that instrument. So, I have to manually go back to MIDI Remote and load e.g. the unconfigured “Default” page (or an empty one I specifically create to be blank to not obscure MIDI Learned controls).
Now, let’s say I go back to the instrument’s MIDI track that doesn’t support MIDI Learn; to control it, I have to manually reload the page again.
This gets really tedious.
Why is there no way to assign a given page to a given MIDI track so it loads & unloads automatically upon MIDI track selection?
Very often when creating the MIDI Remote page, the “New Page” function does not work the first time. I find myself often creating pages called “a” repeatedly until I get one, then having to go back and rename them something relevant. This appears to be just a straight-up bug that should be addressed.
I absolutely support a full rewrite of the MIDI Remote and QC parts in Cubase, so it is easier, more intuitive to control what we want where we want.
The code is all pretty good, it is the UX / UI that is frustratingly obfucscated.
Yes, very much agreed: they should really focus on SIMPLICITY, as outlined in my post above.
This should be as intuitive and fast as traditional MIDI learn and require about as much thought once set. “Set it and forget it” is exactly what is so compelling about MIDI Learn as traditionally implemented on the vast majority of software instruments to this day.
If Steinberg could handle this without overcomplicating every damn thing as they are wont to do, well, I’d care far less about whether or not a given VSTi supported it. But given the state of affairs with MIDI Remote, I find myself having to care – enough so to make posts like this in the first place.
MIDI Remote and a VST plugin that supports MIDI Learn internally are fundamentally different systems.
MIDI Remote is a Cubase level system that translates incoming MIDI to VST parameters. The plugin controlled by MIDI Remote is unaware of MR’s existence and sees the parameter changes as VST automation data. MIDI Remote is bidirectional. It can also be used to control other features such as the Mix Console, transport commands and trigger application commands.
By contrast, a plug-in that supports MIDI Learn does so entirely internally. Cubase is not aware of this functionality at all. It takes MIDI input and internally translates it to a parameter value. It is unidirectional.
Because MIDI Remote operates on an application wide level, it makes sense that it consumes the data it receives and that it cannot be set up for a per track or per plugin use. In my view, it makes generally more sense to stick to MR and ignore proprietary MIDI Learn implementations of individual plugins.
Oh my god, dude. I know what it is. I know exactly what it is, you pedant.
No, you’re completely wrong about how this could and SHOULD work. Always, always, without fail, some condescending… person like you will rush to Steinberg’s defense for NO REASON other than to be contrarian.
This is why progress is impossible and I’m finding myself increasingly stepping away from music. You don’t know my workflow and I’m sure you don’t care to, what with your acoustic instrument avatar.
You don’t understand electronic musicians and what we’re after and why, nor do you understand how easy and sane it would be to implement this by any properly motivated party.