Hi Friends,

I'm ashamed to say in my effort to explore the NDLR, I turned on the Chord Sequencer. Now, I can't turn it off, as I don't know how to access the Chord Sequencer or adjust its settings. Can someone point me in the right direction about how I can turn it on/off. Furthermore, is there a resource published that outlines the functionality of the Chord Sequencer? I don't see it in the manual.

Thank you for your help!

~ Ryan

Hi,

My MRCC won't boot, it doesn't get past step 7 led, and it shows just the initial screen (v1.1.0.20)
I did try the new beta (v1.1.024) su uploading does work still, but same result.

What can I do next?

J*

UPDATE a 'hard' reset (using stand-by button and switch MRCC on) did the trick.
I lost all my presets though 

I finally got this to work, but (maybe someone can verify), it looks like it only works if the midi controller channel is not the same as the one set up for other sections?

(it could be something else - like it doesn't like channel 1. something that would explain what i'm seeing).

in any case - wanted to explore more midi interaction today (was controlling the pad section with midi cc yesterday, and that works great)

But yeah - it was not working at all when i had but ndlr cntrl midi set to '1 all'. As soon as I changed it to channel 2, and sent the notes to channel 2, it worked. Not a biggie, but I haven't found this discussed (might very well have missed it) or mentioned in the manual. Ideally I use channel 1 for everything - and thus far sending cc messages was working fine with channel 1.

Since my first 2 posts here are complaints of various sorts (previous one complained about the documentation), I want to mention first how thrilled I am with the NDLR. I had one once before, didn't have much in the way of midi synths at the time, and eventually realized that I should sell it if it wasn't been used.



But yeah. Damn. I pretty much do 'noise music', meaning in this context that I don't care about what key I'm in, etc, and am more timbrally focused than harmonically focused....so the ndlr might seem like a strange choice (and ultimately i'll probably have some requests to try to make it more flexible for silly people like me), but i think unless you're starting with white noise or something similar, the starting point is always something more down to earth, which is then mutated in various ways at various levels. And the ndlr seems great for that....the idea is to learn it thoroughly as a starting point for various loopers and crazy devices like the cocoquantus.



Sorry for the long preamble. I didn't want people to think that I'm not enthusiastic about the machine.



ok - I ran into a strange issue, and after troubleshooting it for a bit, I figured that I should maybe reboot the ndlr in case something was stuck somehow. (what was happening was that pressing play/stop for the pad had no effect at all. I couldn't turn it off. it would briefly flash that it was off, but then toggle back to on). I would be interested in what that could be (probably some kind of dumb user error, or maybe that it's that I"m using the latest beta, or who the hell knows), but what I ran into was that settings were not saved automatically.



Now, I get that you can save multiple 'sets' of settings, but I really wish that the working settings would just be retained when turning the machine off/on. Hell, I'd even wish that the entire working state of the machine would be retained when recycling the power. Is that technically possible? Wouldn't that be desirable?



It looks like doing that global save saves everything? It's easy to do, and of course a long time user should be familiar with having to save one's work. I guess that this is one area where I came to really like the elektron aesthetic where everything was just retained on a reboot.



Well, apologies again. I'd love to hear from people who are using the ndlr to make strange atonal music.

This feature would make me purchase an MRCC immediately (or at least as immediately as I could since I didn't get in on the campaign):

A mode that allowed me to control enabling and disabling the blocking of NoteOn messages for a given port and MIDI channel. 

Unfortunately (in my opinion), toggling the various track enables of the NDLR causes them to go out of sync. I want them to stay in sync and just be able to selectively mute and unmute the parts as they play. I envision a capability where I can plug in a MIDI device like an old ART X15 or similar into the MRCC and I can assign a pedal (or more specifically a certain NoteOn/NoteOff event so that it could be sequenced) to control one of the MRCC's other MIDI ports (at the most basic level) and one of its channels (ideally) which would allow me to toggle whether or not NoteOn messages go through (everything else would).

That way I could turn on and off the NDLR parts without them losing sync, which I realize some view as a feature but which makes its use live problematic for non-ambient styles.

Hi, new user of The NDLR here.

I have the Novation Mininova connected as Pad; about 10 notes, medium range, position, strum, 60 BPM external Midi clock. All works fine.

When I set up the user-LFOs 1 and 2 to 40s, saw or square, and select Global Key and Chords as their targets, the pad plays changing keys and chords. Fine.

The odd thing is: when I set the probability to low values, say 1, the keys/chords still change up to 15 times in just 2 minutes. Way too often, as if the probability parameter is ignored. Even with 0 the keys/chords still change (though zero prob. should mean that no modulation is taking effect at all).

What am I missing? Thanks for any hints,

Cee.

I have been using the chord sequencer for a few weeks now and while my experience has been mostly positive I have noticed that when I set a step to 0.5 1/4 note....the sequencer ignores the step and the modulation within that step. 1 x 1/4 note and 1.5 x 1/4 note work, but not .5

Also disarming the sequencer doesn’t really disengage it and set it back to manual manipulation. I have to go in a set A,B,C to “-“

I'm just about to bail for the evening.

I'm not finding the docs relevant to me to be anywhere near helpful.

I owned an ndlr a couple of years ago, reached a point where i didn't have midi gear, and sold it. Realized that the ndlr would be quite fun now, and found one used.

went to the quick start. of course, the quick start doesn't tell you what is supposed to happen so that maybe you can troubleshoot.  it just says 'and you're NOODLING'. ok. So, I follow the instructions, and nothing happens. I have my midi monitor up. I'll do it again: hit the motif 1 play button (at least I THINK it's the right one) and nothing happens at all.midi monitor shows nothing. ok - so, i guess i need to press a chord button. I do that - nothing.

I first encountered this and noticed that the firmware was old. I see on the site that below a certain version you need to reload the factory defaults. Of course, there is nothing called that in the manual, and the site doesn't tell you quite what you need to do. Of course, I found it, but it took a little while, and I wonder why consistent terminology can't be used?

Now I'm successfully updated, and still nothing happens when I do the quick start. I still don't remember what is supposed to happen. Is the idea that I' supposed to rtfm BEFORE the quick start? That would be amusing.

(and yes - successful connection, which was necessary for the firmware update. Live sees the ndlr, etc. NOT a beginner at this at all)

EDIT: complaints stand. instructions should be given in the quick start about what to check in the midi menu and how to get there. I was tricked in that a couple of times some quick messages appeared in my midi monitor, which showed channel 1. Since I have the usb cable connected, I figured that the connection was ok, but obviously I needed to edit that. (A good place to start, for me, is to just set all of them to all, and then edit from there). A quick start should assume that the user knows NOTHING about the device. In any case, now sending out midi.

If you are not using an additional routing device, the "Y" button could be very useful for other functions. In the device settings, you could choose between the standard operation of the button and (even redefined) additional functions. What could be programmed? for example:
- quick save
- jump to any page of settings
- opening the page of the last modified parameter
- midi stop/panic
- arpeggios on/off
- transpose on/off
- internal clock on/off
- mini monitor page on/off


...any more

Esoteric request, but it would be useful if I could see the names assigned to the remote MRCC ports when I'm sending an input to it.  

Basically, hold down the "Y" button and press a destination and the name pops up like it does for local ones