N13 select several tracks with controller issue

Today I started with N13. All seems to work fine here but I have to investigate much more on the new features.
I’ve realized that now I can’t select several tracks using a remote controller (neither Yamaha DM2000 or AVID Artist Mix) using shift + select channels or command + select channels.
Has anyone same issue?

1 Like

Hi,

What happens, if you do so, please?

Only the last track selected remains selected.
If you select various tracks in mixer window, the “select” buttons in controller engage too, and you can for example adjust the fader or sends together for these selected tracks with the remote controller, but you’re unabled to make the multiple selection directly in the surface.

Hi,

Confirmed and reported to Steinberg. Thank you

Thanks a lot for the coverage.

Updated to N13.0.20 and this bugstill remains…

Same issue here: Unable to select multiple tracks when holding shift on my keyboard + select buttons on my DAW controller (Mackie Control Pro). N13.0.20.

Steinberg, please fix this in next update!

Well, next update arrived and this issue still remains. No words from Steinberg. Are you planning to fix it or 8 or more fader DAW controllers will work more or less as a simply Faderport?

13.0.40 ínstalled and this bug remains. When will it work as before N13?

Same problem here. I use a SSL Nucleus and I can’t select several channels on the controller while holding SHIFT on the keyboard. Very, very irritating.

Issue remains in 13.0.41. It would be so much appreciated Steinberg told us when it will be fixed…
I think Nuendo is a platform used if very professional setups, but I wonder why there’re not more voices telling about this issue.
I’m mixing symphonic setups for films and I’ve to move along a couple of hundreds of tracks. It’s usual to select a section like 2nd violin strings and modify any parameter. It was very quick before N13 and now I’ve to return to mix with mouse instead big daw controller setup. Annoying.

Hi,

Steinberg always communicates this in the Release Notes of every single update.

I think that in the release notes they communicate what HAS BEEN fixed in the update, not what will be fixed at some point in the future.

The OP want to know when in the future the issue will be fixed.

Updated today to N13.0.50 and this bug still remains…
Very angry with Steinberg.