MIDI clock in: clock, start, stop and song position into the transport #166
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bcox/tymbal#166
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/modular-gaps.mdnames without one, whether or not it is ever done. Engine claims are from reading the tree at6a3fede9onmain. Nothing here is built, measured or listened to.Summary
The MIDI decoder discards real-time and system-common bytes (
midi/decode.h), and nothing in the tree syncs the transport to an external clock; #47 is tempo inside the song. A modular or a DAW that sends MIDI clock cannot drive the sequencer's tempo or position.What the tree has
midi/clock_pair.handqueue_anchor.h, which put the sequencer's queue time onto the audio clock; the transport incontrol/transport.h; the host lane's locate and jump.The work, as a sketch
Open
Who owns the tempo while synced, the song's tempo track or the external clock, and what a tempo ramp in the song means then.
Also: HUI control