MIDI Remote / Channel Strip: Inconsistent Mapping & Missing "Exclusive Solo" Command

createartrecords · February 17, 2026, 10:49pm

Subject: MIDI Remote / Channel Strip: Inconsistent Mapping & Missing “Exclusive Solo” Command

Hi everyone,

I’ve been a pro engineer for over 30 years and I am currently pushing Cubase 14 to its limits. My default project runs 26 instruments in unison at a rock-solid buffer of 48 samples. While the audio engine performance is stellar, the MIDI Remote logic is a major bottleneck for professional hardware integration.

The Issue: Inconsistent Parameter IDs in the Channel Strip I am using a hardware controller to achieve a tactile “multi-point” experience—shaping sound with both hands simultaneously (e.g., Gain and Q-factor).

However, the internal Parameter IDs for the Channel Strip compressors (Standard, Vintage, Tube) are not synchronized. This is a massive workflow killer:

Redundant Mapping: To use all three compressor types, I would have to sacrifice dozens of my physical controllers just to map the same basic functions (Threshold, Release, etc.) over and over again for each model. This is a complete waste of hardware resources.
Forced Workarounds: Currently, I am forced to stick to the Standard Compressor only, or revert to my Kensington Expert Mouse to manually fix what the MIDI Remote should handle automatically.

Specific Command Request: Exclusive Solo I am still struggling to find a way to map Exclusive Solo (the Ctrl/Shift + Click behavior) to a single MIDI button. Is there a command I am overlooking that replicates this behavior without a mouse/modifier combination?

The Request to Steinberg: Please implement an Abstraction Layer for the Channel Strip. Core parameters (Threshold, Ratio, Attack, Release, EQ Gain, Q) must have fixed IDs across all models. We shouldn’t have to choose between “plugin variety” and a “consistent hardware layout.”

Let’s bring the MIDI Remote logic up to the same high professional standard as the audio engine. So that no Midi Remote User are restricted to one Compressor-Type.

And by the way, to have the Possibility change the Compressor-Style with a Command without use a Mouse would be heaveny..

Best regards,

(Ron)ald Scherler (CreateArtRecords)

m.c · February 17, 2026, 11:51pm

Here’s a table with the 8 parameters for each channel compressor:

I see for example that Attack is in the very same slot for all three compressors. The Release differs on Vintage, since it has also the AU.
Nevertheless, we can always alter the position of the parameters by using the remote control editor.

I’m not sure I understand which IDs you’re referring to. Is it the “real” tags inside Cubendo engine, or the slot indexes? In case we’re talking about slot indexes, we can deal with them relatively easily.

Say we have the Vintage compressor selected.

Now, say we want to get the “Release” parameter to slot 4, so that it will be aligned with the other two compressors. First click on the “e” button, so we can move to the more detailed view:

Now, we go and right click on the “Release” knob:

In the popup menu, we can choose the ‘Add “Release Time” to Quick Controls’ and set it to Slot 4, as I already did in order to test it.

Have a look at this macro:

Mackie supports this and can be implemented in the MIDI Remote, but one would need to script it. I obviously don’t encourage this approach, I’m with you in getting key commands for these processes. However, if you want more info on this, I can provide it.

createartrecords · February 18, 2026, 1:48am

Thanks M.C. for the effort and the table!

However, there is a fundamental misunderstanding regarding the use of Quick Controls. It would be only natural and, frankly, the only way it makes sense for a professional workflow to have a global, hardware-based mapping for the Selected Track that just works out-of-the-box. When I select a track, I expect my controllers to work instantly and consistently.

One has to wonder how this is handled for Steinberg’s own hardware, like the CC121. If dedicated controllers can access the channel strip logically, the MIDI Remote system should offer the same consistency for third-party hardware.

The issue isn’t the GUI, it’s the underlying ID logic. Whether a compressor has 4 or 8 parameters, the core functions like Threshold, Ratio, Attack, and Release should always occupy the same fixed ID slots. Additional parameters should simply be added at the end of the index, rather than shifting the entire order and breaking the physical layout. This is a matter of consistent data design.

