Timing clock F8h being parsed in a sysex response

Bug reports
1

While working on the Zoom MS70 I noticed the patch dump which should be 146 bytes long, sometimes arrives as 147 bytes, scrambling the parsing attempt . Further investigation via Midi-Ox showed that the Zoom pedal consistently transmit 146 bytes, but the E1 sometimes receives 147. When I looked for the additional byte, I found the byte to be 0xF8, which is a real time sysex clock message. It appears randomly and sometimes not at all in the sysex string as seen by the E1.
But this should not happen.
This byte should not be considered as part of any sysex string, as it is allowed by MIDI 1.0 standard for Real-Time messages to be interleaved with a System Exclusive.

Could it be a fairly new bug?

2

What’s happening: both requests were done the same way, but the last response yielded a faulty additional byte F8h. The actual response coming out of Zoom was 146 bytes in both cases.
With that second response, anything parsed beyond byte 112 is faulty. The F8h byte occurs randomly and in different places.

image
image1077×697 37 KB

1 Like
3

I will look at this while working on the v3.7.0 beta.

1 Like