Hey there!

This might be a lack of knowledge on my part about configuring Ableton....

I have my AKAI MPD218 (USB MIDI Only) connected to a USB Hub which is connected to my Mac Mini.
My MRCC 880 is also connected to the same USB Hub.

Is it possible for me to play the pads (live) on the AKAI and then route them straight out to the MRCC 880 and onwards into another MIDI device via one of the DIN outputs on the MRCC 880?

If so, then I can't get this to work and I think it's an issue with my MIDI settings within Ableton Preferences.

Ideally, I'd like to route the AKAI straight into Ableton and straight out to MRCC 880 (Port 1), and do this by setting the 'Input' of 'Control Surface' MPD218 to 'MPD218 (Port A)' and the 'Output' of the same Control Surface to 'MRCC 880 (Port 1)'.

However, I suspect the above 'Input' and 'Output' might have to be 'MPD218 (Port A)' and then ticking the correct boxes below within the Inputs (Track/Sync/Remote/MPE) and Outputs (Track/Sync/Remote).

I've also looked at making a direct connection between the AKAI and MRCC using the MIDI Studio within the Mac's Audio MIDI Setup.

My expectation is that when I use the MIDI MON feature on the MRCC, I should see MIDI activity when I hit a pad on the AKAI, but I see no MON activity. I do see MIDI activity flashing in Ableton when I hit the AKAI, so I know the USB input of the AKAI into Ableton works.

Hopefully somebody out there is doing this and can explain where I'm going wrong.  


EDIT: So, I've tried routing USB MIDI into the 880 using a Novation LaunchKey Mini MkIII and that doesn't work either. I've hooked up another MIDI controller to DIN input 1 and when using MIDI Mon I see activity flashing on that input. When I start playing/recording in Ableton I see the incoming clock sync activity flashing on Virtual Port 1, but I get no incoming activity from either of my USB MIDI controllers (AKAI or Novation). When I press the PC input button MIDI IN 1 is lit green. If I then select the PC output button, it makes no difference to any incoming MIDI Monitoring whether I have Output 1 lit blue or not. Why won't USB MIDI signals from my controllers appear in the 880????? As mentioned above, even if I ignore Ableton and try making direct connections from the AKAI or the Novation using the MacOS MIDI Studio, I still don't see anything.

Hello there, new member and new owner of both NDLR and MRCC. 

I would love some help with my configuration. 

I have set up my synths midi inputs to be played by the NDLR. 

Polybrute channel 1
Minifreak channel 2
Volca FM 2 channel 3
Roland JV-1080 channel 5

NDLR settings sends sequences to these 4 midi channels (MIDI all.)


NDLR is plugged into input 2 of my MRCC. Polybrute is used as a controller for my rack synths, and is plugged into input 1 of MRCC.

However, because of the channel settings I made for the NDLR, the Polybrute can only play JV-1080 if it is set to output on midi channel 5.

I thought that having the MRCC would allow me to route any input to any output without having to play with the channels. The NDLR needs to send to different channels for the sequences to be received by only one synth, but I thought I could also control any synth with my Polybrute via the MRCC. 

Is there something I'm not seeing in the MRCC settings that would help me do this? This seems like the exact sort of thing the MRCC is made for. I want to select the destination for the controller via the MRCC, and not by changing the midi output channel on the controller (being the Polybrute in this scenario.)

Thanks for the help! 
Dre

