| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| engine | ||
| packs | ||
| research | ||
| tests | ||
| ui | ||
| .gitignore | ||
| PHASE2_LOOPFINDER.md | ||
| README.md | ||
| TODO.md | ||
| autotune.py | ||
| demos.json | ||
| foundry.py | ||
| kitgate.py | ||
| kitindex.py | ||
| restage.py | ||
| server.py |
`loopAt` is exact, so a rounded tempo is a stretched loop — and the cheat sheet is where the number gets typed. It reported ANGIE and BIG HEN as "133 bpm" over files cut at 132.51, which plays every one of them 0.4% fast. Two decimals now, and each kit prints its own `setcps` line rather than leaving the ÷60÷4 to the reader: `loopAt` squeezes the file into N bars of the *current* cps, so the cps is half the instruction and omitting it is what makes the rounding bite. Same fix in La Cale's UI, where the transport read 123.05 next to a row reading 123.0 — one `fmtBpm` for the transport, the rack header and every row, because the same tempo printed two ways reads as a disagreement in the data.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| engine | Loading commit data... | |
| packs | Loading commit data... | |
| research | Loading commit data... | |
| tests | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| PHASE2_LOOPFINDER.md | Loading commit data... | |
| README.md | Loading commit data... | |
| TODO.md | Loading commit data... | |
| autotune.py | Loading commit data... | |
| demos.json | Loading commit data... | |
| foundry.py | Loading commit data... | |
| kitgate.py | Loading commit data... | |
| kitindex.py | Loading commit data... | |
| restage.py | Loading commit data... | |
| server.py | Loading commit data... |