Proud owner of The NDLR for two weeks, but I noticed something which seems like a bug.
When I use the modulation matrix to send out CC's, the destination is not saved with the Global settings. As soon as I turn on the NDLR or load a Global Setting, the destinations are set to 1-MIDIA even though I changed it and then saved it. Am I missing something? Firmware is 1.1.073

Also in addition, an offset for the MIDI CC value would be nice.

Greetings knowledgeable noodlers. My question is: Is there any info from the designers here on how to use the Chord Sequencer?  I'm not getting much from the manual and I've looked here on the forum a bit and discovered nothing in the way of basic operation.  Thanks for any help.

Just dreaming, but a fully digital, iPad-only version of the NDLR would be super awesome. It's easy to get midi out of iPads, and with a touch screen, you could overcome some of the limitations of hardware, like exposing all 4 lanes of controls at the same time, dead-simple rhythm editing, more memory, and the like.

Love the NDLR, and am just imagining about how to extend its NDLy appendages....

Hi All,

I am using the NDLR with the MC707 and I'm running into some wierd timing issues when I try to put the midi notes into the 707's sequencer. For the Motif's, as long as I am over 1/4 division and I adjust the quanitization from the MC707 side to 15/85 "whatever that means", I can get the first note to align with the first step. However for the drone and for the pad I can't get the first step and the first note to land. Any suggestions here?

I'm not sure if it's a bug or a feature, but my port filters reset every time I power cycle, which was messing me up a bit. 

It took me a while to realize that the port filter configuration wasn't saving with the preset (I assumed and therefore we're all now asses). Additionally, the program change messages that I'm filtering out from Midi channel 1 are not filtered from controlling the MRCC, even when the port filter is on for the channel (I later realized I had to turn MRCC MIDI Cntrl to another channel to stop this from happening). This created a cascading problem for me that was difficult to solve.

Since the MRCC was responding to program change messages that I thought were being filtered, I would find myself on a different preset later and not know how I got there. The presets are also loading with program change messages (which makes sense) but that means the presets have been changed before I can troubleshoot (I know now that the MRCC preset is changing with my EMX-1 preset, even when the port is filtering program change messages to the midi outs). 

So, a few suggestions that could be implemented alone or together.

1. Create an "OFF" for MRCC MIDI Cntrl port and make that the default or make the default a port other than 1
   
2. Allow port filter configuration to be saved with presets either as a default or via an option
   
3. Allow the MRCC to remember the last port filter configuration and start up with that configuration rather than a clean slate 
   

Just a line or so to tell you about the perfect tabletop stand for most any tabletop synth. Or, in this case, my favorite sequencer. It's cheap, sturdy, adjustable and nice looking. I don't benefit in any way from this. I just found something that works, and I want to share it.


I made a 90 second video if you care to watch.

https://youtu.be/cp60xe2SOrA

Or, here's a link to the item on Amazon.

https://www.amazon.com/gp/product/B089M6...UTF8&psc=1

If you look around Amazon you can find smaller sizes. Or, pair up your NDLR with your Typhon or nts-1 or what have you on one large stand.

You really should watch my little video! ?

I went with the SF Express shipping because the nice discount on shipping from Conductive Labs covered nearly the entire cost of shipping. Take my advice: Don't do this.

Now, don't get me wrong. I have no doubts that SF Express as a shipping company will deliver when they said they would. But that's the problem: I am going nuts with anticipation over how long it takes. 

If you're like me, which is to say it is difficult for you to be patient once you've decided you need the NDLR, spring for the extra shipping costs. 

I've waited two weeks already, and there is another two weeks to go. Aaaaaaaaaaaaaa!

Hi,

Just got my NDLR and started playing around with it, so far so great when triggering my different synths.
However, when i try to get clock out to my drum machines, the clock they receive is either stuck at 300 BMP (if i use USB) or 30 BMP (if using DIN5 midi).

My setup is as follows:

NDLR -> RK006 -> Analog4, MachineDrum, Xbase09, Tanzmaus etc.

Is there a clock multiplier or divider for the clock being sent out that i've missed in the settings?

Hi,

Is there anyone who can tell me more about the 'rotation algorithm'-feature? It's under [shift+menu] encoder 2. But I haven't got a clue.

I already posted this in the advanced features-section of this forum, but it's a little quiet down there.

https://conductivelabs.com/forum/showthr...p?tid=1456

Cheers,
John

A. Currently Pad quantization has 3 settings. 

 1/4, 1/8, none

Could this be expanded to : 

1/2, 1/3, 1/4, 1/6, 1/8, 1/12, 1/16, 1/24, 1/32.... none

without compromising the overall integrity/stability of the operating system?
(actually hopefully improving the stability/integrity of the operation system...)

I am requesting this because while I have found more stability with pad quantization set to 1/8th for use with the MV8800...this makes it much harder to trigger a chord on a triplet....and the current CC assignment has 3 integer values for 128 available integers...So by expanding the pallet of quantization and letting us "stick shift" the values via automation via external sequencers...it could be a win/win solution that is not too hard to realize.

B. Max pad voice limit to range... Currently if we raise the spread, it has a direct effect on the amount of voices used...I thought it would be nice to perhaps have a "range within" function...so triggering the pad with a limit of (x) voices...could be distributes across a wide range without trigger a hole heap of notes...but would "pick" them out of the range in either a random or predetermined format that was kept to (x) as the pad voice limit.

I am requesting this because triggering 14 voices at once is cool for some patches but sometimes unnecessary because it can cloud the frequency lanes as we use different synth patches...resulting in a muddier mix to manage...I love having lots of voices...but the range is what decides how many are triggered, it seems.

C. Pad Strum (direction) , Pad Strum (skip), Pad Strum (carry over):

Pad Strum (Direction): up, down, SeeSaw(up then down), Random.(the direction options would be added to the current midi cc assignment)...and triggered each time Pad is triggered.

Pad Strum (Skip) : there is a probability variable assigned to the Pad...for sparse, happenstance notes being struck...providing a different way to achieve generative tones, passing notes and embellishments.

Pad Strum (Carry over/Cascade): If a Pad is hit before a strum is finished completing itself, could a "carry over" variable be applied for a specific interval of BPM time(1/2,1/4,1/8 note)...so they could "cascade"?