[NAME_BUG]: WinMM Port names of MIDI 1.0 devices using MIDI 2.0 driver are partly irregular

[tosugawara]

Windows Version

Canary Build 27808

Service Installation Method

GitHub

Location

App using WinMM MIDI 1.0 (Classic API)

Device Make and Model

KORG minilogue xd (having 2-in / 2-out ports), KORG nanoKEY2 (having 1-in / 1-out ports) etc.

Name(s) you saw

minilogue xd: input: "minilogue xd _ MIDI IN", "minilogue xd" output: "minilogue xd", "minilogue xd" nanoKEY2: input: "nanoKEY2 _ KEYBOARD", output: "nanoKEY2"

Name(s) you expected

minilogue xd: input: "minilogue xd _ MIDI IN", "minilogue xd _ KBD/KNOB" output: "minilogue xd _ MIDI OUT", "minilogue xd _ SOUND" nanoKEY2: input: "nanoKEY2 _ KEYBOARD", output: "nanoKEY2 _ CTRL"

MIDI KS Info Output

MIDI endpoint properties

minilogue xd:

nanoKEY2:

Additional notes

On WinMM Port names of MIDI 1.0 devices using MIDI 2.0 driver, the name of first input port seems to be same as GTB name on ep properties, and others (including output ports) are same as product name.

MIDI Settings App port info.
minilogue xd:

nanoKEY2:

Pocket MIDI port display:
input:

output:

Is it correct, or intended?

[Psychlist1972]

Thanks for reporting. WinMM Naming code in the Canary builds is not yet finished.

I have a nanokey2 here. This is a good reminder for me to test it again with the new code before releasing.

[Psychlist1972]

This should be fixed in the latest preview on Discord. Please verify. (Note that midi endpoint properties now shows associated midi 1 ports, rather than group terminal blocks, for MIDI 1 devices)