[solved] Receiving more bytes than being sent

Hello,

Using

Send SX (Win 7) --> USB --> MIDI Sport 2x2 --> MIDI Cables --> Akai Advance 49 --> USB --> Send SX (Win 10)


I have MIDI sport 2x2 as my in and out on Win 7.
I have MIDI keyboard as my in and out on Win 10.

I am sending from win 7

F0 47 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09 00 F7

and I am receiving on win 10

F0 00 00 47 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 06 00 00 07 00 00 08 00 00 09 00 00 00 00 00 F7

I have done all the standard troubleshooting recommendations. I changed out MIDI sport, USB, MIDI cables, and MIDI Keyboard and get the same result..used many different combination of Send SX settings and still have this problem. Any ideas on how to troubleshoot this?

Hi,
sorry for the late reply. In general, your setup should work fine. I have not seen such behavior before!
Maybe you can simplify the setup for testing to see where these extra 00 bytes are inserted?
Does it happen when you connect everything to the Win7 computer? How about the Win10 computer?

One thing we know is that some (USB) MIDI interfaces and some MIDI drivers have problems with System Exclusive messages.

SendSX tries to always receive ALL data, even if malformed. For that, it also displays data which is marked as "corrupt" by Windows. Maybe the inserted 00 bytes are such corrupt bytes. But that still doesn't explain why they occur.

Any further information is appreciated!

Regards,
Florian

This turned out to be a FW issue with the keyboards I was using. Thanks for the reply.