Could we get some exotic scales or a way to add custom scales? I'd like some Kojin Koshi, Hirajoshi, etc. flavors to choose from

Hi!

   I've read that the NDLR can be used as a MIDI splitter. That is, signal sent into A, comes out of both A + B. Is this true? Not talking about start/stop messages, complete MIDI THRU. I can't figure out how to make this happen. Is there a setting I'm missing somewhere? Sorry for the general question but I'm going bonkers trying to figure this out. Thanks in advance!

Cheers,
~jess~

Here’s a doodle. Moog sub 37. Waldorf Striechfett. Behringer D, Deepmind12 and Odysee. 

[/url]
[url=https://soundcloud.com/hafstrat/dolphins]https://soundcloud.com/hafstrat/dolphins

A Tangerine meme. Not a very sophisticated use of the NDLR but I like the knobs for varying the motifs on the go.

Hi there !

Just wanted to check on the status of NDLR batch 3A. I bought in and can’t wait to get my unit. Is everything on schedule for a delivery in April as announced ? Let’s hope the bug doesn’t get us into trouble 

Cheers

This morning I started a new Teensy project.  Downloaded the latest Teensyduino, plugged in a Teensy 3.2, opened Blink, and hit the download button.

My NDLR was connected on another USB port.  And you can guess what happened next -- I flashed Blink onto the NDLR.

So now I know there's a Teensy inside the NDLR, and I can see its amber LED blinking away.

I was able to reinstall the NDLR firmware easily enough; after all, I already had the Teensy loader open.  So this story is a comedy, not a tragedy.

Hello,

I tried searching for if this bug is already documented, but couldn't find anything.

I updated to the latest release (from december) yesterday and noticed that it's no longer possible in the rhythm pattern-editor to scroll counter-clockwise from Rest to Tie to 127,126... etc. The only direction that is possible to go from Rest is clockwise to 1,2,3.. 

For me this is quite a big problem and really breaks the workflow of this amazing little machine. Being able in 1 step to go from Rest to Tie is so much more convenient than to scroll through 128 steps when trying out patterns, especially as I'm using it to trigger a CV-gate where only note on, off and slide matter (value 1-127 are the same to me). 


Keep up the good work 

Greetings,

I've noticed that Pad notes occasionally get stuck while changing chords.  In troubleshooting this the Pad range was reduced down to 1 note but oddly the NDLR sends two different Note On messages (which seems like a bug?).  After a chord change it sends a single Note Off message, leaving one note hanging.  
The Panic function doesn't kill it.  Have to power cycle the sound module or temporarily switch to a different patch.  This appears to occur frequently and is fairly repeatable.  Am running the latest FW release.  Like Spread thinks there's more than 1 available note to play...

Had also experienced some other strange behavior with Pad, where by Poly-Chain was set back to 1 but the display would display Pad (+3).  Power cycling doesn't clear this out either.  The only thing that I hadn't done was reset it back to factory default settings...

My apology is this was already posted, hadn't checked recently.

Hi all,

I've just started using my NDLR. I already received it back in November but I haven't been home for the past months. 

I quickly noticed problems with the responsiveness of all buttons. Pressed slow they seem to work. Pressed quickly (with light tap) they are very unreliable. The haptic feedback from the click does not at all mean the press is registered.

I can fairly quickly alternate between two buttons and more often then not the clicks are not registered. Switching quickly between two buttons is not something you might want to do, but I also get failures when I start pressing around the different modal stages and don't press down long enough, and that seems problematic to me. I do think you will get used to this after a while and learn to make each press firmly enough, but it I think it gives a bad overall feel to the hardware.

To me this seems like a software issue because it equally applies to all buttons. I'm guessing it's related to the logic scanning the button inputs and registering their state. I've started out using firmware that came with (.60?) it but now upgraded to the latest version. Both seem to behave the same.


I also noticed the encoders when turning are similarly laggy, seems like there's a delay of about 100ms between feeling the encoder increment/decrement and seeing the value on the screen change. Similarly to the buttons turning them quickly will result in unpredictable behavior. For example try to making a small turn back and forth on the pattern position. Although it might feel you're doing a similar range, the position will differ because the amount of registered incr/decr steps is fluctuating.

If the Teensy isn't already pushing its limits in terms of CPU cycles, I hope this behavior can be improved quite a bit.

It is just a hair too big to fit in my snoopy lunchbox...