From 056f794e867146d321b128171fa874b4c6621b9c Mon Sep 17 00:00:00 2001 From: trav Date: Sat, 17 Oct 2026 22:44:51 -0700 Subject: [PATCH] CLAUDE.md: loops start on the nearest beat, not the next --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 2b07cac..ec7d998 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -428,7 +428,7 @@ persistence) → GUI (Qt widgets that read the manager and connect to its signal B lanes in the centre, and below them each deck's **whole-song overview** (`OverviewWave`: played part shaded, playhead, loop band; click jumps, drag moves) with the crossfader between. **Loops**: Loop + a ‹ size › - stepper (1/32 … 8 beats); a loop starts on the *next* beat; the engine + stepper (1/32 … 8 beats); the engine renders up to the loop end in pieces and wraps (`Deck.loop`), shown on both waveforms. **Sync sets once** (trav's call): it puts this deck at the other's tempo and stays lit only while that holds (`_check_sync`: same