Chord Detection not working if I select output channels other than 1 and 2 on Mac M

Dorico
1

Hello Steinberg Support,

I hope you can assist me with a very odd issue.

I have been experiencing an odd issue with the latest Dorico version 6.2.30.6245, For that matter it may occur on older versions too.

I have Dorico configured to output on ADAT channels of my RME UCX II e.g. channels 13 & 14 of my 20 channel audio interface utilizing a Aggregate Device on my M3 Ultra Mac Studio. I have no problems with Dorico in this configuration execept one.

Chord Detection stops working. If I highlight a stack of notes and right click a group of notes and choose Generate Chord Symbols and Diagrams/Generate Chord Symbols from Selection it will open the Generate Chord Symbols from Selection window and when I click on Ok it resolves the chord from selected notes.

If I put the cursor on a beat and open the Chord C7 button on the right or press Shift + Q to open the Chord Popover it detects nothing when I play a clearly created chord,

Note entry works fine so it’s not a midi issue.

If I reset the Dorico 6 output channels to 1 and 2 then no chord detection issues.

I can explain why I need to have Dorico on a specifac stereo channel pair but part of the reason is I use Hardware Loopback channels to bounce audio to a different stereo pair.

Since nothing else in Dorico misbehaves with this alternate configuration I am puzzled. I also tried a different set of stereo outputs and chord detection does not work.

Oddly if I close Dorico and reopen it with alternate output channels it will detect a midi played chord via the chord pop-up (once or twice) then it stops working again.

Has anyone else experienced this?

Thank you

Curt

2

Yes, we’re aware of a problem in this area, where chord symbol input via MIDI keyboard can stop working, which is particularly likely to happen when you switch from Dorico to another app, or when you stop chord symbol input and return to regular note input. We hope we’ve got this problem properly fixed, and the fix will be coming in the next Dorico 6 update when it arrives. Sorry for the inconvenience caused in the meantime.