CLAUDE.md: loops start on the nearest beat, not the next
This commit is contained in:
@@ -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**
|
B lanes in the centre, and below them each deck's **whole-song overview**
|
||||||
(`OverviewWave`: played part shaded, playhead, loop band; click jumps,
|
(`OverviewWave`: played part shaded, playhead, loop band; click jumps,
|
||||||
drag moves) with the crossfader between. **Loops**: Loop + a ‹ size ›
|
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
|
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
|
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
|
other's tempo and stays lit only while that holds (`_check_sync`: same
|
||||||
|
|||||||
Reference in New Issue
Block a user