Waveform Problem Plugins

[synergyforge]

@synergyforge
I've recently purchased Phase Plant. I use it in Waveform PRO 12.0.54 on Windows 10. I'm not experiencing any crashing in Waveform (so far) but I do see the crashing in the plugin validator. It happens when the validator gets to the "Editor" test. My guess is that it might be graphics-related. Try going to Settings -> Advanced -> Performance and change GUI Rendering Mode to Software Renderer. I had problems with some plugins until I changed that a while back.

Thanks for the suggestion, but that's not it. I actually changed it from software to OpenGL the other day, and I noticed no change. I think either Waveform Free 11 doesn't handle VST3's as well as Pro 12 does, or maybe it's an issue between Waveform and my onboard motherboard audio chipset from Realtek. This is the only plugin I've noticed an issue with though.

[pough]

I think either Waveform Free 11 doesn't handle VST3's as well as Pro 12 does

A-ha! Version numbers are helpful. I have Waveform PRO 11 and 12. Phase plant works fine in 12* and crashes 11.

By the way, you can go to the Maintenance section of Settings and click the "Show the Log File" button.

I wonder if it would be worthwhile letting Kilohearts know about pluginval. I've tried to introduce it to other companies and they've mostly been dismissive; either ignore it or the email equivalent of a nod and smile.

* I've only had it for a few days, so I'm not 100% sure it works fine in all circumstances.

[synergyforge]

I think either Waveform Free 11 doesn't handle VST3's as well as Pro 12 does

A-ha! Version numbers are helpful. I have Waveform PRO 11 and 12. Phase plant works fine in 12* and crashes 11.

By the way, you can go to the Maintenance section of Settings and click the "Show the Log File" button.

I wonder if it would be worthwhile letting Kilohearts know about pluginval. I've tried to introduce it to other companies and they've mostly been dismissive; either ignore it or the email equivalent of a nod and smile.

* I've only had it for a few days, so I'm not 100% sure it works fine in all circumstances.

Ah! Thank you so much for confirming so that I don't have to lose my mind chasing endless, fruitless leads. Guess now I have to decide whether or not I want to shell out for Waveform Pro or wait til there's a Free version of 12. It works in the trial version of FL Studio, but I think I like Waveform's workflow better.

Also, thanks for the help on how to get to the Waveform log.

[pough]

I should add this only affects the VST3 version of Thorn. VST2 version works just fine so I'm not at a loss just yet. Just wanted to put this here so I might get looked into for the VST3 version going forward.

FWIW, in Waveform 12, as on your computer, Thorn VST 2.4 is no issue at all. VST 3 works, but seems kind of glitchy GUI-wise. No crashes, but strange start-stop redraws when moving the GUI around. It's definitely worth a gander, so to speak.

I just got Thorn and it's great but for me the VST3 version completely locks up Waveform 12, requiring me to open the Task Manager and end the task.

[BloodyCactus]

how about their own? LoFreq Modern wants to update to v1.1.1 but its Linux url is toast so their own updater fails to update their own plugin... Go Team Tracktion!

[asprog]

V1.1.1 of all Retromod are broken!
No sound when you press a key, a brief sound when you release...
I tried VST2 and VST3 with Waveform 11 and Waveform 12.

[DCPImages]

Not loading:
Concept.vst3 KROTOSAUDIO.COM
Spacecraft.vst3 TRACKTION.COM
SpacecraftFX.vst3 TRACKTION.COM
Duckout.vst3 IMAMUSICMOGUL.COM

[ON BEATS]

This is a shame to read guys. Are you all using Waveform 12 and having these problems?

I was considering upgrading because I heard the interface is smoother. Not sure if its worth the jump yet..

[Watchful]

The only issue I've had is some older Waves plugins no longer load, but that's more a Waves Central issue. Everything else, whether vst2 or vst3, has been fine.

[ON BEATS]

Yeah VST2 seems better now for me. VST3 doesn't open the plug-in properly on screen first time when opening.

I heard that if a plug-in is created as a VST then rendered as AU it doesn't perform as well, and the same goes for AU files that are rendered as VST.

Not sure if it's true, but Waveform 11 performs better when I use VST only and avoid VST3/AU

[pough]

I should add this only affects the VST3 version of Thorn. VST2 version works just fine so I'm not at a loss just yet. Just wanted to put this here so I might get looked into for the VST3 version going forward.

FWIW, in Waveform 12, as on your computer, Thorn VST 2.4 is no issue at all. VST 3 works, but seems kind of glitchy GUI-wise. No crashes, but strange start-stop redraws when moving the GUI around. It's definitely worth a gander, so to speak.

I just got Thorn and it's great but for me the VST3 version completely locks up Waveform 12, requiring me to open the Task Manager and end the task.

There is a 1.3.1 version update to Thorn that's currently only available through the DS Audio website that seems to fix the issues I was having with the VST3 plugin.

https://dmitrysches.com/thorn-changelog

[Schmidi]

Not sure if mentioned or not, but in demoing Waveform 12 all my Arturia VST have GUI issues. They will appear shrunken and off centered to the lower left of the Waveform plugin window.

When I open Pigments, Waveform will open 3 instances of the plugin on the track I'm using. Even when delete the duplicate instances, Waveform will often reopen new ones when I change presets.

I like it overall and I does seem FAR more stable than previous versions (I last tried 7 I believe)

[citrusui]

Chiming in to note that the KORG wavestate native plug-in is broken in Waveform 12. Just adding it to a track will cause the application to freeze up, then the sandbox process will crash. Tested the plugin in Studio One and FL Studio - no problem there. What's weird is that I *know* the plug-in worked before, as I had rendered a track with it back in March.

Edit: wavestate native 1.0.3 works fine, no problem. Something in version 1.0.4 or 1.0.5 (latest) introduced the issue. Unsure if this is on Korg's end since as previously stated, FL and S1 handle the plug-in fine.

[jonatello]

Scaler 2 in Waveform 11 Pro

GUI is either smaller than window, with the cursor way off target, or with "Enable DPI Awareness", the window is cutting off most of the GUI, making it unusable.

I'm add this in here, since I couldn't find any mention of it. With Scaler 2 being so popular, I'd be surprised if I was the first person to try using it in Waveform 11

[hummingbird]

Collective 1.3.2 pitch bend stops responding to midi controller while note is being played. Waveform Version 12.1.8 (Built: 28 October 2022) (64-bit), Windows 11. My windows 10 laptop has Collective 1.3.1 on it and it works perfectly. I recorded some midi from the controller and everything was there in the clip but again no pitch bend while note sounding. I uninstalled Collective 1.3.2 and installed 1.3.1. It works perfectly.