I'm using a Keystep midi out connected to the midi A in on the NDLR, sending note data to a couple synths on the A out. 

From what I can tell, it appears that the NDLR is not passing through / transmitting any pitch-bend data to the connected synths. Is this expected? Is there a setting for this that I have missed?

I sometimes find it difficult to make fine adjustments to parameter values via the encoders. I seem to turn them just a little to far, or too fast and skip over the values that I'm trying to select. How about a global sensitivity / acceleration setting for the encoders so we can adjust the overall encoder "feel" to taste?

I would hope the team could do a thorough check of all functions controllable via CC from a DAW.

1/ What is very obvious is the 'flashing' of the display, that does not happen when editing locally.
2/ When driving from CC's often a red 'MTC' will appear which is distracting and probably unnecessary
3/ CC47 DIV is not functioning
4/ CC48 and CC50 trigger bad screen flashes and a yellow 'NO' in the bottom LHS
5/ Events (especially notes) triggered via CC are way slower than when triggered via notes. Example: Bitwig keyboard Vs Bitwig button CC's, both piped through the same signal flow i.e Bitwig>NDLR>Bitwig Instrument
6/ In Bitwig there is only latched buttons on/off available to trigger notes, modes, scales etc via CC. So what happens is when selecting another button, instead of triggering a new event and killing the old one....the CC's are summed. 
ex: Press a D,E,F,G,A or B note, press again to release and the C drone is triggered.
ex: Press a 2,3,4,5,6 or 7 Mode, press again to release and the 1 mode is triggered
ex: Press mode 2 + 3 and mode 5? is triggered etc....
i.e additive behaviour when using CC's ....a bit like the old rhythm machines where you could hold down multiple buttons to combine rhythms.

Hello all!

I am happily awaiting for my NDLR.  I run all of my MIDI through a MOTU MIDI Time Piece.  I was wondering if any one else is doing the same.  I know it should be simple in setup and execution, but I was looking to see about the experience.


Cheers,

LeVillian

Hi,

I was playing about with motif patterns and noticed that my NDLR was playing two different pitches when the pattern length is set to 1. I did a few experiments and discovered that it only seems to happen for certain variations (Ping-Pong and Odd-Even). The pitches played seem to be based on the first 2 steps of the pattern (i.e. motif pattern length of 1 and 2 produce the same notes). 

Needless to say this is only noticeable if the pitches for steps 1 and 2 of a pattern are different   .

Just thought I'd mention it in case it wasn't a known bug. Is there a list somewhere? It would be useful to know what issues are known about.

Hi all, I have a problem with encoder 5. I can select left to right but whilst it clicks it doesn’t change from position to patt-len. 

It’s the same for both motif 1 and 2. I’ve done a factory reset and a few power cycles. The feel of the encoder is no different to the others. 

Really hoping it’s not faulty and I have to return to states. 

Any ideas?

The NDLR was used sparingly to drive the Volca FM in this studio jam session:

https://www.youtube.com/watch?v=rKDJLmR0pGY

Hi,

In my setup I have all my MIDI devices connected to a iConnectivity MIO 10 which handles all of the MIDI routing / merging. I'm trying to use my sequencer (a Deluge) as the master clock and have set the NDLR to external clock mode. In this case, the MIO 10 will route the clock from the Deluge to all the other MIDI devices, including the NDLR. 

The problem I'm having is that the NDLR is echoing the clock to its MIDI outputs and so back to the MIO 10. This makes sense when the instruments are directly connected to it's MIDI outputs. However, in my case it means I get two sets of clock signals, which are then merged by the MIO10 and so cause all sorts of problems.  It doesn't help that the Deluge auto detects internal / external mode for the clock by listening for clock messages. As soon as the NDLR echos a clock tick, the Deluge switches from internal to external clock and everything stops.

So, is there a setting in the NDLR to disable the clock echo? The MIO 10 lets me work around the problem by filtering out real time messages from the NDLR's MIDI port but it means remembering to undo this change if/when I want to make the NDLR the master clock. I was wondering if there is a way doing this where I only have to reconfigure the NDLR...

Here's a raw capture of an early play with the NDLR after spending a couple of days integrating it with my setup. All melodies are generated by the NDLR sequenced from a Deluge. The instruments used are:

Motif: MakeNoise 0-Coast
Pad: Audiothingies Micromonsta
Drone: Behringer Model D

Drums and Chord Sequencing: Synthstrom Deluge

Man I love this thing!

https://soundcloud.com/drgrov-482815708/...-1/s-5UWsQ

Hi all.

I've just got my NDLR and I'm having fun integrating it with my setup.

I've been testing the sync with an external sequencers (a Deluge in my case) and seem to be having some problems with sync. The Deluge is set up with simple 4 beats to the bar drum pattern. The NDLR is the master clock and is also sending start/stop messages. I set the clock divider for both motifs to /1 so the note patterns would match the rhythm from the Deluge.

From stopped, I can start one of the motifs using the relevant button and everything is in sync. The Deluge drum beats are in time with the motif notes.

However, if I start from the "All" button, the NDLR seems to pick up the sequence from where it last stopped and the Deluge drum beats can be out of sync with the motifs. When this happens, I can stop/start motif 1 and it will be back in sync with the Deluge but out of sync with motif 2 (until I stop/start motif 2).

There's definitely something odd going on.