Hi!
I think I found a bug.
My NDLR chrashes when I'm doing the following:
Going to MOD MATRIX, chosing a Mod Source, setting Mod Destination to MICI CC #1
and then when I turn Mod Source to "SCR OFF" again, it crahes.

As far as I can tell now it only crashes when I have set Mod Destination to "MICI CC #1" not when I chose any other Mod Destination (like MICI CC #2 etc..)

Can anyone reproduce this behavior?

btw: I have FW v1.1.014 installed but problem still exists.

BI don’t know if I’m missing something or not but if anyone can help me out here i’d Be grateful.

I’m trying to use an external midi keyboard to transpose the patterns / pad / drone. I’ve connected my keystep via 5 pin midi A and set the trans input in the settings to the correct midi channel but I cannot get the nldr respond to the keystep output. The output is working and on the correct channel as it works if I set it to the control input and use the same midi channel To control the chord and black as expected.
My question is, does the trans input do what I assume it does and transpose the patterns from the keyboard and if so then what am I doing wrong?

As I wait for my NDLR to rise to room temperature (it arrived by courier van, and where I'm at IT'S COLD)
I'd first like to comment on the stellar packing job. It was packed better than any instrument I can remember from any manufacturer- ever; job well-done guys! It doesn't seem like a 'homegrown' production imo- very professional presentation of which I am extremely impressed. Little things like this matter, so I wanted to commend Conductive Labs setting a precedent of excellence for Kickstarters everywhere! .

And don't think I didn't notice the build quality- 10 out of 10- even the screen protector is quality and I may not even remove mine

Seriously CL, it's nice to see you really care about this product. I've backed a kick starter in the past that was close to garbage in build quality and the developer is an a-hole who made function promises 3 years ago that still haven't been implemented- even though all the backers paid for the extra functions.

You guys are clearly on the path to success. If this is your first effort, I can't wait to see what you do in the future!


All the best!

My NDLR just arrived in the mail, so this is my first post. Excited to dig in!

Was checking out the various options and got an idea. Title says it all. I think it would be interesting to be able to modulate the global tempo using the modulation matrix. I was looking at Appendix A. MIDI CC (Control Change) Implementation and was thinking I could potentially send the MIDI CC LFO signal back into the NDLR, but being able to directly select it in the destination option would be slicker. 

Also, in Appendix A I stumbled upon this:

Quote:NOTE: CC messages 75-79 (4Bh-4Fh) are used as inputs sources (#12-#16) to the Modulation Matrix

Hello NDLR users!

I am now exploring if it is possible to use a MIDI foot controller (in my case, a Roland PK-5 or a Behringer FCB1010) to change the programs in the NDLR while it is running.  I’m not sure I have found the proper information in the current V1.12 manual to support this idea.
 
I have a concept for live use:  I can call up a preset, say in the key of A minor on the NDLR.  I have all my synths set to their respective part (pad, drone, motif).  After hitting play, the NDLR does it’s stuff in the I chord, the A minor.  Perhaps I am tweaking knobs on one of the synths, or playing another synth as well, or guitar.  Then I step on my MIDI foot controller and it changes the NDLR from the I chord to the V chord, another step to the VI chord, another step to the II chord, and then back to the I chord.

This way the NDLR changes live in real time under control, instead of sequenced.
 
Is this something that the NDLR can support?

I appreciate all of your input in this matter.

To skip mambo jumbo go to "here is how this feature looks in manual” a few lines down 

In order to make a single session more responsive for live musicians we could introduce snapshots. 
As with my previous feature request we could use Motif Knob #5 and it’s 3rd slot with arrow/triangle pointing to the right. 
Also you need a small "real estate on display”; You can shrink the "Pad, Motif ranges" area by 25% thus getting extra real estate 
For this feature you need an extra letter+number into the right top corner (the left corner could be used for my previous feature quick sequencer)  
Create adhesive or sticker that advice that there is one more function on the knob #5 (I can chip in here)  
The only drawback is that you need 26 values, when compressed you’d still need approx. 15 bytes per one panel snapshot x 3 thus 45 bytes for panel and 6x4 24x2 (the only one you can compress is source only 10 values there and let say 2 modulation snapshots would be enough) 
so snapshot memory will cost  50+45 ~ 100 Bytes per session. Yaaack  

Here is how this feature will look in the NDLR manual 

You can save/recall 3 panel snapshots and 2 modulation snapshots with most of the values. 
The panel snapshots will save all motif1-2 values and all Drone and Pad values (9x2+4+3) 
How to save a snapshot 
1. Dial Snapshot feature by pushing the encoder #5 and setting the triangle pointing right
2. Choose S (Save) in the top right corner  
2. Then hold the button “II” for 3 seconds. All the settings for 4 channels will be saved to snapshot position II
3. You can use button ‘III”, ‘IV’ to save 2 additional snapshots per session 

To recall a panel snapshot:
1. by pushing the encoder #5 get to the snapshot function (triangle pointing to the left)   
2. A letter appears in the right top corner. Choose R for Recall  
3. Click one of the 3 left buttons (‘II’,’III’,’IV’) to recall one of the panel snapshots 

You can also save and recall modulation matrix All sources, destinations, ranges and offsets for modulation slots 3-8. 1-2 are the same for all snapshots within a session.   
The procedure for mod matrix snapshot is similar to saving the panel snapshots but you will use ‘V’,’VI’,’VII’ buttons for this (3 if you have enough memory).

Notes:

I purposely left the fourth knob values out of the snapshot b/c it is unlikely to change a key (unless you’d do transition) in a middle of a session 
I purposely left 2 first modulations “static" b/c the chances are that you'd NOT be chaining ALL the modulations.
You essentially increasing number of modulations slots using this feature.    

This feature is NOT as easy to program as the "quick sequence” feature (my previous post). When you change a lot of parameters at the same time you'd need some order at which these changes are sequenced applied so no MIDI panic is needed after applying snapshot (Especially modulation snapshot). But I guess you’ve done this work with recalling sessions right ? 

Yes no more memory left in the unit ... yeah I got that, but again I'd sacrifice a few chord patterns for 2-3 snapshots.  
And this is NOT "shooting in dark feature request". I spent with NDLR closed to 60 hours. (Count that hours not spent with my kids) 

And Darryl, you can take this to the next level by altering some of this description to fit into your schedule, 
especially the memory issue.  I hope you will keep improving this. 

The future for NDLR is bright... I will hook the NDLR soon to my modular via some "MIDI to CV" interface, just give me note length humanization into next release.  

There are 5 knobs with only two functions. One could be used for quick sequencer/chord progression. 
Just enter a chord degree and chord type. This could be saved with a session. To activate use one of the knobs. 
Say we use knob #1 (Pad) and dedicate a small part of display to 3 letters P,E,M (Play, Erase, Manual) Yes there is a bit of real estate for one extra letter) 
Those are only 3+3 bits and 2 bits for repetition so with 10 bytes you could program up to 40 bars of chord progression.  
(3 bits because there are only 7 values) 
This kind of pattern programming is familiar from Pocket Operators very intuitive and easy. 
With more memory you could save 7 sequences per session. (there are 7 buttons) 



Here is how manual addition would look for this feature.

Quick Sequence Feature
You can program a quick chord progression with NDLR.

1. Click the first knob to navigate to QS function, A letter in the left top triangle will indicate sequencer state 
2. Select the ‘P’ to record and play chord progression 
3. If you have a previous sequence programmed  dial ‘E’ and hold button “I" for 3 seconds to erase
3. Start to add steps by using 7 chord buttons same as If you would play NDLR 
4. To repeat a chord just click the button twice (chord type from previous step will be remembered) 
5. As you entering notes the chords are being played and number next to the R shows bars already entered
6. If you make mistake just go from P to E and press the “I" button to delete the last entered step
7. The M - manual mode is to trigger the chord change manually with the “I" button 

Yeah I know we would need a sticker on knob #1 but hey for a quick sequence to practice with NDLR why not

Hi,

Currently, when driving the NDLR from an external sequencer, the NDLR disarms all the parts when it handles a MIDI stop message. I'm finding it a bit frustrating as I have to remember to re-arm the particular parts when re-starting the sequencer. Could we have the option so the NDLR doesn't do this? It should still do everything else it does on a stop message (e.g. release any held notes on all parts), just leave the arm state of each part alone.

Cheers,

Ian

There is no way to alter the velocity of the drone. 
Is there anything that could be done about that ? 
Thanks

This only applies to MOTIF tracks. 

Yes we can create new rhythmic patterns where we use the TIEs to make the NOTE-ON/OFF interval longer. I’m already running out of slots doing that.

What would really help is to double the humanize range from 1-10 to 1-20 with the second half randomizing Note duration too. 
so values 1-10 would still do Velocity/Timing (Not sure if timing is there already) 
and values 11-20 would add note duration randomization with focus to shorten notes rather than make them longer.  

....Another option would be to add a new destination called "Note length” to MOTIF sections ...But that would take 2 of precious slots
away. 

Thanks!