Per-host quirks for MOTU Digital Performer. More...
Go to the source code of this file.
Namespaces | |
| namespace | pulp |
| namespace | pulp::format |
| What the product grants a device: the quota table indexed by capability tier and live thermal state. | |
| namespace | pulp::format::host_quirks |
Functions | |
| void | pulp::format::host_quirks::apply_digital_performer (HostQuirks &q, HostVersion) |
| Populate Digital Performer host-gated flags onto q. | |
Per-host quirks for MOTU Digital Performer.
Digital Performer revives the edit controller on preset-load / project-import paths without re-querying the previously published parameter list. Plug-ins that mutate the parameter set via restartComponent(kParamValuesChanged | kParamTitlesChanged) end up with stale labels and stale value-domain bounds in DP's automation lane.
The independent fix layers an additional kReloadComponent notification onto the standard restart bundle when the detected host is Digital Performer. Cubase / Logic / Reaper do not require this — they re-query the parameter list whenever the edit controller is recreated.
Documented across Digital Performer 10.x and 11.x; no fixed release announced. apply_digital_performer fires the flag unconditionally.
LessonOnly as of the 2026-05-26 iPlug2-audit batch — documented from Steinberg's VST3 SDK + MOTU Digital Performer Plug-Ins Guide, no in-tree bench yet. Promote to Speculative after the per-symptom isolation tests ship; promote to Validated after Digital Performer bench evidence lands.
Reference-Lineage: independent reproducer=#3046 docs=https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Workflow+Diagrams/Edit+Controller+Call+Sequence.html