I have a new MIDI controller keyboard and I’d like to set it up within Cubase to control external hardware synth. I assume Mapping Assistant is for this, but I’m not sure how to use it other than for setting up to control Cubase itself. Is there guidance on this somewhere?
Can you remind us again of which edition of Cubase you use (Elements, Artist, Pro)?
Elements 15. I suspect that Cubase can’t map an external controller to external hardware so I’ll have to find a way to make the controller itself do it.
Unfortunately Cubase is not really made for transforming incoming midi data into some other outgoing midi data on a bigger scale And Cubase Elements has no such tool at all.
See if you can get your midi controller to send exactly the midi data that the external hardware synth requires.
Alternatively you can use virtual midi ports (Win11 and macOS have this built-in, for Win10 I recommend “loopMIDI”) and then an extra software that does the mapping, like MIDI-Ox on Windows.
The midi controller would send the data to the mapping software. From there the altered data would go through the virtual midi port into Cubase.
I consider it a long standing weakness of Cubase that it does not allow for large scale midi mapping.
Thanks for that. It’s as I thought.
Hey @Airlane1979,
yes, sadly it can’t, and @Johnny_Moneto’s advice is also correct.
I just took a minute and asked Microsoft Copilot, then receiving a response that contains two perhaps practical ways for you to work around the DAW’s limitation:
- Blue Cat's Remote Control - virtual MIDI Control Surface (VST, AU, VST3, AAX)
- Bome MIDI Translator Pro – Bome Software
Both are not gratis, but do in fact look useful, regarding your configuration tasks.
I’ll copy my Copilot inquiry to this “hidden” commentary section, so you can read it:
Summary
20260620
— Quote AI inquiry —
[User Question]
Cubase can’t map an external controller to external hardware. Is there a MIDI mapping VST plugin that could do this?
[Microsoft Copilot]
Short answer: Yes — you can use a MIDI‑mapping VST plugin to translate controller CCs to external hardware, even though Cubase itself cannot directly map external controllers to external MIDI devices. The most reliable solution is a MIDI‑processing VST that can remap CCs, generate SysEx, or route MIDI out to hardware.
Below are the best options, how they work, and what to consider.
The VST plugins that can map MIDI to external hardware
- Blue Cat Remote Control
What it does:
A fully automatable VST that exposes virtual knobs/faders. You map your hardware controller to the plugin, then the plugin outputs MIDI CC to any destination (including external hardware via a MIDI track).
Why it works for your case:
Converts Cubase automation or controller input into arbitrary MIDI CC
Can send MIDI out to external gear
Works as a VST inside Cubase
Very stable and widely used
Limitations:
No SysEx
Requires setting up a MIDI loopback (e.g., LoopMIDI) to send to hardware
- Bome MIDI Translator Pro (not a VST, but integrates perfectly)
What it does:
A standalone MIDI processor that can:
Convert any MIDI message to any other
Send SysEx
Create complex rules, conditions, macros
Route to external hardware
Why it’s often the best solution:
Cubase’s MIDI Remote cannot send SysEx or arbitrary CC to external hardware — Bome can do all of that.
Limitations:
Not a VST (runs alongside Cubase)
More complex to configure
- Piz MIDI Plugins (free, if you can find them)
What they do:
A set of MIDI‑processing VSTs:
CC converters
Channel filters
Note/CC generators
MIDI routing tools
Why they help:
You can insert a Piz plugin on a MIDI track and remap CCs before sending them to your external hardware.
Limitations:
Development stopped years ago
Hard to find 64‑bit builds
No SysEx
- MIDIShaper by Cableguys
What it does:
Generates LFOs, envelopes, and CCs as a VST.
Why it helps:
If your goal is to automate external hardware parameters, MIDIShaper can output CCs to hardware.
Limitations:
Not a general-purpose mapper
No SysEx
How to set this up in Cubase (works with any of the above)
Create a MIDI Track
Insert the MIDI‑processing VST in the MIDI Inserts
Set the track’s MIDI Output to your external hardware
Map your controller → plugin → hardware
This bypasses Cubase’s limitation that MIDI Remote can only target Cubase functions and VST parameters, not external MIDI devices.
Why Cubase can’t do this natively
Cubase’s MIDI Remote system (introduced in Cubase 12) is designed to control:
Cubase functions
VST parameters
…but not external MIDI hardware.
This is confirmed by Steinberg’s documentation and user reports: MIDI Remote cannot output arbitrary CC/SysEx to external devices.
Recommendation
If you need simple CC remapping, use Blue Cat Remote Control.
If you need complex mapping or SysEx, use Bome MIDI Translator Pro.
— Quote AI inquiry —
Best wishes,
Markus