In another thread I learned that throughout the MRCC it is possible to set a total of only 6 CC modifiers - to be divided into all input devices (midi/usb), output. This is a very small amount that can be used with just one device. Usually, one CC is not changed and a certain group (e.g. for USB devices, where it is not possible to configure them without a computer), or for strangely controlled devices like Volca Drum (e.g. the lack of velocity and other parameters in single/multi-channel mode).

Therefore, I have a proposal that, as it is done in channel mapping, one CC module would contain several IN-OUT modifiers. In example - one CC1 mod include set of 6 CC modifiers.

I'm having issues registering midi input from my Keith McMillen 12 step that I've plugged in via USB. It works when I plug it into my computer, but I'm not seeing any output from the MRCC's own midi monitor. I get a green light from the USB port and I've tried selecting all the "virtual cables" and routing them to different devices but nothing's showing up in the MRCC or any connected devices. I'm wondering if there's a step I'm missing here involving using midi, or if the 12 step is unsupported/needing more setup. I've updated both the MRCC and the 12 step to the latest firmware. I have possible workarounds if I can dig up the midi expander which would just use regular 5 pin cables, but I'd love to make use of the MRCC's USB ports where it makes sense to. Let me know if there's any additional information I can supply!


Update: After a couple hours banging my head against the wall and having trouble keeping track of my work, I literally turned the MRCC on and off with both of the USB devices (this and the Squarp pyramid I've mentioned issues with in the other thread) I've been having trouble with plugged in, and they seemed to work this time. Not sure what clicked, and I'm desperately afraid after getting to the edge of sleep on this problem it's going to all be back to square one in the morning. But it seems like it there's something that needs to happen for the MRCC to "recognize" a midi device that I can force with a reset sometimes. Rewiring my MRCC tomorrow to be responsive to these changes, will update if I get any interesting results.

I don't know the lingo yet, and i'm just digging into the mrcc. I suspect that the answer to my question is in the manual, but I'm not finding it quick at this point to open the manual with the goal of finding the answer to a rather vague question.

So, bear with me.

What I'm wondering is whether one can name the input and output ports in the mrcc so that these names are communicated to my software. Most specifically, right now, in Ableton Live, I can choose the mrcc ports, but they are all generically named. This would come in handy in routing midi to and from the MRCC.

hope the question makes sense. Maybe most people are using this in a more stand alone capacity, but I'm trying to figure out to what degree it can replace my current midi interfaces, which I don't much like. (in which case, i plan to buy a second mrcc)

Hey There folks.

Happy recipient of the MRCC here... its a bit of a game changer for my room.... no more reaching for MIDI cables or re-plumbing every other day... Hooray!

I have found a little idiosyncrasy though, this might be a very fringe case but non the less.... 

I am using a Novation Circuit Tracks MIDI via USB Host A, when I patch this through to the MIDI Din port 1 on channel 1 to drive a Buchla Easel command 208C all is good... until I start navigating around the Circuit Tracks. The Sysex messages sent when changing a view or page on Circuit Tracks seem to be randomly combining with a note message to trigger a very high note. I noticed that some of the MIDI notes are also being stopped outputting while navigating around the Circuit Tracks too.

This is also the same on the Circuit Rhythm again I'm fairly certain it's caused by the sysex messages being sent out of the USB on the Circuits.

When I switch to a Din output on the Circuit Tracks or Rhythm this problem is not there. The sysex messages are not being sent out of the DIN ports on the Circuits so that makes sense. 

The issue is also not there when I send MIDI from Circuit's USB to other synths either so it could be something within the Buchla 208C's MIDI implementation not enjoying being sent a spurious sysex message.

So for my two pence.... it would be great if Sysex was a filter option which I think would solve the issue from an MRCC perspective. 

I work at Novation too so I'll be asking the engineers about the need for these sysex messages. I'm not 100% certain they are actually needed unless its a requirement for the Novation components software to manage the synth editor in Circuit Tracks. I certainly don't see any particular need for these Sysex messages in the Circuit Rhythm though. 

The good news is that I can confirm that (except this strange sysex thing with Buchla) the Novation Circuit Tracks and Circuit Rhythm are class compliant enough to happily work with the USB host ports. As does the Summit and Peak synths.
I'll be testing out the Launchpads Mk3's Launchkey Mk3s, SL MKIII, Bass Station 2 and the LaunchControl XL in due course soon too so will report back on their compliance.  

Sadly the Monome Norns music computer isn't class compliant enough for MRCC to show up via USB though.

Other than this small (and not insurmountable) issue MRCC is a joy to use and is taking pride of place in the studio.

Cheers
-CALC-

I have started experimenting with the 3.5mm TRS outputs (number 11 and 12) connecting to the Korg NTS-1 with a straight (stereo audio) 3.5mm TRS cable. 

Unfortunately the NTS-1 doesn't receive any MIDI data using that cable. Neither the A or B flavors of the TRS ports work.

Using a TRS to MIDI conversion cable on the NTS-1 side works fine, but in that case I will "loose"  a MIDI port on the MRCC. As I have all MIDI out ports on the MRCC in use already, I would like to use the TRS ports as well.

Does anyone have any suggestion on which cable to use to connect 3.5mm TRS on both sides (MRCC and NTS-1)?

Last night I finished adding the last couple of labels, saved them, then scrolled through the list, but midway through the alphabet (sometimes MAC, sometimes Mixer) all following slots were blank: no user created, no factory ones.  The longer I scrolled clockwise, the longer it would take to return to visible entries, so it seems there were just blank slots there.  Power cycling the unit a few times did not resolve the disappearance of the missing items, which included a bunch I had made the previous day.  However, ones in the first half of the alphabet, both custom and factory, are still there.  OS is 1.1.020.

We are currently including a 10 Meter Ethernet cable with orders of the MRCC Remote 7. We would like to get a feel for whether this is a good default length or is it overkill? After completing the survey, feel free to comment below.

I have a question about the number of mods of one type (e.g. CC) for the whole MRCC. Is it possible that only 6 different modifiers of one type can be created in the entire configuration (not a single IN-OUT routing) ?

If this is true then this is a very small amount (if you consider that it has to support such a number of devices, including USB, which often without a computer you can not change anything and you need to do it on MRCC).

In some cases, I would like to use these 6 CC modifiers for only one device... and is this the end of the possibility of changing CC? I hope I'm wrong...  

I am preparing to do a more complicated configuration for different hardware (quite flexible, as there will be several parallel settings for different synthesizers, which will be independently enabled on midi outputs). I will use a large number of modifiers and wonder if after creating a dozen modifiers it will be possible to remember what the individual modifiers are used for (their names are very short).

Is it possible to add an additional field with a description for connection pairs? Using aliases for devices is extremely useful, but it's telling nothing about reason for modifiers. 
If we have keyboard support, and you can even do it in a configuration file, this option would make it easier to understand later how it works.

It could be enough to create description field for each connection, e.g. for IN1 -> OUT3 pairs, a description of "modulation to LFO" or "aftertouch to cutoff on synth3" or "random arp for bassline" etc.

Hi

Im facing some strange issues with the MRCC when connecting the NDLR.

I have a Sqarp Pyramid sequencing some synths (through usb 1) + running the clock, which syncs my computer (Ableton) + all my synths.
This works great (so far).

As soon as i connect the NDLR to one of the MRCC usb ports the clock jumps all over the place (on all devices) 
Even when the NDLR has not been routed to anything.

If i put a filter on clock on the output port of the usb port NDLR is connected to it resolved the "jumping clock", but then the NDLR isnt getting sync

Been messing around with this for a while now and need some pro tips of how to fix this.
Found a post with disabling the clock out completely through the boot menu on the NDLR, but that did not help anything at all. (disabled 2 first options and the last option set to 1 instead of 1-4) 

Was on the "current" beta, but also updated the ndlr to beta fw trying to figure this out + resetting to factory settings etc.

Can the NDLR be run as "slave" with only using USB? 
Also how can this mess up clock on everything even when the USB port its connected to on MRCC isnt routing out to anything?

I see the NDLR sending CC19 (to nothing) every bar on the MRCC display, but all the pads etc are not even set up using USB, so not sure whats going on
help!

update; it works as is should if i use the internal clock on the NDLR, but as soon as i try to "slave" it makes the clock jump around and i would really like to use the pyramid as clock as its quite central in my setup + this also caused the MRCC to freeze up while clock jumping around :|