07-24-2024, 12:47 PM
I can confirm that sysex to more than one destination is *generally* hosed.
You seem to be able to successfully send to multiple destinations if the destinations are one each of USB, PC, ports 1-5, and ports 6-10
I was using a Korg DL8000R dump all which is 18468 bytes
In 1 -> USB A, PC (3), and port 1 was successful.
In 1 -> DIN ports 5,6 consistently dropped 1 byte.
In 1 -> DIN ports 5 and 7 dropped many many bytes.
and so on.
Basically there either needs to be better/more buffering of sysex inside the MRCC or users have to restrict sysex transfers to a 1 to 1 mapping for ports (in general).
Yes, I know that sending sysex to multiple ports is most likely not what you want to do in 99.9% of the cases, but if you happened to have more than 1 of the same device and wanted to send sysex to them both, this would be a legitimate use case. In any scenario, you would expect the sysex buffer to be transferred cleanly no matter how many destinations were selected.
You seem to be able to successfully send to multiple destinations if the destinations are one each of USB, PC, ports 1-5, and ports 6-10
I was using a Korg DL8000R dump all which is 18468 bytes
In 1 -> USB A, PC (3), and port 1 was successful.
In 1 -> DIN ports 5,6 consistently dropped 1 byte.
In 1 -> DIN ports 5 and 7 dropped many many bytes.
and so on.
Basically there either needs to be better/more buffering of sysex inside the MRCC or users have to restrict sysex transfers to a 1 to 1 mapping for ports (in general).
Yes, I know that sending sysex to multiple ports is most likely not what you want to do in 99.9% of the cases, but if you happened to have more than 1 of the same device and wanted to send sysex to them both, this would be a legitimate use case. In any scenario, you would expect the sysex buffer to be transferred cleanly no matter how many destinations were selected.