I must say it's a strange issue. I just tested the vst3 version of Saturator in a Live set and put it everywhere. No crash.
The session that was crashing systematically before that was so screwed that I couldn't even open it again, but just before it started to be unusable, it was perfectly fine (with already few instances of Saturator on few tracks).
Could it be linked to other plugins in the session ?
PSP Audioware VST3-plugins don’t work properly
-
- KVRist
- 61 posts since 22 Jun, 2012
Hi everyone,
At the beginning of 2026, we plan to focus on resolving the compatibility issues some users have reported with our plug-ins in Ableton Live and Bitwig.
We’re currently looking for users who would be interested in helping us identify and resolve these issues. In particular, we’d love to work with users who have experienced crashes, unexpected behavior, or other inconsistencies in Live or Bitwig and are willing to spend some time testing our plug-ins to help us identify reliable reproduction steps and usage patterns.
If you’re interested in participating, please get in touch with us at contact@pspaudioware.com and include details about your system, DAW version, and the issues you’ve encountered.
Thank you in advance for your help and support - your feedback plays a crucial role in improving our products.
Best regards,
Antoni Ożynski
PSPaudioware
www.pspaudioware.com
At the beginning of 2026, we plan to focus on resolving the compatibility issues some users have reported with our plug-ins in Ableton Live and Bitwig.
We’re currently looking for users who would be interested in helping us identify and resolve these issues. In particular, we’d love to work with users who have experienced crashes, unexpected behavior, or other inconsistencies in Live or Bitwig and are willing to spend some time testing our plug-ins to help us identify reliable reproduction steps and usage patterns.
If you’re interested in participating, please get in touch with us at contact@pspaudioware.com and include details about your system, DAW version, and the issues you’ve encountered.
Thank you in advance for your help and support - your feedback plays a crucial role in improving our products.
Best regards,
Antoni Ożynski
PSPaudioware
www.pspaudioware.com
-
- KVRAF
- 2048 posts since 13 May, 2004 from Germany
I don't have crashes or so with the vst3 in Cubase on windows 10.
But I have CPU overloads in Bluecat Patchwork when the gui is open.
I haven't tested with the vst2 version but it would be great if that issue could be resolved as well.
Bluecat told me that they have done everything they could and that it must be a problem with the plugins (in my case Easyverb 2, psp 2445 and psp 285)
But I have CPU overloads in Bluecat Patchwork when the gui is open.
I haven't tested with the vst2 version but it would be great if that issue could be resolved as well.
Bluecat told me that they have done everything they could and that it must be a problem with the plugins (in my case Easyverb 2, psp 2445 and psp 285)
-
- KVRist
- 250 posts since 13 Oct, 2018
I Antoni. I just did send an email. I'd be glad to help...PSP wrote: Wed Dec 24, 2025 11:34 am Hi everyone,
At the beginning of 2026, we plan to focus on resolving the compatibility issues some users have reported with our plug-ins in Ableton Live and Bitwig.
We’re currently looking for users who would be interested in helping us identify and resolve these issues. In particular, we’d love to work with users who have experienced crashes, unexpected behavior, or other inconsistencies in Live or Bitwig and are willing to spend some time testing our plug-ins to help us identify reliable reproduction steps and usage patterns.
If you’re interested in participating, please get in touch with us at contact@pspaudioware.com and include details about your system, DAW version, and the issues you’ve encountered.
Thank you in advance for your help and support - your feedback plays a crucial role in improving our products.
Best regards,
Antoni Ożynski
PSPaudioware
www.pspaudioware.com
Nice initiative !
- KVRian
- 1112 posts since 26 Jun, 2008 from Czech Republic
Oh, I'm going to write you as well. I suspect it's a problem in the graphics part of the plugin. I experience it with Infinistrip and Staruator. Weirdly VintageWarmer is OK even with the new version.
Event viewer in Windows says thet ntdll.dll tried access a wrong memory. That might be a clue. Also it's deffinitelly happening while the plugin is either reading or writing the preset data. As it never happens when I directly open it. Only when saving a project, or loading a project.
Also it feels like this might be related to the massive graphical issues I do have with Ohmforce Omnicide(S). It feels to me like the nVidia Optimus might be worth investigating. That's how my installation differs from a normal PC. This is a plaptop with two GPUs.
One possible explanation: When I was writting my own plugin, I noticed that Ableton specifically doesn't keep the GUI in memory. Once you close it, it destroys the object instance. It creates it again when you open it. I don't think this is common in most other DAWs. Could it be that while loading the preset, the parameter values are propageted to a GUI instance that doesn't exist at the moment? Just guessing.
EDIT: Btw Kontrast by Dawesome has the same problem. Crashes while saving/loading. Creates the same ntdll.dll memory access violation event in the Windows Event Viewer.
Event viewer in Windows says thet ntdll.dll tried access a wrong memory. That might be a clue. Also it's deffinitelly happening while the plugin is either reading or writing the preset data. As it never happens when I directly open it. Only when saving a project, or loading a project.
Also it feels like this might be related to the massive graphical issues I do have with Ohmforce Omnicide(S). It feels to me like the nVidia Optimus might be worth investigating. That's how my installation differs from a normal PC. This is a plaptop with two GPUs.
One possible explanation: When I was writting my own plugin, I noticed that Ableton specifically doesn't keep the GUI in memory. Once you close it, it destroys the object instance. It creates it again when you open it. I don't think this is common in most other DAWs. Could it be that while loading the preset, the parameter values are propageted to a GUI instance that doesn't exist at the moment? Just guessing.
EDIT: Btw Kontrast by Dawesome has the same problem. Crashes while saving/loading. Creates the same ntdll.dll memory access violation event in the Windows Event Viewer.
Evovled into noctucat...
http://www.noctucat.com/
http://www.noctucat.com/
