I will guide you through Midi-Ox, but tomorrow, I am on my smartphone at the moment and it’s already late in Europe.
Catch ya later!
Good morning!
It’s pretty simple, just start MIDI-OX and then choose from the menu Options > MIDI Devices. In the list of MIDI Inputs you simply highlight the device that you want to monitor (in your case your keyboard, in mine the Steinberg UR22) and then click on OK. MIDI-OX will open that port then and in the Monitor - Output window you can see all the incoming events.
There are only a few note on/off events coming in, that is not the problem.
But how about the other device, the masterkey 49 ? If you highlight that one instead…
With these filter options selected, the output monitor shows a constant stream of “Timing Clock” events but only MIDI on/off events when I play the keyboard.
The masterkey 49 is a second midi keyboard which I ordinarily do not use, and which has been turned off most of the time I’ve been having this problem, so I don’t think it’s related, but when I monitored it, I got similar results, and it did not work inputting notes to Dorico either.
What kind of MIDI-Keybard do you have connected? Is it possible that you can stop the MIDI RealTime message (the Timing clocks) from being sent? The sort of MIDI-keyboards and synths that I know usually have a MIDI setup page somewhere with the option to switch it off. I guess it is the RealTime events that confuse Dorico.
It is a Yamaha P90 digital piano. I don’t know where or how to access controls to turn off that timing information.
However, the other keyboard I have, (Acorn Masterkey 49) is not sending that stream of timing info when I have it connected, and yet it does not work with Dorico note input either. Both keyboards work fine to input midi notes into my DAW (Reaper). So the timing stream doesn’t seem to be causing problems there.
I came across this thread, as MIDI input now also fails on my machine using Xkey Air/Widibud. Might it be, that this issue is related to installing KB5074105, which introduces new MIDI features?
[Windows MIDI Services] New! This update improves MIDI on Windows with enhanced support for MIDI 1.0 and MIDI 2.0, including full WinMM and WinRT MIDI 1.0 support with built-in translation, shared MIDI ports across apps, custom port names, loopback and app-to-app MIDI, plus performance improvements and bug fixes—delivering a better experience for musicians.
Can you start a separate thread on it, so it doesn’t get confused with the 2024 issue? Feel free to @ me in that thread.
Also, go to About Windows MIDI Services - Windows MIDI Services and run the tool there (from a terminal window) to see if Windows MIDI Services is enabled on your PC, or if you are still using the old MIDI stack.
Pete
Microsoft
Hello Pete,
thank you very much for your help! My post is just an addition to the issue brought up by Joshua three days ago. If he can confirm, that it might have started after installing that update, it is likely that this might be the cause of this problem. So i will watch the troubleshooting steps here…
Is there a way to check, if any loopback connections are enabled related to the new MIDI stack?
Did you start a separate thread on this? If so, please link it here.
Pete
Microsoft
Well, my update history shows the update in question was installed on 1/30 and this total loss of midi input did start just in the last few days, so that is possible…
I tried downloading and running the Windows MIDI Services checker, which confirms it is active.
I was really trying not to pollute this thread, which originally has nothing to do with Windows MIDI Services, and sending notifications to everyone from that thread.
Joshua, the fact that you said it’s working in other DAWs means it’s not necessarily an infrastructure issue, so we’d need to look at it further. Also, Matzix’s issues are with BLE MIDI with a USB adapter, from what I see (Xkey Air/Widibud) vs straight up USB MIDI, so a different connection mechanism.
Pete
Microsoft
The loopback ports in the new stack are not there by default. You have to create them using tools we’ll release later. So that won’t be a concern here.
You would see them in any app which lists MIDI ports.
Pete
Microsoft
I’ve just tried using my FP-30X with USB MIDI and its the same behavior as with BLE MIDI: The green light stays on after pressing a key. No note input at all, but VST sounds are audible.
I also can confirm, that DAW (Nuendo) works well with both setups.
Ok. Sounds like this is not something with Windows MIDI Services then, at least not obviously so. If MIDI wasn’t getting through at all, you wouldn’t hear the VSTs, and it wouldn’t work with Nuendo.
I’m not a Dorico user, so will defer to others who know more there. I still recommend folks starting new threads for new issues if they want to get attention paid to them from other users, and not necrothread an already-solved issue (helpful folks will often ignore threads marked as solved).
Pete
Microsoft
Hi @Psychlist1972 , thank you very much for also chiming in here.
Hi @joshuasaulle , to be honest, I’m running out of steam.
Actually, I have a Yamaha P120 here, which is pretty similar to the P90 (software wise). My P120 also constantly sends out MIDI RT messages, but that does not affect by any means Dorico. The green do only lights up upon receiving MID-NoteOn or -NoteOff messages. So it must be something else in your case that makes the green dot light up constantly and therefore jams the note input in Dorico. But I don’t know why or what…
Ulf,
I do appreciate your efforts. I have a concert I’m composing music for in less than two months, so I really need my MIDI input to work. Do you have any other suggestions for how to fix this? I’m really at my wit’s end here and willing to try anything.
Thanks,
Josh
You sound really desperate @joshuasaulle .
And you really tried the Filter CCs option in the Dorico Preferences (on the Play tab)?
And in the Preferences on the VST Plug-ins tab at the bottom you pushed the Reset Audio Engine Data button and restarted Dorico?
What I would also try, is resetting the P90 to the state when it came out of the factory. A Google search found following:
To factory reset a Yamaha P90 digital piano,
turn the instrument OFF, then press and hold the highest key on the keyboard (the rightmost white key) while turning the power back ON. This action clears user settings, such as registered memory and MIDI configurations, restoring them to original factory settings.
But do at your own risk, don’t hold me liable for a bad outcome of this.