Frame timelines: position as a destination, for the FS1R's scratch mode and the V-Synth's Time Trip #158
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bcox/tymbal#158
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
bcox asked on 2026-10-06 for a ticket for each gap
docs/feature-survey.mdnames without one, whether or not it is ever done. Engine claims are from reading the tree at6a3fede9onmain. Instrument claims are from that document's research, read from the manuals by research agents and not re-checked; the sources are listed there. Nothing here is built, measured or listened to.Summary
A frame timeline runs at its speed lane and is not positioned from outside. The FS1R's FSEQ has a scratch mode in which a controller sets the position in the formant sequence, and the V-Synth's Time Trip pad stops the wave "at the current playback location" and moves it either way under a finger "without affecting the pitch". The FM pair's and the unvoiced layer's frame timelines are the engine's formant sequences.
What the tree has
FrameEnvelopeindsp/frame_envelope.hwith up tokMaxFramesframes, a speed lane and a curve per segment; four timelines on the pair.The work, as a sketch
Open
Whether a position jump is a click on a lane that is not interpolated, and whether the pad's "beat keep" (chase back to where playback would have been) is wanted.