A record-and-overdub looper on a live input #168

Open
opened 2026-10-06 16:24:15 +00:00 by bcox · 0 comments
Owner

bcox asked on 2026-10-06 for a ticket for each gap docs/modular-gaps.md names without one, whether or not it is ever done. Engine claims are from reading the tree at 6a3fede9 on main. Nothing here is built, measured or listened to.

Summary

#78 is sampling and #141 granulation, and neither names a plain looper: record a live input into a region block for N bars, overdub on later passes, play it back at the transport's tempo. docs/modular-gaps.md marks it as unnamed in either.

What the tree has

  • The storage region and the long delay's line in it; the external input on every channel; the transport's position and epochs.

The work, as a sketch

  • A channel-scope layer owning a region block sized to a bar count, with record, overdub and play as commands on the host lane, its length set from the tempo at record time.

Open

Whether a looper is a layer or a strip insert, and how it survives a tempo change.

bcox asked on 2026-10-06 for a ticket for each gap `docs/modular-gaps.md` names without one, whether or not it is ever done. Engine claims are from reading the tree at `6a3fede9` on `main`. **Nothing here is built, measured or listened to.** ## Summary #78 is sampling and #141 granulation, and neither names a plain looper: record a live input into a region block for N bars, overdub on later passes, play it back at the transport's tempo. `docs/modular-gaps.md` marks it as unnamed in either. ## What the tree has - The storage region and the long delay's line in it; the external input on every channel; the transport's position and epochs. ## The work, as a sketch - A channel-scope layer owning a region block sized to a bar count, with record, overdub and play as commands on the host lane, its length set from the tempo at record time. ## Open Whether a looper is a layer or a strip insert, and how it survives a tempo change.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bcox/tymbal#168
No description provided.