Regarding Exclusive Solo: I will check the macro, but it remains a professional oversight that such a basic console-style command isn’t available as a native, direct target for MIDI Remote mapping without needing workarounds.

To summarize why the suggested Quick Control approach leads into a logical dilemma for a high-density setup like mine:

The Preset Burden: Quick Controls are track-based. To make them “follow” my selection across a 50+ track project, I would have to manually assign them or manage track presets for every single possible channel configuration. This is the opposite of a professional, automated workflow.
The 8-Slot Limitation: Even if I did the work, I would be limited to only 8 parameters. With 47 physical controllers on my Pro 88, I want simultaneous access to EQ, Compression, and Sends at the same time. Using Quick Controls would mean 80% of my hardware stays idle while I’m forced to switch software layers.

I am convinced that Steinberg would significantly profit in the market by refining the MIDI Remote feature in this way, now. It would also open up great opportunities for cooperation with hardware manufacturers. After all, maintaining support for third-party protocols like MCU or EuCon is a constant effort anyway—a solid, native “Abstraction Layer” within MIDI Remote would be a far more sustainable and professional solution for everyone.

Thx for interest,

Ron

m.c · February 18, 2026, 2:22am

There’s surely a misunderstanding here, I agree. I’m almost sure you’re talking about Track Quick Controls. I’m not. What you describe is already achievable, you have to set your controls to the proper objects in the MIDI Remote Mapping Assistant. There’s no 8 slots limitation there. You can have as many parameters as you choose to if of course your controller(s) can handle them.

IF I understand correctly what you’re suggesting, this is not possible out-of-the-box. It could be IF there was a unified protocol for all vst vendors. Let me explain this: A manufacturer has the freedom to choose what parameter goes to what index. Cubase or any other DAW out there, cannot automatically map, or if it tries to, cannot do this reliably, it would use some type of word regex. The closest solution to this is users sharing vst matrices created in a way agreed between them.

Not sure I follow you here. Once you setup assignments to the “selected track” object, these will update whenever you change the selected track. Again, I think you’re talking about the “Track Quick Controls”. Setting up a MIDI Controller or a bunch of them to work consistently require mapping to the dedicated host objects. Track Quick Controls are great for what they’re supposed to do: Handling specific parameters for a specific track each time. Generic mapping is great for everything else, be it EQs, Strip FX, Inserts, Sends, Instrument. Doing this, holds mappings for every track you then select.

Aurasphere · February 18, 2026, 9:10am

Hi Ron

Ive been around this mountain many times.

Each DAW has its issues…Im VERY frustrated that the midi remote editor is half baked for sure. Im not programming anymore but even softube, artist mix are a pita. Firstly, I encourage you to dig deep, ditch any plugins that have cross over and simplify before you start the automation process. I have been mixing/producing for 35 years and eg EQ has only a few stages…and so much of what I see on YT is, with respect just BS.

Correction/troubleshoot/Surgical. This is quite often graphic, so use a graphic ui and some knobs if you need to
General shaping; honestly, if there are more than 4 bands, you are wasting your time. I actually use tonelux tilt. 1 knob to spectral balance and HP/LP filters to clean up overshoote
Masking for groups. Just use the cubase eq, already has spectrum overlay and is decent sounding or BYO

Im just highlighting, that this reduces it to a couple of knobs that are tuned to what you feel/hearing…the rest is just options paralysis tbh but of course you may not be there yet.,.you sound passionate. I have waste probs 10s of thousands $ on software…at least I get cash back for hardware…actually make money tbh

Apply this to the rest of plugs…doing more with less will move your mixes forward as you will lean into the art and not the science.
Im saying it with full respect but mastery over art makes professional results. If Im using more than 8 ifx slots…there is something wrong with my source material.
Less is more…

If you want serious mapping for anything you need gestures…Ive posted here many times but for button type stuff…you need to look outside the DAW. Midi remote editor is for very light stuff with coding.

ITs from a google SS sheet and it outputs an xml file that imports as a legacy remote map. A lot can be done but I use it for mainly program navigation along with an artixt mix/eucon and avid control on ipad…its wild…takes ages to learn but now my colleagues are pretty blown away. Do something for long enough ie play the same song on violin for 7 years…you are going to get decent at it.
All the best with it… @m.c is a guru!

