Hello,

I just received my unit the other day and I was curious if anyone is have issues with latency regarding a drone note when pads and motifs are playing.  When I press the circular black button to change notes the drone sometimes does not trigger with the pads and the motif at the same time and comes in late. When I record what I am doing within reaper I can see the drone note definitely comes in late from the other instruments.  Any help would be much appreciated.

Hi all,

I'm jamming ndling around within the scale of Eb minor and noticed that the VI chord is displayed as C, but it should be B. (C is the VI. interval for Eb Major) It's sending out the correct notes for a triad chord, though.

But when changing the chord mode to sus4 the notes B F and F# are sent, but it should be B E and F#. 

I haven't checked it in every key and mode but the wrong notes for the sus4 chord are sent in other scales and modes as well and it's somehow connected to the Intervals and not to the chords itself. 

For example: F#sus4 VII in G Major scale is sending a wrong note (C instead of C#), but F#sus4 I in F# is sending the correct notes.

I used http://www.looknohands.com/chordhouse/piano/ for looking up the chords and using Firmware v1.0.6.3

Cheers Triscus

You can see it here: 
https://youtu.be/b3_AkXiLxRY

It looks like there may be quantization bug when playing chord sequences (firmware v1.1.063).

Steps to reproduce:

1. Set Pad Quantize: Pad Qt: 1/4
2. Create the following Chord Sequence:

Section A, Slot 1:

• 4.0 x 1/4 Notes.
  
• C Major
  
• I C Triad
  

• 4.0 x 1/4 Notes.
  
• C Major
  
• IV F Triad
  

• The chords correctly start on the first beat of each bar.
  
• Each chord plays for 1 bar + 1/64th extra, causing an overlap of the chord notes on the first 1/64th of each bar (from bar 2 onwards).
  

• The first chord plays for less than one bar (57/64ths).
  
• The second chord starts 7/64ths early, i.e. it begins during the first bar.
  

Greetings,

I do apologise if this has been discussed.

Downloaded latest Teensy 1.48 for Mac

unzip .dmg and unzip latest FW to .hex

Connect USB from Mac to NDLR 

load FW.hex to Teensy and press button onto Teensy

Nothing Happens, checked NDLR, still the old FW.

Any advise highly Appreciated 

Peace
JY

Just got the NDLR and am learning the ropes, however have an issue with Encoder 3. It responds to a press, but will not change values when turned. I've power cycled and updated the firmware - the first time I updated it appeared to resolve the issue but it quickly returned and hasn't gone away. Big bummer. Seems like exactly what I am looking for to drive my synth rig so don't want to refund/send back but also don't want to wait for weeks to get going. Not sure I've seen anything similar so definitely feel a little deflated at the moment. Any suggestions? Thanks!

Hello. It would good to have the option to de-couple the motif from the chord changes, keeping it locked to the root, as with the drone. I'd also like to be able to de-couple the motif from chord invert, so it plays more like a 'traditional' sequencer, just transposing the pattern while the pad inverts. 

Thanks

Rob

Greetings all,
I got my NDLR a couple of weeks ago, but with job and life haven't had much of a chance to dive in until today. I just made this little ambient noodle using a Depmind12 on the pad, Neutron on the drone, Model-D on motif1 and another Neutron on motif2. Drumbrute is providing a little support.
Ambient Noodles?

I am having persistent problems getting my NDLR to work consistently at a basic level. I am using it with an iPad and I have successfully routed the four modules to various synth apps. I have done this using port 1 and channels 1 to 4, although I have also tried using individual ports (1-4) with all channels (omni) selected, or even port 1/channel1, port2/channel2, etc. I don't really understand what the ports are, but in any case it makes no obvious difference to the following behaviours.

I am persistently getting a lot of stuck notes. Now I don't yet know whether this is down to the NDLR or something on the iPad setup, but in exploring it I have zeroed in on another, perhaps related issue I have noticed from day1. That is that I sometimes press a chord change button but even though the NDLR screen changes to show the new chord, the chord doesn't change. In fact it's worse than this, because sometimes the chord changes for one part (e.g. motif1) but not another or others. I have captured this with some MIDI monitor screen shots.

Here's what happens when I press the Pad button to start. The screen shows the chord as Ic in white and it plays a C major chord. So far , so good. But now I press the IV chord button. The NDLR screen changes to show the chord as 'IV F' in white, but the sound doesn't change. Here's the monitor - the Pad part is the leftmost column and the MIDI messages are shown with the most recent at the top:

   

Now I press Pad again to stop, but it looks like only one OFF action is sent. Here's the monitor:

   

This leaves some notes stuck on. I can clear them with shift+panic. Now I press the I chord button and Pad again, but I get an unexpected sequence of OFF/ON actions (I have cleared the log screen so only the new messages show):

   

And finally, here is the aftermath of the same problem but with the Motif1 part also running (column 2). You can see that Motif1 has been transposed to play an F chord, but the Pad has not:

   

Does anyone else see this?

Good Afternoon Everyone. I'm bad at ndlr

I would be very grateful if someone could offer step-by-step instructions.


Thanks