07-02-2022, 01:01 AM
|
#1 |
|
Human being with feelings
Join Date: Dec 2007
Posts: 32
|
VST3 internal state change not recognized (FIXED)
If a VST3 plug-in changes its internal state that is not represented by a parameter exposed to the host (e.g. changing internal parameter via GUI), it can notify the host via a setDirty() call.
https://steinbergmedia.github.io/vst...-state-support Unfortunately, the call seems to be ignored by REAPER. As a result, the state change is not recorded in the Undo history. |
|
|
|
07-03-2022, 06:39 PM
|
#2 |
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,223
|
ah thanks, adding support for this!
|
|
|
|
|
07-05-2022, 08:19 AM
|
#3 |
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,223
|
The current +dev build adds support for this (see the pre-release forum)
|
|
|
|
|
07-05-2022, 12:28 PM
|
#4 | |
|
Human being with feelings
Join Date: Dec 2007
Posts: 32
|
Quote:
|
|
|
|
|
|
08-10-2022, 10:58 AM
|
#5 |
|
Human being with feelings
Join Date: Jun 2012
Location: Spain
Posts: 7,470
|
I wonder if this dirty parameter could be used by REAPER to know if it needs to reencode all the vst chunk data or just use the same data. This could be great for faster saving the project RPP files if plugins are not marked dirty.
|
|
|
|
 |
| Thread Tools | |
|
|
