You can get to the MIDI Mixer by pressing SHIFT + the lowest Knob on the left side. It generates CC7 on the channels you have assigned your parts to.
Works well......BUT: If you use the polychain feature for the Pad it goes only to the Pad channel itself and not to the chained ones.

So this is another bug for the list of bugs that did not get shorter fot a very long time meanwhile....

The answer will be: There is no space left in the code to fix that.....as usual... 

Thank god I have a Blokas MIDIHUB so I can make a workaround and the NDLR can stay in my setup.

Hello,

I just received a new NDLR and upon starting to learn it found a strange issue
It is related to the change of the pad notes - the range parameter, and then
moving to different chords.

I have the NDLR connected to the computer and using a sequencer and a software synth
and I am recording the midi input that comes from the NDLR into the sequencer.

The p-chains parameter is set to 1, so all the notes should be sent to only 1 midi channel.

The issue is occurring when increasing notes for the pad (the range parameter) and then changing chords.

I started with 3 notes, then increase to 4, change chords, works fine, 
then increase to 5, right away I see an additional note, so has 5
but then when I change chord it play a 3 note chord
then I decrease the notes back to 4 and now it is playing 4 notes
then I repeat the whole thing and the same issue.

Firmware is 2.0.011 (I did not update to the newer one)

I discovered that this happens when the spread is 2 or above
when it is 1 and I increase notes, it always work (I went upto 7 notes)

I am attaching a screenshot of the midi recording with an explanation
of each step I did, and would like to ask about this strange issue.

Thank you

Attached Files

Thumbnail(s)
   

I often use Stepic - a software sequencer that can send CC to external devices - to sequence the NDLR. Today, I decided to encode every CC for the NDLR into a Stepic device patch (which I will share later) rather than just the basics.  My thinking is that with all CC codes, I can automate the switching of instruments connected to the four NDLR tracks via changing channel numbers for each, etc.

While doing this, I noted an error in the manual: page 59 lists CC 26 for the Motif 2 MIDI Port, while page 56 shows CC 26 as the Chord Degree. 

I *think* page 59 is in error.

The hex codes in the page 59 table correspond to CC24 and CC25, but the CC codes are 25 and 26, respectively. 

Hope this helps others using CC codes to manipulate the NDLR in real-time.

hi,

i recently have returned to the ndlr world... forgot how fun and awesome this little thing is. I know that new features seem to be really hard to fit on the memory or that is what i've read a lot but i was thinking that it would be super cool if we could pick for the 4 slots, which type of arp is set. By default its motif 1, 2, drone, and pad. I think it would be super cool just to have the ability to have 4 x motif 1's or 2 x motif1 and 2x motif2 or maybe 3x motif1 and 1x pad. 

anyway keep the NDLR alive and kicking!

thanks JA

Hello there,

I am currently in the process of setting up my MIDI controller rig for live performances and could really use some advice from those with experience in this area.

I have a MIDI controller that I want to integrate into my live setup. My goal is to use it to control various hardware synths and software instruments seamlessly during performances.

I am particularly interested in how to optimize the MIDI mapping and setup for efficiency and reliability on stage. What are some best practices you've found effective for ensuring minimal latency and maximum responsiveness?

Additionally, I am curious about any specific software tools or apps that you recommend for managing MIDI configurations and mappings. Are there any hidden gems or popular choices that I should consider?

Lastly; if anyone has experience with similar setups or has encountered common pitfalls to avoid, I would greatly appreciate your insights.

To give you a bit more context, I primarily play and often perform in venues where space and setup time are limited, so practical solutions are key.

Also, I have gone through this post: https://conductivelabs.com/forum/showthr...p?tid=2097uipath which definitely helped me out a lot.

Looking forward to hearing your thoughts and learning from your experiences. 

Thank you in advance for your help and assistance.

https://youtu.be/YQ6MyCJSDPQ?si=ndOncO7L5raj4iy2

Attached Files

Thumbnail(s)
       

I'm just getting into the NDLR and freely admit to being quite overwhelmed by the product's interface and capabilities.  Quite a lot going on here!

From a UX perspective, it would be helpful (for me at least) if the italicized labels (e.g., interior circle 'Triad,' '7th'...etc) that require the SHIFT button to activate were color-coded to have the same color as the SHIFT button (i.e., blue for the NDLR v2).  That would be an easy way for me to remember to hold the SHIFT button to activate those features.  

Curious if anyone else has asked for this?

Is there a way to have to set note On duration as a percentage of note duration? Maybe modulate that? Looks like arpeggio are played legato only. If not possible, what is the idea behind what appears like a limitation a first glance?

I have both MRCC and NDLR and am trying to set it up in the most straightforward way:

- Clock is generated by Elektron Analog Rytm connected to MIDI 1 and routed to USB A
- NDLR is plugged into USB A and set up to receive the clock on USB 1


So, the expected chain is
Rytm => MIDI 1 => USB A => NDLR
...

Unfortunately, as soon as I route my MIDI 1 to USB A - MRCC freezes.

Some observations:
It's not freezing before NDLR is plugged in (or powered up).
It's freezing regardless of whether NDLR is configured to receive the clock over USB or clocked internally.
It works as expected when using MIDI-only to connect NDLR.
When MRCC freezes, NDLR indicates that a Clk signal is still received at 39 bpm over USB-1.
If you disable sending the clock from Rytm when MRCC is frozen, it will unfreeze in ~10 seconds. During that time, NDLR will show that it receives the clock at 39 bpm.


And more details:
NDLR and MRCC are on the latest firmware
I've used the blank presets on MRCC and NDLR to replicate the issue.
The clock from Analog Rytm (or other Elektrons) works well with all other gear. 
Anyway, it freezes even using a clock from MRCC, when routed to USB A.


Assuming that it potentially narrows to loop issues, I've played a bit with settings and boot menu clock options, trying to disable any possible clock messages forwarding\echoing. Did not help (or I didn't find the correct setting\menu).
As the Boot menu is almost not documented in the Manual - it's not clear what it is actually doing



That is such a simple setup that I feel dumb stating that I've spent over 8 hours searching and reading, but here we are.

Surprisingly, there is no tutorial example of how to route the MIDI input to USB-A-D outputs. For the MIDI => PC, there are, but it's not the case.
Also, I'm quite curious: why can we specify which USB ports to route FROM, but we don't specify which of 1-4 ports to route IN when routing from MIDI?

But the main question is, has anyone had the luck to set up MRCC + NDLR to be clocked externally via USB?

Hi everyone 
On paper a little looks great so I am definitely going to try it out. Would prefer the price of v1 but just want to check if there are any persisting issues. I assume that you are not going to be (m)any further updates, so it would be good to know up front especially of showstoppers. 

Thanks a lot 
T