08-26-2021, 11:00 AM
(This post was last modified: 08-26-2021, 11:02 AM by fgeorgy.
Edit Reason: typo
)
No, it doesn't work for the synth I listed.
I don't use any special software such as Arturia (even if the MRCC should be agnostic to that).
Sending CC messages, PC messages, Note On, Note OFF work fine, always. This confirm that my routing is configured correctly on the MRCC. I suppose the sysex messages I sent are received by the synth, but it's the synth sysex responses that do not pass through the MRCC, probably because of some timing (some synth answer very fast, within 1-2 ms after having received a sysex request) or some buffer size limitation. I think is more time related than size related because, for example, the Hydrasynth responds very fast but send short messages. But it sends quite a lot of short sysex messages.
I expect the MRCC to be totally transparent and accept/forward any kind of MIDI message. If that is not possible then this is a big problem (at least for me). If you have some MIDI issue you can not be sure if it's your synth, your controller or the MRCC. This can quickly become hard to debug.
I don't use any special software such as Arturia (even if the MRCC should be agnostic to that).
Sending CC messages, PC messages, Note On, Note OFF work fine, always. This confirm that my routing is configured correctly on the MRCC. I suppose the sysex messages I sent are received by the synth, but it's the synth sysex responses that do not pass through the MRCC, probably because of some timing (some synth answer very fast, within 1-2 ms after having received a sysex request) or some buffer size limitation. I think is more time related than size related because, for example, the Hydrasynth responds very fast but send short messages. But it sends quite a lot of short sysex messages.
I expect the MRCC to be totally transparent and accept/forward any kind of MIDI message. If that is not possible then this is a big problem (at least for me). If you have some MIDI issue you can not be sure if it's your synth, your controller or the MRCC. This can quickly become hard to debug.