Waveform Pro 13.5 keeps crashing with certain (e.g. Soundtoys) plugins

[stippenstoh]

Waveform Pro 13.5 (MacOS Sequoia) has been pretty frustrating since I bought it as it cannot handle a number of plugins it seems.

Soundtoys Effekt Rack e.g. does not remember any settings after saving when using the AU version and the VST3 version sometimes crashes projects. Other plugins that I use less frequently, can crash it too.

Is this a known issue with Waveform (not being stable with 3rd party plugins)?
I contacted Soundtoys and they said they don't officially support Waveform

[alejandrozalaquett]

I have the same problem with the AU version not saving settings...

[stippenstoh]

It just crashed trying to load Voxengo Span (I mean, come one). It cannot use the VST3 version at all, the AU version seems to work. Several other plugins keep crashing Waveform on one occasion while they run the next time I open Waveform, then the next day the same plugins may crash Waveform again and I have to open with those plugins "Disabled". Enabling them in an opened session may or may not crash Waveforms, I cannot spot a pattern.

Happens with many other plugins, too. Waveform Pro is unusable like that. I have zero issues with the same plugins in Ableton or Reaper.

[fde101]

Is this a known issue with Waveform (not being stable with 3rd party plugins)?

This is a common issue with most DAWs, it is just the specific plugins that don't get along with them that change.

Having said that, I just pulled up a random project and added an AU instance of Little Plate, a VST2 instance of SieQ and a VST3 instance of SpaceBlender to my master bus as a test, no crashes or issues whatsoever.

WF 13.5.13, macOS 15.7, M1 Ultra chip, running native (not under Rosetta), current SoundToys plugin versions (5.5.3).

[stippenstoh]

Thanks for testing.
The problem is that, with Soundtoys Effekt Rack for example, it only happens occasionally. So it might work fine for two days then suddenly cause issues. Plugins from smaller developers can be worse and as I said, Ableton and Reaper do not have any issues with the same plugins.

[talby]

I would always report this to Tracktion, even if they are known to not answer promptly, even if the answer might only show up in a next release (hopefully) and never arrives in a personal answer. Not reporting the issues won't let them notice the issues which users suffer and which beta testers haven't run into.

Right after a crash, make a copy of the last version of the log file and attach it to the report. This gives them a chance to relate your description to some details about what might have technically been involved in causing the crash or the wrong behavior.

Use their chat-bot and asked it for the link to the bug report form.

[jabe]

Have you tried the 13.5.15 beta? It may answer the 13.5.13 problems.

[stippenstoh]

Thanks, yes I have but it unfortunately keeps crashing.

EDIT: it even got worse:

Screenshot 2025-11-01 at 11.50.46.jpg

[stippenstoh]

I would always report this to Tracktion, even if they are known to not answer promptly, even if the answer might only show up in a next release (hopefully) and never arrives in a personal answer. Not reporting the issues won't let them notice the issues which users suffer and which beta testers haven't run into.

Right after a crash, make a copy of the last version of the log file and attach it to the report. This gives them a chance to relate your description to some details about what might have technically been involved in causing the crash or the wrong behavior.

Use their chat-bot and asked it for the link to the bug report form.

That is a great suggestion, I already wrote them but not including any log files (stupid me).