Hi. Long time DAW user here branching out into the world of hardware. I’ve just got my hands on the NDLR and am loving it. Currently set up to control soft synths via Logic Pro and also have it hooked up to my Novation Peak.

My question is; can the NDLR control the start/stop of the play head in Logic (or DAWs in general), when pressing one of the four play button at the bottom, or the global play button?

I’ve gone through all the menus of the NDLR and Logic and tried loads of different permutations but I’m guessing it either can’t be done or I’m missing something real simple. 

Thanks in advance for any help. Pete.

Hi, I'm new to the MRCC, and so far it has been a great experience. I'm currently wiring together a DAW-less setup and want to make sure I'm not missing any tricks.

I've connected my Keystep Pro with USB, and set up channel mods 1-4 so that #1 = exclusive, channel 1 to 1, ch 2-3 to 16; #2 = exclusive, ch 1, 3 and 4 to 16, ch 2 mapped to 1; #3 = exclusive, ch 1, 2 and 4 mapped to 16, ch 3 mapped to 1 – and #4 in the same manner but for ch 4. This way, I can route the Keystep to multiple ports and choose a mod per port in order to control specific synths from a specific tracks without having to change the channel on the synth.

Is this the only way to effectively filter channels on a route?

As far as I know, the Keystep Pro does not support virtual wires, which would've been a much better solution. If I'm wrong, do correct me, please :).

My NDLR does not seem to respond to MIDI Program Change (PC) messages to select presets.  When I send the PC number, nothing happens.  I can recover the presets manually using the physical controls on the device, but I primarily control the NDLR via external MIDI foot controllers, so using the NDLR's physical controls to change presets doesn't work as well for me.  Is there something else that needs to be transmitted with the PC message?  Or some other trick?  (For example, some of my external synths require an additional MSB/LSB number be transmitted along with the PC message.)

Thanks in advance?

Does anyone have an updated or corrected MIDI implementation chart for the NDLR?  The one included in the manual seems to have a significant number of inaccuracies/omissions.  Here are some of the ones I've discovered:

• CC 26 (chord degree) -- The manual chart says the range is 1-7, but it appears actually to be 0-6.  For example, sending a "1" results in a II chord, not a I chord.
  
• CC 27 (chord type) -- The manual chart says the range is 1-7, but it also appears to be 0-6.  For example, sending a "1" results in a 7th chord, not a triad.  (Note -- The range being off by one does not seem to be a universal issue.  For CC 73 (key), the chart says the range is 1-12 and the range really seems to be 1-12, with a "1" resulting in a key of C.)
  
• CC 30 (pad range) -- The manual provides a range of 1-100, but doesn't indicate that the number sent will not be equivalent to the range intended.  For example, sending a "4" results in a range of 1 not a range of 4.  After trial and error, I discovered that sending a "15" results in a range of 4.  So it appears there is a range of numbers that correspond to specific ranges, but finding the right message numbers takes time consuming trial and error.
  
• CC 28 (pad position) -- Similar issue: the number sent is not equivalent to the position intended.  For example, sending a "66" does not result in a position of 66 but instead results in a position of 78.  I can find the right message to send after trial and error, but this is a time consuming process.
  
• CC 90 (all start/stop) -- This CC number doesn't appear to work.  Sending a value on this CC number doesn't impact my device.  To get an all start/stop, I have to send individual CC start/stop messages to each of the 4 parts separately (via CC numbers 85, 86, 87, and 88).  While this is something of a workaround, it doesn't do the re-syncing of motifs that an all stop/start would do.
  
• CC 120 (panic) -- CC 120 isn't included in the manual's MIDI implementation chart.  I only learned that it was a possibility when I received the Nov. 22 newsletter about the new firmware update.  The e-mail says that the CC is being changed from 120 to 123 -- but neither CC is included in either the v. 1.9 or 2.0 manuals.
  

What are the differences between the two versions?
Will all new functionality developed for v2 be ported to the v1?

When I try to route a MIDI input or USB input to the DAW routing does not work. 
I can route from hardware ports fine. 
When I try to set it up i get this on the routings page:

(physical port 6 and USB A1 used as examples)
6 -> none

OR 
A1 -> none

Turning the knob does nothing. Of course there are no buttons for these virtual ports, so I only can use the Routing page. 
Please help, if I can't actually send MID via USB into my DAW the MRCC isn't going to do me much good
Cliff

Is it possible to use the 880 from the MRCC as an expander, i.e. from the 1 of the 4 MRCC USB midi to the 880 PC usb?

Fellow knob twiddling folk, 

I have already noticed some requests for the NDLR to gain some of the capability of pseudo-random sequencing devices such as the Stochastic Sig or the Vermona Melodicer, and I would like to add one of my own - a feature of the MIDIcake ARP:

Take an existing MIDI stream as an input and then be able to produce a related MIDI output based on a combination of how the NDLR is configured for that particular patch (that is the scale type and root key) combined with pitch information it is receiving as MIDI note input data. That is, essentially re-sequencing the MIDI input notes using the NDLR as an intelligent modifier of pitch data, to produce new drone, chord and arpeggiated sequences. 

[Note: I'm not talking about the way NDLR can currently respond to incoming monophonic notes by way of an alternative to the front panel controls.]

Something along the lines of what the MIDIcake ARP is doing here:

https://youtu.be/d5xK471xlJ8

I'd also like to see the NDLR be able to generate Pgm Change messages, as well as respond to them for selecting its own internal patches (i.e. setup configs) ... unless I've missed this capability!

Finally, a flabbergasted comment: 8 patch or setup memories!? Dear Lord ... just how retro are we going to get with some of this new gear!? Has anyone not seen how cheap MicroSD cards are?

Other than that, I'm still loving it! 

Anyways, just my personal thoughts...

Cheers,
Steve.

Hi All - I have been using the MRCC in a medium sized dawless setup and have been very pleased at how intuitive and reliable the functioning has been, including with regard to using the MRCC as a master clock for my hardware synths.

I occasionally use a DAW (Reaper) and have been recently trying to sync the DAW to MRCC clock without success.  I have read both the MRCC and Reaper manuals, watched the relevant videos, and searched multiple forums, but can't seem to find a solution to this problem.  

I am able to successfully output midi clock via the PC port on the MRCC to my MacBook Pro, and confirmed using Mac MidiMonitor that the clock is being received.  Within Reaper, I can select MRCC on the appropriate port in "External Timecode Synchronization", but can never get past the "waiting for timecode" error message when I try to play/record.

As near as I can tell, MRCC can only send MIDI clock (MidiMonitor does not show any MTC or SPP messages incoming to my computer), but Reaper will only sync to MIDI Time Code (MTC), SPP, or LTC.  I can't for the life of me figure out a way to either 1. have the MRCC send MTC, SPP, or LTC or 2. Reaper receive MIDI clock.

Has anyone been successful syncing Reaper as a slave to the MRCC?  I have a few VSTs (Scaler, Cthulu) that I would like to use to send chord progression/arp patterns to my hardware through MRCC, but can't figure out how to do this while staying synced to the MRCC clock for my other devices.

Is it possible for MRCC to send MTC or SPP?  Would getting an external MIDI clock like an ER-M solve the problem?  

Thanks for your assistance and please forgive any technical ignorance (I'm trying to read manuals and better understand MIDI but its still hazy).

Ted

Just received my NDLR v2 with the red base which I updated to the v2.0.014 firmware . The encoders “click to value” is inconsistent sometimes it takes 1 click to change the value sometimes 2 or 3.  It looks like in some older posts this was also a issue .  Is mine defective or Is this just the way it is ?