Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

VST3 initialization and preset issues #80

Open
l0calh05t opened this issue Jan 3, 2018 · 1 comment
Open

VST3 initialization and preset issues #80

l0calh05t opened this issue Jan 3, 2018 · 1 comment

Comments

@l0calh05t
Copy link

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)

@olilarkin
Copy link
Owner

will look into it. VST3 factory presets suck. reaper displays .vstpreset files in the right folders

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants