MIDI Remote requires repetitive user action in practice; cannot replace MIDI Learn as is

Cubase
, ,
1

I’m having two major issues:

  1. 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?

  2. 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.

1 Like
2

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.

4 Likes
3

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.