By default the MRCC identifies itself as USB host as MRCC, “Midi 1 (MRCC)” etc
Though when assigning midi ports to these host ports the MRCC already knows the label.
I.e. I got my “Moog One” connected to midi 1, mapped to USB host “Midi 1 (MRCC)”
It would be great if there is an other than the “none” label assigned, that label is broadcasted to the DAW rather than the default device name
So “Moog One” rather than “Midi 1 (MRCC)” 

iConnectivity works this way, it makes DAW connectivity a lot easier.

Today I've discovered an issue with the labels in the MRCC
The assigned label positions seem to move when adding new labels.

i.e. If you create 4 labels: Synth 1, Synth 2, Synth 3, Synth 4
and assign them to midi in 1,2,3,4 
Then create a Synth 5, then the assigned label positions move, i.e. midi in 1 is no longer assigned to synth 1, but synth 2
It seems the way it enumerates is absolute sequential and not logical.

The consequence is that when buying or selling gear and because of that creating new labels, you'll need to validate all ports for still having the correct label.
Is this a known bug?
can this be fixed?

Hi,

we have our Remote 7 plugged in and working great. It's a blast.

However. I'm trying to find the out ports of the Remote 7 in the out port filter screen. I see the 12 hard out ports, the 4 USB ports, the PC ports... and that's it. Can the messages leaving the Remote 7 not be filtered?

I’ve installed the latest .44 fw and can’t get my Prophet-10 rev4 to work via USB. It’s in de compatibility list but no joy so far.
Anybody else got theirs working? Even if older FW pls confirm.

I'll leave my question + answer here, as my problem was solved. I misunderstood how virtual ports are working, but after I change virtual port from 1 to 2 and then create routing, then it works  In that case I cal also confirm SQ-64 works with MRCC via USB (for USB compatible devices list)

I have two the same mono synthesizers that work on two different channels. Usually I use them for different sounds, but I came up with the idea to use them simultaneously with the proposed Channel Spreader module. The point is that every note command that is sent is sent once to one synthesizer, then to another, and back to first again. When two keys are pressed simultaneously, two independent mono messages will be sent to both synthesizers (both for different notes). In this way, we get real 2-voice polyphony. An additional setting would be to send CC commands from the input to both synthesizers simultaneously. After all, it can be sent to polyphonic synthesizers and produced interesting effects.

Additional optional features:
- randomly spreading note commands to different, defined channels (useful, for example, if you have different sounds on different synthesizers and you want random notes to be played with a different timbre)
- range of channels to be spread - you can use several connected synths
- partial spread, e.g. 25% to one, 75% to the other, and then random 58% and 42% in the next, etc.

My mrcc was working normally,  but now all of the leds to the right of midi port A do not light at all.   I have tried power resetting but that did not help.  The din midi routing
does still work.  
Any ideas?

- keykent

So as many of you have noticed the NDLR has sold out everywhere. This is due to a shortage of supply on the main processor chip and we haven't got a date as to when stock will become available again. There is some discussion that suggests there may be stock available in May, and if that is the case then we should be able to get more produced by August. 

In the mean if you are interested in purchasing a NDLR time the best bet is going to be keeping an eye out on the secondary market, (ie Reverb, Craigslist, etc.). I also encourage you to post here in this thread if you are looking for a NDLR and maybe someone on the forum may have one they are ready to part with. I will post links to NDLRs I see for sale in the wild as well. 

Just a quick reminder that while this is a community, it is still the internet, and it pays to be cautious. Always pay with paypal goods and services and ask to see a pic with a written note containing their username to ensure they have what they say they have. Conductive labs will not be involved or responsible for any transactions, but it seems like there are a lot of folks on the hunt for a NDLR and I just wanted to make a place where we could discuss that.

All the best,
Jesse

Please tell me, the NDLR is still supported and new firmware updates are coming. 

I'm wondering after some of the comments...

I just bought one and it will be here this week, I hate think this is already dead.

*The Goal: Trigger Pad+Drone whilst simultaneously sending the trigger notes to a DAW for recording

Current Inputs: Notes (Ch15) > inputs A and B

Current Outputs: B (ch1-7) > iConnect DIN > Bitwig and iOS

Desired Setup: Output A or B (ch1-7 + 15) > iConnect DIN > Bitwig and iOS

*DIN is the only option, to route to both DAW and iOS cause iConnect host port issue

Thanks