I am lost with Cubase. LOL. If the SamplerTrack, which uses a piano roll, is not a midi track, then I don’t know. So how can I load a sampler to the midi track? Is it possible?
As I wrote elsewhere: Cubase is very track specific. A sampler track has midi data on the track but is fixed to send that into the sampler unit of that track. There is no other destination.
In order to be able to route MIDI signals flexibly please use MIDI Tracks.
Also an Instrument Track is not a midi track. It too holds midi data on the timeline but always sends it to the loaded instrument plugin.
A Drum Track is similiar. Midi data on the timeline but a fixed destination (in this case Drum Machine).
Thanks. So midi track can’t be a sampler, hence no midi routing.
Also, Copilot just told me, that:
“Cubase 14 does not support host-level MIDI side-chain routing into third-party plugins. If your Kick is a Sampler Track (Instrument Track) and your Bass is also an Instrument Track, you can still duck the Bass—but only via audio side-chain, not MIDI.”
And this (that’s what you said):
“No. In Cubase, a MIDI track can only receive from physical or virtual MIDI ports—not from Instrument or Sampler Tracks. Sampler Tracks host an internal pattern or audio-sample playback engine, but they do not expose their playback MIDI as a routable output.”
This explains all the restriction that the Cubase have with the routing. To be honest, I really hope that Steinberg will address many of these things in V6.
Thank you for you time Johnny! Very appreciate.
This is typical AI crap. Of course, Cubase supports host side midi side-chaining, also for 3rd party plugins. The 3rd party plugins need to support it, too, though.
Please stop using AI to do your research for you. They are all full of sh*t. We see these really poor AI stuff over and over again and personally I am getting tired of trying to clean up the mess that this stuff causes.
If half of the internet users want to hand over their brain to some companies - go ahead. And have fun with not figuring Cubase out.
2 Likes
If Cubase supports routing only with the “midi” tracks, then I would say it is non-existent. If I have to create “shadow” tracks and various workaround, then it is basically “non-existent”.
I have a SampleTrack which uses midi. I want to route that that. And cubase cant do this, then it is Cubase flaw.
Yeah, I know that those “AI” bots can lie a lot (like 80% of information is BS). Usually do at least 3 various attempts to get a better output from the bot.
P.S. Anyway, I tried using a “shadow” midi track. Yes, it worked with the CablGuys VolumeShaper midi input sidechaining. Yepp, not the most elegant way.
In this case Cubase is not the right DAW for you. You should not continue to use it and move back or on to another DAW.
Ok. So I tried that ModScript code mentioned in the first posts using a midi track as a source for the sidechain. It does its job, by it is very clicky. And those clicks are very unstable. I tried the CableGuys Volume Shaper midi sidechaing and it was smooth as butter.
Even here Cubase didn’t perform well, comparing to other DAWs. Cubase needs to catch up, seriously.