Specs:
Cubase 11.0.10 Build 321
Windows 10 Pro 64bits version 20H2 OS 10.0.19042 Build 19042
CPU: AMD Ryzen 9 3900XT 3.8Ghz
MB: ASUS TUF GAMING B550-PLUS Bios 1401
RAM: 4x16GB of DDR4 Crucial Ballistix Desktop Gaming Memory Kit, red @ 1600MHz
GPU: Gigabyte GTX N970IX OC-4GD
SSD for Win10 + Cubase: Samsung SSD 970 EVO Plus 1TB Nvme M.2
SSD: Samsung SSD 860 EVO 4 To SATA3
PSU: Corsair 750W Gold tier1 on LTT
Case: Be Quiet Pure Base 500DX
I followed all your steps and it’s all working fine here. All selected MIDI tracks are soloed when selected, both through arrows or mouse clicking. I’m on Win10, and latest Cubase version.
Oh, my bad! I just did the test again, reproducing your exact preferences settings and got the same issue as you described. It’s like alternating the solo feature each time we switch a track, by clicking or using arrow keys.
I could narrow the conflict possibilities and ended up with the only two preferences in the Project & MixConsole tab that are causing the problem. If you just check “Select Channel/Track on Solo” and “Enable Solo on Selected Track” the problem occurs.
Also, it’s not restricted to MIDI tracks. It happens to any type.
Thanks for testing and confirming this, you saved me some time as I was about to scrap all my Cubase install.
From my tests it seems that it’s just a graphic bug, because despite the track being displayed as muted, it’s actually being soloed and play the correct audio.
I tested it again and it’s not just graphical, it’s a functional bug. I created a couple of Instrument tracks with Halion. Created a MIDI note in each one, put them in a loop and monitored the level bars while selecting different tracks. Those that are not solo activated due to the bug don’t have any sound.
I checked the only two problematic preferences I mentioned above.
You’re right, I tried in a blank project and recorded different parts. The bug is indeed not just graphical like I was stating in my previous message. Oddly it was just graphical when I tested on a project which was ported from C6 which may explains why it behaved differently in my other test.