An odd one this... all external midi controls for the clock and arpeggio work nicely except when changing the rhythm value (control 26)...
This seems to stop the MRCC's internal clock and subsequently shut down the arpeggio playing.

No matter what I try its always latched, even when the latch symbol is red. Any ideas? I haven't seen any other reports about it. I am doing something wrong or is a bug? Thanks.

I must have had some extraneous messages in my first test and can now confim it working as intended BUT the control is reversed! (ie. a value of 0 latches and a value of 127 unlatches, not a biggie but might be nice to fix in a later version).

I'm having trouble connecting OXI One to MRCC via USB. When using TRS MIDI everything works totally fine, but since OXI has three outputs, I'd have to use three DIN cables with the splitter, which is fine and works, but uses up three of the inputs on MRCC.

I think I saw someone mention they had MRCC working with OXI over USB, but I couldn't really figure out how.

Hi all,

I'm new to the MRCC and it's amazing, but I couldn't figure this out. I assume it can do what I want it to do, but something isn't clicking for me.

I have 4 keyboards and 2 sequencers as IN.
I have 7 keyboards and devices connected to OUT.
Some of these are the same keyboard. Keyboard 1 I will use most of the time to control itself and other synths. But maybe I want to use Keyboard 4 or more likely Vector to control keyboard 1 or any number of others.

IN 1 - Keyboard 1 - Set to Midi OUT Ch 1
IN 2 - Keyboard 2- Set to Midi OUT Ch 2
IN 3 - Keyboard 3- Set to Midi OUT Ch 3
IN 4 - Keyboard 4- Set to Midi OUT Ch 4
IN 5 - Kork SQ 64 Sequencer - Multiple Midi Out Channels
IN 6 - Five12 Vector Sequencer- Multiple Midi Out Channels

OUT 1 - Keyboard 1 - Midi IN Ch 1
OUT 2 - Keyboard 2 - Midi IN Ch 2
OUT 3 - Keyboard 3 - Midi IN Ch 3
OUT 4 - Keyboard 4 - Midi IN Ch 4
OUT 5 - Keyboard 5 - Midi IN Ch 5
OUT 6 - Keyboard 6 - Midi IN Ch 6
OUT 7 - Keyboard 7 - Midi IN Ch 7

I would like to be able to set select any IN and send it to any OUT and that keyboard will play.
I was able to set this up for some of them, but it seemed like I was limited to how many. I was doing it by selecting for example IN 1 and OUT 5 and then going into Channel Mapping Modifier, setting CH1 Preset to do IN midi channel ALL and OUT 5. So that basically takes any midi channel that comes into it and sends it to 5.

However, there are only 6 Chan Map presets in that section.
I put 7 in this example because what if you have 7 or even 12 keyboards that you want to do this with?

I just doing it completely wrong? 
Or is there a combination of things to do to achieve this?
Or is this a limitation?

What's your way of setting it up?

Thanks!
Tony

The light, with nothing plugged into any of the USB ports if has a full constant blinking, looks like sync or something at 100 bpm or so.  It is no where near as bright as I when something is plugged in.  If something is plugged in it will turn green, otherwise it is a dull red/ orange constant blinking, faint but there.  Always.  
Did factory rest, still there.  Any fix or anyone else have this?  Thanks

I would expect it to be the same if I have a Pad sound on 1 Channel or if I have a Pad sound on 3 channels chained in the global settings (of course Synth sound on all three channels exactly the same), but it isn´t not even in the harmonies. I´ve read through the manual and have no explanation for that behaviour.

Can you confirm that a chain on three channels with the exact same sound is the same as play it on one channel in case of harmonies?

Hi, I haven't come across this in my searches... is there any reason why, when using port monitoring (via the lightshow) the first 6 LED's for the input ports don't work and are lit up?
Is this a hardware limitation or could it be added as a feature for a future update? This is a super useful function and something just about every other interface does as standard.
Seems odd as the USB input lights work as expected.

I haven't done much with the MRCC yet as only just got it and configuring it, but its a superb device nonetheless. It will transform my MIDI connections for sure. Cheers.

I guess its all said in the title. I am always running into trouble with that MIDI Thru behaviour of the NDLR

I am having trouble getting a clean clock out of my Push 3 through the MRCC. As best I can tell, it's due to poly aftertouch generating lag in the clock pulses.

Push 3 is hooked up to input 1 via midi din. I have the Polyend Poly on USB port A, and the rest of my hardware on the midi din outputs. I have a sequence running from the Push to my Matriarch that contains aftertouch info (the aftertouch isn't currently patched to anything. The Push is new to me, and I'm learning as I go). Whenever an aT message is sent from the Push to the Matriarch, the clock signal goes haywire across all channels. My eurorack clock (through USB) jumps from 238ish bpm to 90ish, and my delay pedal (through midi din) clock is equally as erratic.

I checked the clock pulse that's coming out of my Poly 2, and I can see that there's a delay in the signal whenever an aT message is sent. To isolate the issue to the MRCC, I routed the Push directly to the Poly 2 via midi din, and the pulse holds constant (I presume the Poly 2 is ignoring the aftertouch, but I haven't checked their docs yet). Sequences without aftertouch don't appear to have this issue.

Any thoughts on how I can improve this situation? I can certainly work around the issue, but it would be great to be able to use the Push as my master clock while utilizing poly aftertouch. Thanks!

would be great. also with midi input, so i can also play chords/lines into the NDLR (plugin) and then record the NDLR output on another MPC channel