Skip to content

[BUG]: Opening removed WinMM port on new stack returns different error than on Windows 10 #970

@Psychlist1972

Description

@Psychlist1972

From Discord:

On Windows 10, attempting to use an already open HMIDIOUT in midiOutShortMsg for a device that has been surprise unplugged results in MMSYSERR_NODRIVER. With the new stack on Win 11, the same scenario results in MMSYSERR_ERROR, unspecified error. I think a different MMRESULT would be more applicable, if possible.

Thread:
https://discord.com/channels/980245825202552942/1475714364135837799/1490751654474154107

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions