home/ atoms/ tidal-setcps-not-setcpm

Tidal sets tempo with setcps (cycles per second); passing a raw BPM to setcps is absurdly fast

Tidal has no setcpm function. Its tempo control is setcps, which takes cycles per second, not beats per minute. To set a BPM you convert: setcps (bpm/60/4) for a 4-beat cycle, so setcps 0.52 is about 125 BPM. Passing a raw BPM like setcps 125 sets 125 cycles per second — an absurdly fast tempo. Old Tidal code may use the deprecated bps or cps controls instead. Reaching for setcpm, or feeding a BPM straight into setcps, are the two common tempo mistakes.

Examples

— Correct 125 BPM: setcps (125/60/4) — Wrong (absurdly fast — 125 cycles/sec): setcps 125

Assessment

Write the Tidal call to set tempo to 120 BPM, and explain what setcps 120 would actually do.

“`setcps`, not `setcpm`.** Tidal has **no `setcpm`**. `setcps (bpm/60/4)` for 4 beats/cycle; `setcps 0.52` ≈ 125 BPM. Passing a BPM to `setcps` (e.g. `setcps 125`) is absurdly fast.”
context/ · L1-instruments/tidal/gotchas.md · chunk 1