There is a major conflict between child tracks and how they're displayed in the routing matrix.
The Routing Matrix is supposed to give the user an overview of all the track routing in a project.
Unfortunately, the track folder feature has thrown this out the window. There's no way to know which tracks are children and which are parents in the Routing Matrix. So, if you're using folders, the Routing Matrix is nearly useless. "Master/Parent" is NOT a route. It's a maze. If it's selected, then you need to look elsewhere (TCP) to get useful routing information.
Since track folders are actually just busses with indentation, it's my opinion that they should be treated as such in the Routing Matrix. In addition, child tracks' Routing dialog should be updated with a field showing what the parent track is.
Last edited by MonkeyBars; 03-02-2016 at 08:29 PM.