-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Labels
area-service-or-api 🖥️Related to the Windows Service, core API, abstractions, etc.Related to the Windows Service, core API, abstractions, etc.area-winmmwmdaud2.drv or other WinMM issuewmdaud2.drv or other WinMM issuebug 🐞Something isn't workingSomething isn't workingfixed-awaiting-public-release 🕙Fixed in our internal builds. Waiting to make its way to a public release.Fixed in our internal builds. Waiting to make its way to a public release.
Description
Windows Version
Build 27959.br_release.250926-1432
Service Installation Method
GitHub
SDK version, if appropriate
1.0.13-preview.13.192
Location
Application using WinMM MIDI 1.0 (Classic API)
Type of bug
Application not working as expected
Steps to reproduce
- Attach any MIDI device to a PC running MidiSrv.
- Launch the attached MMEQueryDeviceInterface.exe.
This application calls midiInMessage() API with the DRV_QUERYDEVICEINTERFACE message to retrieve the device-interface name.
Although calling midiInMessage(DRV_QUERYDEVICEINTERFACESIZE) returns non-zero value, midiInMessage(DRV_QUERYDEVICEINTERFACE) returns an empty string.
MMEQueryDeviceInterface_20251008.zip
Expected behavior
Both midiInMessage(DRV_QUERYDEVICEINTERFACE) and midiOutMessage(DRV_QUERYDEVICEINTERFACE) should return a non-empty string representing the device-interface name.
Additional notes
No response
Metadata
Metadata
Assignees
Labels
area-service-or-api 🖥️Related to the Windows Service, core API, abstractions, etc.Related to the Windows Service, core API, abstractions, etc.area-winmmwmdaud2.drv or other WinMM issuewmdaud2.drv or other WinMM issuebug 🐞Something isn't workingSomething isn't workingfixed-awaiting-public-release 🕙Fixed in our internal builds. Waiting to make its way to a public release.Fixed in our internal builds. Waiting to make its way to a public release.