at present we just do our best to try and follow the input clock. if the clock disappears we let the clock continue running at whatever rate it was set before the clock disappeared.
in contrast, it would seem more useful to detect when a clock is deactivated & stop the internal clock (and trigger clock.stop() event). then restart & trigger clock.start() on the first newly received trigger.
in the stop case, we likely need to wait for 3~4 clock misses to be confident the clock has stopped, vs just a change in tempo.
for startup, we must be sure to activate immediately on the first pulse, and assume the tempo is the same as it was before a stop.
at present we just do our best to try and follow the input clock. if the clock disappears we let the clock continue running at whatever rate it was set before the clock disappeared.
in contrast, it would seem more useful to detect when a clock is deactivated & stop the internal clock (and trigger
clock.stop()event). then restart & triggerclock.start()on the first newly received trigger.in the stop case, we likely need to wait for 3~4 clock misses to be confident the clock has stopped, vs just a change in tempo.
for startup, we must be sure to activate immediately on the first pulse, and assume the tempo is the same as it was before a stop.