Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[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

Open
Psychlist1972 opened this issue Jan 13, 2025 · 0 comments
Assignees
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working

Comments

@Psychlist1972
Copy link
Contributor

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.

@Psychlist1972 Psychlist1972 added area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working labels Jan 13, 2025
@Psychlist1972 Psychlist1972 self-assigned this Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants