Folder/group track bug or feature?

When you convert a folder track to a folder/group track ALL tracks in the folder are routed to the folder/group. While that sounds ok on the paper, it also means that even if a channel is already routed to a group channel (in the folder) it is rerouted to the top folder/group which in turn means you have to reroute the channels back to the group after the fact.

I really do wish there was an option to retain the routing structure within the folder when converted.

It’s not a huge problem since I see converting folders to folder/groups is mainly something I’ll be doing while converting projects created prior to the new folder/group feature - but it sure would be nice to have the option.

Personally I think that reatining the structure should be the default.

I think the whole point is that they route to the new folder/channel. I wouldn’t say it was a bug.

It makes more sense to me if the opposite is true. After all, what’s the point in dropping a bunch of tracks into a group-folder if they’re not routed to that group?

I think the default should be to change routing, but I agree that maybe it should be optional.

I haven’t updated yet, but if I’m understanding the OP…

I agree with the OP.

I usually have 2-4 levels of sub-folders and sub-groups.

Ie, my vocal folder has group tracks for Vocal Lead, Vocal Lead FX, Vocal Harmony, Vocal Double, Vocal BG FX, Vocal FX All Sum, Vocal All Sum.

With this new feature, it’s likely that my ‘Vocal ALL Sum’, would become the Group-Folder.

But I’d want to retain the current sub-group routing.

It shouldn’t be that difficult for Cubase to be able to read routing topology from start to finish across multiple levels to get a picture of what is already routed within a folder.

Ie, it should only take routing of the tracks that are routed to a destination that is outside the folder - like Main Mix.

This could be a simple prompt option… and there could probably be a few different options.

Well certainly I can see the reasoning in only re-routing the first level by default and leaving the rest alone.

The idea is to make the lower levels their own folder groups. Then the problem vanishes immediately. It doesn’t raise the track count as you are exchanging a Group Track for a Folder with Group Track.

Absolutely!

I think this issue will repeatedly arise until an option is offered. I get why it is the way it is. But I’m the minority type of user who does not have a workflow that assumes the “standard” Group Track feature.