I don't have a problem or anything; I just wanted to say that I've been looking for something like the NDLR for years, and this thing does everything I want it to and then some. I'm really impressed with the features and couldn't be happier with this thing. Thank you, Conductive Labs, for this product. If you were a woman in my demographic range, I'd totally ask you out.
-Mike

Hi - the MRCC looks great, and as a very happy NDLR owner, I have every confidence in the product.  Can you say a little bit more about how it would work as a MIDI Interface on a PC?  The current specs suggest there will be "12 USB virtual MIDI ins and outs, all routable from the front panel".  Does that mean 12 ins and 12 outs. or is the maximum port count 12, splittable across inputs and outputs?  Also how would these ports appear in a host DAW for example - do they hard map to specific inputs and outputs on the MRCC, or can you assign any of the MRCC's USB, 5 pin or jack midi connectors to a virtual in or out port?  

I use a lot of external synths and MIDI controllers with my DAW (via 5-pin, jack and USB connectors) and would want to be sure I could assign sufficient MIDI inputs and outputs freely and flexibly in my DAW tracks.  I use Presonus Studio One / Windows 10, and currently use an ancient but still serviceable MIDISport 8x8 interface for my 5-pin DIN and Jack devices, and PC USB ports for devices using USB-MIDI.  Having one device to flexibly rule them all would be very nice indeed!! 

Thanks for any info.

Is it possible to use the NDLR on one synth on multiple MIDI channels?

Hi, I need some help plz.
I want to have a pulsing drone. I have Behringer Model D setup on midi channel 3 via midi din thru midi port B, but it gives me only a constant droning tone, no pulsing, but when playing  arpeggios via motif 1 or 2 with model D everything will arpeggiate and play just fine, as expected. Attack, decay, release all set to zero, no FX... Novation Circuit connected via Midi port A would give me a pulsing drone (midi channel 2)... The drone settings are fine (dots)
Here is video to show it, first is Novation circuit, then Model D
https://www.dropbox.com/s/o8vchsl1wzd1nr...1.mp4?dl=0

Any ideas? What am I missing?

THX

Hi all! I have a serious problem with my NDLR. I'm trying to enter the boot menu pressing SHIFT+MENU buttons while booting up but nothing happens. Any other of you has the same problem? I bought my NDLR a few months ago and so it's updated to firmware 1.1.066. Thank you

Hi, I'm having issues with the gate on the drone part. All I get are clicking noises if is set to anything but the first note of the measure. When trying to set to 4 beats per measure nothing, unless I use samples instead of synths as it will trigger the samples. I've tried playing with the quantize settings etc. Sometimes it will play a note in a measure but never all four.

I was looking at the upcoming MRCC and really like the design of those aluminium side panels. So just wishing for an NDLR add on version.

Hi guys,
just received my ndlr unit..all fine but  i`m going crazy for set it up for jazz improvisations for the four parts and i need your help.

please any suggestions? for the clock divisions,scales,rhythm & patterns  and global mode.

thanks a lot for your help.

[ see below for released version: https://conductivelabs.com/forum/showthr...26#pid3326]

Hi there,

I've been working on a Max for Live MIDI device to view and control the CC parameters of the NDLR and it's almost ready for public consumption.I thought I'd post this to get myself over the finishing line, gauge interest and maybe get some feedback.

The device (a fancy name for an Ableton plugin, more or less) lets you see most of the parameters from Appendix A in the manual. It also lets you set most of them, using dials or drop-down menus as appropriate. It lets you map the settings to whatever physical MIDI controllers you use with Ableton, or to Macros. And finally it lets you automate most of the parameters.

Some CC#s are not responding correctly - I'm documenting the problems in the beta forum. And that leads to an important requirement - you must be using Firmware 1.1.071 for this to work fully. I haven't tested it with older firmwares, but I know it won't work properly since the CC#s have changed over time.

If this sort of thing interests you, I'd be delighted to hear what you think of the direction this is heading in. There's a lot of UI work to fettle and I also need to finish Motif-1 and clone it to Motif-2. Nothing is set in stone, except that this device will always be restricted to whatever CCs are exposed by the NDLR - I have no intention of using the Serial API to do anything fancier. Unless lockdown goes on for another year... If someone else does create such a beast and there's utility in combining, then I'm happy to share this without conditions.

As far as the UI is concerned, remember that Ableton devices all have to be this height. Width is unrestricted, but sensible limits apply (best to fit on a small laptop screen's width rather than force scrolling). Part of me thinks all the performance controls should be on the same panel, but it becomes a monster real-quick. The NDLR Panel stuff shown below will be put into a sliding panel, hidden away when not needed so that gives us a bit more space.

Here's some screengrabs of the device inside Ableton to give you a clearer picture (ha). There will be documentation and the control will be open-sourced on Github. You'll be welcome to fork it for your own purposes or offer improvements for everyone, should anyone be that interested - I'm just as happy if I'm the only user .

Settings screen

Stuff I don't regard as changeable during a performance/session. Setup and leave, basically. The "NDLR Panel" section retrieves the current settings from the NDLR. This is not dynamic - if you want the current settings after changing a physical control on the NDLR itself, you'll have to click the Retrieve button. I guess I could poll the NDLR, but it seems ugly to me.



General

If it's not to do with Pad/Drone/Motif directly, then it goes here. Tempo can be fun - make sure you set Clock In on the NDLR to a sensible value (like "USB 1") and you'll be connected to Ableton's transport. Otherwise make sure you tell Ableton where to get its clock from carefully, or just enjoy a general lack of sync.



Pad/Drone/Motif controls

Performance controls. The big ugly Pause/Play toggle is one of the controls that is not correctly retrieved from the NDLR currently. Send works, receive no-go.






Ableton setup

Create a new MIDI track. Set MIDI From to the information you configured in the "Retrieve" section. Send MIDI to the "NDLR Cntrl" channel and any NDLR port. Monitor should be set to In.



Automation 

Add Automation Lanes to the MIDI track created above and use for playback. Or record knob twiddling, or whatever you normally do with Automation. You can automate yourself into a corner here especially by changing MIDI connection mid-track. Caveat noodlor as the Romans would have said.

Hello guys, 
hopefully someone can easily help me, I'm sure it's something simple but I'm having problem receiving clock from the NDLR, connected via USB with Logic Pro X on a Mac.
It works and I can write midi and pilot both VSTs and external midi hardware (a DIGITONE for example) BUT I can't sync it to the DAW.
I tried all USB ports but I'm sure I'm missing something stupid ?!!?
thanks !

Marco