Exclude Tracks/Buses/Folders from View (Second Level Hiding)

[murat k.]

Currently, Cakewalk only offers a single-level track hiding option, which is not always sufficient. A second-level hiding feature would allow certain tracks to remain hidden even when using the "Unhide All Tracks" command. When needed, we can reveal these tracks all at once with the "Un-exclude All Tracks" command or manage visibility more selectively through the "Track Manager."

Use Case 1:
Imagine working on a project with 100 tracks, but focusing on only 10. We’ve hidden the other 90 tracks. Then, we narrow our focus to just 3 tracks and use the "Hide Tracks Not in Selection" command to hide the rest. However, if we apply "Unhide All Tracks," all 100 tracks become visible again. By using the "Exclude Selected Tracks" command to exclude the 90 tracks, the "Unhide All Tracks" command will display only the 10 tracks we’re interested in.

Use Case 2:
For instance, we can exclude the Metronome Bus from view. Even when we apply the "Unhide All Tracks" command, this bus will remain hidden. To make it visible again, we can untick it in the "Exclude" column in the Track Manager. Additionally, the "Hide Track" command should be expanded to include buses, similar to the request mentioned for the "Delete Tracks" command in this thread.

Note: "Undo view" command is not a solution, and this thread is closed to any workarounds or differing opinions.

[msmcleod]

This seems overcomplicated to me.

Why not just create presets in the Track Manager?

You can then select which preset to use either using the Track Manager button drop down menu (in Sonar), or the Track Manager itself in either CbB/Sonar.

[murat k.]

4 hours ago, msmcleod said:

This seems overcomplicated to me.

Why not just create presets in the Track Manager?

You can then select which preset to use either using the Track Manager button drop down menu (in Sonar), or the Track Manager itself in either CbB/Sonar.

It's not practical to load a View Preset every time for tracks that we don't need to see or no longer need throughout a project—especially given that we currently access the Track Manager through a separate window from the main one. Once this feature is added, we will use the Track Manager only occasionally, not constantly, to show or hide specific tracks we've excluded or hidden or to load customized View Presets.

[Glenn Stanton]

i have a view preset "WIP" work in progess - which is "disposable" in the sense i can overwrite it at will to reflect how i want things arranged. and then i can always just select my custom mix/record etc views to go back to a fuller view.

[murat k.]

1 hour ago, Glenn Stanton said:

i have a view preset "WIP" work in progess - which is "disposable" in the sense i can overwrite it at will to reflect how i want things arranged. and then i can always just select my custom mix/record etc views to go back to a fuller view.

So you end up having to update the View Preset for tracks you don’t use constantly or don’t need to see. With this feature, we won’t need to deal with these kinds of things anymore.

What you need to do is use the Exclude command when you no longer need a track, that’s it. So your workspace automatically will become WIP as it supposed to be, allowing you to use the view commands without having to see unused tracks anymore.

[Glenn Stanton]

true but for me, this works well vs the track manager only (which i do use as well) as i also want different views like console or not, inspector or not, etc. and this captures it quickly and easily. just my workflow input on the subject.

[murat k.]

25 minutes ago, Glenn Stanton said:

true but for me, this works well vs the track manager only (which i do use as well) as i also want different views like console or not, inspector or not, etc. and this captures it quickly and easily. just my workflow input on the subject.

Nice! When this feature is implemented, it will provide you with an additional layer of view preference, serving you much better in your workflow.

While thinking about this topic, another specific example came to my mind.

For instance, you've created an arpeggio consisting of single long notes. You want to use these arpeggio notes as they are played, but since you might want to make changes later, you decided to duplicate the original track with the long notes to keep it safe. You may never need the duplicate, but who knows? By excluding this track, you can keep it within the file, and even when using the 'Unhide All Tracks' command, it will remain invisible.

Use cases can be varied. However, I hope everyone has understood that this feature and its benefits address an important shortcoming in the track view experience and simplify view-related tasks rather than complicating the situation.

[murat k.]

Briefly, this feature ensures that the tracks you exclude remain hidden when using the 'Unhide All' command. Otherwise, you'll need to restore the view using the view preset each time and continuously update your view preset whenever there’s a change. When added, it will look like this in the Track Manager.