Phase 26: add common parameter targets, step automation and MIDI control mapping
This commit is contained in:
parent
7bff7b535d
commit
901a536f10
38 changed files with 740 additions and 67 deletions
|
|
@ -26,7 +26,8 @@ static control. There are at most 1024 points globally, with one per
|
|||
track/parameter/tick. Track deletion cascades to its automation.
|
||||
|
||||
A nonempty lane replaces that parameter's static value. Between points the C
|
||||
engine interpolates linearly at each sample, holding the first/last value outside
|
||||
engine interpolates linearly or holds each segment (Interpolation chooser),
|
||||
holding the first/last value outside
|
||||
their range. Preparation converts ticks to integer sample endpoints, sorts and
|
||||
indexes lanes. When several ticks quantize to one sample at very low sample
|
||||
rates, the last point wins at that sample. Rendering searches prepared bounded
|
||||
|
|
@ -137,3 +138,8 @@ project performance remain unverified; no new dependency was introduced.
|
|||
`test_buses` covers bus routing, exact taps, audio/MIDI cancellation, controls,
|
||||
automation, persistence, invalid routes, deletion/undo and dBFS ballistics. Backend
|
||||
tests cover consuming interval peaks; GUI tests cover routing undo and clipping.
|
||||
|
||||
Phase 26 adds Linear/Hold interpolation for each point added or replaced. The
|
||||
point's mode applies to its following segment. Static controls remain fallbacks
|
||||
while a lane exists; moving/splitting clips does not move absolute track/bus lanes.
|
||||
See CONTROL.md for common parameter IDs and controller/automation precedence.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue