I use the NDLR and some MIDI to CV magic to play a few analog synths. All good. 

My problem starts when I would like to trigger an envelope generator (a Roland 540) every time the drone chord changes. I can't do that, because the gate coming out of the drone is always up... 

... except every few minutes when - I don't know what happens - perhaps some electrical hiccup actually interrupts the gate for an instant and the envelope starts. I like the serendipity but that's not what I wanted :-)

I hoped that the solution was in the trigger / cadence settings of the drone, but so far I had no luck, the gate is always up. Any suggestions? 

For the time being I could solve the problem in an incredibly convoluted way, though fun to describe. The note (aka, the voltage) from the NLDR goes into a quantizer (Expert Sleepers' Disting). The quantizer triggers a trigger when it detects the change of note. The trigger goes then into Make Noise Maths that transforms it into a gate, and that gate finally goes into the envelope generator.

Looking forward to your advice!

G.

It would be cool to have a setting to control if the values that were changed by a Mod Matrix setting could revert back to its previous state, or possibly to their individual save state, after I change the Mod Matrix setting.

My use case is that I set up everything else first, until I go to the Mod Matrix. Once I'm done trying out several settings to see if they work for the current noodle, so many settings have been touched I don't remember anymore where they were.

The workaround could be to save globally before modding, and going back to that save state. Usually that's too radical though. I just want to avoid the repeat work, and with the current situation versus the workaround, either way I have to re-do settings.

Not sure how useful this would be, or if I'm doing it awkwardly ...

When I set up the Mod Matrix, simply scrolling through the available options messes up my part settings.

For example, I set an LFO source to 100% and scroll through the list of Motif 1 destinations. When I arrive at the Motif 2 list, if the LFO was at the "perfect" spot, my Motif 1 clock divider went from 1 to 8 (audibly). This does not reset when I toggle Play, I have to actually go back to the set up and change it to where it was. It happens to many settings. 

Would it make sense to introduce a delay before each setting takes effect while scrolling? If there already is one, what it is set to?

Hi All. I understand that, using the encoder, it is useful that the clock divider is quantized to only a few values, and I also understand the rationale for sorting the even vs the odd dividers (1, 2, 4, 8, 3, 6). 

However, this becomes an unnecessary limitation when controlling the same via MIDI messages, say CC 39 for motif 1. At the moment I still need to follow that sequence (CC message 1 for 1, 2 for 2, 3, for 4...) and all values beyond 6 are wasted. 

Why not allowing the controller device to go through a much more granular set of values, if not as continuos as it gets in the 127 range? 

Besides, that would also make counterproductive the sorting in even vs odd. The clock divider would be calculated as CEILING(CC39 / 127 x 8).

Also, I am sure many users would welcome to push the divider to 16, or CEILING(CC39 / 127 x 16).

Inspiration for this request is a beautiful live performance of Aqeel Aadam at the latest Synthbooth conference, where he does exactly what I describe, changing progressively the speed of what in NDLR would be a motif during the performance. He achieved this easily using some dedicated clock / sequencer in Eurorack.

Thanks!

G.

I get stuck MIDI notes often.  Seems to occur more often if I am modulating Position of Pad or Drone relatively fast (Rate = 4 Beats @ 110BPM).   occurs both USB out and MIDI DIN outputs.  

Anyone else experience this?

fw 1.1.066 currently installed.

Thanks!

-M

Hello,

Beatless ambient jam on the model:cycles. All the music was ‘written’ by the ndlr, and recorded into the cycles sequencer for further manipulation.

Headphones recommended 


https://youtu.be/xeDuIRxp0Hc

... here's a link to my first completed track using the V3 Sound Grand Piano XXL.  The V3 is controlled by NDLR with Pad: Horns, Drone: Piano, Motif1+2: Piano.  Digitakt provides electronic backing.  Enjoy :-)

https://soundcloud.com/flux-us/guadalupe-1531

[font=system-ui, -apple-system, system-ui, ".SFNSText-Regular", sans-serif]Hi everyone, I made this tutorial video to explain how I pair the NDLR with the Deluge.
[/font]
[font=system-ui, -apple-system, system-ui, ".SFNSText-Regular", sans-serif]I explain how to map MIDI from the NDLR on to the Deluge synths, how to use the NDLR LFOs to modulate internal parameters, how to modulate Deluge synth parameters using the NDLR LFOs and how to sequence the NDLR from the Deluge. It was a lot of fun exploring putting these two together![/font]

To support better automation from a DAW, please change the range of CC 26 by adding the value of "8" to represent "the latest played chord degree".

The use case for this is the following: imagine you're improvising using a combination of NDLR and DAW. You want to trigger some automation in the DAW that - wherever you are in your music - re-starts the drone without needing to remember what is the latest chord degree you were playing, so you just send a CC 26 of 8, and whatever that was it is triggered again, and the drone starts.

This idea is originated by what looked like an automation issue to me originally, described here.

Thanks!

G.

Hi All, I've searched the forum and I haven't found anything about this. 

When using NDLR from a DAW, how useful would it be if the NDLR could load and save its entire global settings with MIDI CCs? In most cases this would be more convenient than programming the individual changes for the parameters using, for example, a DAW's automation.

E.g. I'm working on a piece where the pad does a "solo" at some point where position, strum and range all change, to feel more improvised. At the moment I am manually loading the new global settings when it's time, but it may be much more convenient to trigger the same from the DAW.

Thanks!

G.