[BUG] Service is very slow to start up (or reports as failed to start up) when there are multiple MIDI 1.0 ports being created #487
Labels
area-service-or-api 🖥️
Related to the Windows Service, core API, abstractions, etc.
bug 🐞
Something isn't working
Describe the bug
The enumeration of and creation of WinMM MIDI 1.0 compatible devices, including their port numbers, takes a long time at the moment and impacts service startup time. As a result, tools like sc.exe sometimes report that the service was unable to start, even though it does a few seconds later.
Pete and Gary to investigate other ways to handle the port numbering to avoid this startup delay. Documenting here as a known issue that will be present in the port-NAMM Windows Insider Canary release.
The text was updated successfully, but these errors were encountered: