Crow: Skipped gates at high speeds (but not crashing)/Gates merge at high speeds

[imminentgloom]

Triggers are sent faster than trigger length causing triggers to become a constant high gate (then crah crow, see #3),

Find shortest usable trigger+gap at max speed. If performance is poor, limit max trigger rate to speeds that work.

@300bpm = ~2ms trigger (no gaps), 1-(1.8-1.9(?)) ms triggers

set trigger length as function of bpm?

enc(), if 1
params:delta("clock_tempo", d)
pulse_dirty = true
end

if t[1].substep == 1 and pulse_dirty then
crow...action = pulse(bpm_to_pulse_length(), 10)
pulse_dirty = false
end

-- set a max pulse length and min pw%
-- length = length or pw_to_length()

[imminentgloom]

shortest trigger is 0.0007 seconds

implement a speed limit as a param that filters triggers above that rate + enough time to reliably retrigger.

make fill rates configurable, with presets for full and a reasonable limit for crow+modular.

[imminentgloom]

possible fix:
get crow to sync with norns clock so i can send a table of 4x24 substeps for each step so that crow can iterate through them in sync to handle existing notes.
then update tables when new notes are added to reduce message volume (same method as now, bundle of four tracks state pr substep).

gate length should be ok at 1ms