Older Firmware Releases

[HunniBunni]

Possible Update: Is it possible for a USB cable to “partially work.” I assumed a USB cable always fully works, or fully doesn’t work (I don’t mean intermittently). For example: Can a USB cable show a device ID to my computer, but be broken/malfunctioning enough to not pass through other data such as MIDI notes?

I eventually noticed that the issue of passing cross-routed MIDI to the computer seems to only exist with one USB cable (going from the MRCC_? to the computer), yet seems to be fine with another USB cable. However, with both cables, the ports show up in Cubase as active whether or not the issue is present. (That behavior in Cubase updates in real-time, and those ports immediately disappear when you unplug the USB cable, which is why at first the question of a cable issue didn’t come to mind, since on the problem cable, it always shows as plugged in)

Ok. So I'm still having stranger behavior.

I am still trying to get my MRCC working reliably in a pretty basic sense, so I have not tried utilizing many features to control the troubleshooting.

Basically All I am setting up is a bunch of DIM and USB midi devices, all of which are compatible with the MRCC. Many of them are connected to Input and Outputs, some just one or the other.

They have all been routed to their respective PC virtual port that I have labeled in Cubase 11.

My MRCCs are labeled MRCC_C and MRCC_D to avoid the ? thing.

I am usually using Cubase as the midi clock source (but sometimes my RC505 looper). I am only sending midi clock to a few devices that have parameters that respond to tempo controlled elements via midi clock.

While my MRCCs are connected by RJ45, I'm not cross routing anything to keep things simple.

Many of my inputs and outputs work as expected, showing activity on the MRCC and triggering things as expected in Cubase.



Right now however;
I am not getting MIDI data showing for the MRCC USB inputs or the PC ports they're routed to..however, if I take any of those midi devices connected to the MRCC by USB, and plug them into the computer USB hubs, they trigger my midi synths in Cubase immediately. This USB port issue has only been a problem since i installed the latest BETA firmware.

Also, Turning on one of the MRCCs turns on super super slowly, populating the display word by word for several minutes, unless I unplug the PC USB from the MRCC. The top MRCC is receiving midi clock for 3 channels. Sometimes it seems like stopping clock from going to the MRCC from Cubase alleviates this problem, but that's been hard to replicate consistently enough to be certain of.

The above issues have been consistent issues that persist through restarts of the MRCCs, cubase, the devices themselves, and my computer. Any suggestions? :/