[BUG] SysEx Continue Message conversion issue

[sat-okada]

Describe the bug
If I send a 1byte/2bytes length System Exclusive Continue message in MT3 format, output wrong conversion results.

To Reproduce
1.Set the Roland UM-ONE mk2 to class-compliant mode and attach it to the UM-ONE to PC.
2.Driver uses UsbMidi2.
3.Start up two consoles, One is a monitor.

midi ep monitor --verbose

Send on the other

midi ep send 0x30160102 0x03040506
midi ep send 0x30210700 0x00000000
midi ep send 0x30210800 0x00000000
midi ep send 0x3022090A 0x00000000

4.Monitor receives wrong results.

Expected behavior
The following data should be received:
0x30120102 0x00000000
0x30230304 0x05000000
0x30230607 0x08000000

For the remaining 2 bytes (09, 0A), wait for the next SxsEx Continue message and get the first 1 byte to complete the SysEx Continue data.

Installer Name or Version
・Windows.MIDI.Services.In-Box.Service.-.1.0.1-preview.7.24305.1438-x64.exe
・Windows.MIDI.Services.Tools.and.SDKs.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 Pro Insider Preview Build 27729.rs_prerelease.241011-1428

Device information, if this is with an external MIDI device:
Roland UM-ONE mk2

Application Information
midi.exe console app.