After having Dorico 5.1.70.2200 open for a while (hours) and sometimes in the background, when I return Dorico to activity the program no longer outputs sound. I have tried changing the playback template from NotePerformer to Halion and back but to no
effect. The only solution is to quit Dorico and restart it. I’m attaching the diagnostic report for the ‘no sound’ condition. Mac OS 15.2, Mac mini M4, 64 gig ram.
Dorico Diagnostics.zip (3.4 MB)
Hi @tbabcock123 , what if you go to Edit > Device Setup in that moment when you have no sound?
Are FrontLeft and FrontRight are shown as the output ports?
And what if you press the Device Control Panel button? The little window which then appears, does it show the Studio Display audio ports as active?
Next time it happens I will do that. It’s not predictable - are these things ever that? But it’s frequent.
It happened, and I went to the Device control panel. It showed the Studio Display speakers as chosen and the sampling at 41000. I toggled the ASIO driver from the Studio Display to “Built-in Audio” and back, which resolved the issue. Thanks for your help, Ulf.
Hi Ulf,
This keeps happening and the only solution is to go into Device Setup and toggle the dropdown in the ‘ASIO driver’ section of the dialog (or restart Dorico). I’m wondering if there is a more permanent solution. I’m attaching a current diagnostic and a screenshot of the Device Setup dialog. Thanks for your help.
-t
Dorico Diagnostics.zip (3.3 MB)
Hi @tbabcock123 ,
I’m not sure on this, but maybe it has to do with sample rates, because from the logs I can see that your Built-in Audio is set to 48kHz and the Studio Display to 44.1kHz. How does it behave if you set both of them to the same rate?
I didn’t realize that. I’ve changed the Mac Mini speakers to 44.1 khz to match the sampling rate of the Studio Display speakers. I’ll see if that makes a difference.
It was a good thought but it didn’t solve the problem. Sigh. I haven’t tried rebooting the computer - seems like the method of last resort but I will try that and let you know if that does anything positive.
Hi Tom, if the reboot also does not help, then please try with this workaround:
- In your Applications folder is a Utilities subfolder and in there is Audio MIDI Setup.app utility.
- In the left bottom corner of the Audio Devices window is a little plus sign. Click on that and choose Create Aggregate Device.
- Though it is called aggregate device, you just should make sure that only the Studio Display Speakers are selected and nothing else of the in- or outputs.
- Optionally rename the new aggregated device to whatever you like.
- Start Dorico and go to Edit > Device Setup; your new aggregate device shall appear in the list of ASIO drivers and be selectable.
- Do select that device and close the Device Setup dialog.
With that in place, how does your system behave then after sleep?
Hi Ulf,
Thanks for the ‘aggregate…’ suggestion. Here’s an update.
After ensuring all of my audio devices were set for a 44100 Hz sampling rate, the problem seemed to disappear. But it has returned, if that’s the right word. I took your suggestion of creating an aggregate audio device with the Studio Display speakers (set to 44100) as the only audio device in the aggregate. After restarting Dorico (5) the device showed up in the ‘Device Setup’ dialog. It works, but after the computer has gone to sleep (with Dorico either foregrounded or background), the sound output for ‘play’ is gone - until the system is goosed by toggling the ASIO device in ‘Device setup’.
Would another diagnostic help or is this rope at its end?
Another diagnostics is better than nothing, so yes, please do one after waking up the computer. Thanks
Here you are:
Dorico Diagnostics.zip (2.4 MB)
Thanks Tom, but yes, the regular audio engine logging does not say much in your case. So we need to get some different logging going in the CoreAudio2ASIO component. I need to find the relevant info again, I’ll be back…
Thanks Ulf. I’m wondering if it has anything to do with the 8 output channels listed for the Studio Display. I could find no way of isolating output to only two channels.
Update: I tried making a “Multi-output” device and that seemed to confine the output to 2.
I’ll let you know if that makes any difference.
-t
Yes, please let me know.
If still in trouble follow this:
We can get debug output from CA2ASIO but need to enable it first.
Please follow the instructions:
-
Stop Dorico
-
Open a Terminal window (/Applications/Utilities/Terminal.app)
and in there copy and paste the following 2 commands:`defaults write com.steinberg.components.coreaudio2asio "Debug Level" -int 3` `defaults write com.steinberg.components.coreaudio2asio "Debug File" -string /Users/[yourname]/Desktop/CA2ASIOdebugout.txt`
(pease exchange above the [yourname] with your username on that computer and after pasting each line press the Return or Enter key.
-
Then start Dorico and do a sleep cycle 2 or 3 times, leave a few seconds in between each cycle.
-
When you then stop Dorico, have a look at your Desktop for the CA2ASIOdebugout.txt and send me that text file. In order to upload it here you probably need to zip it first.
-
And, because that logging is quite performance hungry, switch the logging off again by doing
`defaults write com.steinberg.components.coreaudio2asio "Debug Level" -int 0`
The “MultiOutput” device gambit didn’t work out. So, I’ll try your suggestion.
Again, thanks for your help.
-t
As a data point, I have the M2 Pro Mini with a Studio Display, and haven’t had any issues with Dorico, or indeed anything else.
I have used a “Multi-output Device”, rather than an Aggregate, in order to work with headphones, and that has worked perfectly, too.
Here is the output you requested (3 sleep cycles - Dorico sound failed after first sleep cycle).
CA2ASIOdebugout.txt.zip (1.6 KB)
I wonder if the difference is between the M2 processor and the M4? Computers… 
I just realized that the “H264 USB camera” that I have attached does not have any audio - input or output. Yet it’s listed with the other audio devices in the Core Audio application. Maybe that’s the problem? I’ll detach it and see if that makes any difference.