Small feature request here: I find I’m using MIDI tools like Scaler and others so often now and using the simple setup of a MIDI track + an Audio track for my hardware synths that it sure would be nice if I could intelligently link them such that if I click on or otherwise select one of them, Cubase knows to treat them as a single unit and make sure both yellow Monitor buttons are lit. That would sure save me a lot of clicks. Also, would be cool if they are both automatically unlit when another track or pair (or more) of linked tracks are selected so I don’t have to go searching for which Monitor buttons are still on.
Yeah, that’s pretty close, but not completely it. I’d like to be able to select any track in the group and have them automatically enable Record/Monitor so I can start playing right away, then undo this when I select a track not in the group. Thanks, though!
There is a couple of preference settings that govern this behaviour:
Maybe the combination of these settings and the link grouping does the job?
They don’t: I already have them set. Steinberg is almost there, just not quite. Much like the situation where Device Panels can’t be controlled with MIDI Remote, necessitating my purchase last night of Blue Cat’s Remote Control. 
I heard with this one you can use it to convert modulator signals into MIDI CC to steer external gear. Would be nice to hear if that actually works.
1 Like
Oh man, that’s pretty funny! I’ll have to give this is a shot. But, this kind of goes to my general point: this is far too complicated.
-
Make the MIDI Transformer insert plugin able to have “pages”, or unlimited slots for different transform operations
-
Just remove the MIDI insert plugin limit, already. Four slots is ridiculously arbitrary and meager.
Either way, problem solved and it’s fast & easy.
Instead, Steinberg lets us hang out on the forums constructing ludicrous Rube Goldberg devices to get around their arbitrary limitations (and sometimes just incomplete/languished features).
Really, really wish they would focus on squashing bugs and completing existing features more, but feel like I’m shouting into the void with this much of the time. So, third-party workarounds it is, for now. I spent hours with CtrlrX the other night–what a fiasco of a plugin. The only thing I like less that closed source commercial products not having been completed or sufficiently tested is open source projects that get forked into something that’s so absurdly complicated for simple stuff you spend hours tinkering only to find there’s no simple, feasible way to accomplish your goal because you’ve spent hours trying to figure out why the plugin is doing something completely unrelated to your original problem but that annoys you.
It’s a traaaaap!