Report the instrument's automatable parameters to the host under a frozen id table, in signal-flow order, with real units

42 of 44 ids issued: pitch key-track and Trigger length stay reserved pending a live path. Master gain reclassified Live — it never reloaded.
2026-08-02 15:14:16 -04:00
parent c7afa3a80f
commit bfaa0f2614
38 changed files with 1742 additions and 218 deletions
@@ -54,6 +54,16 @@ decision about what the render made obsolete.
 - **`kStageTimeMaxSeconds` (the stage-time ceiling `param_taper` owns) is not a reset-list
  candidate at all** — it bounds a knob's taper, is never itself a dialed value, and so has
  no disposition to classify against the ratified reset rule.
+- **A host automation lane outranks the reset, and the bake cannot clear it — a NAMED
+  limitation, not a bug.** Every reset-class value that is also an exposed VST3 parameter is
+  now notified to the host (the reset writes through `setInstrumentParams`, which is the one
+  notification funnel), so the host's DISPLAY follows the reset. A lane, however, lives in the
+  host's project data: if a reset-class parameter carries one, the host replays its curve onto
+  audio that already has that processing baked in — double processing, and the "sounds as the
+  dialled instrument sounded just before the click" claim does not hold in that case. There is
+  no detection available: `IAutomationState` reports the host's automation mode for the whole
+  plug-in, not per parameter, so both "refuse the bake" and "reset only the un-automated ones"
+  are unbuildable rather than merely unattractive. The user's remedy is to remove the lane.

 ## Modules