Been thinking about this, from the perspective of working closely with a number of software developers over the last 25 years. I think the issue is…developmental compartmentalization.
Here’s what I mean. I would bet heavily that the Mixer is developed as a distinct subunit/branch. There are many signs of this. It has similar to, but not actually the same paradigms and constants as the Project window. So coming from the Project window, behavior is often close to, and yet still different than what is expected, which makes the experience challenging. Actually, it makes the experience illogical and less productive.
It seems that SB is attempting to unify the paradigms between the different windows, which could be great. However, the way in which it is being done is counterproductive because of the lack of unity in the development process. The traits I see indicate that 2 different people/teams are separately pursuing the same general philosophy in Project vs Mixer, but each with their own take on what is “better”.
An easy and illustrative example:
- The behavior after selecting multiple tracks in the Project window versus the Mixer.
A. Press “M” key
- Project: all selected tracks toggle Mute condition
- Mixer: only one track toggles Mute condition
B. Press “S” key
- Project: all selected tracks toggle Solo condition
- Mixer: only one track toggles Solo condition
The reason I point out 2 separate commands is because that indicates a decision, not a mistake.
So which is the “better” behavior? I have my opinion, but that is not the point. The point is that there is NO reason for the deviation in philosophy within a single application. The end user should reasonably expect a unified approach to such conventions between windows.
Until this developmental schizophrenia is resolved, all of the various other complaints/preferences/requests regarding the Mixer are somewhat irrelevant, in my opinion. Window focus issues, unexpected behaviors for reason “X”, redundant info displayed, etc are all dependent upon a unified philosophy, or the lack thereof.
Many other examples exist. For instance, if rolling the mouse over empty inserts in the Mixer displays “Empty”, then why not in the Project Channel Edit window? And so on. (Of course, most/all of us think it is not better.)
In my opinion, this is the root issue with the Mixer complaints. Addressing individual preferences one at a time will never be able to correct the bigger problem
Alright then! Thanks for letting me get that off my chest. And Dear SB employees. I have great respect for your efforts and use Nuendo to good effect daily. Please notice that this is posted here on the SB forum, not complaining on GS. I/we appreciate you considering my/our thoughts and suggestions.