Windows support

[atsushieno]

Currently Windows version builds if we use Cmake vs2022 generator. There are various issues though:

• winmidi detection: currently there is no reliable way to detect whether Windows MIDI Services works or not. Because of this, plugin instantiation causes crashes. It is a known problem, likely a transient issue. [BUG]: Current Windows MIDI Services detection sample doesn't work with controlled feature rollout microsoft/MIDI#793
• A handful of VST3 plugins fail to instantiate (reports failure) or crash.
• Same goes for CLAP plugins.
• Plugin UI window size is a bit weird. Maybe it's short of the size of its window titlebar.

[atsushieno]

Currently Windows MIDI Services used by libremidi fails to initialize itself, which seems like some sort of bug at Microsoft and I don't plan to try hard to fix their problem:

Microsoft::Windows::Devices::Midi2::Initialization::MidiDesktopAppSdkInitializer::EnsureServiceAvailable() Microsoft.Windows.Devices.Midi2.Initialization.hpp:100
uapmd::LibreMidiIODevice::LibreMidiIODevice(basic_string<…>, basic_string<…>, basic_string<…>, basic_string<…>, unsigned long long) LibreMidiIODevice.cpp:34
uapmd::createLibreMidiIODevice(basic_string<…>, basic_string<…>, basic_string<…>, basic_string<…>, unsigned long long) MidiIODevice.cpp:148
uapmd::AppModel::enableUmpDevice(int, const std::string &) AppModel.cpp:284
`uapmd::AppModel::createPluginInstanceAsync'::`2'::<lambda_1>::operator()(int,int,basic_string<char,std::char_traits<char>,std::allocator<char> >) AppModel.cpp:177

[Psychlist1972]

Currently Windows MIDI Services used by libremidi fails to initialize itself, which seems like some sort of bug at Microsoft and I don't plan to try hard to fix their problem:

Microsoft::Windows::Devices::Midi2::Initialization::MidiDesktopAppSdkInitializer::EnsureServiceAvailable() Microsoft.Windows.Devices.Midi2.Initialization.hpp:100
uapmd::LibreMidiIODevice::LibreMidiIODevice(basic_string<…>, basic_string<…>, basic_string<…>, basic_string<…>, unsigned long long) LibreMidiIODevice.cpp:34
uapmd::createLibreMidiIODevice(basic_string<…>, basic_string<…>, basic_string<…>, basic_string<…>, unsigned long long) MidiIODevice.cpp:148
uapmd::AppModel::enableUmpDevice(int, const std::string &) AppModel.cpp:284
`uapmd::AppModel::createPluginInstanceAsync'::`2'::<lambda_1>::operator()(int,int,basic_string<char,std::char_traits<char>,std::allocator<char> >) AppModel.cpp:177

What actual error are you getting there? Is this on a system with Windows MIDI Services enabled as part of the rollout?

I'm not aware of any bugs in this check.

However, I also see "uap" here. Is this in a packaged application?
microsoft/MIDI#451

[atsushieno]

I guess you're saying the error I was seeing was actually some sort of wrapped exception which had the actual inner exception...?
In any case, the issue was indeed transient and stale now; the MIDI Service detection passes fine on my latest Windows Insider build.

The latest blocker is at libremidi - I didn't spend much time on Windows and didn't try implementing it by myself, but the issue is very clear.