The track focus behaviour is different between project view and mixconsole

The track focus behaviour is different between project view and mixconsole and misleading in mixconsole

1 create new project
2 create 2 audio tracks
3 in project view select the first track
4 in project view click the second’s track mute button → track focus stays on the first track
5 now hit the key command for mute (m) → the first track is muted - which makes sense, since trackfocus is still on the first track

now do the same thing in mixconsole:
1 in mixconsole select first track
2 in mixconsole click second’s track mute button → track focus seems to stay on the first track
3 now hit the key command for mute (m) → the second track is now unmuted instead of the first track, which is still in focus.

Thus, in mixcontrole, although track focus stays on the first track, it actually switches to the second track. Although the first track is still in focus, all key commands are sent to the second track. The same happens with the key commands for record, monitor, solo, channel setting, read & write automation.

The problem is even worse when using an external controller like softube console 1:
1 in mixconsole select first track
2 in mixconsole click second’s track mute button → track focus seems to stay on the first track
3 now hit the key command for mute (m) → the second track is now unmuted instead of the first track, which is still in focus.
4 now change track on the controller to the second and then back to the first track → track focus switches as expected, but when you hit the key command for “mute” the second track is muted/unmuted, regardless which track is in focus.

I would expect the behaviour to be the same in project view and mixconsole. The behaviour in mixconsole is clearly misleading as the track focus still seems to be on the first track but actually is on the second track.

Going further, I would love a mode where when clicking “solo” (or whatever action), track focus switches to this track. Currently, this behaviour can be set in settings, but only for “solo” and “channel settings”. It would be great to have that option for “mute”, “record”, “monitor”, “read & write automation” as well.

See the video for further details.

MacOS 14.6.1. Nuendo 13.0.40

I agree it should be the same behavior in both areas.

2 Likes

Tried recreating it, and indeed it happens here too. In the Mix Console, when selecting track “A”, and then clicking Mute or Solo etc. on track “B”, then track B is “invisibly” selected and will receive all key commands like Solo and Mute, while visually it still seems like track A is selected.

This is surely a bug?

MacOS 13.5, Nuendo 13.0.41

1 Like

It has been this way since ages, in addition sometimes when creating and inserting, or moving tracks, using the up/down arrows skips over certain tracks or track types, but with each revision the behaviour improves, then of course regresses.

I am supposing it has something to do with Track Archives, in that the order, or format assigned during a projects’ life, determines how a track list can be navigated, thus I create new projects and copy/paste all data from a previous project and I test this by navigating up and down a template.

Cheers