Skip to content

[BUG] Input Port of MME MIDI app does not work after receiving messages of Timing Clock (F8) #445

Open
@tosugawara

Description

Describe the bug
Once MME MIDI app receive F8 (or F1), their input ports cannot work.

To Reproduce

  1. Attach KORG Keystage (MIDI Keyboard product) to PC.
  2. Update the MIDI driver to the USB MIDI 2.0 driver (UsbMidi2.sys).
  3. Open the Pocket MIDI 64bit and choose MidiSrv enumerated ports ("KORG INC. Keystage I-1, O-1).
  4. Keystage transmits Timing Clock messages, so F8 messages are displayed on Input Port monitor of Pocket MIDI (as Group 0 messages on MIDI 2.0 Monitor).
    Image
  5. Press keyboards of Keystage to transmit Note On message, many unrelated messages are displayed on input port monitor, and becomes input ports unusable.Image

notes:

  • In the same way, on other MIDI 1.0 devices having MIDI Interface function (for example, I tried on KORG KP3+), once they receive F8 (or F1), their input ports cannot work.
  • While receiving only F8 messages after the input port is opened, the port is working until other messages.
  • Output ports seems not to be affected by F8.
  • It seems F1 (Time Code Quarter Frame) message causes the same problem.

Expected behavior
Input ports keep to work right, as on the USB MIDI 1.0 driver (KSA).

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 Keystage, KORG KP3+

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

Additional context
I don't know if it's related directly, sometimes MidiService stops after this issue happened,

Metadata

Labels

area-service-or-api 🖥️Related to the Windows Service, core API, abstractions, etc.bug 🐞Something isn't working

Type

Projects

  • Status

    No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions