WaveForm 11.5 and Helix Native VST3 crashes now

[DroneShotFPV]

Ever since I did an update to the newest Waveform (11.5, Pro version BTW, NOT free) My Helix Native, versions 1.93, 3.0, and 3.01 all crash now. It will load, and whatever was the last amp model / patch I had selected will play, but as soon as I try to change a parameter on the Helix Native, such as enabling a Chorus effect already in the loop, change the IR, or swap to a different amp sim / model, it makes a stuttering sound like locked up audio, and crashes with a yellow ! sign on the plugin, and the plugin stops (obviously). If I delete, and re-add the plugin to the track, it works again until trying to make any changes.

In troubleshooting (being the IT Administrator I am) I have removed the plugin COMPLETELY, wiped all traces, re-installed, downloaded older version, used versions 1 at a time, turned off experimental engine in WaveForm, when using experimental tried Hybrid and HyBrid Semaphore, changed install locations, etc etc, it still crashes. When using the VST2 version though, it works perfect... Any ideas why?

Also, using other VST3 plugins, as far as I can tell, work fine... I need to actually put them through a bigger test, but they seem to work (ML Sound Lab Amped Stevie T for example) ...

Anyone have similar issues / ideas as to what else to try for VST3?

In case specs are asked, I run the following:
Core i7 6900k (8 Core, 16 threads)
128 GB DDR4 CorSair Vengeance RAM
Main drive nVme m.2 1TB SSD @ 3500 MB/S Read and Write
Another 8TB of various SSD's and a WD Black Spidle drive
Nvidia RTX 2080 Ti
1200w Gold Rated power supply
Audio input is a Behringer X1204USB, or a Focusrite Scarlet 18i8

Thanks in advance for any input!

[spoontechnique]

Run the Pluginval utility on it. Go to Settings > Plugins, select it, then Validate Selected Plugin. See if it passes the test first.

[DroneShotFPV]

Run the Pluginval utility on it. Go to Settings > Plugins, select it, then Validate Selected Plugin. See if it passes the test first.

Thanks for the reply! I did Validate it just now, and all tests passed successfully. It's so weird because I have used Tracktion since Tracktion 5 (paid for "pro / paid versions of every one from 5 on up) and never had an issue. My Helix Native 3.0 was working perfectly all up until I updated to WaveForm 11.5.1. So weird. I was thinking about uninstalling and re-installing, but not sure since other plugins appear to be working fine.

[Steve Bolivar]

Does Helix have a VST2 version? This is only partially related but iZotope Iris synth VST3 crashes but the VST2 works fine.

[DroneShotFPV]

Does Helix have a VST2 version? This is only partially related but iZotope Iris synth VST3 crashes but the VST2 works fine.

It does, I had mentioned above that the VST2 version works without fail. I wonder if there are issues with certain VST3 types if you are experiencing this also? The crazy thing is that other VST3 Amp model plugins are working fine. My ML Sound Labs AMPED Plugin for Stevie T is working perfectly without issue, and it's a VST3... Maybe there is something in the works for an update.... I can only hope. I guess there isn't anything to worry about with using VST2 over VST3, right? I never really dug into the differences between the 2, so I will assume all is well to continue with VST2 until they fix it?

[gigazaga]

Try it with plugin sandboxing off if you haven’t already.

[DroneShotFPV]

Try it with plugin sandboxing off if you haven’t already.

This 100% fixed it!!! Any idea as to why that was the issue? I would think this is something that would help prevent other issues, but not cause them?

Many thanks for the advice!

[pough]

I would think this is something that would help prevent other issues, but not cause them?

As far as I can tell, sandboxing prevents one issue: a plugin crashing Waveform completely. Other than that, it's just added complexity and reduced and/or awkward functionality. Some plugins only fail when sandboxed, possibly to do with the added complexity of communication with the DAW via non-standard means* or maybe just because many developers have less experience with VST3.

Having a plugin run in a separate process is more complex. It makes windowing go very wrong in some circumstances. You can't take a snapshot of the plugin and sidechain needs special consideration.

My recommendation is to have sandboxing on, but un-sandbox every plugin that works fine without it. I have only one plugin sandboxed (HoRNet VU Meter MK4.)

* I don't really know how it works, but I'm guessing VSTs are designed to exist in the same process as their host.