Dear @Matthias_Quellmann and Cubase Team,
I’d like to share an idea I’ve been thinking about recently. First of all, I should clarify that I’m neither a software developer nor an engineer, just a musician who loves Cubase and enjoys imagining what might be possible with the tools we already have.
It’s entirely possible that something like this has already been suggested, that there’s an existing solution I’m unaware of, or that I’m seriously underestimating the technical difficulties involved. So please take this as a musician’s suggestion rather than a technical proposal!
That said, there’s something about Cubase’s existing Modulators rack that makes me particularly optimistic about an idea I’d love to see explored.
What if Steinberg expanded the existing Modulators rack into an optional, universal FX rack and project-wide modulation matrix?
Let me explain what I have in mind.
1. Building on the Existing Modulators Rack
One thing I particularly like about Cubase’s Modulators is the interface itself. It’s intuitive, relatively straightforward, and already provides some incredibly interesting creative possibilities.
We have LFOs, envelope followers, step modulators, macro controls, and the ability to assign modulation to various plugin parameters.
What if we took that existing concept a little further?
Imagine being able to use the same familiar interface to load not only modulators, but also native Steinberg effects and third-party VST3 plugins, with the possibility of connecting them in different ways.
I’m imagining something loosely comparable to the flexibility offered by tools like Unify, or the modular environments found in other DAWs, but integrated directly into Cubase and using its existing interface philosophy.
I don’t know how feasible that would be, but I find the idea quite exciting!
2. What About Modulating Parameters Across the Entire Project?
This is probably the part that interests me the most.
At the moment, Cubase’s native modulators are generally limited to parameters belonging to the same track.
But what if we could remove that restriction?
Imagine creating a single macro knob that simultaneously controls:
-
The filter cutoff of Serum 2 on one track.
-
The distortion amount of a guitar plugin on another.
-
The threshold of a compressor on a drum bus.
-
The decay time of a reverb on an FX channel.
-
The feedback of a delay somewhere else in the project.
All at once, ideally with independent ranges, modulation amounts, and automation.
Now imagine being able to do the same with Cubase’s existing LFOs, envelope followers, and other modulators.
You could create relationships between completely different instruments, effects, and tracks without having to work around their individual routing structures.
For someone who enjoys experimenting with sound design, automation, and evolving arrangements, the possibilities seem almost endless.
And perhaps the most interesting thing is that the modulation system wouldn’t necessarily have to process any audio itself. It could simply act as a central control environment for the entire project.
3. Adding Native and Third-Party Effects to the Rack
Now imagine extending that same idea to audio processing.
What if we could load Steinberg’s native effects and third-party VST3 plugins directly into this expanded rack, with flexible serial and parallel routing?
For example, we could split a signal into different frequency bands, separate Mid and Side information, or create multiple processing paths with independent dry/wet controls.
Each path could have its own effects and modulation assignments.
You could then use macros to control several parameters simultaneously, morph between processing configurations, or create evolving textures that would otherwise require a fairly complicated combination of tracks, sends, automation lanes, and plugins.
And because the modulation system could communicate with the rest of the project, the rack wouldn’t necessarily be confined to controlling only the plugins loaded inside it.
I realise that this is probably much easier to describe than to implement, particularly when audio routing, plugin compatibility, and latency compensation come into play.
But from a creative perspective, I think it would be a wonderful addition.
4. Could This Also Open the Door to Modular Synthesis?
Here’s another thought that occurred to me.
Cubase already includes TestGenerator, which can generate basic waveforms.
What if Steinberg introduced a more flexible oscillator module that could be loaded into this hypothetical rack, just like an audio effect?
Combining oscillators, filters, envelopes, modulators, and other effects could potentially allow users to construct their own synthesizer-like systems.
Of course, I understand that a proper playable modular synthesizer would require much more than simply adding an oscillator. MIDI pitch tracking, envelopes, polyphony, and other technical considerations would have to be addressed.
Still, wouldn’t it be interesting if the same environment could eventually function as a modular synthesizer, complementing instruments such as Retrologue and Padshop?
Perhaps that’s taking the original suggestion a little too far, but it’s an exciting possibility to imagine!
5. Keeping Everything Optional and Independent
One thing I would particularly like to emphasise is that I’m not suggesting replacing Cubase’s traditional inserts, sends, or mixing architecture.
Quite the opposite.
I love the conventional Cubase workflow, and I think any modular environment should complement it rather than interfere with it.
Ideally, I imagine three possible ways of using such a rack:
1. Parallel Mode
The modular rack processes an independent signal path alongside the conventional effects chain, allowing the two to be blended or used separately.
2. Serial Mode
The rack becomes part of the normal signal path, allowing its processing to interact with conventional effects wherever the routing permits.
3. Control-Only Mode
The rack doesn’t process audio at all. Instead, it acts as a project-wide modulation and macro-control environment, communicating with compatible parameters across different tracks and plugins.
I think this last option could be particularly useful, even for people who have no interest in modular synthesis or elaborate effects routing.
And importantly, anyone who prefers Cubase’s existing workflow could simply continue using it exactly as before.
Here is an mockup example bellow:
“NOTE: MOCKUP GENERATED BY AI, based on the concurrent UI desgin of the modulator rack in Cubase 15 Pro”
6. Why I Think This Could Be Worth Exploring
I know that some other DAWs already offer more flexible modular environments, and I’m certainly not claiming this is a completely original idea.
In fact, I wouldn’t be surprised if other Cubase users had already suggested something similar!
What makes me interested in this particular approach is the possibility of building upon something Steinberg has already introduced: the Modulators rack.
To me, its interface seems like a very natural starting point for a broader modulation and processing environment.
Of course, having an existing interface doesn’t mean the underlying functionality would be straightforward to develop. I’m sure there are architectural limitations and engineering challenges that I don’t fully appreciate.
But I can’t help thinking about how useful it could be to combine Cubase’s established strengths in recording, MIDI editing, arranging, and mixing with a more open-ended modular system.
Rather than choosing between a traditional DAW workflow and a modular one, we could potentially have both available within the same project, independently or interconnected, according to our needs.
And that’s really the heart of my suggestion.
I’m not proposing that Cubase should become something entirely different. I’m simply wondering whether its existing tools could eventually be connected in ways that offer us even more creative freedom.
Perhaps parts of this are already possible and I’ve simply missed them. Perhaps some elements would be impractical, or would require an unreasonable amount of development work.
I’d genuinely appreciate being corrected or pointed towards existing solutions if that’s the case.
But if there is potential in this idea, I’d love to know what Matthias, the Cubase team, and other users think about it.
Would something like this make sense as a future evolution of the Modulators rack? Or would the architecture required be too different from what Cubase currently offers?
Either way, thank you for taking the time to read my rather ambitious thought experiment, and thank you for continuing to develop a DAW that gives musicians so many possibilities to experiment and create.
Best regards,
João Carvalho
