This function should make it possible to switch any out port(s) into a THRU state, where instead of data merged from it's routed inputs, the port processing would be overridden to output the same data as the single selected "THRU-SRC" port, which could be either any input or any other output port.

There would not be any additional routing and merging on these THRU ports as long as they remain set to the THRU mode, even though the pre-existing routing will remain in place and new routing could be added. These will however not be active as long as THRU override is enabled.

This way, we could set all the routing, remapping etc only once at the primary output and then have MRCC automatically replicate the output of the selected primary output to the THRU out(s), while possibly taking less resources than a bunch of separate duplicate routing would take. This is basically substituting a MIDI THRU boxed connected after the primary output.

Or we could do ad-hoc overrides of existing routings for simple passthrough of single input/output. For example to "mute" all the sequencing into a single output and instead temporarily play it manually from the master keyboard.

The switching and sourcing of the THRU mode would be done on a new OUTS THRU / THRU SRC screen, where yellow LED would indicate a THRU enabled port. Enabling the THRU port would be done simply by pressing and holding the desired THRU output and then pressing the single output/input to pass through that output.

This would be useful for setups, where you don't always power up all your gear. 

The setting screen should provide ordered list of 3-5  selectable inputs, that would be cross-checked at all times (or by some refresh soft button action) and only the clock and transport from the highest active input would be passed through to the routings.

The clocks and transport messages from the other inputs on the list would be filtered out.

I have a keyboard poly synth as one of the inputs and also one of the synths on one of the outs dedicated to a bunch of poly synths.

I can easily change global channel on the keyboard and play all the other poly synths.

I want to prevent MIDI loopback on the keyboard synth though, block its channel in the routing.

I know I can remap the channel to channel 16 and use it as a dump, but I would rather not waste usable channel and not send unnecessary messages in the MIDI data stream.

Hi,
Was just wondering when some more MRCC units and accessories will be making their way out into the wild ?

Hi all,
Please would someone remind what power cable/adapter the MRCC comes with (if any)?
I've had my gear in storage for a while, and I'm setting up my studio again. I can't seem to find a matching power cable/adapter for my MRCC.
Have I lost it? Did it even come with one? Maybe you're just expected to plug it into a USB-C PD socket using your own cable? Or if it's powered by the USB connection to a PC?
TLDR; I'm not sure if I've just lost my MRCC power cable/adapter, or if it didn't come with one in the first place!
Please remind me.
Many thanks,
Ben

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)
       

Hello,

Is it possible to recall the 880's configuration over MIDI? If not could we have it added as a potential much needed feature.

Thanks

Dave