12-21-2024, 09:14 AM
Hey Lizard,
The MRCC host ports nominally work with devices that are MIDI Class Compliant, however USB seems to be particularly complicated to apply correctly, and we often see devices that claim to be class compliant which still have incompatibilities due to the way they were implemented. It's not something we can change usually since it is to do with the device trying to connect, but in some cases where we have access to the device in the lab we have been able to sniff out what is going on and let the dev know where to look. In this case we do not have access to the synth, so that will not be an option, (unless that changes).
In the mean time I will ask Darryl to add the Polyend Synth to our MRCC Host Compatibility Tracker so the incompatibility is documented.
By the way you can take a look at that list here:
https://conductivelabs.com/mrcc-usb-host...y-tracker/
The MRCC host ports nominally work with devices that are MIDI Class Compliant, however USB seems to be particularly complicated to apply correctly, and we often see devices that claim to be class compliant which still have incompatibilities due to the way they were implemented. It's not something we can change usually since it is to do with the device trying to connect, but in some cases where we have access to the device in the lab we have been able to sniff out what is going on and let the dev know where to look. In this case we do not have access to the synth, so that will not be an option, (unless that changes).
In the mean time I will ask Darryl to add the Polyend Synth to our MRCC Host Compatibility Tracker so the incompatibility is documented.
By the way you can take a look at that list here:
https://conductivelabs.com/mrcc-usb-host...y-tracker/