Dorico's enigmatic choice of audio outputs

I’m a Dorico user since version 2 or so. Although many things concerning audio have improved since then, I often run into a situation, in which I don’t hear any playback after opening Dorico and have to adjust things manually.

For example, I see this:

Why does Dorico not choose the only available output automatically?

By the way - there is also a Fireface UFX connected to the computer and seamlessly recognized by all other apps - but Dorico does not see it.

It would also be nice, if Dorico would ask the user, if the last used device is not available and suggest an alternative (like when I was using AirPods working in a train and want to continue working at home…)

Or do I miss something here?

1 Like

I’m currently not having a Mac at my hands, but I see in your screenshot, that your microphone is set to 44.1 kHz and the outputs to 48 kHz. Though the operating system can cope with different sample rates, Dorico’s audio engine can not, there is only one sample rate allowed for input and ouput. That has to do with not using Apple’s CoreAudio directly but relying on Steinberg’s ASIO technology and having a translating bridge component in between (CoreAudio2ASIO).

I guess what’s happening is that Dorico picks the Built-in Audio device, detects the sample rate mismatch and disables the output, because the input’s sample rate has precedence.
How does Dorico behave when you set both to the same sample rate?

Hi Ulf,

thanks for your reply.

To be honest, I don’t know, why the sampling rates were set differently.

I did not change them by purpose.

Maybe the output SR ist changed to 48kHz when using AirPods and not changed back after disconnecting them…?

Interestingly - if I check the box next to “MacBook Pro Lautsprecher” and confirm the dialog pressing “Close” everything works as expected - I can hear the sound through my speakers - so this mismatch does not seem to be a problem that Dorico can’t solve by its own. :slight_smile:

Suggestions for this situation:

  1. The Output SR should have precedence, because Audio Input is seldomly (never?) used in Dorico (so far)…? For me it is more important to hear what is written than to input audio.
  2. Ask the user to change the outputs sample rates, when it can’t be done automatically. At least tell him, that there is a mismatch which is causing this “problem”.

True this area of the program has still lots of room to improve. I will put it on our agenda again, but can’t make a promise of what or where or how we are going to improve.

The best workaround at the moment for Mac users is to create a separate aggregate device for each hardware audio device that you have and there make sure that no inputs are used.
The same holds true for you Airpods, because the in your Airpods integrated microphone poses the same problem to Dorico.
Additionally, the Airpod’s Mic does not even offer 16 kHz, the minimum required sample rate of Dorico’s audio engine.