Bug Report – Q-Link Output Routing with Tracks Inside a Folder
Environment:
Nuendo 15.30
Windows 11
Steps to reproduce:
Create a standard Folder Track with no Group Channel assigned to the folder.
Create 3 audio tracks inside this folder.
Create 1 Group Channel outside the folder.
Open the MixConsole.
Select the 3 audio tracks.
Use Q-Link (Shift + Alt) to change the output routing of the selected tracks and assign them to the Group Channel created in step 3.
Expected result:
All 3 selected audio tracks should be routed to the same Group Channel simultaneously.
Actual result:
Only the first selected audio track is routed to the newly created Group Channel. The other two selected audio tracks are not routed to the Group Channel and remain assigned to their previous outputs.
This means that Q-Link (Shift + Alt) does not apply the output routing change to all selected tracks when they are located inside a standard Folder Track.
Additional information:
The issue occurs with a standard Folder Track that has no integrated Group Channel output.
This appears to be a regression in Nuendo 15.30, as the expected behavior of Q-Link is to apply the output routing change to all selected tracks.
It is important to hold down Shift + Alt before clicking the field for output assignment.
Q-Link won’t work if you press the keys after opening the pop-up menu.
Can you please check if the issue persists when applying the above?
Of course, I hold Shift + Alt before clicking the output assignment field. I’ve always done it this way.
I used this feature all the time and it worked perfectly before, but now it simply doesn’t work for me anymore. Q-Link does not assign all the selected tracks to the same output.
What else can I do to troubleshoot this issue? Would you like me to make a video showing exactly what happens on my system?
I’m happy to provide any additional information you need, but I would really appreciate some help finding a solution.
I posted, because there is very close codebase sharing between Nuendo and Cubase and I thought I would test in Cubase to see whether this was a more generic problem across both apps, or not.
My conclusion would be it seems specific to Nuendo (and/or Windows only). Sorry I can’t help further (no access to Nuendo here).