Yesterday I tried connecting my Synth to my MRCC via USB, and doesn’t seem to register as MIDI device.
The Synth 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, which indicates that it is not recognized as a class compliant MIDI device.
Synth does not receive MIDI messages, and the MCRR does not indicate that it receives any MIDI messages from the Synth when I play the GRID.
I have tried other USB devices on the same USB port, and they work, so it’s not a defective port on the MRCC. Also I connected my Synth with the same cable to my Mac, and MIDI over USB works just fine here.
Also I measured the current the Synth draws from the USB ports, and I could not get it to draw more than 455mA, so it is within the 0.5A the MRCC can provide per port.
For the time being, I’m using DIN MIDI. I had one free port left anyway, but USB MIDI should work, I already asked on the Conductive Labs forum, but that is typically a bit slow to respond. Maybe someone here has an idea what I could try?
I have the MRCC but only the tracker and play +. I use the 3.5 type b without issue. I’ll try the USB and see if I can get it to work. I know it’s not using Synth but shouldn’t be that different.
Thanks. Watch out for the LED right next to the port you plug it into, that should light up once the Play+ has finished booting, to indicate the that it been identified as a MIDI device.
Play + will not work with USB on MRCC. I power it on and no green light on MRCC.
Tracker + will work. I can get transport out. I did not get notes to come out but not as familiar with the Tracker + to that like the Play +.
Without having the Synth, I can’t say for certain but based on my unscientific testing, sounds like it could be something with the Synth needing more juice than MRCC can push. Strange Tracker Plus works but not Play + Recommend to use the 3.5 Type B ports on the MRCC, provided you have the “big boy” MRCC.
Hey, thanks for taking the time to test this. So whatever it is, it looks like it’s possible that a fix will fix this for more Polyend devices, not just for the synth.
Now i wonder what is the next step in figuring out where that fix needs to happen, in the Synth or in the MRCC.
I don’t think that is the case, I used an USB meter (like the one below) to measure how much the Synth actually draws when the CPU is overloaded, and it’s still less that what the MRCC manual claims one USB port can deliver.
Do any of you have one of those USB y-cables that allows you to power things from another source? It might be worth giving it a try, to find out whether it’s a power issue.
Is this supposed to be an actual wish? Or is this just a general discussion topic?
If it’s a wish, let me know. because you removed the mandatory template/structure.
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 loo
So they say it’s a bug in the Synth.
@Sandroid should that thread be converted into a bug, or is a separate bug more appropriate?
I’ve dealt with similar issues with some midi devices not working as expected with the MRCC. The response conductive labs gave me was the device needs to be class compliant midi for it to work. I relayed this info to the developer of the device I had issues with and they found their device wasn’t actually class compliant so they made firmware changes to ensure it was and then it worked great with the MRCC. With that said I’m wondering if the Polyend devices are class compliant?
Polyend Tracker +, Play +, yes. Polyend Synth, midi only over USB when connecting to the iPad. In that case, yes, these devices are in context of the iPad. With that being said in this case, there is the option to run 3.5 midi into the MRCC type B 3.5 midi and that works great.
Apparently these also don’t work with the MRCC. I’m not saying that this might not be a problem with the MRCC, but how do you know they are class compliant?
Class compliance is not defined in the context of specific operating systems or devices. So it is not class compliant, but it works with certain devices.
Either Polyend needs to get a MRCC in their lab or Conductive Labs gets Polyend devices in their lab to debug/test. Short of that happening, we are not going to change anything here. As there are options to make it work as mentioned earlier, I don’t see either happening soon. While I don’t know either companies road map, this doesn’t seem high on the triage list. Stranger things have happened. For now, consider using 3.5, as that works great. Choice is yours.
Agreed. But Still I wonder where you get the information from that Polyend Tracker +, and Play + are class compliant? I found no mention of this anywhere.
