Question on MIDI and WASAPI [Solved]

I've been using Sonar with WASAPI so a Windows screen capture program could capture the audio without the usual nasty Windows latency, and I could run Vegas at the same time. So far no problems, but last night Sonar simply refused to recognize my MIDI keyboard controller. Other programs could when using ASIO. After tearing my hair out for a while, I switched from MME MIDI to UWP MIDI, and now it seems to work. But I'd never had it on UWP before, so I'm not sure if that's the issue. 
 
Does anyone have a definitive protocol for using MIDI with WASAPI low-latency mode?

More WASAPI woes...

I would try asio4all. Works better for me when I'm sans audio interface and has better RTL. 
It got a bad rap in the past but like all software is always being updated and bugs fixed. 
Things like it taking over your real ASIO driver don't happen for me. Might still be true for some ASIO drivers but not for Tascam or Focusrite. 
I was using asio4all for months and I brought that laptop home and installed my Focusrite driver and I can use either one. If I boot Sonar with the interface on Sonar uses that driver. If the interface is off it uses the asio4all driver. 
I later out of curiosity installed my Tascam driver and that also caused no issues. 

chris.r
Perhaps you know it already but in case you don't, there's a great software Voicemeeter from vb-audio.com, check it out it might be helpful in your case. I remember using it in winXP and it was doing wonders.

 
Thanks for the tip, I'm not sure how useful it would be without recording the video at the same time so the sound and video are synched. But I can think of other uses.
 
To follow up, MIDI worked just fine last night without having to do anything other than turn the system on. I'm going to chalk it up to Windows update settling in, because that was the only difference between turning the computer off an turning it back on again
 
Thanks again Noel. It still may have something to do with MME vs UWP MIDI but all I know is that it's working, and that's all that matters!

Noel Borthwick [Cakewalk]
I've seen MME go belly up on occasion so the reboot fixing it seems "logical"

 
Only thing is I rebooted multiple times when it stopped working. Then again by using UWP in the Playback and Recording section of the MIDI preferences, maybe that bypassed any tendency for MME to be problematic.

That solution is to use WASAPI shared mode :)

"Solved" in the sense that is must be system-specific, because on a more recent computer, both MME and UWP work with WASAPI shared using either Sonar or CbB. However the issue remains repeatable on the older machine. I blame Windows 

Thanks Noel. Sorry to bother you about this. MIDI does work with UWP when WASAPI shared is selected. But again, unless someone else can reproduce this, I'll have to assume it's system-specific so probably not worth spending your time on it...you have bigger fish to fry right now 

Grem
Not sure this is related, but I have an Alesis Q49 that I have been using for a few years now. Just recently Windows wouldn't recognize it, so I couldn't use it in any DAW I have. Google searches didn't turn up much of anything either. So I put it down to Windows updates as that was the only thing that has really changed on my music machine.
 
After reading something someone had wrote about another problem with a USB device and Windows updates, it was suggested to try another USB port. I did that and now I have the Q49 back working. Using ASIO (RME 400 Fireface) and UPW.
 
HTH 

I remember a discussion on the forum a year or so ago about resetting USB ports. Windows allows a limited number of devices to be plugged in to any given port. I don't know what the number is, but if, for example, it's 10, the 11th USB device you plug in to that port won't be recognized. I found this info here. Maybe it will help:
Scan For Hardware Changes Using Device Manager

1. Right click Start then left click Run
2. Type devmgmt.msc and click OK, which will open Device Manager
3. Right click on the name of your computer, and then left click on scan for hardware changes.
4. Wait for the scan to complete and then check your USB device to see if it works.

Disable and Re-enable the USB Controller

1. Right click Start then left click Run
2. Type devmgmt.msc and click OK, which will open Device Manager
3. Locate Universal Serial Bus Controllers in the list
4. Click the arrow next to the little USB cable so that it points down instead of to the right
5. Right-click on the first USB controller in the list and select ​uninstall.
6. Repeat step 5 for each USB controller you find.
7. Turn your computer off and then back on again.
8. Windows will automatically reinstall the USB controllers, so check to see if your device works.