hi i am just getting round to setting up mrcc. ive also purchased a widi bud pro and am wondering could this work in the usb port of the mrcc to connect to my other wireles bluetooth midi devices? any info appeciated
Phil

I have been trying to use the ndlr with my setup for the past 6 months or so but it just is extremely disappointing and frustrating experience to the point I do not want to use it.

I haven't even learned most of the functionality because these issues are making the device pretty much useless. Most of them have been reported here on the forums but no fixes / improvements have been implemented.

Issues:

- MAJOR BUG: When NDLR is configured to receive clock from USB 1 it will send out clock signal causing tempo to double on all other devices !
- BUG: All notes play incredibly low, changing position has no effect. Everything returns to normal when pressing any of the Chords (I - VII).
- BUG: Notes keep playing (stuck) if stopping at the right time. And with ARPs it's very often that time.
- BUG/UX: Disarming all Parts does not work logically. If I explicitly disable them when (ext) clock is not running and then start external sequencer which starts sending clock and play message they are enabled again. Why can I even toggle these (stopped) if it has no effect? If I turn them of I want them to be off.
- BUG/UX: Using external sequencer to trigger Chord changes is nice, but it is guaranteed to mess your patterns once you go into edit screen.
- UX: Dark blue text on black background. Really hard to read. Please use light blue.
- UX: Pots and buttons miss clicks often. Yes I've read about the detentless encoders in early versions. Not an acceptable excuse.
- UX: Setting Tie / Rest in Rhythm editor is definition of pain. Scrolling 129 values with the two Tie / Rest mixed in with encoders which miss clicks often. This could be easily remedied if shift + left rotation would go directly to Rest and shift + right rotation to Tie (or other way around). That way nobody has to hunt those. Easy and quick.
- UX: Going into pattern editor, mod matrix etc is behind seemingly unnecessary complicated key combination. Shift + menu and then clicking encoder. Why not just shift + encoder? That would be available unless I'm missing something.

I really like the idea, but it's very hard to like the execution here. Apologies for being quite negative here. Any help on any of the issues is greatly appreciated.

Have you considered open sourcing the firmware if you are no longer actively developing it?

Is there any chance that devices that currently work on a MioXL via USB will work on the MRCC
i.e I've got a Pioneer TORAIZ Squid. work perfectly under USB on the MioXL, but not recognized by MRCC.
The Moog One is another one.
Yes I can also use DIN but I've got these already purposed for other stuff. 
So I guess my question is can someone look at these and get them fixed?
My assumption (mother of all..) would be that if it works on iConnectivity, it could be made to work on the MRCC as well right?
What's causing those differences?

Midi messages from all 4 functions -Pad, Drone, Motif 1&2 work fine on Midi channel A but none transmit on channel B. I've carried out a Factory Reset but still nothing. Can anyone suggest a fix please. Thanks

Question for Steve -- in the MIDI spec, there's 3 CCs listed for dealing with the NDLR status/settings - 
CC 15, 16, and 17

Using 15 and 16 to set the port and channel for status, is that supposed to change the NDLR status channel as seen in Settings page 1 or is this trio of CCs only temporary to handle receipt of the CC 17 output?

In other words - if I send CC 16 and specify a channel of 7, does all subsequent NDLR status messages need to come in on channel 7 to be recognized?

thanks

Can we rename the user presets?
or are we tied to User 1, User 2 etc?

I'm trying to migrate from MioXL to MRCC.
Currently setting up my DAW mapping

PC IN to DIN OUT works fine
Using PC virtual port 1 (named MRCC in DAW)
I push the PC left button (green)
Select virtual port 1 (highlights green)
Select the MIDI OUTS 
send data over the right channels and everything works

PC IN to USB B out, doesn't work
Now, I connect a Moog One via USB to USB B > USB light > GREEN
Again I select PC Left button
This time I choose virtual port 2 (or MIDIOUT2 (MRCC) )
I select the right USB B button (turns blue)
I play on the right midi channel in DAW pianorol
nothing arrives at Moog One

Moog works fine when connected to MioXL via USB

Any suggestions? where am I going wrong?

Can someone be so kind and answer me if polyphonic aftertouch (genereated from Hydrasynth or Microfreak e.g.) is getting blocked (filtered out) as it is still in the NDLR?

First I wanted to buy the MRCC as an addition to my NDLR - but as the poly aftertouch problem still exists in the NDLR I am thinking about selling my NDLR...

Thanks in advance.
Mumari

What, exactly, does NDLR stand for?

Hey everyone, I can't get my poly D to play nicely with my mrcc when connecting via usb. All proper settings were handled in the synthtribe plugin, but when I press play it just starts the sequencer and carries one note until I stop, sometimes overloading my mrcc. Have all my other ins connected via midi cables. For some reason having issues even connecting my keystep pro via usb to ableton. Any insight would be greatly appreciated I think it might just be my misunderstanding of the routing.