This one really has me stumped. I’m a veteran NDLR user but I’m using it through a MPC One for the first time. I’m recording NDLR output onto individual MPC midi tracks simultaneously.

My pad channel works totally fine until I activate Motif 1. When Motif 1 plays, the audible and  recorded sustaining length of the pad notes is truncated to short quarter notes as long as the motif is running. As soon as I pause motif 1, the pad notes resume their full sustaining length and get recorded as long sustaining notes. You can see it right on the screen - the recorded pad notes stop being long duration notes and are only short truncated notes as soon as I start motif 2.

Drone or Motif 2 doesn’t do this, only Motif 1.
No modulations are active on NDLR.
NDLR routing is all four parts set to MIDI channels 1-4 on MIDI A into MPC One MIDI input to four individual armed MIDI tracks for recording. 

I’m a NDLR / MIDI veteran so I’ve done a lot of troubleshooting but I’m stumped!

Hi,

since the NDLR is still fun to me and takes a major role in my setup, could you please give an update where the journey goes to with this device.
When I look to the posts in "Feature Requests" there are mostly over two years old.

Just one example: https://conductivelabs.com/forum/showthr...ht=midihub

I know it has hardware limitations but it is sometimes asked to make it open source or split up to a beta testers section for not to ruin the reputation on the market, do you go in that direction one day?

Hey guys, new to MRCC here and really loving this thing...except for some reason I cannot get the button under the first MIDI Out Channel to perform any function whatsoever. Whether it's selecting it for routing, checking the labels, or even assigning the labels, it seems to do absolutely nothing and I'm trying to figure out if I'm looking at a firmware bug, user error, or an actual dud hardware unit. I sent in a support request to CL too. I just want to make sure I'm not missing something obvious. 

I updated it to the latest firmware before testing this feature, and even updated it to the new Beta FW, but it's still having the same problem. Thanks in advance everyone!

Hello, i have a issue with my MRCC.
After i press the Firmware button, my device freezes , Firmware update failed and also after switch off the device dont start anymore. Sometimes i am able to power up, but it like freeze.

What should i do or ? Please help
Greetings

Many folks in the DAWless community post jams in January under the heading of "Jamuary." I didn't want another year to pass and miss out on this golden opportunity, so I threw a little something together yesterday. It was more of a learning experience about creating YouTube videos than anything else. Please opt for good headphones or decent speakers.

https://youtu.be/muziDIDh69E

Obligatory gear list:
Controllers-
Conductive Labs NDLR
Torso T-1
Routing-
Conductive Labs MRCC
Synthesizers-
ASM Hydrasynth
Korg MS2000R
E-mu XL1
Yamaha FS1R

Greetings,

Am attempting to route the NDRL thru MRCC to Polyend Poly 2 (MIDI to CV module).   The issue is that Poly 2 recognized just 1 of 4 parts (Motif 1).

The NDLR is connected via USB to HostA and Poly 2 via 5-pin DIN.  (No other routing issues have been encountered with other gear connected to MRCC). 

If NDLR is plugged directly into Poly 2 via USB then all parts are recognized on Poly 2.  And if a MIDI controller keyboard is routed to Poly 2 (via 5-pin) it also recognizes CC's over the same 4 MIDI channels; which tells me it's not a Poly 2 configuration issue.

Suggestions?  I appreciate any assistance you can offer.

Regards

EDIT:  Figured it out..  Forgot to define each of the virtual ports on HostA port.  Of course it didn't dawn on me until after hitting the submit button

Hi guys, ndlr user here, got it during the kickstarter way back when, anyway. Im super interested in the mrcc, my setup has grown over the years, and midi over usb is driving me insane and im all out of midi din in and outs.
Would i be correct in thinking i could sync my mac to the mrcc just for updates and maybe using the ndlr for soft synths. but more importantly sending a clock into the mrcc from my erm multiclock and sending the clock out to all my other gear, it looks like the mrcc has its own clock but the erm is rock solid.
Also i have a little dawless (well its still connected to the computer of sorts) elekron setup with the octatrack as the main sequencer, i presume i could route the sequence/stop start and all that and also switch between my digitone sequencer also to sequence whatever. Such as any soft synths or my virus ti2 and ob6, man alive the mind boggles!
I assume all this is possible, just need someone to say "yes, it is" and im buying it instantly as im at the end of my rope getting things to work via usb only haha.
Many thanks guys.

Yesterday evening my NDLR died. 

When I connect it to my MRCC, the little LED inside flashes once, and it shows  the loading screen with the serial and the firmware version, but then the LED flashes again and the screen goes black (the backlight is still on). 

I noticed a faint smell of burnt electronics, and when I opened it up I saw some residue between the screen and the VII button, so maybe one of the small components here is damaged?

I was able to enter the boot menu and select options there, and I was able to re-flash the firmware, so it appears it is not entirely dead. Any ideas what may be the cause, and is there anything that can be done?

Hi and happy new year!

Some time ago I decided I wanted to get myself a NDLR. I would have opted for a brand new one if that was available, but had to go for a used one. After spending some time with it, it looks like one of the endless encoders is not working how it's supposed to. I've just updated the device to the latest firmware 1.1.079 and have factory resetted the device afterwards, after doing so I still see the behavior below:

The 2nd from the top on the left side of the device labeled 'Range Spread' doesn't allow me to scroll through all possible values. As example, if I hit the 'menu' button the encoder controls the midi channel and port for the Drone channel. By default is set to MIDI A, channel 3. If I normally turn the encoder one click in either direction, no change occurs. If I turn it very slowly and hold it in between clicks, the value changes to USB4, Channel 3 until I move it to the next click. If I turn the encoder very quickly, it will sometimes stick to that last mentioned value. When the encoder is assigned to other parameters, I see similar behavior.

Based on what I'm seeing (and have seen in the past with wonky endless rotary encoders), I have the impression that the encoder may be defective. Is there anything else I can try to further troubleshoot? If it ends up being a hardware defect, is this repairable?
Thanks for your response!

(Hope it's okay to post this here, given the current 'unobtanium' status.)

I thought I'd sell my NDLR as I'm really not doing it justice. It seems better to offer it to someone here than on eBay. It's as new in original box. Serial no. 011-0281-1909, with firmware 1.1.063. Bought through the Indiegogo campaign in October 2019, but little-used. (I posted a few noodles in the forum if you want to search.) I'd prefer to sell to UK, but outside of that you need to beware that taxes/duties etc. are beyond my control. Asking price £300. Shipping at cost, according to buyer's preference.

Please contact by email (should be possible through my profile).