Hi...my NDLR x 2 FW 1.073 is crashing alot

[Ghostz_of_Moar]

I can't see anything from your setup that would suggest a problem. This seems to suggest a bug somewhere that we haven't been able to pin down. Keep your eyes peeled and let me know if you find a pattern to the crashing, or if you notice a change in frequency. I'll talk to our team and let them know what's going on, and take some more time to poke at mine to see if I can make it crash. I wish we had a quick fix, but it's so hard to solve these things until it becomes clear what is actually happening.
Jesse

Hello.

The main issue I have with the NDLR is with automating the chord triggers from an external source.

When I try to trigger faster than an 1/8th it caused an overflow.

even with sticking to 1/8th notes it would crash occasionally.

So if I plop down a line of external commands that trigger the chord every 16th note then within a few minutes it will fail and then the NDRL will have to be rebooted.

I guess this is why in the menu the user is given a choice between : 1/4 note, 1/8 note and no quantization.

Which is sad because if this did not crash the unit with an overload we could do rhythmic keyboards stabs and vamps quite easily...the kind of articulations we find in funk and soul genres.

I haven't checked in because I got busy with life but the issue is still there and I am not looking to make the product look bad or the question the programmer's efficacy in such said matters.

The other issue I have with the Chord/Pad function is how we can have a massive wall of 24 voices but very very little control over the velocity dynamics of those voices...sure they are in the same key/scale but without weighting the velocity on most of my systems it sounds like trash because the triggered frequencies are going full bore all at once. I sure would love a large spread of possible notes while being able to trigger a strictly set number of voices.

So for now with the chord triggers I tend to use a voice count of 2-5 and make my own strum by changing the chord position manually or via automation because currently the strum implementation only seems to go in one direction at a set array of time divisions.

it's still fun to use...its just stuff I had to learn that wasn't made available on the site, the ads, or the manuals.