MRCC Firmware Release 1.1.095

[Jesse Johannesen]

It's possible to remove the internal SD card and collect the save data to send it to me, but it's way too much work, it's invasive, requires a hex wrench, and probably wouldn't help. The purpose of simplifying is mostly to remove the possibility of user error. The more complex the setup the harder it is to be sure that some overlooked error is influencing the scenario in an unexpected way. By taking away all the other variables we can eliminate a lot of the possibility for those errors.

In this case playing three notes into a DIN input should never be an issue, we can send 40notes from a NDLR pad into an input without any problems, so something else must be happening when we press the hold button.

---

Can you tell me how the MIDI is routed to the MRCC from the SL3? Is this a USB issue or a DIN MIDI issue?

---

My MRCC keeps freezing. Less then before during normal operation, but still sometimes I found it frozen for unknown reason.

Besides that, today I froze it many times when sending MIDI LFO's from Oxi One through it.
Seems that not only MIDI loops freeze it, but also MIDI flood of a lot of messages.

Additionally, I've found out that with really fast LFOs on OXI, the MIDI que gets so big that it's not processed in real time anymore and and there is a delay to notes and everything. 
I have to do a bit more investigation thought, whether the issue is already in Oxi, in MRCC xpander, or MRCC itself.

Thanks for the report. 

It is definitely possible to flood the MIDI buffers with events. I think we've seen it with poly aftertouch in some fringe cases with a ton of other data being sent. I've asked the team if we have data on those buffer limits. 

I think it was also mentioned with the expanded number of routings possible, that at some point it would become probable that you may run into some limitations to the amount of DATA being sent. 

It would also always be helpful to know when reporting issues how things are connected and if we're discussing DIN or USB MIDI connections.

---

Im curious if you could give some information on what happens when we plug in to an input or output that has both TRS and DIN, using two cables and plugging both types in as if it were a merge. I experienced some issues doing this so I stopped using both inputs simultaneously on the input of MRCC USB expander. But I have been doing it on the MRCC itself.

Inputs and outputs are both linked, and as a result, if 2  connected inputs receive data at the same time it becomes garbage, (it might even be a problem to have them both connected but not sending data) but two outputs can be used at once without any issues.

OK I understand the merging aspect isn’t there, I was getting some kind of additional voltage that was causing an MPC not to be able to boot correctly, does this sound correct? MPC was hooked by DIN and push three was hooked to the TRS, on USB expander input A.

I can't imagine what might be happening that would prevent the MPC from booting, but anything's possible.