Hi,
If I leave my main music-making PC (A Dell Alienware Aurora R10) connected to MRCC into the "PC" port on the MRCC, after a few hours the MRCC crashes and won't respond until power-cycling it.  The really strange thing is that this happens even when the PC main power is off.
If I use the same cable connected to my laptop, everything is fine!
Can someone suggest how I can troubleshoot what's going on please?  I've tried rebooting, keeping the PC on and off, different cables, different ports in the PC (front and rear - the rear ones crash less often than the front ones for some reason)...
Any help would be much appreciated!  Thank you...
Jon

This is a request for a possible hardware improvement if/when another MRCC is produced.
I haven't looked inside the MRCC to see if this is possible, but there is a lot of bleed through between the LEDs, which at times makes it hard to tell if one is selected or not.
If I turn the LEDS up this isn't a problem because there is plenty of delta between on and the neighboring off LEDs. 
My issue with that is that I like LEDs to be turned close to as far down as possible. I like my studio dim, and the bright LEDs are blinding because you are usually trying to see the things around the LED.
Unlike some companies that have no control over brightness or basically let you adjust them from blinding to still way too bright, Conductive Labs got the attenuation of the LEDs right, it's just when they are dimmer there is still a lot of bleed through.
In mine, If say OUT 1 is on, I can see the light the whole way to LED 4.

The request is some kind of dividers between the LEDs in the case, so that LEDs that are on don't bleed through to the others.

Had a frustrating afternoon today with the MRCC...

Setup is as follows:

INPUTS:                    OUTPUTS:
----------                    -------------
5  (Korg Trinity)          2 (Behringer 2600) & 4 (Roland JX-3P)
C  (Korg M3 88 Note)  A (Korg M3 61 Note)
                                1 (Roland MC-505)

MRCC Clock output sent to all outputs. No clock out from any of the other devices. 
MRCC arpeggiator sent to output 2. No other routing, modifiers or filtering used.


Everything works great for 15 minutes or so... jamming away and bang! The MRCC stops working causing hanging notes, all controls unresponsive & requiring a restart.

It did this about 6 times before I lost my temper with it. Nothing unusual was happening, just various arp's/Karma modules on my synths all running along nicely then it takes a nose dive randomly. No program changes, no tempo changes or any settings changed on the MRCC whist playing. Just notes and chords being played on ther Trinity and Korg M3 61 Note.

Even stranger is, I went to make coffee with nothing running apart from the MRCC Clock and the MRCC had still locked up when I came back!

I have given up on using the internal clock entirely now as its so unreliable for me and I haven't been able to reproduce the lock up when using an external clock yet. I will post again after more thorough testing using an external clock and see if the same happens.

Has anyone else had this issue? Could it be too much midi information being generated? (in which case how come it seems to lock up randomly, in the middle of playing a chord or indeed when doing nothing?)

I can't find an answer to this, maybe because it's so basic or obvious. I've watched the videos and read the manual but admittedly sometimes my comprehension isn't the greatest. 
With a lot of controllers, like the SQ-64, f you turn it off and back on, your last config is saved. 
With the MRCC when I turn it back on I'm back to the factory preset of nothing mapped and no configuration. Obviously this is annoyjng if I have to set it all back up again. 
Do I have to go to save and save a user preset before turning it off to save my configuration?
That's fine if I do, I just haven't seen anything that says you have to, and if you do I'd assume it would have been covered in the first video. 
Maybe I missed it? Maybe my unit came bunk?

I have an Electra 1 controller and it would be great to be able to pick a feature in the MRCC and map that to a knob or slider on the E1. I can change patch with it now but it would be useful to use it to change a channel or even cause a save. We could turn clock on or trigger start, the arpeggiator could be controlled, there are loads of uses for this I would have thought.

I followed the instructions here on the site. using the links therein
I tried the update with my Macbook, which only has three USBC ports. I did the initial using a hub. Then I removed the hub. still nothing
when I pressed the firmware button everything went black. 
I made sure and used the correct MRCC firmware available on the update page. 
I have tried many different cables usbc usb b to usbc
I have tried my PC with all of the same cables including long and short.

when I power on the MRCC the PC LED flashes briefly 
Factory reset does nothing 

I have tried earlier versions of firmware. No Joy
Thoughts?

Hi there,

I have a Novation LaunchKey MIDI controller. The keyboard sends note on/off via MIDI channel 1, and the drum pads send via channel 10. I want to tell the MRCC to listen to the channel 10 notes, filter them out, but use them to direct the Channel 1 notes to different destination ports.

This way I could just tap a pad on the Novation and it would send to a different synth immediately, and easily.

Is there some way to configure the big MRCC to do this? Any alternative ideas?

Thanks!

I just got my red NDLR. Most of the time, parameters do not change immediately when I turn a knob. It can take 2, 3 or 4 turns before a parameter begins to change.

Is this by design?

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).