Oh, if you don’t need any midi channels in the MixConsole at all the easiest solution would be to hide them.
That would only leave the little item of having to give the midi track and the associated audio channel the same name.
Yes, as I am testing Cubase for the past 2 months, have created workarounds. mainly using instrument tracks for each instrument with its own kontakt instance.
I dont really see any advantage of doing it with midi or rack instruments.
Rendering the multitrack is easier with this.
timeline and console is clean with only relevant tracks.
When selecting the track in arrange the corresponding console track is selected.
This does add the inconvenience of needing to duplicate or adding new instance for every new track. (which you have to browse to the same family to add the next one.
Yes, as I am testing Cubase for the past 2 months, have created workarounds. mainly using instrument tracks for each instrument with its own kontakt instance.
Yes, in 2025, separate instrument tracks is usually a better way to do it anyway. The number of cores in the average CPU is much larger today than when this thread was started, and that favors using separate instances due to better performance.
While there is a use case where one would want to use a multitimbral instrument multitimbrally with a separate midi input channel and a separate audio output channel for each one, that’s a pretty narrow use case these days.
Well, I am an orchestral producer. using multitimbral stuff is pretty common.
Used to use studio one because of this feature, but that daw is lacking too many features.
Reaper has too many GUI performance issues.
Ableton has performance issues
Logic is only for mac
Pro tools is pro tools.
Oh well, one instrument per track is the only way forward I guess.
I understand. I’m just saying for many orchestral projects, there are advantages to using separate instrument tracks anyway. Just because a VI is multitimbral, that doesn’t mean using it multimbrally is always the best way to use it.
That would probably be personal preference i would say.
REAPER being very good at cpu actually gives you slightly better cpu usage. Idk how cubase handles that.