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] MIDI Service cannot be restarted if there are open WinMM Connections #555

Open
Psychlist1972 opened this issue Feb 20, 2025 · 1 comment
Assignees
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. area-winmm wmdaud2.drv or other WinMM issue bug 🐞 Something isn't working

Comments

@Psychlist1972
Copy link
Contributor

Psychlist1972 commented Feb 20, 2025

If there's a winmm connection through wdmaud2.drv (a DAW, or the midi1monitor app, for example), the MIDI Service will not shut down/restart.

This problem does not happen with apps that are using the MIDI 2 SDK/API directly.

This is compounded in cases where we have something like the Native Instruments Komplete Kontrol service, which appears to hold a connection open. It's a Windows Service, so it's long-running.

@Psychlist1972 Psychlist1972 added area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. area-winmm wmdaud2.drv or other WinMM issue bug 🐞 Something isn't working labels Feb 20, 2025
@Psychlist1972
Copy link
Contributor Author

Possibly related: #463

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. area-winmm wmdaud2.drv or other WinMM issue bug 🐞 Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants