micdah
commented
1 year ago Can you provide some code to reproduce the issue or similar?
I believe I should get entire MIDI messages from the underlying rtmidi library, and when I decode the data I look for the status byte and react to a SysExStart:
internal const byte SysExStart = 0b1111_0000;
internal const byte SysExEnd = 0b1111_0111;In which case we:
case Midi.Status.SysExStart:
if (SysExMessage.TryDecode(message, out var sysExMessage))
SysEx?.Invoke(this, in sysExMessage);
break;Which simply does
internal static bool TryDecode(byte[] message, out SysExMessage msg)
{
if (message.Length <= 1)
{
Log.Error("Incorrect number of bytes ({Length}) received for SysEx message", message.Length);
msg = default;
return false;
}
if (message[0] != Midi.Status.SysExStart || message[message.Length - 1] != Midi.Status.SysExEnd)
{
Log.Error("Not a valid SysEx message received for SysEx message", message.Length);
msg = default;
return false;
}
msg = new SysExMessage
(
message
);
return true;
}So if the messages was truncated, I expect there should be an error log as the last byte wasn't the expected SysExEnd, or if only the start byte was received we should have seen an error on receiving only 1 byte.
It uses Serilog, so you can enable output by configuring Serilog in your code.
MacroDX
Hi there, I tried to receive a SysEx data dump with a size of 18108 bytes. Waiting for the callback always results in a timeout which suggests that the message is swallowed in an undelaying layer. On the one hand I have not found an option to set a buffer size and on the one hand I would have expected for the callback to be invoked multiple times until all packages have been received. Is that a known issue? And is there anything that you or I can do? Thanks