Issue with Keyboard Maestro MIDI triggers

When using a midi trigger in Keyboard Maestro, Dorico’s Note Input stops displaying ghost notes and selecting pitch with MIDI does not work.
At the same time MIDI Thru works.

After this happens, Dorico crashes on quit.
So for now any MIDI triggers in Keyboard Maestro are basically unusable.
This is 100% reproduceable here.

Dorico Diagnostics.zip (865.3 KB)

PS: All software are latest versions, incl MacOS

When you play on the Maestro keyboard, does Dorico flash in the bottom right corner of the Main window a little green dot for each MIDI message received?

A macro editor for MAC that can send and receive MIDI data also.

Sorry, I do not know that, but anyway, Dorico recognizes Maestro as a MIDI device. So when you send MIDI-Data via a macro, still these MIDI events should be treated as normal MIDI and therefore also flash the green LED at the bottom right corner of Dorico’s main window. Does that do?

It is all weird and starts resemble the “have you tried to turn it off and on again?” from the famous IT Crowd series!
Yesterday I got dissapearing shadow note in Note Input and crash when quitting Dorico after that. I tried to remedy the issue with allowing only MIDI from IAC bus to enter Dorico and routed MIDI appropriately in DAW (DigitalPerformer). The shadow note stopped dissapearing and there were no more crashes on quit.

TODAY: I reverted all, allowed Keyboard Maestro and MIDI Keyboard again in Dorico and shadow notes are not dissapearing. Why? No idea! Today seems to be a better day, maybe a relapse will come tomorrow.

ANSWER: Keyboard Maestro sends out only CC109 value 68 and I have a feeling that the green dot is triggered only by MIDI Note and not pure CC data.

QUESTION: All that hassle with Keyboard Maestro sending out CC109 68 value is because Dorico starts up with MIDI Thru following the Tuning preference in settings (a=444 in my case). After the first playback the tuning for some weird reason resets to 440 in all instruments when using MIDI Thru. Playback is 444 by tuning pref. and Thru 440. That is why I had to set Keyboard Maestro to send out MIDI CC109 value 68 to NotePerformer. Weird workaround but it works…
Any possibility to not have NP reset the tuning after playback has stopped?

To clarify: the Keyboard Maestro macro is sending out CC109#68 every time it catches a MIDI packet that is a NoteON message from my interface. Any note, any velocity. That is why RegEx matching is needed.

I don’t really know on the internal handling of MIDI in Dorico, but I do see your Maestro is recognized by Dorico, because it turns up in the MIDI devices list under Dorico preferences.
And I checked with my Korg keyboard, when I turn the pitch bend or control wheel, the little green light does in fact light up, so yes, the green light is flashing for any kind of MIDI data, unless you set in the Dorico preferences to filter out MIDI Controller data, but I can see in the diagnostics that you don’t have that option set to on.
So I also wonder what is going on in your case.

Just happened again, after an hour of work.
Shadow notes stopped appearing and crash on quit again.
I don’t know if there is anything to read in the report, but just in case…
Dorico Diagnostics.zip (955.8 KB)

Thanks for the data.
The crash on quit is same as it was before, so for a fix please wait until the next maintenance update.

Regarding the MIDI issue, actually, in the Dorico logs I can see

2024-11-16 10:19:01.967 [info] Disabling input device: IAC Driver Bus 1
2024-11-16 10:19:02.146 [info] Disabling input device: MIDI Keys

So yes, MIDI Keys gets disabled. I guess it comes from the project data. You just opened that project and then immediately those MIDI devices get disabled. But don’t ask me why.
What if you enable them again and then save the project under a different name. If you then quit Dorcio and start again, does it get disabled again?

After a crash on quit I did disable IAC Bus and MidiKeys (DigitalPerformer virtual midi kbd) myself in preferences. So this is not related, I did that.

I don’t suppose this will be the cause, but do make sure that you don’t have the same MIDI device selected as an output device (in the VST and MIDI panel in Play mode) and as an input device (on the Play page of Preferences), as that will create a MIDI feedback loop that very well may result in a crash.

1 Like

I did check because I know my highly evolved ability of making mistakes.
There are no MIDI instruments selected at all.
3 instances of NotePerformer in VST Instruments, nothing in MIDI Instruments.
So, sadly, the MIDI loop is not there, would have been nice and easy solution.