Yet another limit? Routes are maxed out at 43!

[Joris Röling]

Hi ConductiveLabs,

I seem to have run out of routes! ( = IN (green) to OUT (blue) connections)
I did count my current routes and it seems that it is maxed out at 43?
After that, no more can be made?

Now I have to 'disconnect' another route before being able to 'connect' the one I want to make. This is not what I expected from a modern MIDI Router Control Center.

I do understand that everything has a limit, but it seems I have assumed that I could (on the MRCC) make a route from any IN to any OUT.

Unexpected and not documented anywhere as far as I know.

What say you?

Best,
Joris

PS I stumble across these MRCC limitations again and again (this routing limit, the unsupported SysEx on certain ports and the asymmetric USB IN-OUT ports) and a start to get annoyed with these a little. Wished the where communicated more clearly ahead of time.

[Raphie]

Why would you need 43 routes on a 6 in /14 out interface? the routes are per port / not per discrete midi channel (16 per port)

[Joris Röling]

Why would you need 43 routes on a 6 in /14 out interface? the routes are per port / not per discrete midi channel (16 per port)

Hello Raphie, 

I don't understand your response.

You question my reasons to have 43+ "routes" (green-blue combo's as I explained)? 
Well, routing ports is the purpose of the MRCC, I'd say.

I never mentioned "channels" (intentionally), as the MRCC is a port router with very limited channel filtering (sadly). I'm very aware of that.

The MRCC has more than 6 in / 14 out (as you suggest), it's more like 34 in (6 DIN +16 USB A +12 USB B) /  28 out (12 DIN + 4 USB A + 12 USB B). 
I have my MRCC ports filled (maxed out). I need more than 43 from-to routes, yes I do.

Still, I do not understand your response: I discover a limit and you question my reasons and assume I'm talking about channels.

I'd love to hear from Conductive Labs on this matter.

Best,
Joris

[Jesse Johannesen]

Joris, I believe the maximum number of routings possible is currently 50, can you let me know which firmware version you are using?
Jesse

[Joris Röling]

Joris, I believe the maximum number of routings possible is currently 50, can you let me know which firmware version you are using?
Jesse

Hi Jesse,

Thanks you for responding.

I've got FW v1.1.035 running here.
Is there any chance this number (50) can be raised? 

Best,
Joris

[Jesse Johannesen]

At this point there is a unknown issue preventing more routings than that from behaving properly, but if Steve can uncover what the issue is I expect we will expand that in the future. Sorry for the inconvenience in the mean time.
Jesse

[Joris Röling]

At this point there is a unknown issue preventing more routings than that from behaving properly, but if Steve can uncover what the issue is I expect we will expand that in the future. Sorry for the inconvenience in the mean time.
Jesse

Thanks Jesse.

Is Steve actually working on this unknown issue? Is there a release planned in the near future?

Best,
Joris

[Jesse Johannesen]

It's one of many things that are in a list of things to fix, however I don't think it's "under the microscope" currently. I would not plan anything around that changing, but rather be excited to hear about it if the day comes that it's been included in a future fw update.
Jesse

[telder55]

I'm also finding that I'm maxed out on routes! +1 one for adding more routes.

[SteveECrane]

It's one of many things that are in a list of things to fix, however I don't think it's "under the microscope" currently. I would not plan anything around that changing, but rather be excited to hear about it if the day comes that it's been included in a future fw update.
Jesse

To whom this might concern (Jesse / "Steve"?),

Whereas this merge limitation was an issue I could previously work around with some careful cable planning (and by employing several MIDI Thrus on devices - something I have ALWAYS avoided previously, even 1 hop), it has now become a severe limiting factor in my current setup and something I have had to deploy multiple Kenton Merge and Thru units to circumvent.  Much to my annoyance, I am having to consider pressing into service an old MotU MIDI Express XT and/or an ESi M8uEX (both in standalone mode) - the very devices I bought the MRCC to replace based on the myriad hyperbolic claims - in order to ensure permanent any-to-any connectivity in my setup.

Given that this merge issue appears now to be several YEARS old, has this matter been dealt with by "Steve" and/or the CL team?  What is the current (definitive) state of play?  If this is a limiting issue of the Raspberry Pi 4's processing capacity - and not simply a coding issue - then perhaps the limitation needs to be mentioned upfront, specifically in the technical specs for the unit(?).

I genuinely look forward to receiving a definitive response to this, rather than anything assumptive, speculative or vague.

Kind regards,
Steve E Crane.