I tried a simple test today of routing a one-way sysex bank dump though the MRCC (MIDI In 1 to MIDI Out 5) to a Roland D-550.

The bank was being sent from a PC using Bome SendSX software, routed out the MIDI DIN port of a RME UFX II -> MRCC In 1.
MRCC MIDI out 5 was cabled to the D-550.

The bank dump was transmitted successfully when MIDI IN 1 was routed just to out 5. It It also worked when it was routed to outs 5 and 6.

But, if I route MIDI In 1 to three outputs, (5, 6 & 7), the bank receive on the D-550 will fail with a 'MIDI communication error' message on the D-550 screen. The other synths on outputs 6 & 7 were turned off.

Obviously this is early testing with just one receiving device. But, this leads me to believe that the MRCC is possibly unable to reliably route sysex simultaneously to more than two output destinations. 

If this is true, it is going to make me have to use many work arounds, and possibly be quite limiting on how I use different sysex librarians and editors, whether on PC, Patchbase on Ipad routed through PC rptMIDI, or from my Electra One. I have around ten hardware synths that need to be controlled, many from multiple sources.

One answer is to use a PC virtual MIDI cable for each controller/synth combo, but this increases the complexity of my set-up a lot, and will be a pain to set up.

Has anyone else here experienced unreliable sysex when routing through the MRCC to more more than one or two outputs?

This would be useful to for example trigger external filter envelopes from a midi keyboard being used to play a synth routed through that filter. 

Would implement that as new EXTRAS screen with selection for MIDI input and MIDI channel + electric properties of the CV signal.

Mute / solo for routings should work in relation to a single input port. They should be remotely controllable, possibly via note on/off messages.

This would be useful for example when having a single "universal controller" input (i.e. Faderfox EC4, Electra One, or simply a master keyboard controller) with configurations for multiple devices with overlapping midi channels that are spread across multiple outputs, where the channels are obviously not overlapping on a single output (i.e. 50 channels on 4 outs, with most of them being utilized on 3 or 4 ports, each for a different device).

So when having devices on 4 outputs and having all those outputs mapped to the controller input, it would be possible to remotely from the controller itself mute the routings to the outputs 1-3 and only control devices on output 4 until deciding it's time to control devices on output 2 and soloing that routing.

I realize this could be accomplished by manually creating and removing routings and / or by having multiple presets and toggling between them, but for my case, that seems much more complicated then being able to solo / mute routings remotely ideally while having a visual feedback on the MRCC LEDs.

Can you please explain LED lights animations to me? 

Where can I see the effect?

If I try to set them as activity / note monitor, I don't see any change.

This function should make it possible to switch any out port(s) into a THRU state, where instead of data merged from it's routed inputs, the port processing would be overridden to output the same data as the single selected "THRU-SRC" port, which could be either any input or any other output port.

There would not be any additional routing and merging on these THRU ports as long as they remain set to the THRU mode, even though the pre-existing routing will remain in place and new routing could be added. These will however not be active as long as THRU override is enabled.

This way, we could set all the routing, remapping etc only once at the primary output and then have MRCC automatically replicate the output of the selected primary output to the THRU out(s), while possibly taking less resources than a bunch of separate duplicate routing would take. This is basically substituting a MIDI THRU boxed connected after the primary output.

Or we could do ad-hoc overrides of existing routings for simple passthrough of single input/output. For example to "mute" all the sequencing into a single output and instead temporarily play it manually from the master keyboard.

The switching and sourcing of the THRU mode would be done on a new OUTS THRU / THRU SRC screen, where yellow LED would indicate a THRU enabled port. Enabling the THRU port would be done simply by pressing and holding the desired THRU output and then pressing the single output/input to pass through that output.

This would be useful for setups, where you don't always power up all your gear. 

The setting screen should provide ordered list of 3-5  selectable inputs, that would be cross-checked at all times (or by some refresh soft button action) and only the clock and transport from the highest active input would be passed through to the routings.

The clocks and transport messages from the other inputs on the list would be filtered out.

I have a keyboard poly synth as one of the inputs and also one of the synths on one of the outs dedicated to a bunch of poly synths.

I can easily change global channel on the keyboard and play all the other poly synths.

I want to prevent MIDI loopback on the keyboard synth though, block its channel in the routing.

I know I can remap the channel to channel 16 and use it as a dump, but I would rather not waste usable channel and not send unnecessary messages in the MIDI data stream.

Hi,
Was just wondering when some more MRCC units and accessories will be making their way out into the wild ?

Hi all,
Please would someone remind what power cable/adapter the MRCC comes with (if any)?
I've had my gear in storage for a while, and I'm setting up my studio again. I can't seem to find a matching power cable/adapter for my MRCC.
Have I lost it? Did it even come with one? Maybe you're just expected to plug it into a USB-C PD socket using your own cable? Or if it's powered by the USB connection to a PC?
TLDR; I'm not sure if I've just lost my MRCC power cable/adapter, or if it didn't come with one in the first place!
Please remind me.
Many thanks,
Ben

I often use Stepic - a software sequencer that can send CC to external devices - to sequence the NDLR. Today, I decided to encode every CC for the NDLR into a Stepic device patch (which I will share later) rather than just the basics.  My thinking is that with all CC codes, I can automate the switching of instruments connected to the four NDLR tracks via changing channel numbers for each, etc.

While doing this, I noted an error in the manual: page 59 lists CC 26 for the Motif 2 MIDI Port, while page 56 shows CC 26 as the Chord Degree. 

I *think* page 59 is in error.

The hex codes in the page 59 table correspond to CC24 and CC25, but the CC codes are 25 and 26, respectively. 

Hope this helps others using CC codes to manipulate the NDLR in real-time.