I came back to a project to export and, while all the melodic parts were routed to a ‘melodic’ group channel that plays to the master, I noticed that the various drums were routed directly to the master, though I had there a drum group channel.
I put the drums into a new foldr, group channel, track and then changed each routing to the drum group channel, and that is set to the master. I hear nothing. the drum group channel doesn’t light when they play. Nothing involved is muted. What’s wrong?
A screencap of the drum group might help as tracks look to be working fine, so something in the group is presumably where things are falling down.
Just to confirm, if you route these tracks to stereo out you hear them OK, how about if you route to any other group you know is working?
Best guess would be if you had the solo on before making the change and didn’t turn it off and back on after making the change. I have seen that some changes like this don’t force solo state changes to update. I end up having to turn solo off, then solo what I want to be soloed (in this case probably the either the group folder track or the drums group track would work equally well).
Also, in your screenshot, while I see meter activity in the individual drum tracks, I don’t see any on the folder/group’s meter, and I’m thinking there should be activity there (I’m not in Cubase at the moment to be able to confirm that).
I’ve always thought that was a strange bug to leave unfixed. It can lead to disastrous results. I can appreciate how it might be difficult to get the soloing correct when changing the routing, but if it’s not possible to fix this bug, Cubase should put up an error message saying routing can’t be changed while in solo mode.
I tend to agree. However, I can at least conceive that there might be a semantics question on whether you want what was soloed before routing changes to still be soloed afterward. Also, with respect to feasibility and warning, I can also imagine the two parts of the underlying code might be ignorant of each other, with what is soloed only being determined at the point of pushing (or disengaging) a solo button, but not tracking changes made in between solo button states.
Independent of logic, though, it can at least be frustrating, and my experiences with this bug or limitation are typically in the same context as the OP, where I’m working with something and notice some routing mistakes (most commonly something going to the Stereo Output that should go elsewhere as, in the early stages of my projects, prior to starting mixing, I almost always just use the default routing when adding new tracks, but sometimes I forget to adjust some tracks later in the game, or maybe I add a submix bus but forget to set its output to another submix bus).
