I have experience with midi and syncing hardware, and I tried all the logical settings, but my NDLR doesn't recognize the midi clock from akai Force.
MPC force midi clock out-----} NDLR midi din input B , clock external.


I tried usb ndlr clock out, but doubles the timing on the force.

Dear fellow NDLRers! Ive just received my NDLR and while Im temporary away from my hardware synths I decided to test it with software synths in Logic. Perhaps Im doing something wrong since Im not super familiar with this DAW, but I cant seem to make Logic play four different parts coming from NDLR (drone, pad, motif1, motif2) via 4 different software instruments using different sounds/synths for each instrument. 

Whenever I add 4 software instruments and start noodling - all NDLR parts (drone, pad, motif1, motif2) play with only 1 sound at a time, although Im allocating different sounds (synths) for each part in Logic. Yes, Im allocating each synth its own MIDI channel (I set up the same in NDLR setup), but this still doesnt help. Looks like I need to somehow allocate the corresponding virtual USB ports in Logic, but this doesnt seem to be a straightforward procedure.


Anyway, if anyone knows how to set up Logic to work with 4 virtual USB ports and to play 4 different synth parts for every part coming from NDLR - please share this knowledge. Perhaps there's a YouTube video or a web article somewhere for that, but I cant find it.

Thanks!

Hi

I'm really enjoying my NDLR!

However I'm having a weird issue with motif 2 starting of at a way too high pitch. The behavior I'm seeing:

1. Only motif 2 does this.
   
2. It starts at what seems to be the highest possible octave.
   
3. I can't really hear if it's playing different notes up in this octave.
   
4. After some time (10-30 seconds) the played notes seem to quickly move down to the note range I expect from the settings.
   
5. All of this only happens if I start all parts at once (using the upper left button).
   
6. If I start motif 2 alone, there's no problems. If I start any or all of the other parts first, and then motif 2, then there's no problem.
   
7. It doesn't seem to matter at what position I decide to put motif 2 in before it's started.
   

My Ndlr is a couple of weeks old... the label  at the bottom is flaking off just below the PAD, DONE 1 MOTIF 2 Buttons.    It has only been lightly used the rest of the paint is fine.  Can I do anything about this?

Apologies if this has been discussed already, and it is likely obvious to most, but worth mentioning...

If you have a midi controller driving the NDLR take care not to touch any of the controller's sliders, knobs etc while on the NDLR's channel. 

There are a few cool abilities like being able to change scale or tempo using a knob or being able to change your knob midi assignments on the fly, but in most cases it causes some menus to produce strange results, eg the Keyboard Control setting in Settings Menu 1 gets really screwy, showing options you cannot otherwise select. 

It can be fun, but in most cases getting too knobby creates unpredictable results. I wouldn't mind seeing this more flushed out though! I would love to assign all of the NDLR's different encoder options to an external controller.

Develop rack ears for 19” rack...

(My NDLR is connected MIDI IN B to Deluge MIDI OUT, NDLR MIDI OUT A to Deluge MIDI IN
 MOTIF 1 "CLK OUT on boot screen is switched OFF
 NDLR has external SYNC by Deluge)

When I turn the Position (knob top right) from MOTIF1 down to lower values the mystery starts: The Deluge speeds up in tempo throughout till max or - in other cases it slows down which can be "controlled" by not turning the Position knob too far to the left.
In other situations deluge startet recording what was also caused by the NDLR
There seems to be a correlation with higher Patt Length (also top right) but I am not sure yet.
I have got to make some MIDI OX logs sometime, but at the time I´ve got no MIDI interface for PC.

By the way: Factory reset did not help.

I really like the NDLR but this issue prevents excessive ndling at the moment.

I will keep on exploring

As the title says, would be really nice to have the strum pattern as a LFO modulation.

I am using my NDLR as my master clock because it has the most stable clock of my entire setup. 

I want to be able to start the clock (press "play") but NOT start the pads, drone, or motifs. I want those to ALWAYS be manually engaged. 

Is there a setting to change the play button to work this way? Or something else?

Thanks

I might just be misunderstanding this feature.

I assumed the midi start/stop output setting sent only midi start/stop signals. 

I assume that if I set midi start/stop output to "all" that it should not interact with the midi assignments for drone, pad, and motifs. 

But when I set the midi start/stop output to "all" it wildly interferes with what is being sent to the other midi outs. It seems like the start/stop output is sending notes also! 

My NDLR is ths most ROCK SOLID midi clock of my entire setup and my Blofeld depends on this, otherwise it "clicks" eg as Ableton tempo drifts. But I need NDLR to output start/stop to usb AND midi without interacting otherwise. Is that possible?

Thanks!