Waveform Problem Plugins

[aMUSEd]

Haven't tried yet with my Virus Ti but every version has been unable to render anything but noise from it so I assume that problem persists.

[unholyeyebrows]

Hi. I have found an automation issue with the Trance Gate plugin by Kilohearts. I have a project with this plugin and an automation track to bypass or un-bypass it. I set the automation curve to either 100% or 0% to bypass / un-bypass the plugin and this works fine when plugin sandboxing is disabled.

However with sandboxing enabled this becomes unreliable, with the automation sometimes working, sometimes not. I can get it to work more reliably if I reduce the values to say 80% and 20% rather than 100% and 0%. However this seems like a bug to me.

I'm happy to share some diagnostics if anyone has time to investigate. This is on Waveform Pro 11.5.2 Windows 10.

Thanks
Nick

[unholyeyebrows]

Hi. I have found a problem using the Scaler 2 plugin in Waveform 11.5.2 on Windows. I create a chord progression in Scaler and then use the 'Drag' button to drag this onto a MIDI track. This works but results in two clips being created, one on top of the other. Therefore if I then drag the new clip, there is another lurking beneath meaning I have to delete the duplicate each time.

Easily reproducible.

Thanks
Nick

[boomt]

Hi. I have found a problem using the Scaler 2 plugin in Waveform 11.5.2 on Windows. I create a chord progression in Scaler and then use the 'Drag' button to drag this onto a MIDI track. This works but results in two clips being created, one on top of the other. Therefore if I then drag the new clip, there is another lurking beneath meaning I have to delete the duplicate each time.

Easily reproducible.

Thanks
Nick

I can also replicate this. Kind of got used to deleting the second clip.

[pough]

Easily the most problematic plugin for me is the VST3 version of Luftikus. It keeps crashing the sandbox. That might not sound so bad, but for two things.

1. It's not sandboxed.
2. It's not even loaded.

Just the fact that it's installed on the computer seems to crash Waveform's sandbox.

25 Feb 2021 19:44:09 *** ERROR: Plugin sandbox crashed:
Crashed
Thread 0:
** Plugin crashed: Luftikus (VST3)
0: tracktion_bridge_slaveplugin.cpp:tracktion_bridge::BridgePluginWrapper::parameterValueChanged:223

[burn]

CamelCrasher has no gui, just a black rectangle. Waveform 11.5.9 on Catalina 10.15.7

[scotofil]

...
I am using the free version of Waveform 11.1.0 on an x64 Win10 PC, and I am having issues with Unfiltered Audio's G8 v1.2
...

11.5.0 made a great leap forward: using the lookahead did not immediately crash either the plugin or W11, however moving it around during regular work was still causing crashes ever so often. Now I finally went to 11.5.9 and based on a quick check, it seems to be stable. Should I face major issues nevertheless, I'll report back. Thanks for all potential actions on this one!

[scotofil]

Voxengo .vst3 plugins have GUI issues: buttons which would open drop-downs and pop-ups don't work (neither the drop-downs nor the pop-ups appear, and the buttons get stuck "pressed"), and some of the other buttons (I wasn't able to narrow down "which kind" of buttons) don't seem to work either. The VST2 .dlls of the same plugins are working well. I made a quick test with SPAN 3.10, Marvel GEQ 1.10 Correlometer 1.4 and Latency Delay 2.7, each of these seem to produce the same behaviour.

[asprog]

viewtopic.php?f=22&t=563028

[pough]

CamelCrasher has no gui, just a black rectangle. Waveform 11.5.9 on Catalina 10.15.7

From what I can see online, some Mac users get the black screen. Apparently it depends on OS version and DAW. I don't use a Mac, so I can't tell you much more than that. (It works fine on my Windows 10 machine in Waveform.)

[pough]

Voxengo .vst3 plugins have GUI issues: buttons which would open drop-downs and pop-ups don't work (neither the drop-downs nor the pop-ups appear, and the buttons get stuck "pressed"), and some of the other buttons (I wasn't able to narrow down "which kind" of buttons) don't seem to work either. The VST2 .dlls of the same plugins are working well. I made a quick test with SPAN 3.10, Marvel GEQ 1.10 Correlometer 1.4 and Latency Delay 2.7, each of these seem to produce the same behaviour.

Voxengo VST3 + Sandbox = trouble. That's been my experience. Your issue might be a different problem because I was having crashed Sandbox issues, not interface issues.

[scotofil]

Voxengo VST3 + Sandbox = trouble. That's been my experience. Your issue might be a different problem because I was having crashed Sandbox issues, not interface issues.

Nope, that's not it, as with W11.5 I decided to abandon sandboxing.

[pough]

Yeah, I'm seeing it now. None of the controls in the VST3 versions that have drop-downs or pop-overs work. They work fine in the VST2 version. And both versions work fine in Cantabile, FL Studio, and StudioOne. Toggle controls seem to work fine in all versions.

There is something about the combination of VST3 and Waveform that inhibits Voxengo's drop-down and pop-over controls.

SPAN VST2 passes all tests in pluginval 2.9 with a strictness level of 10.
SPAN VST3 crashes pluginval 2.9 with a strictness level above 5.

Waveform's built-in version of pluginval tests at a strictness level of 5, so it will seem as though it works fine, but it doesn't. I've found that the Waveform edition of pluginval can deal with a crash but you can't set the strictness level. The standalone pluginval allows you to set the strictness level, but a crash results in an empty log file.

Software is weird.

[asprog]

Same thing with u-he, Arturia, Cakewalk vst3s, as said here:
viewtopic.php?f=22&t=563028
with FigBug answer.

[marksmusicaustralia]

Camel Audio Alchemy player 1.55 shows blank GUI after Waveform update 11.5.9 (was working perfectly before this). VST is only showing up in plugin list (AU is not showing).
Running OS X Catalina on 6 month old intel Mac mini.