• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

List any Plugin Issues with version 8 here

Are you suggesting that if you use an amazing plugin for years with excellent results, you would simply abandon it when it stops working after an update of a DAW because of the integrity of the coding? If so, you are prioritizing computer programming over audio engineering/production at that point

Yes. If that "amazing" plugin was put together poorly but somehow managed to dodge SDK checkpoints for several years but one day decides to crash my session AND I lose work because of that crash - I would of course check all angles - and no - I would not absolve SP straight away but sooner or later the culprit will be revealed and there is a very high likelihood - it won't end up being the DAW.

I have been an S1 user from April 2011 to today - I have used every major and minor release issued and I have documented exactly 4 crashes in that timeframe - all were due to dodgy plugins.

So after 15 straight years of usage (AND 15 years of using a finely tuned VST engine within S1/SP) - it goes without saying that I trust Studio One and will put the same trust in Studio Pro when my upgrade lands in early spring 2026. It has never let me down yet.

Plugins on the other hand - need to earn my trust. They can only do that by demonstrating stability year in and year out while passing all checkpoints and standing up to repeated and constant usage as required.

Now - does this happen often with my "go-tos?" - never that I can recall.

My only priority is the stability of the DAW (and the session that is loaded at any given time). This easily outweighs any importance of any third party plugin - regardless of how good it might be.

I have yet to install v8 but look forward to seeing if any of my standard stalwarts fail a nicely tightened and refreshed VST SDK spec checkpoint.

VP
 
Last edited:
I'm experiencing a ton of bugs with plugins that are otherwise well-known on the market (Waves, Plugin Alliance, etc.). Are you experiencing the same thing? Just to be clear, these are official plugins.
I'm just curious: What Waves plugz are you having problems with? I have tons o' Waves and am not having any issues with them (so far)...
 
Can someone describe the difference between a plugin crashing and a plugin being blacklisted? If a plugin crashes due to its failure to meet vst3 improved standards then shouldn't it be blacklisted?
 
Not regulary. But you can convert back FSP 8 sessions back to Studio One Pro 7 songs with https://s1toolbox.com - which of course will only work if none of the new features were used.
Hi Lukas,
Does import session data work from v.8 to v.7 so to keep working on the previous version from a song that was created in version 8?
 
Can someone describe the difference between a plugin crashing and a plugin being blacklisted? If a plugin crashes due to its failure to meet vst3 improved standards then shouldn't it be blacklisted?
Just throwing this out there.

Could it be exlained by...
Declared parameters on scan are OK (passive check), but when in use throws out data that exceeds declared parameters (stop doing that/Bang) ?
No time to blacklist, capture state of program Memory (Dump).

Declared parameters on scan do not conform...(Blacklist) crash averted.

Does that make sense?

Kindest regards.
 
Can someone describe the difference between a plugin crashing and a plugin being blacklisted? If a plugin crashes due to its failure to meet vst3 improved standards then shouldn't it be blacklisted?
A plug-in is blacklisted when it crashes during the plug-in scan. The plug-in scanner runs as a separate program/process, so crashing plug-ins won’t take down Studio One/Pro during the scan. When a plug-in responds successfully, it is added to the list of detected plug-ins. If it crashes or does not respond, Studio One/Pro will add it to the blacklist (or blocklist).
 
I'm just curious: What Waves plugz are you having problems with? I have tons o' Waves and am not having any issues with them (so far)...
Also, please let me know what WAVES plugins you might be having trouble with....I might be able to help with that.
 
Also, please let me know what WAVES plugins you might be having trouble with....I might be able to help with that.
It was the poster, Julien Ober, above who mentioned problems with Waves that I was simply responding to. I have no problems with my plugins.
 
For anyone experiencing issues with a VST3 plug-in in version 8: Could you please check whether setting Process Precision to 32-bit (instead of 64-bit) in the Audio Setup resolves the issue as a temporary workaround?
 
Hi Lukas,
Does import session data work from v.8 to v.7 so to keep working on the previous version from a song that was created in version 8?
Yes, and it works perfectly. I've done it for all the titles I created with FSP 8 and everything is fine. However, as Lukas told me, for it to work, no FSP 8-specific tools should have been used in the session.
 
I'm just curious: What Waves plugz are you having problems with? I have tons o' Waves and am not having any issues with them (so far)...
Not so much Waves, but especially Plugin Alliance with the TBTECH CENOZOIX. The DAW crashed several times when I placed this plugin on a track. I also had crashes with UVI Falcon. In total, 5 crashes in one morning, more than enough to make me go back to SO 7
 
For anyone experiencing issues with a VST3 plug-in in version 8: Could you please check whether setting Process Precision to 32-bit (instead of 64-bit) in the Audio Setup resolves the issue as a temporary workaround?
Thanks for this suggestion Lukas, it is perfectly repeatable in my case for Oxford Drum Gate which is the one I was having most issues with.

If I change it to 32 bit, the playback is fine, if I switch it to 64 bit I get latency issues with the playback of those tracks.

I recall this being an issue a little while ago with Softube's Tape which I use a bunch on drums in the MixFX slot.
 
For anyone experiencing issues with a VST3 plug-in in version 8: Could you please check whether setting Process Precision to 32-bit (instead of 64-bit) in the Audio Setup resolves the issue as a temporary workaround?
Thanks for this suggestion. I'll try that next time I get to the studio. 👍
 
For anyone experiencing issues with a VST3 plug-in in version 8: Could you please check whether setting Process Precision to 32-bit (instead of 64-bit) in the Audio Setup resolves the issue as a temporary workaround?
Thanks Lukas. I tried that and so far, zero crashes in an hour of work. Fingers crossed it stays that way. Just out of curiosity, how does this 32-bit option seem to work to avoid problems?
 
For anyone experiencing issues with a VST3 plug-in in version 8: Could you please check whether setting Process Precision to 32-bit (instead of 64-bit) in the Audio Setup resolves the issue as a temporary workaround?
Pulsar Plugin now works in 32 bit processing mode. So this is clearly a bug. Thanks for passing along the temporary workaround. Second question, are we losing rendering quality using 32 bit plug in processing vs, 64?
 
I'm experiencing a ton of bugs with plugins that are otherwise well-known on the market (Waves, Plugin Alliance, etc.). Are you experiencing the same thing? Just to be clear, these are official plugins.
Don't have any Waves product, but my Plugin Alliance products appear to be working fine ... so far....
 
Pulsar Plugin now works in 32 bit processing mode. So this is clearly a bug. Thanks for passing along the temporary workaround. Second question, are we losing rendering quality using 32 bit plug in processing vs, 64?
I can confirm Pulsar Echorec vst3 version crashed. It worked fine as an insert. I then set it up as an FX send, sent from my drum buss to it. At that point it didn't crash but engage the fader flip on the drum buss immediately crashed it. I couldn't replicate this behaviour a second time, it was stable
 
Slate Digital "Virtual Tape Machines". It pretends to work, but just pumps out a lot of noise at max volume.
 
Back
Top