Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
T
Tidal
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PLN
  • Tidal
  • Repository

Switch branch/tag
  • Tidal
  • tools
  • foundry
  • engine
  • stempack.py
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    fix(foundry): the cheat sheet printed 133 bpm over loops cut at 132.5 · 831d3f14
    `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.
    PLN (Algolia) authored Aug 21, 2026
    831d3f14
stempack.py 40.1 KB
EditWeb IDE
×

Replace stempack.py

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.