This has been revised now and Gesture 2 (pres and hold) and gesture 4 (double press and hold) now just just the scroll wheel. eg Press and hold the Zoom undo button and you can use the mouse to fly through where you have been in seconds.

createartrecords · February 18, 2026, 11:09am

"@Aurasphere: A warm hello to you! I am very glad you reached out and that I’ve ‘met’ you here. It sounds like we might have started our journey around the same time with Cubase VST/24! Thank you for your honest perspective; you confirmed my suspicion that the MIDI Remote is indeed ‘half-baked’. I totally agree with ‘Less is more’, but for that to work, the ‘Less’ (the few knobs I use) must be 100% reliable. If I have to fight the software just to keep ‘Threshold’ on the same knob, I lose the artistic focus. It’s a pity we have to look ‘outside the DAW’ for solutions that should be core features of a professional system.

@m.c: Have you actually tried mapping the ‘Compressor’ host objects yourself recently? If you do, you will see exactly what I mean. Bank 1-8 is incomplete, and 9-16 are just duplicates. There is no ‘deep’ access if the parameters are ‘ghosts’. This isn’t a UI misunderstanding; it’s a flaw in the current data population.

The solution is simple: To avoid overwhelming casual users, Cubase already allows us to choose how many parameters are shown in the browser list. But these slots must have a function! If Steinberg provided 24 or 32 slots with a consistent, labeled assignment for each compressor model, it would be a professional game-changer.

It feels like we are constantly sold new features while these fundamental ‘half-baked’ areas are never truly fixed. As a customer, I am paying for a system that suggests it can handle this, but instead of finishing the existing architecture, the focus always seems to shift elsewhere. Professionalism is about reliability and tactile consistency."

createartrecords · February 18, 2026, 11:20am

"@Aurasphere: Just a small addition to clarify: I’m actually 100% on your side regarding the ‘less is more’ approach! That’s why I focus on the internal Cubase modules. The internal EQ with its 4 bands is exactly what I need. My goal isn’t to control massive, complex plugins, but simply to have those few internal bands reliably on my physical knobs, when i sit withbmy Guitar in my Hand. It’s great to meet another veteran from the VST/24 days who values the art of mixing!

@m.c: I’d also love to hear your thoughts on the ‘Exclusive Solo’ function. One of my main goals is to work as ‘mouse-free’ as possible, which is what the MIDI Remote is designed for. However, for a classic console feature like Exclusive Solo, it seems I still have to reach for the mouse.

Don’t you think that adding such fundamental mixing commands as native targets would make the MIDI Remote much more powerful for professional workflows? It would be the icing on the cake to stay entirely on the hardware without having to switch back to the mouse for such a basic task."

Make Music have Fun!

m.c · February 18, 2026, 2:24pm

Sure, but this is not directly related to the midi remote. I mean, it already has the functionality to support it. What could be done is that Steinberg maps these fx.

Tried the macro I suggested?

I’ve said that again in this forum, and I’m not suggesting anyone does the same. There are plenty of things to correct/improve/add in Cubase. After all this is why we have updates. However, when I really need something and it is doable, no matter how complex it may get, I will try to do it, simply because I don’t have the time to wait for Steinberg or any other manufacturer (I’m not talking about DAWs only) to implement it. When it gets implemented, I’m happy, till then I try my best to provide a solution to my problem. But again, that’s just me, I totally understand the feature requests.

You bet

Aurasphere · February 18, 2026, 9:24pm

Yep agreed…again @m.c

Aurasphere · February 18, 2026, 9:38pm

Hi again @createartrecords
Great to “meet” you too!

Im a bit more ancient…v1.0 on Atari lol

I use other DAWs eg I know Live quite well, having learnt learnt the api for hardware programming (chinese oem)…and for other clients who send me projects and want them sent back so they learn etc

After the amazing rewrite of SX…and then dumping critical plugs like Multiband (still unmatched in the market) I vowed to not use any DAW based plug. I still keep a copy of sx3 as a host and route externally to it when mastering and I have the need for that…so BEWARE! (The channel strip in C has remained fairly constant though and eqs are decent dig for sure, they are simply yamaha)

