• Hi and welcome to the Studio One & Studio Pro User Forum!

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

List any Plugin Issues with version 8 here

louieshowers

louieshowers

New member
UPDATE: THIS WAS A BUG and was corrected with the release of version 8.0.1

My studio partner upgraded from 7 to 8 and we have experienced issues with specific plugins (which were updated to the latest versions). One example is Pulsar Echorec. It is causing a surge of audio noise and keeps ramping, making it loud and unusable....The same song on existing sessions of Presonus Studio one 7 behaves fine.

Can anyone chime in and let me know if you are experiencing this and also any other plugins that are causing issues in Fender Studio Pro 8?

Thanks!
 
Last edited:
louieshowers said:
My studio partner upgraded from 7 to 8 and we have experienced issues with specific plugins (which were updated to the latest versions). One example is Pulsar Echorec. It is causing a surge of audio noise and keeps ramping, making it loud and unusable....The same song on existing sessions of Presonus Studio one 7 behaves fine.

Can anyone chime in and let me know if you are experiencing this and also any other plugins that are causing issues in Fender Studio Pro 8?

Thanks!
Click to expand...
It's blacklisted a couple of my plugin alliance Bettermaker plugins
 
PSP Chamber (almost always)
Kirchhoff EQ (sometimes)
 
louieshowers said:
My studio partner upgraded from 7 to 8 and we have experienced issues with specific plugins (which were updated to the latest versions). One example is Pulsar Echorec. It is causing a surge of audio noise and keeps ramping, making it loud and unusable....The same song on existing sessions of Presonus Studio one 7 behaves fine.

Can anyone chime in and let me know if you are experiencing this and also any other plugins that are causing issues in Fender Studio Pro 8?

Thanks!
Click to expand...
Hi. Mustang plugin works for a few minutes then deactivates with the warng saying Mustang Native has been deactivated because it produced invalid data. Rumble Native works fine. No clue why this is happening

Thanks
 
louieshowers said:
My studio partner upgraded from 7 to 8 and we have experienced issues with specific plugins (which were updated to the latest versions). One example is Pulsar Echorec. It is causing a surge of audio noise and keeps ramping, making it loud and unusable....The same song on existing sessions of Presonus Studio one 7 behaves fine.

Can anyone chime in and let me know if you are experiencing this and also any other plugins that are causing issues in Fender Studio Pro 8?

Thanks!
Click to expand...
Hi. Mustang plugin works for a few minutes then deactivates with the warng saying Mustang Native has been deactivated because it produced invalid data. Rumble Native works fine. No clue why this is happening

Thanks
 
As stated in another thread Dreamtonics Synthesizer V Studio 2 Pro 2.2.0 is blacklisted and wont work when tested in Version 8.
 
Eaglepass said:
As stated in another thread Dreamtonics Synthesizer V Studio 2 Pro 2.2.0 is blacklisted and wont work when tested in Version 8.
Click to expand...

Is that ARA or VST?

Just tried mine - both Synth V Pro and Synth V Pro 2. In ARA I just get the ARA splash screen and no access to the app. In VST3, everything's working fine with both.
 
Last edited:
In ARA…..

Sorry I did not test VST as I have become used to only using the ARA mode.
 
Muse Plugin streams bad audio in SP8. Worked fine in S17
 
I wonder what has changed between versions and the way they handle vst3 :unsure:
 
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.
 
Julien Ober said:
I'm experiencing a ton of bugs with plugins that are otherwise well-known on the market
Click to expand...
Some of them are even well-known to not confirming to the VST standards.

louieshowers said:
I wonder what has changed between versions and the way they handle vst3 :unsure:
Click to expand...
Studio One/Pro regulary updates the VST SDK. These updates sometimes introduce stricter checks and more standard-compliant behavior on the host side. As a result, bugs or incompatibilities in plug-ins can become visible - especially in plug-ins that don't fully adhere to the VST3 specification or haven't been thoroughly tested in different hosts.

In many cases, these issues were already present in the plug-in, but older VST SDK versions were simply more tolerant or didn’t expose them.

So it's a normal side effect of keeping the DAW aligned with the VST3 standards, and usually requires plug-in developers to update their products accordingly.
 
I get what you are saying and on paper it might be the correct thing to adhere to strict VST3 standards, but in reality, as a user, I do not care at all about these standards. I need my DAW to be a stable functioning Plugin Host, no matter what junk I throw at it. To me it is a clear marker of a "good" DAW to be able to just make things work. FSP8 in its current state does not appear good to me, especially in comparison to other DAWs (or even previous versions itself) that don't seem to have a problem to make those kind of renegade plugins work. On top of that, FSP has not the status of for instance Protools, that can crash left and right, but just stand there arms crossed and demand all plugin developers to follow their demands.
 
FMN-Music said:
I get what you are saying and on paper it might be the correct thing to adhere to strict VST3 standards, but in reality, as a user, I do not care at all about these standards.
Click to expand...
Sure... I completely understand that perspective.
 
Is it possible to open a session created or saved with FSP in SOP 7.2? Because I need to make rapid progress on several projects, I will probably have to switch back to SOP if FSP is too unstable due to plugins or for other reasons.
 
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.
 
Last edited:
Lukas said:
Studio One/Pro regulary updates the VST SDK. These updates sometimes introduce stricter checks and more standard-compliant behavior on the host side.
Click to expand...

Exactly what I was going to say. S1/SP is VERY good at checking for shortcuts, workarounds and general shoddy programming when it comes to plugins.

Tons of very well known names do this - and just because a plugin worked without issue in a prior version of S1/SP - that does not mean it's in the clear now (or in the future).

And despite some users reservations on not being particularly interested in these standards - I am on the other side of the fence - which is stability.

If I suddenly found out one of my usual plugin vendors were suddenly getting flagged due to a stricter VST SDK checkpoint - that would be the end of that plugin here. Regardless of what it is or who makes it.

There is no such thing as a stable functioning plugin host if that host permits vendors to shirk the rules due to lazy or non-compliant code.

VP
 
Last edited:
Vocalpoint said:
Exactly what I was going to say. S1/SP is VERY good at checking for shortcuts, workarounds and general shoddy programming when it comes to plugins.

Tons of very well known names do this - and just because a plugin worked without issue in a prior version of S1/SP - that does not mean it's in the clear now (or in the future).

And despite some users reservations on not being particularly interested in these standards - I am on the other side of the fence - which is stability.

If I suddenly found out one of my usual plugin vendors were suddenly getting flagged due to a stricter VST SDK checkpoint - that would be the end of that plugin here. Regardless of what it is or who makes it.

There is no such thing as a stable functioning plugin host if that host permits vendors to shirk the rules due to lazy or non-compliant code.

VP
Click to expand...
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. If a plugin works and produces desirable results for years, I honestly do not care at all about vst compliance coding standards.... Also, you mentioned a contradictory argument suggesting that you would eliminate a plugin for not working in a newly updated daw, but not abandon the daw update itself? Aren't they both software products? When a plugin doesn't work anymore in FSP8, it's not compatible. Therefore , as a user, I am forced to abandon the variable that has changed, aka FSP8.
 
You must log in or register to reply here.
Back
Top