View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001115||OpenMPT||Audio I/O||public||2018-04-18 12:34||2023-09-11 12:22|
|Reporter||Saga Musix||Assigned To|
|Target Version||OpenMPT 1.32 / libopenmpt 0.8 (goals)|
|Summary||0001115: Support Windows 10 UWP MIDI API|
The new UWP MIDI API in Windows 10 supports features such MIDI over Bluetooth and being able to open a port from more than one application at the same time.
|Tags||No tags attached.|
|Has the bug occurred in previous versions?|
|Tested code revision (in case you know it)|
https://github.com/jcelerier/libremidi/ has a Windows UWP backend
Support for RtMidi was also merged recently: https://github.com/thestk/rtmidi/pull/299
RtMidi has been updated to v6.0.0 in our repository, which means that UWP support can now be enabled for testing purposes.
An odd side effect of turning on UWP MIDI support in RtMidi makes the
It appears that output port names (but not input port names, mysteriously!) from devices that only implement the MM API are butchered when they are exposed through the UWP API. RtMidi tries to work around this but it doesn't always succeed. This is definitely one reason for not completely replacing MM with UWP when both are available.
|2018-04-18 12:34||Saga Musix||New Issue|
|2021-11-17 17:26||manx||Target Version||OpenMPT 1.?? (long term goals) => OpenMPT 1.31.01.00 / libopenmpt 0.7.0 (upgrade first)|
|2023-04-10 08:24||manx||Target Version||OpenMPT 1.31.01.00 / libopenmpt 0.7.0 (upgrade first) => OpenMPT 1.32 / libopenmpt 0.8 (goals)|
|2023-07-28 15:48||manx||Note Added: 0005767|
|2023-07-28 15:59||Saga Musix||Note Added: 0005768|
|2023-09-10 17:24||Saga Musix||Note Added: 0005779|
|2023-09-10 19:08||Saga Musix||Note Added: 0005780|
|2023-09-11 12:22||Saga Musix||Note Added: 0005781|