Troubleshooting - 2 MRCCs, midi clock, ?

[Nelson Baboon]

Hey Nelson, I'm sorry to hear that mate, it seems like you're looking at the situation with the right things in mind, (what changed etc.). As for that mode, let's call it Remote Routing Mode for now. When this (Remote Routing is unresponsive) is happening is everything else on the MRCCs still working? Does pressing the Y guy button cause the remote routings to show up yellow on the LEDs still, so it looks like you should be able to make changes?

We have seen failures with one unit when sending to a or from USB host port device that isn't fully compatible with the MRCC, I have had the Digitakt cause my MRCC to freeze for instance, and when that happens in a scenario with 2 MRCCs I could imagine it requiring a reboot to get things back up and running between them. In my case, the Digitakt didn't work via USB at all initially, but their newest FW update seems to have changed that, and now it works...if I don't send clock or whatever the triggering issue was. In the past I think we were seeing a similar thing with the OXI we were testing, and were able to send the Dev a message as to what error we had found to be causing the issue in their USB implementation and I think they were able to get it solved in a firmware update (It may be that the issue was partially addressed, I don't have one so it's not something I ever experienced personally, the situation was related to me anecdotally). The DIN ports are almost 100% guaranteed not to be problematic, so that will help us narrow down the issue hopefully, but what are the devices connected to USB that you were sending to?

I am always available to set up a video call if you would like to have an extra set of eyes on the issue, feel free to send me an email at Support@conductivelabs.com with your availability and timezone and I can send you an invite at a time that works for us both.

Jesse

I appreciate the response. I should reiterate that I don't know for sure whether the components that i mentioned were all that were involved with the issue. I know someone who tried something similar with the hapax and didn't replicate this. I do know that since reconnecting the hapax with a din connection, things have been ok, and i already had pretty much resolved that simply a midi clock between the 2 mrccs wasn't the issue. As far as the 'y guy' - the connections seemed to dissove....at first stuff didn't seem to be working (wish i had a better memory), and then each mrcc wouldn't see the other when i tried to establish the Y connection, and ultimately the mrccs were frozen. BUT, i am disinclined to spend more time and stress on this. ultimately, when i am done with work, i want to make music, and i think that my biggest point is that what i think is needed is a better way to troubleshoot mrccs especially in complex set ups. Whatever can be done with some kind of computer application that would look at the active connections, etc. It is just difficult and time consuming to troubleshoot. For me, at least. While i much prefer the mrcc midi hook up, when using a midi interface, it is easier to see all of the active connections (because, well, they are set up in Live, for instance). I understand that it's built into the concept, but i am still not convinced that a computer application is impossible.