Hello all.  I have been using the MRCC for a while now in a Dawless setup, and I have a firm grasp on how to route everything, including PC ports. I was always eventually going to start using Studio one, and I like I can switch between dawlees and PC via the user profiles. The problem I am having is the way studio one lists the ports when adding a new instrument. It lists the ports with a number that doesn'r correspond to the mrcc numbers, and none of the 12 PC ports show up either on the initial setup screen, or within the program on a track by track basis. I does have on MRCC port with no number, and I think that is the PC port, as I do get midi activity to my mono-timbrel synths, but it doesn't have any option to select any of the 12 PC ports. For my mono-timbrel synths that's fine, omly need one midi channel per, but for my multi-timbrel synths I was going to use a single port each for them so they can use all 16 channels of that port.  I have read other posts about a FW update that changed the way the MRCC does this, but I was thinking it could also be a Studio One thing. Perfect world, the labels I gave each port on the MRCC would show up in Studio One for ease of use, but if Studio One isn't seeing multiple PC ports it would defeat the purpose. Hoping for any advice on this especially from Studio One users using the MRCC.  I use a combi of din and usb just for clarity. I could also be missing something obvious lol. I do have another midi router I could use but I really like the MRCC and would hate to have to switch routers when I want to switch from dawless to PC. Cheers, TBrett.

Hi everyone,

I'm a new user of the NDLR and I just wanted to say how impressed I am with this device – it's really fantastic! I'm still discovering all its features bit by bit, and it's been a lot of fun so far.

However, I've run into a little issue: it seems that the velocity setting doesn't work for Motifs 1 and 2. It works perfectly on the Pad, but when I try to adjust velocity for the motifs, it doesn't seem to have any effect.

Am I missing something? Is there a specific setting I should check or a step I may have overlooked?

Thanks in advance for your help!

Is anyone here using MRCC successfully with a SysEx heavy software like a Librarian?

I have a TEO-5 connected to MRCC Port C (routed to PC port 9 In/Out) – and I'm getting constant error messages or corrupted SysEx transmissions this way. When I connect the TEO-5 directly via USB to my MacBook it works flawlessly, so it's clearly MRCC causing the problems. I'm on the latest MRCC beta firmware (v1.1.089_02-19-25).

Hi all,
I've checked the forum for anything on this but everyone here at least seems to be able to get their NDLR to be "seen" by their computer (if they're using one).  However in my case.....
My new NDLR (v2, red case) powers up over USB, DIN MIDI connections seem to work properly (i.e. will drive external HW synths), but USB communication does not work at all:
NDLR is not recognized in DAW (Ableton Live)
USB connection is not recognized by computer (tried 2 Mac M2s, iPad, tried multiple USB cables, with and without powered hubs), despite drawing power from the USB connection.

Couple of red flags that might indicate a faulty unit (vs user error):
1. Initial power up showed a "hardware test" screen (unexpected, no mention of that in the quick start guide).  I was able to figure out that I needed to actuate all the controls to get it to proceed, which it did.  Anyone else seen that?
3. F/W version shows v3.1.025 - I can't find mention of a v3 online, latest I can see at Conductive Labs' page is v2.
4. Serial number on packaging and case shows as 020-0873-2308, but on the unit's display is listed as "000-0000-0000"
So maybe this unit has been unpacked before, monkeyed with, and replaced in a non-working state?

What else can I try before I return this to the shop?
Any help is welcome.
Rob

My new MRCC is great, except when I am turning the knob to do various tasks, it gets to a rotation point and becomes very stiff.  I turn past it and it eventually stops being stiff.  Turning it backwards, it becomes stiff again.  Does this happen to anyone else?

When I recently got my MRCC in the mail, the green, blue, and black buttons were loose inside the packaging. I gently pushed them back on but when I turned the unit over, they fell off. Is this normal? Should I push harder to snap them in?  Should I glue them on? I don't want to void the warranty or break the electronics inside, so I'm waiting to learn what I should do. Thanks!

Hey! I can't seem to set up Aura plugins 1st editor for virus ti2 when midi goes via MRCC. 
In the standalone editor all MRCC ports are just called MRCC without any number, maybe this could be a problem.
In the vst editor it seems to completely ignore the MRCC port input and always gives an error, this does not happen if I connect via a non MRCC port.
Has anyone had issues using vst editors for hardware synths with MRCC?
Thank you,
Ivan
       

Dear developers, is it possible to achieve synchronous start of the LFO generator along with the start of the NDLR?  This will allow you to get controlled modulations that coincide with the beginning of the clock cycle. In the current firmware, the LFO starts immediately, and does not depend on the start.