USB compatible (or not) devices list

[User]

Thank you, it seems my config was incorrect and USB connection works now, thank you. I just need to configure it to avoid loops, because its not only one sequencer and there are few synths and controllers and I have got freeze when play.

[RadekPilich]

How is the USB host supposed to work on MRCC? Does it only work for MIDI?
What about if the USB device has audio interface and internal HDD?
Can these still be recognized and utilized by a computer connected to the MRCC if lucky?

[Dark Waves]

How is the USB host supposed to work on MRCC? Does it only work for MIDI?
What about if the USB device has audio interface and internal HDD?
Can these still be recognized and utilized by a computer connected to the MRCC if lucky?

Unless I'm severely mistaken, only MIDI data is passed through the MRCC.

[Jesse Johannesen]

Just works with MIDI. It will not act as a USB hub for an attached computer as it doesn't pass any USB data, it only converts to MIDI and sends that. No HDD, and no audio interface on board.
Hope that clears things up, let me know if you have any other Q's.

[Lizard of Oz]

I just tried the Polyend Synth with the MRCC, and it doesn't seem to work. 

When I connect the Synth to one of the USB ports, it powers up reliably, and I can route MIDI to that port. 

However. the LED next to the physical USB port on the MRCC does not light up, and the Synth does not receive MIDI messages, and the MCRR does not indicate that it receives MIDI messages from the Synth.

I have tried other devices on the same USB port, and they work, so it's not the port, I would guess. What can be done to fix this?

[Lizard of Oz]

Some more info on the Polyend Synth: When I connect it to my Mac with the same cable, it sends and receives MIDI just fine, no driver necessary. I measured the current, I could not get it to draw more than 455mA, so it is within what the MRCC can provide.

[Jesse Johannesen]

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/