No, you are clear. I cannot support the feature request though. I like how it is now. Why?
If you want to have a “Master Visibility Configuration”, you can set it up in the project window, with Track & Channel Sync on, and then use a macro: 1. Project: Bring to front 2. Visibility Configuration 1-8. This way, you ensure that you are recalling visibility configuration 1 through 8 without paying attention to focus. Edit: Without key commands, I would probably “double save” the configurations. Save one config in project window, change over to mixconsole (that is synced to the project), save there as well. Go to project, make changes, save number 2, go to mixconsole, save it there, etc etc)
The way it is set up now is: You can make 8 (or more) different configurations for the project window, 8 (or more) different configurations for the mixconsole, and then with Track & Channel Sync on, and careful focus management, have 16 different configurations at your fingertips using just 8 key commands.
That’s just the way I see it, of course. I’ll repost something I’ve written at the key command thread here as my rationale:
“If working with Sync Project & MixConsole on, I find it better to make configurations “native” to the target window. For example, in the project window I wouldn’t waste a configuration that would show me just channels 1, 4, 6, 9 and Group 1, their destination. That’s because I could easily select Group 1 in the Mixconsole, then issue the command Show Channels connected to the First Selected Channel, and have the Project window mirror the visibility change since I have Sync Project & MixConsole active. Likewise, it would feel clumsy to me to make a visibility configuration in the MixConsonole for Tracks with Data between the Locators, since I would have far better visual feedback from the project window, and the MixConsole would mirror that visibility change regardless, since, again, I have Sync Project & Mixconsole active.”