@m.c has explained it well one way. Im pretty sure I know what you are trying to do; thats what I do ie all parameters are in the same location etc
Dynamics:

Knob 1 = Parameter 1 = Threshold
Knob 2 = Parameter 2 = Attack
and so on.

As a 1 off, open each target plugin, as @m.c pointed out, go to the plugin options and use the (PLUGIN) remote editor to order the plugin params and you have unlimited banks in grps of 8

Layout the remote (SURFACE) editor so that the names are all visible.

DONT use QC but use parameters + parameter banking which will get you across everything
Do the parameter ordering in plugin/remote editor as discussed above (not to be confused with remote SURFACE editor, obviously schema is by coders not hardware guys) and everything will be consistent.

Voila! away you go.

That will pretty well cover you.

QC are just for quick hooking up/exceptions or specific track controls
and I learnt by converging a number of items to get there but put plainly, it takes time to do that really well…because only you know your workflow

BTW @m.c exclusive solo works fine…

EDIT:

As an example…its a bit messy, finishing my studio refit in the next couple of weeks but I use
Simple hardware Iconpad for knob control and switching for basic FX. Avid control on the ipad is the fastest way I have found to get around IFX but the Iconpad also augments that.
It uses parameters and banking to always have the same params in same spots
The artist mix is for multi faders passing for levels but also flip faders for fine and ergonomic sends ie mix by feel with eyes closed
The Old Kore is purely a dedicated Control Room surface
The game pad is for program nav and most common use items, I barely touch the keyboard now
eg 1 button is dedicated to zoom workflow
1 press zooms in on selected
1 press and hold zooms locators
double press hold zooms out full etc

ie gestures on 1 common button do many things in an intuitive way…anyway hope that helps…the point is that a simple midi remote controls all the params in banks of 8, manages A/B comparisons and bypass (you can press the encoders too) etc you get the idea
My left hand barely moves to get to any function and mouse has qualifiers and shortcuts on it…this is a handy way to add shift etc to midi remote knobs

The table is just a prototype template that gets hacked along the way…will be acoustically transparent steel mesh…

the ipad/avid control unplugs so I can as an unplugged remote ie set musician monitor levels, inputs, rec arms etc. Its such a great tool

createartrecords · February 20, 2026, 12:41am

Final Forum Post (English):

"Thanks for the clarification, @Aurasphere and @m.c!

I’m actually very grateful that you reminded me of the Remote Control Editor. I tried it years ago, but I just couldn’t ‘get warm’ with it back then and eventually forgot it even existed! It’s great to be back in the actual ‘brain’ of the mapping.

The ‘Aha-moment’ for me was realizing that I should load the internal compressors as VST Inserts instead of using the Strip modules. This gives me full access to the Editor, lets me fix the ‘Parameter 1, 2, 3’ labels, and ensures my M-Audio Pro 88 always has a consistent layout. With this setup and my new understanding of the Editor, I think I can finally work efficiently.

However, I still wonder: Why hasn’t Steinberg combined the Remote Control Editor and the MIDI Remote into one seamless system? Currently, we have this ‘parameter mess’ because they feel like two separate worlds. It would be so much more intuitive if they were integrated—using the MIDI Remote for quick, focused assignments of unprogrammed plugins, while having the deep, custom configuration of the Remote Control Editor directly built-in. And we will have one visual reference what my hardware is doing.

But for now, this hybrid approach is my winner:

Remote Control Editor for consistent, deep VST control via hardware.
Stream Deck Mobile (Smartphone Sidecar) for ‘Sticky’ UI modifiers (Shift/Ctrl) to handle the Listen Button and other UI tasks without the finger acrobatics.

Cheers for the help and the Atari nostalgia—this really helped me bridge the gap and find a workflow that actually works for a guitarist!"

Thx a lot for your inspirations.. cheers

Ron

createartrecords · February 20, 2026, 1:12am

The “Missing Link” between MIDI Remote and Remote Control Editor

"I’ve finally realized why the new MIDI Remote feels so frustrating when it comes to controlling plugins and compressors: There is a massive ‘Missing Link’ in the UI design.

