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.

Sign up for GitHub

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

Jump to bottom

[BUG] WinMM calls may fail if the calling thread hasn't been CoInitialized #467

Open
Psychlist1972 opened this issue Dec 16, 2024 · 0 comments
Open

[BUG] WinMM calls may fail if the calling thread hasn't been CoInitialized #467

Psychlist1972 opened this issue Dec 16, 2024 · 0 comments
Assignees
@Psychlist1972 @garydan42
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working

Comments

@Psychlist1972
Copy link
Contributor

If an app uses the new service through the MIDI 1.0 WinMM API, and the calling thread hasn't been CoInitialized (or winrt equivalent), the call to the MidiSrv Transport will fail.

Tracking here as a known issue in case others run across it. Gary is working on how to resolve.
@Psychlist1972 Psychlist1972 added area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Psychlist1972 Psychlist1972

@garydan42 garydan42

Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working
Projects
Windows MIDI Services
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Psychlist1972 @garydan42