I soloed a few instruments in the Mixer and now, the (RED) Solo Buttons are disabled I am unable to UN-Mute the Mixer.
I have a screen recording but the file is 80MB and not sure if that is why I am not able to upload.
Is this a bug or some esoteric hidden feature who’s solution is also hidden?
Here’s a DropBox link to the video screen recording … the Cursor wiggle at the end is “Trackpad” for “WTF???” 
Here’s another video … It’s like playback tik-tak-doe …
I’m using Cantai BTW and if I change the Playback Template to Iconica, all the Cantai work has to be redone and re-loaded (as well as all my Delay and other plugins I have for this project) and before I do that, I want to make sure that this is not a Cantai Issue and/or some Playback Template issue/bug causing this.
Could the other plugins I’m using (Metric Halo) be causing the issue?
Any help would be swell, thank you!
Have you tried Deactivate All Solo States or Deactivate All Mute States from the Play Menu?
Hello @David_Tee, and thank you for taking the time to reply, I really appreciate it.
The above video (second one I linked) is from the Play Menu (Cmd/Ctrl + 4) …
I am assuming you’re asking because there is probably a hidden “Deactivate All Solo Statesl” and/or "Deactivate All Mute States" button of some kind (like the button “Deactivate Button” that is not working at all in my case in the “Mixer” which is displayed in the linked first video above). If so, might you kindly share where that might be?
Yup … been doing that … see the linked video 1 & 2 above and I just made a 3rd screen recording video just right now … Same thing, the “Deactivate All” buttons are doing absolutely nothing, not working. The “Deactivate All” buttons are not working in the Mixer, nor the Play Menu.
I’m assuming I’m the only one who’s experiencing this bug?
In which case you should probably upload your diagnostics (Help>Create Diagnostic Report), so the team can see what is going on…
And it would be also nice if you could provide your project file to me. If you don’t want to post it publicly, you can send it to u dot stoermer at steinberg dot de
Thanks
Hello all, ok… the issue is fixed (bug still there, if it is indeed a Dorico bug) …
Solutions … [SEE PHOTO]
Reset “Use Auto Playback Template” that (sometimes, I don’t know why sometimes, even if I’ve already clicked “Do not show this again” or “Use Auto Playback Template” or “Continue”, depending on the project, it just keeps popping like Jason, Freddy, A Vin Diesel Franchise) and it fixed the issue, but I had to reload all of my Plugins and Cantai voices (don’t worry, I saved it in a different VERSION so I could go back to the older version as I don’t like to rely on Dorico’s automatic saving). So that DID fix it, but I lost everything … I then went to the previously saved version and …
One by one clicked the MUTE of every single channel and one by one clicked the SOLO of every channel and the “Deactivate all:” (for Solo and Mute) buttons are now working.
I believe the CAUSE of this issue (which is only for this specific project ) is/was/continues to still be a UNIVERSAL AUDIO “Powered Plugin” that I have since removed from the Dorico project but I still get the dreaded
"UAD Powered Plug-Ins Info
UAD plug-ins are disabled because no
UAD hardware is detected.
You can enable UAD plug-ins after connecting UAD hardware." POP UP, even though the plugin as been removed and is no longer there [SEE PHOTO] … I only have Metric Halo plugins …
… Again, this is the only project that has had the “Deactivate All: button gets stuck and Resetting playback fixes it, but the ‘UAD popover’ keeps popping up even though the UAD plugin has already been removed” …
I have UAD Powered AND Native plugins and sometimes I use my Apollo interfaces (at the studio), sometimes my Metric Halo interfaces (at my home studio, where I have BOTH MH & UAD connected to that M1 MacStudio), sometimes I do not use an interface and only use the M3 MacBook Air, and sometimes use my AirPods when I’m traveling …
So, in my Dorico projects, I use different configurations depending on where I am. If a project was made that used a UAD Powered Plugin where the Apollo is not connected, it has wreaked havoc on my Logic, Cubase and Dorico projects. There’ something about who those plugins authorize that is causing an issue, even though I’ve removed the UAD Powered Plugin from Logic, Cubase and Dorico, those projects have issues. In those cases (in Logic for instance), luckily I’ve been able to save that project and relink and re-do the project from scratch, which is what I’ll to do in the case of this project.
Unfortunately, many of us are under contract with labels and/or publishers and we can’t upload copyrighted projects.
Thank you ALL for your replies and attention on this matter. 
If this IS A bug with Dorico, perhaps it can be addressed, but it is more than like UAD Powered Plugins causing the issue.
Many times, with these kind of VST/Audio problems, a copy of your file that is cut down to eliminate most or all of the copyrighted content (or changing notes and rhythms to disguise it) is enough to diagnose the problem and offer a solution.
— Jim
Yup, UAD plugins are causing similar crashes and other issues even in Logic.
This seems to be ONLY with the UAD Powered Plugins; the ones that use the Apollo hardware … the ones that require Mac users to change their Security … the ones that (we Mac users) constantly get the dreaded (paraphrasing here) “This plugin will not work with future version of Mac OS”.
I am assuming that UA has been working frantically to get more of their plugins ported over to their NATIVE UA Connect architecture, and they’re even gladly updating the things you’ve already bought and making them not usable for future OS (somehow) so that they can take more of our money. Now THAT is shock!
This is the reason why I gave up on Waves years ago as the “pay to update to be able to use in the next OS” bull$*** was just too much. New features? No more crashes with their updates, SURE, I’ll pay, I get it. That old pay to play (Waves) has been replaced with the SUBSCRIPTION ONLY BS.
So, the UN-MUTE Mixer issue seems to be only caused by this particular project with the UAD POWERED plugins, not a Dorico thing.
I bought my first Macs in 2008 (post Power PC), and upgraded to Snow Leopard and Logic 9, in 2010 … Then in 2012, I bought the new Logic X, and had to upgrade my MacPro from Snow Leopard, then Mavericks to even use Logic X, which, didn’t provide enough usage for me to keep using Lion and beyond, so I continued to use my old clones and Snow Leopard all the way up to Mac OS Sierra, and when Mojave stopped letting me use my old clones in 2018, I just did a fresh install of everything, that year, and started using Logic X.
The point/lesson is, … I will gladly pay for the upgrades when they don’t burn the bridge of the older plugins that burn the bridge and demand tribute/tax/subscription. There are good companies (Steinberg, Metric Halo/Make Believe, East West and Native/Kontakt), and it looks like UA is going to be left behind and I’ll keep a few Macs frozen in Mojave (a great and stable OS) and Sonoma. I can dual boot in Mojave and Sonoma on my trashcan MacPro to use my UA stuff (UA even burned the bridge with the Firewire UA $tuff) but I can still use the trashcan MacPro (and my 2008 Mac Pro) as a Recording or Mastering Machine and use all the old plugin$ that paid for.
Sad thing is, Cubase and Dorico and Cantai do not work on my MacPros even with 100GBs of RAM (trashcan) and 32GBs on my 2008 MP.
Happy composing and recording everyone! Now where is my dusty Tascam 4 track and Roland 1880?!?!?
