A bug with UWP midi ?

Just sort of wondering how the latest Windows API for MIDI is supposed to work with an older device?
 
https://www.midi.org/articles/midi-enhancements-in-windows-10

scook
http://forum.cakewalk.com/FindPost/3579747
 

So what is the actual use case for UWP MIDI if you are not using bluetooth MIDI or some other newfangled device?
 
I would anticipate possible driver conflicts with older devices that do not have updated drivers ...

abacab

scook
http://forum.cakewalk.com/FindPost/3579747
 

So what is the actual use case for UWP MIDI if you are not using bluetooth MIDI or some other newfangled device?
 
I would anticipate possible driver conflicts with older devices that do not have updated drivers ...

Well, I'm hesitating to purchase that Bluetooth guitar.
 
Another use case that will be more and more frequent in the future is to use Win32/64 music apps (Sonar) with UWP music apps.
 
For quite some time, Microsoft has given the priority to UWP for new features, and retrofit them with a Win32 api compatibility layer.

You answered your own question: "Sonar only allows selection of one MIDI driver mode at a time, either MME or UWP."
 
So if wanted to use both my FW-1884 and a Bluetooth guitar/midi instrument, or have someone play a bt instrument while I'm at the console, I would need an UWP driver/support in Sonar that would support both, since the FW-1884 was discontinued years ago and will never have its driver made UWP compatible.
 
Again, I perfectly understand if Cakewalk wanted to invest its time on features/fixes potentially much more impactful. I wrote this post on the off chance that A. fixing channel names is trivial for Cakewalk's dev team, B. this fix would interest more and more people as time goes by and they begin to experiment with BT/UWP midi while still not throwing out their whole Midi legacy equipment. 

So this will mean having to switch between a a Yamaha BT midi adapter and my Korg USB nanopad. I take it the later will be MME. Wish I new that before ordering the Yamaha 3 weeks ago.
 

For example the FW-1884 discussed earlier with the UWP problem is a MIDI 4in/4out device, among other things ...
 
I don't think that the restriction applies to using multiple USB or BT MIDI devices, just that the drivers for each device need to be fully supported in UWP.

Kamikaze

abacab

Kamikaze
So this will mean having to switch between a a Yamaha BT midi adapter and my Korg USB nanopad. I take it the later will be MME. Wish I new that before ordering the Yamaha 3 weeks ago.
 

How did you reach that conclusion?  As far as I can tell, the Korg USB Nanopad is a single port MIDI device.  Why wouldn't it work with UWP?

CedricM
You answered your own question: "Sonar only allows selection of one MIDI driver mode at a time, either MME or UWP."
 

 
From this. I thought it was saying there are only 2 midi driver options. I'm quite happy to have reached the wrong conclusion, if that's the case.

That is true, there are only two MIDI driver options in Sonar settings.  Either MME or UWP.  You can only pick one at a time, and hopefully all of your devices will be happy with your choice!

Presently, the UWP Midi drivers have a number of serious issues.
 
(1) Device enumeration is faulty.
(2) You are not able to send SysEx commands on any port that does not end with "[0]" in its name.
(3) Bluetooth has problems with polyphony past a 6 note chord, notes stick on.
 
Push on Microsoft, these are not Sonar Midi issues!  Since the UWP MIDI API is all Microsoft will support moving forward, lots of folks need to make a lot of noise about this.  UWP is in a precarious position, developers are reluctant to move to it because it is not mature, so Microsoft has the impression there are no problems with it because no one is complaining.
 
UWP MIDI will be a good thing in the long term.  It's just that it doesn't have much visibility within Microsoft because it is getting so little use.