You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 095f870
Browse filesBrowse the repository at this point in the historyBrowse files
Take a lost lock back on the beats' own evidence; clocks and rule lengths follow the beats going out
A lock taken at a wrong tempo (double time, or 176 over a record at 130) and then lost left the
number frozen there while every beat went out at the record's real tempo — for minutes, because
replacing a long-held lock needs up to 300 frames of unbroken agreement and the decoder's tempo
dips past the lock's band as each beat arrives. Over the 109-g playlist played straight through,
steady beats went out under a number more than 6 % off them for 31.8 of 715 live minutes.
Tracker:
- Unlocked after a lock, once the lock has been gone 3 s, the last eight published beats are
steady (interquartile range under 5 % of the median gap) and the decoder's tempo over the last
beat agrees with them, the lock moves to the rate the beats are going out at. Replacements
only: a first lock, and a lock coming back to the tempo published, are earned as before.
- The octave the filter's beats sit at against its cloud is kept through a lock move, and the
first lock after no signal, only if the beats do not cleanly show another; it used to be kept
through everything but a reset.
- TempoState::gridBpm: the rate the published beats are going out at — the number on the beats'
octave while it agrees with them, their measured rate when it does not. clockOctaves: the
operator's x2, which doubles the number and cannot double the beats.
Outputs:
- The MIDI clock and Link run at gridBpm, times two under a x2; the clock's receiver and Link's
session count that many of their beats to each beat going out, so a x2 or a number left behind
no longer stops and restarts a receiver every bar, and a receiver's bar 1 is the tracker's
downbeat.
- The beat scheduler predicts at gridBpm, and a rule's waits and follow-ups in beats or bars, and
TEST's hold, are counted in it (Context::beatSeconds).
Window: the line under the tempo says what the beats are going out at whenever the outputs are
live, locked or not ("number held from last lock" unlocked, "press ÷2 to match" locked).
Measured over the same playlist played straight through: steady beats under a number more than
6 % off them for 9.3 minutes rather than 31.8, the longest stretch 9 s rather than 145; tracked a
record at a time, 6.1 minutes rather than 22.7. The refeval gate passes (tempo accuracy up, beat F
unchanged), Ballroom is bit-identical, and on the agreed fifteen the number is off the reference
for 331 s rather than 405 s while the outputs are live (258 rather than 273 with the 70-140
window).
takt4-cli --trace writes beats_bpm and grid_bpm.
0 commit comments