CONTROL publication and MIDI order¶
One CONTROL intent producer and one AUDIO consumer use the existing SPSC queue.
For raw profiles, ordinary acknowledged scalar updates and validated complete
state can be published while AUDIO is inside a getter or native DSP. A host
SetParameterNormalizedValue success means request acceptance only: the matching
acknowledged model update determines DSP intent. Parameter-manager access retains
its SDK caller/thread requirements. CONTROL reads its own intent/staging and
atomic queue indices; it does not inspect AUDIO diagnostics or event scratch.
Stopped lifecycle, profile, telemetry and timing-candidate operations require the caller to stop/join AUDIO and serialize CONTROL. An admission-bit check detects an already entered callback; it does not provide atomic exclusion against a newly starting callback. These operations are not a general cross-thread control lock.
Whole block preflight validates every packet, effective trailing control and both audio directions before complete state application, dequeue, transport collection or native DSP. A last accepted complete restore supersedes earlier intent; its trailing controls retain original order. At equal offset 0, effective queued controls precede original MIDI order. Total controls plus MIDI must fit the full prepared capacity. Late malformed packets, excess combined capacity, metadata, layout and transport refusal preserve pending intent and native history.
All defined complete one-, two- and three-byte channel/system messages use the existing canonical policy, including standalone F7 as EndOfExclusive only. F7 never infers a SysEx stream; SysEx payloads, undefined statuses, malformed lengths, non-seven-bit data, nonboolean immediate flags and invalid order/offsets are refused. The SDK compatibility contract identifies timestamp 0 as immediate while the flag is currently unset; boolean 1 remains accepted with authoritative ordered timestamp, including valid offset 0/zero-frame use. The note-only defaults retain their narrower policy. Raw offset 0 events and queued controls are valid for zero frames, with no audio/FIFO frame advancement. Native kind14 contains exact wire/channel bytes but no MIDI source-port identity; this profile does not merge unidentified nodes or invent port provenance.