You can see that the track order in the output routing in this screenshot does not reflect the order of the tracks on the arrangement. It seems the ordering is by track creation, not alphabetical and not reflective of repositioned tracks on the arrangement.
If I understand correctly what happens if you reorder tracks is that the key command for next/previous track works fine, but not when selecting multiple tracks by using the shift+next/previous track⌠meaning if youâve âbrokenâ the order somehow there wonât be a âlogicalâ renumbering of tracks based on what we see on screen. Iâm not saying btw that the problem is the numbering of the tracks necessarily, it could simply be that some things shouldnât rely on it and instead rely on the actual order visually.
There are other cases where I think not being able to reorder is a pain (or a new order isnât reflected where âdesiredâ). Itâs just a bit clunky is all.
In the lists it was always in the order of creation⌠this represents a hierarchical order, important in the case of auto creation of sends.
But the order in the project view could be totally different.
I canât see a problem here.
If you have a template with an already implemented order and the order would change to alphabetical, it would be disappointing for all relying on the prebuilt order.
And I have ordered my groups with the use cases in mind.
Youâre right, re-opening the project re-orders the tracks in the list to reflect the order as displayed in the arrangement. This just affirms my stance that this is a bug, since Cubase intends to list the items in the same order as the arrangement, but lists donât reorder when an arrangement track reorder event is triggered.
You can see in this updated screenshot that after closing and re-opening Cubase, the output list of the channel updated to reflect the order of the tracks in the arrangement, specifically the âSubbassâ group is no longer listed at the bottom but is now correctly listed before âBassesâ