Routing Bug in Cubase 13 still exists in 14

The inspector and the mix console each show different router settings for the same track.

Hi,
I cannot reproduce this issue. Or is this already a known and reported issue?

If not, can you please explain how this happened, even better, provide a step by step procedure?
Which Cubase version (Pro, Artist, etc) are you on, which OS etc?

It’s been reported to Steinberg. From what I heard the current behaviour is by design.
So this is not so much a bug fix but a request to change the design. I am working on trying to convince Steinberg to change it and it would be awesome to see some more support for the request.

Thanks for the response!
I reported it when I first noticed it in Cubase 13 Pro, probably about a year ago. I am now running Cubase 14 Pro (14.0.05) on Windows 11 Pro 23h2 and the problem still exists.

How to I created it:
I opened Superior Drummer 3 and created separate outputs for each drum category (Kick, snare, toms, etc.) and routed each of those drums to the separate outputs in SD3. I then selected all of the output tracks that SD3 created in Cubase and after right-clicking on a track I chose- ā€œGroup Track to selected tracksā€ The result was that all of the individual outputs now are routed to this drum bus group. I then selected my hi hat and cymbals tracks and used the same procedure to create a new (metals) group track. Now, I click on each Cubase output track one at at time and in the inspector window it shows that each output is routed to the drum bus, which is incorrect.
However as I showed in my previous image, the routing in the mix console is correct showing the two tracks I changed to the metals group as being routed to the metals group. (I did just now recreate this in an empty project.)

Let me know if you need any more info.
Hope this helps!
-mike

Thanks. There is no need for more info, the matter is perfectly clear. The output routing display in the Inspector always shows the output routing of the main out. It does not change to display the output routing of the selected audio return channel.

Displaying the wrong group bus routing in the track inspector is by design ? lol. I’m confused as to why it gets stuck on the incorrect ā€œDrum Bus Groupā€, but of course it should update to the ā€œMetals Bus Groupā€ if that’s what you routed the tracks to. How could this current behaviour be beneficial in any way ? I don’t understand.

1 Like

I let an old wise man take over…

Obi-Wan has taught you well, young Skywalker…

Thanks Mike for explaining - that is indeed very confusing! No idea how this could possibly be of any benefit as a default. It’s just wrong - but what do I know…
May the force be with us :fist:

By design? Then how come I can change the routing in the inspector at all? You can choose the routing there but it just changes back to the previous routing for what seems like no reason.
Seeing conflicting routings for the same track is, at the very least, confusing.

2 Likes

Yeah this needs to be addressed and fixed by Steinberg.

Where was this stated?!

I used direct communication with Steinberg and was lucky enough to receive a reply.

Any word on the status of this issue? I stumbled upon this when trying to figure out multitimbral routing for BFD. It’s a confusing subject to start with, only made more so by this behavior. Is there anyway to know if Steinberg is addressing this. I see it was mentioned that they know about it. I find the navigation of this forum and communicating/tracking issues equally confusing. Maybe somebody could explain that to me. I’m not being flippant. I would really like to understand that better so I could participate in bringing issues to light in a respectful way.

It looks like the ā€œby designā€ means the Inspector Panel shows the ā€œmother VSTiā€ main output bus. Not the child routing.
tbh if this is the only issue, not a big deal, once aware of it just pay attention to the mixer routing.
Of course if can be solved in the much awaited .30 update then all the better, but there are other pressing issues I’d rather see dealt with before, eg remote script, zoom, performance, etc..
Side note and feature request :
In this example I’d like Cubase to make the ā€œmetalsā€ bus routed to the Drum bus.
In other words : if tracks are routed to a sub, make ā€œGroup Track to selected Tracksā€ bus output to that sub. So that drums can remain in the drum bus. Hope it makes sense.

Here is a other thread about the same issue. (I think)

It has short video that shows the bug.

I’m seeing something odd here too. When setting up Quick Controls in the Inspector for an output channel coming from VEP, under ā€˜Inserts’, it is showing 3 plugins that are on the ā€˜Mother’ VSTi channel. But in the MixConsole the exact same channel is showing the plugins that actually are on that channel. C14

Thanks for pointing out the additional implication of the current design.

It is the same issue in a different dress.
The Inspector allows access to the main channel only. Even if you select a different child track the Inspector will refer to the main track and main audio return channel.

1 Like