updateStreamingEnabled → disconnectEventInput: Akai MPK88 Port 1; id => 10 StreamId => 0
I see connectEventInputs as well, but always followed by a disconnect. So your AKAI does get recognized from Dorico but not connected for reasons I don’t know. Does @dspreadbury maybe know why that is happening?
I can see some entries in Dorico’s application log that suggest the audio engine is periodically not responding (Dorico is sending MIDI events to be auditioned, for example, and the audio engine is not responding) so I wonder whether there’s some kind of problem there. Is playback working OK in general?
Today (after a complete system reboot) the MIDI is back working normally again. So I don’t know what to say other than the gremlin went away.
Playback seemed to be working OK - only MIDI input was broken yesterday when I reported this.
I’m struck by the mention about the audio engine. I’ve been having quite a few problems with my UAD audio interface. In theory, that shouldn’t mess with MIDI, but I’ll mention it since you mentioned the audio engine not responding. I won’t bore you with details of the UAD issues but they are related to the UA custom drivers getting confused and sometimes not working properly, because the UA software goes haywire when there are multiple users in macOS logged in simultaneously.
I guess there’s not much followup to do here since the issue went away, unless you have any other recommendations for things you want me to try, should it happen again.
Dorico communicates with MIDI input (and output) devices via the audio engine rather than directly, so if the audio engine isn’t running properly, MIDI input won’t be working either.