(08-08-2020, 06:29 PM)james@ticalun.net Wrote:Hi James, there's a MIDI Note Off command before every new MIDI Note On. So I guess its 99.9% gate? Its a MIDI command, not a CV gate, so all gate means is how soon MIDI Note Off comes before the next Note On. It shouldn't matter to the synth if its MIDI implementation is correct.(02-05-2020, 04:04 PM)Darryl Wrote: Its a fundamental limitation with the architecture of the code. The NDLR turns notes off only when there are new notes to turn on. There's no timer method for note gates, so it would be a significant rework of the code to get a gate length. We've been working on The NDLR code for a couple of years now, and this is something we would also like to have, but right now we are prioritizing bug fixes as we are heads down on new product development. Once the new product is launched we can circle around to see about getting some new features implemented.
This is quite frankly, a fairly significant problem. Every analog mono synth will have issues with this as the envelopes will not retrigger on each step which renders them useless with NDLR. If it isn't possible to make it editable, the default gate really shouldn't be 100%.
James
Just FYI, though more efficient, we elected not to use Running Status, though it would have helped to reduce overall MIDI data load on the NDLR. Even running status should cause a retrigger, but we haven't tested how widely/correctly implemented it is on synth modules. Its possible some boutique modules don't implement it and would not retrigger with new note events of the same note, but this would violate MIDI spec.
We haven't heard of a problem with retriggering envelopes, but maybe nobody notices.