I have a MODX6 since a few days, and I already ran into the same issue.
It looks to me as if the MODX tries to send data on the first USB-MIDI output port, and if this data is not consumed, then the MODX will block the reception of data on the corresponding USB-MIDI input port.
That looks like an issue with the MODX. When using amidi with the -S option (and not the -d option), then it will only open the USB-MIDI output port (on the host side). With MIDI 1.0, USB-MIDI input and output ports should be independent. However, that does not seem to be the case on the MODX.
I have not checked why the MODX also seems to skip messages when using amidi with both the -S and -d options. It seems to work occasionally, which makes me think that there is a race condition on the MODX.
It looks to me as if the MODX tries to send data on the first USB-MIDI output port, and if this data is not consumed, then the MODX will block the reception of data on the corresponding USB-MIDI input port.
That looks like an issue with the MODX. When using amidi with the -S option (and not the -d option), then it will only open the USB-MIDI output port (on the host side). With MIDI 1.0, USB-MIDI input and output ports should be independent. However, that does not seem to be the case on the MODX.
I have not checked why the MODX also seems to skip messages when using amidi with both the -S and -d options. It seems to work occasionally, which makes me think that there is a race condition on the MODX.
Statistics: Posted by mx49 — Sat Jan 20, 2024 12:24 pm