Envelope triggers beyond the key: an LFO wrap, a clock or a comparator edge that fires an envelope #116
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bcox/tymbal#116
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-05 for a ticket for each engine gap that the third set of instruments in his
moregaps.mdleft without one. Engine claims are from reading the tree atf6aa8ebaonmain. Instrument claims are from that day's research, read mostly as archive.org OCR of the manuals by research agents and not re-checked; the sources are listed in that document. Nothing here is built, measured or listened to.Summary
Only a note fires an envelope:
NoteOnandNoteOffare the segment envelope's only entries (dsp/segment_envelope.h:160,:199), and only the key restarts an LFO (dsp/layer.h:589-593). The workaround is a loop (loop_mode,dsp/segment_envelope.h:85-99) whose period equals the LFO's, which drifts if the rate moves and cannot be started mid-note by anything. Ten instruments in the third set fire envelopes from something other than the key, and the first two sets already named the ARP 2600's clock.What the instruments do
The work, as a sketch
kGreater(dsp/mod_ops.h:35) already turns any source into a gate, so an "edge of this entry" trigger is the general form and gives the audio trigger and the sample-and-hold clock as well (#117 and #118 lean on it).retrigger_envelopealready distinguishes for steals.held_state.Related