Hi guys,

Just received my remote 7 and looking to start rewriting part of my studio.
I was wondering whether using a midi thru box on the remote ports would add issues or whether it should be fine (can the remote power a thru box through 5 pin midi or would they need separate power is a sub question to this).

Thanks in advance.

Pep

Hi,

I managed to connect the Launchpad Pro (not the MK3 version) to the MRCC and make it work in Ampify Studio! 
https://support.novationmusic.com/hc/en-...Comparison


I use MIDIOX to verify the midi messages. Very helpful!
http://www.midiox.com/

Ampify Studio
https://ampifymusic.com/ampify-studio/
https://support.ampifymusic.com/hc/en-gb...ify-Studio-
https://support.novationmusic.com/hc/en-...ify-Studio

It helped me to remove all routings and start from scratch to see which virtual port or which pc port or MRCC channel works for your configuration.

Step 1: 
Connect Launchpad Pro with Power Supply and Orginal USB-B cable to the MRCC
Connect the USB cable from the Launchpad to one of the USB connectors of the MRCC. In the pictures, my Launchpad is connected to B.
Connect the USB cable from the PC to the PC connector of the MRCC.

Step 2: 
Select and hold the green button of the MIDI IN/OUT connection of the Launchpad and select Virtual Port 1.
Release the green button of the Lauchpad connection.

Step 3: 
Make sure that the green button of the Lauchpad connection is still lit.
Select and hold the blue button of the PC connection and select virtual port 1 (out of 12). Make sure all other virtual ports are NOT connected. 

Step 4: 
Verify the routing. In my setup B is connected to P01
Now the Launchpad is connected to the PC.

Step 5: 
Set the Launchpad in the Live mode and make sure the Midi In and Midi Out buttons are lit in the setup.
Press Setup button
Check the Midi in and Midi out pad lightning settings
https://support.novationmusic.com/hc/en-...nchpad-Pro

Both need to be enabled to see any lightning response from midi and when you press the buttons on the launchpad.
Select the Live Mode and the Launchpad will restart.
   

Step 6
The Launchpad Pro will restart in the Live Mode and you can try to press some buttons on the Launchpad. 

Step 7
The main area is dark and only the buttons pressed light up with random colors.
Verify in MIDI-OX wether midi messages are coming into the PC or not.

Step 8
Make the PC to Launchpad Pro connection by first select and hold the green (left) button of the PC connection and select virtual port 1 (out of 12) from the PC.

Step 9
Release the green (left) button of the PC connection and make sure it stays lit.
Select the blue (right) button of the Lauchpad connection

Step 10
The connection from the PC to the Launchpad is made. Verify the routing. In my setup P01 is connected to B.
   

Step 11
In MIDI-OK you can enable the Keyboard modus. By pressing keys on your keyboard, it will send midi notes to the Launchpad. You should see pads light up on the Launchpad.
This is an important step. Double check if the midi in/out/pad lightning is enabled in the setup modus of the Launchpad. The PC is now able to send midi commands to the Launchpad.

Step 12
Open Ampify Studio (or Ableton Live or any other DAW) and configure the Launchpad Pro as controller. The Launch Pro is displayed but disconnected.
   

Step 13
Click on the 3 dots and select MRCC as the input device

Step 14
Select the MRCC as the output device

Step 15
Open a Sound Pack in Ampify Studio, select open template and the layout of the Launchpad should reflect the sounds in Ampify Studio.

Step 16
Select a few sound in Ampify Studio

Step 17
The Lauchpad should highlight the playing sounds. Now you can also control Ampify Studio from the Launchpad Pro

   

I hope this helps!

Thanks 
Marcel

ps. the number of images in a post is limited, so it took a while to rewrite this post 

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