You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
For plugins without presets, IPlugVST3::initialize causes issues, because it calls RestorePreset(0) which causes the plugin to use some random/unititialized parameters. Also, presets do not appear (at least in Reaper), unless the (undocumented) define VST3_PRESET_LIST is set. Am I doing something wrong? In Reaper, if I select a preset in the VST3 version it will also jump back to displaying the default preset's name (after loading the selected preset), which doesn't occur with the VST2 version of any of my plugins. Furthermore, selecting "Restore factory default" will cause a new preset called "No preset" to appear (again only with VST3). The latter two things may be Reaper-only issues (have no other host to test on)
The text was updated successfully, but these errors were encountered:
For plugins without presets,
IPlugVST3::initialize
causes issues, because it callsRestorePreset(0)
which causes the plugin to use some random/unititialized parameters. Also, presets do not appear (at least in Reaper), unless the (undocumented) defineVST3_PRESET_LIST
is set. Am I doing something wrong? In Reaper, if I select a preset in the VST3 version it will also jump back to displaying the default preset's name (after loading the selected preset), which doesn't occur with the VST2 version of any of my plugins. Furthermore, selecting "Restore factory default" will cause a new preset called "No preset" to appear (again only with VST3). The latter two things may be Reaper-only issues (have no other host to test on)The text was updated successfully, but these errors were encountered: