MRCC Firmware Release 1.1.095

[ekkomouse]

https://www.dropbox.com/scl/fi/3ydgvnjoh...zicu8&dl=0

Here I was experiencing the clock issue on USB-C, so I factory reset the second mrcc, I only had one routing to a mioxl by usb D this time, that input was not routed anywhere else, but I was receiving double clock on remote 12. Filtering inputs from D did not remove clock, filtering output on D did work, but again it was not assigned anywhere. So it seems like there’s something routed before it reaches the USB filters.

[ekkomouse]

I am experiencing roughly 1bpm of jitter on midi clocked devices down the line from the MRCC, this is from a clock when directly connected has about .1 bpm of jitter. Not sure if this can be improved, it's not a huge issue but I think I have lost connection on push 3 before from this issue. And then that jitter gets amplified when used as a source to other devices that are themselves sending clock to other devices.

[RadekPilich]

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.

[ekkomouse]

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.

[RadekPilich]

@Darryl Here is one 100% repeatable way to freeze MRCC.

I did further testing after the recording and I can freeze it messing only with 3 notes. And the more notes I add the faster I can freeze it 

[Jesse Johannesen]

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.

[RadekPilich]

My SL has two outputs, they are simply wired into DIN INPUT 1 & INPUT 2 and then straightforwardly routed into 1 to 4 outputs each,  both DIN & USB.

Oxi is routed in the same manner, but has 3 OUTs, that go through expander DINs that is connected to USB1. This is a workaround, because the direct OXI-MRCC USB connection can currently handle only 2 rather then 3 outs.

The outputs of the SL / OXI are "synth groups" - out 1 = monos, out 2 = polys, out 3 for add-hoc routing into drum machine / grooveboxes.

Outs from MRCC are similar, but sub-groups in nature - i.e. OUT1 monos on the left side, OUT 2 monos at the right side, same with 3 and 4 for polys, 5 is digitakt, etc.

[ekkomouse]

There’s a definite bug when using two MRCC units and routing from one to another on usb, there are phantom routings that come back unintentionally, I think I’ve posted a couple videos already. Can you confirm that you’ve got this and understand?

https://www.dropbox.com/scl/fi/rj0y5923d...swncq&dl=0

[ekkomouse]

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.

[Jesse Johannesen]

on the in port filter page, by default you get one to 6, A, B, C 1-4 and D1-2, missing is D3-4, P1-12. 

on the outport filter page you get 1-12, A-D, P1-4, Missing P5 to 12. 

Separately I have an issue where I have a routing where clock is going from MRCC one to two, MRCC 2 Is sending clock back to a remote routing on 12 unintentionally when it’s not assigned , The only way I can stop it is to filter on the outport page. 

https://www.dropbox.com/scl/fi/nv8podofy...ksdrs&dl=0

So I was trying to reproduce the issue in the video by sending the MRCC clock out of PC port 1 on MRCC1 to the C port of MRCC2, Factory reset MRCC 2 and it still shows clock (red arrow on input) which matches the video, however that is the expected behavior. If I send Clock to a DIN port it also shows red Clock arrows at that ports input. I thought initially that it was only showing what is actually routed, but I tested it with notes as well and was it also shows that data on the inputs as green arrows regardless of any existing, or non existing routings.

I still want to get to the bottom of the phantom loop back issue, but can you help me understand if this specific report can be closed or if I need to try something else to reproduce what you're reporting (did I understand the assignment in other words).


Thanks again for reporting.