P/F SO stability vs plugins

[BobF]

I've been using P/F SO since V2. I've *never* had a plugin problem that turned out to be a problem with SO.

- IKM
- iZotope
- Native Instruments
- Nomad Factory
- Plugin Alliance
- Scaler
- Toontrack
- Waves
- XLN Audio
- PreSonus and Fender

Several hundred in total.

Folks get defensive when reports about plugin problems get responses that focus on the plugin and environment. This is the reason I do.

The reports frequently declare a list of DAWs that don't have problems with a plugin. Fair enough, but consideration should be given to the number of plugins that do NOT have problems. Especially so when other users don't share the same problematic experience.

So apologies in advance if I question a plugin or environment first in response to specific plugin problem reports.

 

[Craig Anderton]

Likewise at this end. Assuming a plug-in issue involves a DAW (not just Studio Pro) when it doesn't diverts attention from fixing the plug-in related problem.

 

[Vocalpoint]

Likewise at this end. Assuming a plug-in issue involves a DAW (not just Studio Pro) when it doesn't diverts attention from fixing the plug-in related problem.

And in my experience - it's not just the obscure players who cause issues. I have had several instances over the years of the "big boys" causing grief as well.

VP

 

[sintil8]

Maybe things are not so cyclic these days, Daw vs Vst ping pong syndrome and it's not our problem, I'm sure folks know that drill.
I've been on that bus myself, it's not a nice experience being bounced around.

@BobF I do not see any need to apologise, it is what it is and such questions often draws others into the conversation. How else can you help folk without checking, are you clairvoyant

Kindest regards.

 

[Craig Anderton]

And in my experience - it's not just the obscure players who cause issues.

Maybe this is why DAWs have blocklists for plug-ins, but plug-ins don't have blocklists for DAWs

 

[Vocalpoint]

Maybe this is why DAWs have blocklists for plug-ins, but plug-ins don't have blocklists for DAWs

The thing that really astounds me is this concept that many have - the "mere existence" theory.

The plugin is there, I bought it and it installs and i see lots of other people using it - therefore - I should be good to go?

And when they are not good to go - they are incredulous when they discover it was the plugin all along.

VP

 

[BobF]

Maybe things are not so cyclic these days, Daw vs Vst ping pong syndrome and it's not our problem, I'm sure folks know that drill.
I've been on that bus myself, it's not a nice experience being bounced around.

@BobF I do not see any need to apologise, it is what it is and such questions often draws others into the conversation. How else can you help folk without checking, are you clairvoyant

Kindest regards.

I'm not trying to keep people from reporting and discussing plugin problems. Just explaining people respond here the way they do.

 

[sintil8]

I'm not trying to keep people from reporting and discussing plugin problems. Just explaining people respond here the way they do.

Never crossed my mind, erm isn't this a user support forum...and folk are here for all sorts of reasons.
I look at it as problems are an opportunity to learn, but I suppose that's just my warped logic.

Kindest regards