Chord Sequencer Issue

[Jesse Johannesen]

Hi Jesse,

1. As far as the update procedure goes update doesn't affect saved pattern and chord seq data, though if you are updating from a version before 1.1.066 you would need to do a factory reset afterwards due to updated save state data formatting. You won't need to do this however.
I did the update but the bug is still there

3. I've seen that pad last-note sticking issue before but it seems rather elusive, for instance I haven't had it happen to me for months, but one of the guys I tutor has it occur frequently. If I could get more info about how you're interfacing with the NDLR when that occurs it may be helpful in finding what needs fixing. For instance if it's only when connected to a Mac while using USB on Tuesday (obviously not the case, but you know what I mean) the more details the better chance I can find the bug. You can easily stop all notes by holding [SHIFT] and pressing [Panic] (AKA the motif1/2 button).
The panic button is not stopping it, the only way I found is to send a start all/stop all command. Sometimes I need to do it twice in order to stop the outgoing signal.

4. The display has the lowest priority in the hierarchy of the device, so it may not update as fast to ensure the actual output IS updated on time. It may also be a bug, I can take a look and see.
It could be a priority issue but I feel it's not, when the sequence starts in the correct way the box is always perfectly in synch

Bless,

Claudio

Thanks Claudio,
I'll be out of town for the rest of the week, but I'll take a look at this in a little bit more detail when I return.
Best,
Jesse