Crash selecting "Init" preset in VST plugins, when then "Init" preset is the only choice

Help, Support & Bugs
1

while trying to select a the “init” vst-preset, renoise closes down, without entry in the Logfile or anything. Tested on Manjaro-Linux and MX-Linux, booth with KDE.

to reproduce, you need one of the following VST`s

any Airwindows Vst2,
Surge XT effects - Vst3
Delay architect Vst3
any Dragonfly reverb, Vst3 (vst2 doesn`t crash**)
possibly any other effect, that has no vst-presets but “init”

start renooise 3.5.1 and load one of the vst-effects anywhere
click on the “init” preset - the dropdown appears
clicl again on “init” preset. > Crash

here is how the logfile looks in the end:
…
Application: Successfully loaded template document.

GraphPort: Initializing in WindowedMode…
GraphPort: Successfully initialized

Application: Init OK

StartupWindow: Closing the window…

Application: Enter MainLoop…Renoise

Vst3Plugs: Instantiating: /home/demo/.vst3/Delay Architect.vst3…
Vst3Plugs: Failed to apply initial component state to controller (not critical)

…end - here Renoise closes down

**maybe useful (maybe not)
the Dragonfly vst2 - version does not has a “init” preset, but a “default” named preset, that doesn`t change any value, when it is selected

2

I totally missed version 3.5.2 - :flushed: :flushed:

tested Renoise 3.5.2 on the manjaro-computer and the same happens there

3

Related to this, or the same prob: Device.active_preset (the index) is 0 for VST3, but 1 for VST2 - #2 by ffx

4

Thanks for reporting. This only happens in plugins which have (expose) no presets at all and will be fixed in the next update.

1 Like