Bug: MRCC stops creating new routes

[ilmai]

I've encountered this twice now: for an unknown reason, MRCC stops creating new routes until I power cycle. Routes can still be removed and the interface is otherwise responsive, but new routes simply don't get created.

This is on latest firmware (071)

---

Actually, this situation has more symptoms: MRCC stops routing events when this happens. Interface does stay responsive though you can't create routes.

[Jesse Johannesen]

It sounds to me like you may be hitting the limit of routings (I think it's either 48 or 44) after which no more routings can be created. You mention the MRCC stops routing events, do you mean all the connections which are already routed? If so this may be something else, what should be happening is if you hit the max, the device no longer routes new connections, but otherwise behaves normally. If you don't have 48 (or 44, whichever it is) routings connected when you experience these symptoms that would be another indicator that somethings else may be at play. Maybe send me an email to support@conductivelabs.com with a followup and we can try and see if I can get mine to do it.
Jesse

[ekkomouse]

What are you considering a routing? I’m not aware of this in the manual.

Is a routing considered towards the limitation only midi in to midi out? Or does that limitation also consider port in/out filters, mods, etc? 

Is that limitation doubled when you have a second MRCC or increased with the remote7?

[Jezric]

I just ran into this limitation. I wasn't aware that there was a limit to how many port routes you could setup. I am using all 6 midi din inputs, all 4 usb inputs and 8 of the midi out dins and I see that I cannot setup routes between all the ports I need.

Is this a limitation due to the software design or something else, because I would think that with this many ins/outs available, one would be able to setup routes between all of them simultaneously. But you can't, it just stops allowing you to enable additional outputs once it runs out of routes.

The only way around this I can see for me at least is merging inputs or outputs using external midi mergers before going into the MRCC so that I can stay within the routing limit, but to me that sort of defeats the whole purpose of the MRCC (i.e. to be able to handle all of my gear routing based on the physical inputs and outputs) and also then doesn't allow me any filtering etc. between those merged devices.

Is there any way around this? It would be nice to hear from the devs on this.

Thanks

[Jesse Johannesen]

As I mentioned above, there is currently a limit of (I believe it's) 48 routings per patch. We ran into some unknown instability when this number is increased, and we are looking into figuring that out, but the cause hasn't been illuminated yet. It is at the top of our list for potential problems to solve, though. I will make another push and see if I can get Steve to look into it again soon.

---

A routing is any connection from one input to one output, or in other words: anywhere you can put a modifier.

[Jezric]

As I mentioned above, there is currently a limit of (I believe it's) 48 routings per patch. We ran into some unknown instability when this number is increased, and we are looking into figuring that out, but the cause hasn't been illuminated yet. It is at the top of our list for potential problems to solve, though. I will make another push and see if I can get Steve to look into it again soon.

---

A routing is any connection from one input to one output, or in other words: anywhere you can put a modifier.

Thanks Jesse. Yeah, it says nothing about this in the manual from what I have found. Would have been nice to know before investing in this and thinking I was hitting some sort of bug.  

I also submitted a support ticket before seeing this reply.

Looks like my only option is to add MIDI mergers and splitters to my setup (which is what I thought I was avoiding by using the MRCC).

[oltec_modular]

Are you serious guys? I've just purchased MRCC, Remote and two Xpandrs, tried to configure routes to all my stuff, it took HOURS, and then realised there's LIMIT for max routes? There NO single word about that in manual! There is no notification about that on MRCC itself! Why do you even sell expanders if we can't have enough routes? How can you sell product with such serious LIMITATION (it's completely unusable for my setup) without even mention it in manual or in product feature page??? I am completely pissed off, last firmware upgrade almost a year ago...

[DesmondWatson]

I totally get your frustration, really. MRCC has this route limit (exactly 64), and yeah, they don’t make it clear in the manual. I had a similar problem too, but I learned it’s a hardware-software limit. With complex setups, it’s best to test if routes are even doable.

And hey, it might help to ask support – maybe they’ll tweak it in an update, though yeah, it’s been ages since the last one...  :-)

[SteveECrane]

I've recently acquired an MRCC and a remote expander in order to remove all my Kenton MIDI Merge and Thru boxes from my setup such that I can make multiple routes and efficiently route MIDI Clock.

I'm currently on day 5 of trying (and failing) to create my required routes and veered into the forums for some advice, as I simply cannot create any additional routes and I'm nowhere near finished!

I'm also rebooting my (updated) MRCC because it's locking up so frequently that it's getting tiresome.

The routing limitations as mentioned above weren't detailed anywhere else that I can find prior to purchase (and are still nowhere to be seen now!) and, if true, I am going to be seriously e££ed off given all the hyperbolic promises mentioned in every single piece of promotional literature I've read from Conductive Labs.  Hopefully their unfounded ... especially given the UK price of this!!!

I've a relatively complex setup and the MRCC was meant to be the single solution to this and the complex MIDI tree I had previously created using an ageing MotU MIDI Express XT / Esi M8U Ex and the aforementioned Kenton units.

This (potential) limitation requires a definitive post by the manufacturer (and a clarification from the firmware developer about whether it's fatal or curable) not to mention a 'sticky' post on the forum and somewhere prevalent on their website before any other unsuspecting (potential) customer is lured in by the sales rhetoric.

Clarity, please...!  A definitive statement is required here.

[Jesse Johannesen]

Yes the limit is 50 routings per preset, and it's mentioned under device specifications on our main page for the device. I'm so sorry that limitation has been causing you problems. If you are experiencing lock ups it is likely either a USB device that isn't fully compatible, or a MIDI loop. We try to keep an up to date list of device compatibility reports from users, you can find that here:
https://conductivelabs.com/mrcc-usb-host...y-tracker/

If you need more than 50 routings, it will likely require that you utilize a few different presets for different use cases, so that in a given use case you can load up a preset with all the needed routings for that job.

If you want some assistance I may be available to help you strategize if you want to draw up a detailed diagram or list of needed connections. You can send it to me at Support@conductivelabs.com if you like and if needed we can set up a Zoom call to talk it over.

Anyway sorry for the headache. Let me know if you'd like someone to take a look with you.