In Mod matrix slot 5: Mod 4 Uni/8beats set at 100% with target Drone On/Off, resultant mod range 0 to 1.  Elsewhere a 48 beat LFO modulates drone position (mod range 0-5), giving occasional boings all over the place - as intended. 

However, if NDLR is stopped (All Stop button), the drone is reactivated by the Mod (including blue light on the main screen) and continues to sound, even if the unit is in stopped mode.  The position LFO no longer modulates the drone position though.

Anyone else seen this/can reproduce?  I can't see why this would be correct/expected behaviour - when NDLR is stopped, there should be no further activity/output - right?

I also note that if - while NDLR is playing - drone is paused manually, it will also be re-activated by the Mod, but in this case, the position modulation no longer functions (white display, no movement) until the drone is manually re-activated via the button - position modulation then resumes.  It's not clear to me that re-activation of the drone by Mod should only re-activate the triggering, and not the associated position modulation... Oddly, drone position modulation also resumes when another part is started (eg Motif 1).

Perhaps I've misunderstood the Mod Matrix?  Nice box, though - I'm having a lot of fun with it

cheers,
auto

Edit: subscribe

Hi,

The NDLR is a wonderful little box. 

Middle C (MIDI note number 60) is C5 in the NDLR? 

Why not C3 or C4 ?

Kind regards
Francois

I was twiddling knobs and then this happened. Its really simple and under-uses the hardware, but I thought it was catchy...

https://tonyfleig.com/BoogieSynth.mp3

Hi There.

First post here, so I would like to say ''Thank you'' to Conductive Labs for creating an excellent and unique device.

I have had my NDLR for about a month and unfortunately the silver/grey design around the Play/Pause buttons has began to wear off. I would not say that I am particularly heavy handed or even that, that area gets touched the most and also it is not wearing in any other area of the panel. It is only cosmetic but it looks unsightly.

Does anyone have an idea how I could prevent this from getting worse... obviously besides touching it any more?

Which sort of reminds me of that old joke -

Patient goes to the Doctor and says ''Doctor, it hurts when I touch there!'' (touches knee.)
Doctor says ''Well, don't touch it there then!''

All jokes aside any ideas would be appreciated. I suppose I could find something to coat it with or try to match the colour and attempt to re-stencil that area back in.

Thank you.

Initially I thought it would be competition for NDLR (and to some degree I believe it is) but combined with NDLR would be super fun.  I have modular as well, so the CV bits plus NDLR's MIDI bits would be inspiring.

Noodles, noodles everywhere...

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

Hello,

So i wanted to try something different with the ndlr, and move away from ambient musings...and i think it worked pretty well.

Samples on Circuit were prepped in the IOS app Koala, and the parts used on the NDLR are drone & motif 1. Still having loads of fun with the ndlr controlling my grooveboxes, it has breathed life back into them.

Headphones recommended:

https://youtu.be/Xw5uw0V5Hwo

Hello guys,
i'm starting to play with my new ndlr but i'm sure i'm light years behind a lot of you so i have a problem i'm sure someone can help me with.
I know i can control the change of key not only with the ndlr buttons but with a midi keyboard.
I have the ndlr connected via USB only as i work with softsynths only for the moment using Logic. I also have an M-Audio 88 keyboard connected as well via USB.
I can't wrap my head around the menu Keybd Cntl (and the Ndls Cntl) but i'd like to set it up so i can switch key on my keyboard controller as well.
Can someone help me ?
thanks a lot in advance

Marco

Hello

Is it possible to send lfo data only from the ndlr? Let me try and explain...

What I want to do is record some ndlr parts into my elektron sequencer, so I can manipulate these using conditional triggers and the like. But I would also like to use the mod matrix on the ndlr to send lfo information to various CC parameters on the model:cycles.

So, I don’t want the ndlr to send note information in this case (as the model:cycles will already have that recorded). I don’t actually own a model:cycles yet, so can’t just experiment with the settings at the moment.

Thanks
John

Hey, I'm new to the NDLR, but have spent quite a few hours with it already. But try as I might, I can't seem to figure out how to get the LFO to start in phase with the overall chord sequence. It just seems to freely run on its own, so I can't get a reliable result each time I reset the sequence.

Is this normal behavior? I  couldn't find any reference to this in the manual.

I thought maybe the 'Pad Qnt' needed to be set. I have an issue with 'Pad Qnt' because when I have it enabled, my pads late/out of sync with the rest. Turning off 'Pad Qnt' fixes that issue...

Any thought of including MIDI looper functionality to the NDLR?