The Client’s Challenge
It’s a scenario familiar to many composers: you invest in a premium software instrument like EastWest’s Opus and a beautiful boutique MIDI controller—in this case, a ‘Choi Sauce 100’ with wonderfully tactile faders—expecting a seamless creative experience within your trusted DAW, Cubase. Yet, you hit a wall. A simple, fundamental task—controlling the ‘Expression’ of a string patch with a physical fader—refuses to work.
The client was understandably frustrated. He had followed the logical steps, attempting to use Cubase’s powerful Mapping Assistant to link his controller to the plugin. Everything appeared correct on screen, but the fader remained stubbornly disconnected from the sound. This isn’t just an inconvenience; for an orchestral composer, direct, physical control over expression (MIDI CC#11) is as vital as a painter’s brushstroke. The client was left with a high-end setup that felt broken at its very core, unable to perform its most essential function.
The Investigation: A Three-Way Conflict
This wasn’t a case of user error or a faulty device. It was a fascinating and deeply technical ‘Edge Case’—an architectural conflict between the design philosophies of three different manufacturers. My investigation revealed that Cubase, EastWest, and the controller itself were all operating correctly according to their own internal logic, but their logics were fundamentally at odds.
Clue #1: Cubase’s ‘Modern’ MIDI Handling
Steinberg has evolved Cubase to favour a managed approach to MIDI control. Systems like ‘Quick Controls’ and the ‘Mapping Assistant’ are designed to act as a universal translation layer. Think of it as a central switchboard operator. You tell the operator, “Connect my fader to the volume on track one,” and they make the connection. This is brilliant for flexibility, as you can easily tell the operator to redirect that same fader to a filter cutoff on another track later. However, this operator can only connect you to pre-approved ‘automatable parameters’ that a plugin explicitly publishes to Cubase.
Clue #2: EastWest Opus’s ‘Classic’ MIDI Implementation
EastWest Opus, like many high-end orchestral libraries, is built on a legacy of direct MIDI control. Core performance parameters like Expression are hard-wired to listen for a specific, non-negotiable MIDI message: Control Change number 11 (CC#11). To use our analogy, Opus’s Expression control is like an old, direct-dial phone line. It doesn’t go through the switchboard; it only answers when you dial its exact number (CC#11).
The Root Cause
The problem became clear. The client was asking Cubase’s ‘switchboard operator’ (Mapping Assistant) to connect his fader to Opus’s Expression. But because Opus doesn’t publish Expression as a standard automatable parameter, the operator had no ‘extension’ to connect to. It was a communications breakdown: Cubase was trying to make a managed connection, while Opus was waiting for a direct-dial call that was being blocked by the switchboard.
The Solution: A Direct Line
The solution was not to fix a broken component, but to bypass the conflict entirely. We needed to program the MIDI controller to place a ‘direct dial’ call to Opus, instructing it to ignore Cubase’s central switchboard for this one specific task. While this sacrifices some of the dynamic re-assignment flexibility of Quick Controls, it restores the essential hands-on connection the client needed. Here is the workaround we implemented:
-
1
Access the Controller’s Editor
We opened the dedicated hardware editor software for the client’s MIDI controller. Most professional controllers have an application that allows you to change the underlying MIDI messages sent by each knob and fader.
-
2
Assign the Fader to CC#11
We selected the physical fader the client wished to use for expression. In the editor, we changed its message type from its default setting to ‘Control Change’ and set the CC Number specifically to ’11’.
-
3
Save as a Hardware Preset
Crucially, we saved this new configuration as a preset directly onto the controller’s hardware memory, naming it something memorable like ‘Opus Strings’. This means the controller itself, not Cubase, is now responsible for sending the correct command.
-
4
Activate the Preset for Opus Tracks
The workflow is now simple: when working on a track with EastWest Opus, the client activates the ‘Opus Strings’ preset on his controller. The fader now sends CC#11 directly, and the plugin responds perfectly. For other tracks, he can switch back to a standard preset to use Cubase’s Quick Controls as intended.
Additional Reflections: A Clash of Philosophies
This case is a perfect example of how even the most mature, professional software can fail to integrate smoothly. Neither Steinberg nor EastWest is ‘wrong’ here. Steinberg is pushing forward with a flexible, abstracted control system designed for the modern studio where a single controller might need to perform dozens of different tasks. EastWest, on the other hand, adheres to the long-established, musically intuitive standards that composers have relied upon for decades.
The problem arises in the gap between these two philosophies. It creates a frustrating experience where the user is caught in the middle. While the workaround we implemented is perfectly functional, it does break the ‘all-in-one’ control promise that modern DAWs aspire to. It’s a compromise, but a necessary one to restore artistic control. It highlights that in the world of professional audio, understanding the deep-seated design intent of your tools is often the only way to resolve these hidden architectural conflicts.
If you are seeking professional help with a Cubase MIDI controller fix, VST integration conflicts, or other complex MIDI routing issues, one-on-one remote support services are available from Audio Support.
Not sure it’s the same problem? Ask a question first
