[BUG] Input Port of MME MIDI app passes some kind of messages from Group except index 0 on the same MIDI 1.0 device.

[tosugawara]

Describe the bug
Using USB MIDI 1.0 device having multiple MIDI input ports on MME MIDI app, selected Input port, which is Group 1 (Index 0), passes some messages from other Group number port.

To Reproduce

1. Attach KORG minilogue-xd (keyboard synthesizer) to PC.

2. Update the MIDI driver to the USB MIDI 2.0 driver (UsbMidi2.sys).

3. This synthesizer has 2 pair of MIDI In/Out ports, and its virtual Group Terminal Blocks indexed by UsbMidi2 driver is this list. Group 1 ports "MIDI IN, MIDI OUT" are for MIDI interface through 5-pin DIN jacks.
   

4. Open the Pocket MIDI 64bit and choose MidiSrv enumerated ports ("KORG INC. midilogue-xd I-1, O-1).

5. Timing Clock messages are displayed on input port monitor although nothing is connected to the MIDI IN jack. And press PLAY button of sequencer of minilogue-xd, Start (FA) and Stop (FC) messages are displayed. Other messages like note messages from keyboard seem not to be passed.
   

Expected behavior
No messages are displayed on input port monitor.

Installer Name or Version
Windows.MIDI.Services.In-Box.Service.-.1.0.1-preview.7.24305.1438-x64.exe
USB MIDI 2.0 class driver (USBMIDI2_10.0.1.7.x64.zip)

Desktop (please complete the following information):
OS: Windows 11 24H2 build 26120.2415 (Insider Dev channel)

Device information, if this is with an external MIDI device:
KORG minilogue-xd, KORG monologue

Application Information
MORSON Pocket MIDI 64-bit
https://www.morson.jp/pocketmidi-webpage/

Additional context
Add any other context about the problem here.

[Psychlist1972]

Thanks. This is a known limitation of this release. All incoming and outgoing data has a hard-coded Group Index 0

Dup of #418