Originally Posted by Rustyspoon#
Jeff,
We had this discussion in the past. The main issue of what you are proposing is constant "manual" reselection and that will be extremely challenging for several reasons.
#1 - each view is different. Selecting a random group of tracks will not be a unified process. Especially in expanded views. They would have to be minimized. Existing Bar Settings works in any view equally same.

#2 Intersection is defined by either selecting a particular bar, nearest bar to cursor position, or type in the panel itself. I think reinventing the wheel here is not needed.

#3 amounts of clicks and moves it will take to do things like:
Bar 1 -Mute all except for 2,4,5,8,9,12,15,17,22,24
Bar 3 - Unmute all except for 3,7,11,14, 17,22,24.
Bar 10 -Mute all except 2,6,23

To simply put, it can't be programed automatically, because of rules and overrides(Exceptions). And you can't automate selection inversion, as each change at the bar is individual user preference. Exceptions (overrides)

---------
I fully understand the concept you are proposing, I just believe existing logic for mutes/unmutes is brilliant and user should not think: "How do I do this in this view?". Since we talked about this before, it would be very interesting to hear from somebody else who is using Bar Settings - "Mutes" often.
#1 Yes there are cases especially if non continuous that the current approach which recreate the track view in the chord view works as good.
More importantly I'm beginning to see your side of the conversation only because BB is unique in that originally had a hard coded array of 7 x 255 chords, so they're hard coded approach to 7 tracks made sense. I think you have noticed when they tried to expand that to 24 it became more awkward.

#2 I don't understand the argument, but I was only showing how all DAWs deal with settings across many tracks (no reinventing at all). Just the idea of settings being in panel so they can be applied to many tracks as a good thing.

#3 this seems to be the same argument as #1

I do understand your point that the current hard coded approach works good for your scenarios (if real).
I am just used to dealing with settings be adjusted by the "selected tracks" norm, which is my key point.
There currently is no behavior/ action in BB that works by multiple selected tracks. This is due to the fact
that a multi-track view did not exist in the past. Now it does.

Hopefully we can agree that there are two good but different points here.

Last edited by jpettit; 01/30/25 09:40 AM.
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).