The MIDI Remote acts as the translator for our hardware, while the Remote Control Editor is the actual brain that defines the parameter layout for VST3 plugins. The problem is that Steinberg has kept these two systems completely separate graphically.

If there were a simple button within the MIDI Remote interface labeled ‘Open Remote Control Editor’, users would immediately understand how they work together. Instead, we have to hunt for a tiny sub-menu inside the plugin header to fix ‘bad’ default mappings.

By using the Remote Control Editor to customize our Inserts (like the internal compressors, Oxford, or FabFilter), we can finally turn our controllers into a truly tactile experience. We can stop flying ‘drones’ over 24 anonymous parameters and start actually ‘touching’ the sound again.

It’s a game-changer once you find the ‘hidden’ door, but it’s a shame Steinberg makes it so hard to discover."

Aurasphere · February 20, 2026, 1:14am

No probs

Im not sure if Im following but the param type of mapping is how other DAWs handle it efficiently and they are still kind of diff parts of the equation

Just to be clear:

Remote Editor for Plugins

Was simply a way for high end eg Nuage etc hardware to fairly simply map in…back a couple of decades

This is purely now, for easy editing or parameters in their required order (dont forget +ctrl to overwrite/replace when drag dropping the elements to diff slot)
You can map a lot of rows of 8 which are then traversed by the command “± parameter bank” which is in both legacy remote and the latest Remote Surface Editor

This allows the user to easily order those parameters…in Ableton, it start off…before mapping, with "favourite” parameters which can be changed or “factory reset” to them but its the same deal of param 1, param 2 etc

Remote Surface Editor

You can have as many maps of what you wish.
My default map is params and banking, AB etc. There is nothing to think about here as it is all determined by the users choices in the above section/remote editor/plugin. These are persistent values
I still have a map (2nd mapping page) for QC etc for the interim needs of QC for track channels, instruments etc and so on

So I still see it as reasonable to have 2 separate perspectives ie 2 diff editors…Im my case anyay

True…I would vote for that just for quick fixes but all my stuff has been mapped…a long time ago when I used mainly legacy remote

Ive tried so many things…I cant vouch for Avid Control enough…it will blow you away, direct integration into Cubase (Eucon) no hardware required, runs on iPad OR android tablets etc

createartrecords · February 24, 2026, 10:43pm

Final conclusion on this thread:

Now I finally understand why there is hardly any hardware produced with a high number of controls: because this idiotic software is still not capable of handling it, even 20 years later.

The Remote Control Editor (RCE) is nothing but a lazy leftover. It seems it only exists because they were too lazy to build a proper GUI for a long time. Now that we finally have a modern GUI, you can basically throw the RCE in the trash. It is a false glimmer of hope—it serves no purpose if it doesn’t allow us to assign more than eight knobs simultaneously.

To stay stuck at this rigid limit of 8 assignments while my Pro 88 offers 27 is absolute kindergarten. It’s not a professional program; it feels like Lego for kids who have too much free time, no musical training, and think they are “Sound Engineers” after a six-month certificate.

Even the suggestion to switch to Avid Control is an insult. Am I supposed to smear my fingers all over a tablet screen—blocking my view of the monitor—just because Cubase can’t handle a professional MIDI controller? It’s pathetic that we are forced to look for third-party “translators” because the native system is a total failure.

Furthermore, even if I were to accept the limitation of only eight knobs, the way they are organized is completely illogical and unpredictable. There is no consistency in how parameters are mapped across different plugins, which makes it impossible to develop any kind of muscle memory. Instead of a professional, streamlined workflow, I’m forced to constantly stare at the screen to figure out which knob does what. This total lack of a predictable structure is the final nail in the coffin for any professional use."

Thx for Tips

mlib · February 25, 2026, 12:05am

You are greatly misunderstanding something here. When using MIDI Remote (introduced in Cubase 12) there is no 8 parameter limitation. The only job of the Remote Control Editor is to define the order of the VST parameters of individual plugins that you then use MIDI Remote to connect to.

createartrecords · February 25, 2026, 8:45am

"I always appreciate constructive feedback and I’m grateful for any help I can get here, but I think there’s a misunderstanding of my specific problem.

