Hi, 
First of all thanks for making a great product. 

I'm struggling a bit though with some things. One of the things is that I seem to be getting Motifs that sometimes run synced to the beat, but sometimes seem to start (and run) off the beat. 

This is the way I can reproduce it:
1. I use cakewalk, it sends out a midi clock (90 bpm in my example)
2. Ndlr clock in=> USB 1
3. I have drone and motif 1 "on" before starting the sequencer. Motif 2 is off. Simple 1/8th patterns
4. I start the track on cakewalk, drone and motif 1 run in sync with Cakewalks metronome
5. Now using the switch on the Ndlr, i switch Motif 2 on. Sometimes it will run exactly on the beat. Sometimes it will start in the middle of the beat and stay that way. I can switch off and switch on again and sometimes the motif is on the beat again, and sometimes it will be off the beat. So completely independent. 

I have a feeling it has something to do with how close to the beat I switch the Motif on, but it's really hard to make certain it doesn't go wrong, so this will make it very hard to use in a (semi) live fashion.

Hope i'm not repeating something that has been asked before, I have searched.

By the way, version of the firmware: 1.1.066.

Best regards,
Arian Prins

[ NOTE: this thread has changed from a question about reading settings into a working Max for Live MIDI Effect which will request all the current CC settings. Jump to post #9 for that juicy goodness, and then you'll also skip my silly floundering before Jesse put me on the right track ]

Hi there. Just started work on a NDLR CC control widget for Max for Live. Basically just wrapping Appendix A in a load of control knobs that send the appropriate CCs.

All good so far, sending CC's like a good 'un and messing with the automation that allows. But there's a bit of setup I'm struggling with - I want to get the initial values of the settings and pre-load them into the knobs so that there's no "jump to zero" when you connect to the NDLR (or the first time you turn a particular knob).

So, can I read the existing settings? If I'm being an idiot, feel free to set response to "Burn". I need to learn!

Thanks.

I'd like to humbly request a couple minor changes to the CC#s that the NDLR responds to currently. This is actually a two-pronged request, and I realize I should probably split it into two separate threads for clarity, but I'm lazy - so please treat this as two separate and independent change requests.

REQUEST 1:
I'd like to have another CC# added to control the Pause / Play aspect of all four parts, in one word. Currently there are four CC#s used, one for each part, with accepted values of 0-62 implying Pause and 63-127 resulting in Play. I'll skip the lengthy reasoning why this is difficult for me to integrate into my NDLR usage, but having one CC# for all parts would make it easier (for me). Use just the bottom four bits for control, and ignore the higher order bits. Perhaps something like:

Bit0 = Motif 1
Bit1 = Motif 2
Bit2 = Drone
Bit3 = Pads
Where, 0 = Pause and 1 = Play

This implies a 0-15 acceptable range, but if higher order bits are ignored, then the pattern of 16 valid codes repeats through the entire range of 0-127.

REQUEST 2:
I love the Modulation Matrix, but I'm disappointed that there just aren't enough sources. I'm not requesting more LFOs or preset modulators, but rather a path for user supplied external oscillators to be used as sources. Very similar to the MIDI inputs, but more of them and with a consistent usage pattern. Therefore, I propose using a block of eight CC#s from 100 to 107 as sources for the Modulation Matrix. My justification for this request stems from my past usage of an Alesis MMT-8 sequencer as an octal MIDI-sync'ed LFO generator. This would give a greater frequency range, wave shapes, phase relationships than the ones included in the stock NDLR.

SUGGESTIONS TO FULFILL REQUESTS:
I made a chart showing the CC#s as defined in the NDLR currently, and suggested changes to realize the two separate requests of this post, see attached.


  NDLR CC chart.txt (Size: 8.18 KB / Downloads: 4)

This chart displays all 128 possible CC#s and NDLR uses, in addition to standard MIDI definitions of common or reserved CC#s. The vertical columns are (from left to right):

CC# - the CC#
Resr - Reserved
Genl - General use functions of NDLR
Mot1 - Motif 1 specific functions in NDLR
Mot2 - Motif 2 specific functions in NDLR
Dron - Drone specific functions in NDLR
Pads - Pads specific functions in NDLR
Prop - Proposed new functions in this request
RANGE - Indicates allowable values that are recognized per CC#
TARGET - A brief description of the CC# function

The dashes under Resr, Genl, Mot1, Mot2, Dron, and Pads visually show how each CC# is used. Periods are used in those fields for the proposed changes, which are designated with YYYY and XXXX in the Prop column (differentiating the two different requests).

I hope this makes sense. If any clarification is needed, please ask. I also hope that the level of effort in making this request gives a hint as to how much I'd appreciate having these features added.

Thanks,
House de Kris

Hi there Ndlr’s
I was wondering if it’s possible to power the Ndlr  from polyend seq over usb.
I got a usb a/b converter so the connections are made..
I’ve seen a tutorial on YouTube with the Ndlr and a deluge..
and I thought it should work as well, but it doesn’t??
Thanks for the help.
Cheers
Malte

Hello there, just got my brand new NDLR and was very excited to connect it to my iConnectivity MIDI 4+ so I can integrate it into the studio. Sadly, it's not recognized. This is an issue for me as I am entirely out of DIN ports to run it through. 

I saw the thread on the MioXL not working either but I figured I'd start a new one since I didn't want this additional incompatibility to get lost in the shuffle.

It is just before dawn.

The sprinklers have just come on.

The span of its rays undulate in meditation.

Its fluctuations create the illusion of perspiration.

Upon blue surfaces 

Cool bodies lie. 

Minute droplets appear.

Disappear.

All music was created from various modules in VCV Rack and from various softsynths, all controlled by the NDLR, then edited in Logic Pro X.

All video was created from various copyright-free clips from the Internet Archive website, then further manipulated using the Hyperspektiv app, all the Edited in iMovie.

Click here for Sprinkler: A Poem

What settings or features are planned for the "shift menu" and "shift encoder" options? Knob 2 and 3 on the left side, and 3 and 4 on the right side.

Hi all,

Just wanted to say hello to everyone.
New to this forum but not so much to electronic music.
Willing to give this NDLR a go and actually waiting delivery of a second hand unit.
Can't wait to be honest.

Will be using with various hardware (and VSTi).
MiniNova
MicroFreak
Deepmind 12D
Toraiz AS-1
TR-8
Digitakt

Best,
v

I read the manual and didn't find how to set the velocity of the pads / motifs and drone so it is use the incoming velocity instead of a fixed value. Is this possible ? Could it be a possible value please ?

ps Just started using NDLR and I really appreciate the device.

Using only the NDLR and MPC One. My first ever jam with the NDLR. Something a little more uptempo than a lot of ndlr jams I've seen. 

https://drive.google.com/file/d/1pZDfyFy...p=drivesdk