05-29-2025, 11:42 AM
(11-30-2021, 06:42 PM)Jesse Johannesen Wrote: 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.To whom this might concern (Jesse / "Steve"?),
Jesse
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.