I am well aware that the MIDI Remote in Cubase 12 isn’t strictly limited to 8 parameters. However, my issue is about workflow and stability while I’m actually making music. When I have a guitar in my hands, I need a rock-solid, fixed layout where the most important parameters are always in the same place without me having to manually re-assign or ‘focus’ them every time.

If you have a concrete, constructive solution on how to organize these mappings more efficiently so they stay consistent across different tracks and plugins, I would love to hear it. But pointing out technical specs without addressing the workflow hurdle doesn’t really help the situation."

createartrecords · February 25, 2026, 9:08am

Correction: "I have to correct my previous statement. I’ve realized that the Remote Control Editor is, in fact, the crucial place to fix the often absurd default parameter assignments of VST plugins.

While the new MIDI Remote GUI is a great addition, the RCE remains the only way to reconfigure and reorganize the parameters in a way that actually makes sense for a reasenable workflow. It’s not about the number of knobs, but about which parameter sits on which knob by default. I’m using it now to clean up the mess of the standard assignments so I can finally work intuitively again."

"Some of you reading this thread might wonder why I’m so obsessed with these details. The reason is simple: For me, the computer isn’t just a recording device—it needs to be a seamless extension of my musical expression.

When I’m in the zone, playing guitar or performing with a synth, any technical hurdle is a wall between me and the music. If I have to stop and think about which knob does what, or if I need two hands for a task that should be one-handed, the creative spark is gone. I’m looking for that ‘blind’ intuition you have with a physical instrument. That’s why getting the RCE and the mapping right is so vital to me."

Do you know the Feeling when you turn 2 Knobs at a time?

Northunder · February 25, 2026, 9:21am

I can confirm, and at the same time ask anyone: when you start (any DAW) in order to create music, what percentage of time - in average - do you spend doing tech stuff, and how much actually creating music?

createartrecords · February 25, 2026, 9:29am

If no one say nothing, it will never change something. I am in the hope for solutions or demanding from the developers;)

"To give you some context on why this workflow is so critical for me: It’s about a multi-stage process of recording and mixing. During the real-time recording phase, I need to keep Cubase’s latency as low as possible—between 32 and 96 samples.

On my current system, I can play at least 26 of my instruments simultaneously at 32 samples. At this stage, I cannot afford to load heavy third-party plugins that destroy this latency (for example, when I’m performing VSL String Spiccatos). This is why I rely on the internal Channel Strip compressors and EQs during the tracking phase. They are efficient and ‘latency-free’ within the engine.

As the project progresses, I gradually introduce specialized Inserts to complement or replace the Strip processing. This way, the ‘Constrain Delay Compensation’ feature actually makes sense because the mix doesn’t fall apart when I need to overdub another instrument. There is nothing worse than having to stop the creative flow, performe a Mixdoen from the Song, open a new project, or mess with buffer settings just to record one more track. Thats bullsh..t

I monitor my analog instruments directly through an analog desk. Some might say I’m oversensitive to latency, but playing VSL Spiccatos at 32 samples with a roundtrip of about 3ms is a completely different world of responsiveness. If you haven’t experienced that level of ‘real-time’ feel, you’re missing out on what’s actually possible today."

createartrecords · February 25, 2026, 10:27am

Letzte Meldung

"To bring it to a point and clear up the confusion: The suggestion that ‘Pages’ in the MIDI Remote solve the problem is a total fallacy in a real-time performance context.

Think about it: If I followed that logic, I would have to flip a page on my hardware/GUI and then somehow flip a corresponding page in the plugin’s internal mapping just to reach parameter number 9. It’s like having to switch your car’s steering wheel to ‘Page 2’ just to be able to use the indicators. ‘Hallo?!’ – that’s not making music, that’s administrative data entry.

When I have a guitar in my hands or I’m performing a synth line, I need immediate, intuitive access.

The ‘8-slot limitation’ is a bottleneck. My solution using the Remote Control Editor (RCE) is the only way to bypass this ‘paging’ madness. I use the RCE to force the 8 most important parameters into the first bank of the plugin itself. This ensures that the moment I touch the track, the right controls are already there—no flipping, no searching, and no double-paging."