List any Plugin Issues with version 8 here

[louieshowers]

As previously suggested, switch to 32 bit precision processing as a temporary workaround. It solved the pulsar echorec issues. I assume it will fix others too.

 

[Arionas]

This 32bit workaround does change the sound quality?

 

[marrybanilow]

Just re-tested with 32bit workaround and sessions that would crash after the plugin list finishes loading are now loading fine. Slate FG-Stress also looks to be working also. I havn't tested for an extended period of time though

 

[Vocalpoint]

I realize everyone is claiming "workaround" here - but I just checked v7.3.2 here and this thing has been on 32 bit (presumably since the beginning of time).

I have never acknowledged this checkbox nor changed it.

And when it comes to "quality" - if anything - 64 bit "could" require more processing but if we were all subjected to a standard blind test - highly unlikely that anyone in this forum would notice anything "audibly" different for any typical production.

Especially me - recording here - as I always have @ 44.1khz and 24 Bit.

If anything (and Studio Pro is doing what it is supposed to do) - all this checkbox is really doing is exposing those plugins that really do not work at 64bit precision anyway.

Also - oddly - this could be the exact reason that I haven't seen a plugin crash in years. That said - have no idea when this "precision" checkbox made its first appearance or why it is set to 64bit as a default in Studio Pro 8.

VP

 

[louieshowers]

I realize everyone is claiming "workaround" here - but I just checked v7.3.2 here and this thing has been on 32 bit (presumably since the beginning of time).

I have never acknowledged this checkbox nor changed it.

And when it comes to "quality" - if anything - 64 bit "could" require more processing but if we were all subjected to a standard blind test - highly unlikely that anyone in this forum would notice anything "audibly" different for any typical production.

Especially me - recording here - as I always have @ 44.1khz and 24 Bit.

If anything (and Studio Pro is doing what it is supposed to do) - all this checkbox is really doing is exposing those plugins that really do not work at 64bit precision anyway.

Also - oddly - this could be the exact reason that I haven't seen a plugin crash in years. That said - have no idea when this "precision" checkbox made its first appearance or why it is set to 64bit as a default in Studio Pro 8.

VP

Evidently, many people are working in 64 bit depth (for many years in my case) and I respectfully reject your claim that this bug is because of the plug-in. Also, I'm wondering how you stating that you have not had a plugin crash in years contributes to this conversation?

As far as the workaround label. This is a workaround, because when switching to 32 bit precision, the instability problem (which is new to version 8) is resolved. I thought the purpose of support threads was to help others navigate issues ? We were provided with a temporary workaround that allows frustrated users a resolution. This was a huge contribution from Lukas. In the meantime, we will wait for this bug fix from Fender before resuming normal functionality.

 

[Vocalpoint]

Evidently, many people are working in 64 bit depth (for many years in my case) and I respectfully reject your claim that this bug is because of the plug-in. Also, I'm wondering how you stating that you have not had a plugin crash in years contributes to this conversation?

Can you please confirm for us that your specific precision switch has been set to 64 bit - since this checkbox was introduced into the system?

The simple fact that we are now getting actual reports of users turning this FROM 64 bit back to 32 bit and suddenly having success - is already telling me that there is a high likely hood that this switch had not been set to 64 bit by default (in prior versions of S1).

Right now - all I have to go on is what I see here as my baseline. IF this checkbox in v7.3.2 - that I have already clearly stated I have never acknowledged the existence of - until this thread - WAS set to 64 bit all this time here - this issue may present differently

But mine is 32bit and has been 32bit for all time - since I never knew of it to change it. And no problems with any plugins whatsoever. Like ever.

Until Fender confirms this setting IS an actual issue - which they have not - what is exactly causing this is unknown.

However if Fender states that there is nothing wrong with this checkbox or Studio Pro's precision processing - you will then have your answer. Plugins are being outed - straight up.

That said - for those plugins where users have already switched back from 64bit to 32bit and those plugins magically start working - it is obvious to me these plugins have already been outed.

Also believe it's highly unlikely that anything will be found wrong with Studio Pros precision processing either. But I guess we need to wait and see.

VP

 

[louieshowers]

Can you please confirm for us that your specific precision switch has been set to 64 bit - since this checkbox was introduced into the system?

The simple fact that we are now getting actual reports of users turning this FROM 64 bit back to 32 bit and suddenly having success - is already telling me that there is a high likely hood that this switch had not been set to 64 bit by default (in prior versions of S1).

Right now - all I have to go on is what I see here as my baseline. IF this checkbox in v7.3.2 - that I have already clearly stated I have never acknowledged the existence of - until this thread - WAS set to 64 bit all this time here - this issue may present differently

But mine is 32bit and has been 32bit for all time - since I never knew of it to change it. And no problems with any plugins whatsoever. Like ever.

Until Fender confirms this setting IS an actual issue - which they have not - what is exactly causing this is unknown.

However if Fender states that there is nothing wrong with this checkbox or Studio Pro's precision processing - you will then have your answer. Plugins are being outed - straight up.

That said - for those plugins where users have already switched back from 64bit to 32bit and those plugins magically start working - it is obvious to me these plugins have already been outed.

Also believe it's highly unlikely that anything will be found wrong with Studio Pros precision processing either. But I guess we need to wait and see.

VP

This feature option toggle to choose between 32 and 64 bit has existed for many years. Since there is the greater potential for calculation errors working in 32 bit, I have always worked in 64 bit. As far as your default setting inquiry, I believe that when updating to version 8, the user preferences carried over to the new update. SO, those who worked in 64 bit like me and others on this thread, have had that setting carry over. For me it is simple. This is a bug. The plugins worked in version 7... same settings, same sessions, suddenly stop working after version 8.0. Is it so far-fetched to to think that a maintenance update is needed after an initial release? Will you concede that it is likely for an initial release? Like you said, time will tell.

 

[Vocalpoint]

This feature option toggle to choose between 32 and 64 bit has existed for many years. Since there is the greater potential for calculation errors working in 32 bit, I have always worked in 64 bit. As far as your default setting inquiry, I believe that when updating to version 8, the user preferences carried over to the new update. SO, those who worked in 64 bit like me and others on this thread, have had that setting carry over. For me it is simple. This is a bug.

Fair enough. If you say you have been at 64 bit for a long while - I am good with it.

And yes - my understanding is that all settings carry over

What is most odd however - is that if Studio One has had these setting for many years - and it has never caused any issues - until now - that can only mean two things:

1. The code that governs the precision settings area - after being stable for (presumably) years - was suddenly altered to become unstable
2. Specific plugins that "advertise" accurate 64 bit precision - are now being outed and actually do not provide what they say they do.

This condition could also be related to (or intertwined with) the changes communicated by Lukas - with the normal cadence of tightening the VST SDK once again in v8

Whatever this is - I do find it curious that all these outlier plugins suddenly "snap to their senses" when Studio Pro is set back to 32bit precision.

The cause will be one or the other - but I am very skeptical on it being #1 above.

VP

 

[Vocalpoint]

I checked, and Fender Studio Pro 8 is set to 32-bits; so I will experiment with switching to 64-bits to see what happens.

Perfect.

My guess - most (if not all) of your "brand" names will be fine.

Some more obscure ones - may suddenly exhibit what others have already reported - unstable etc etc.

Do let us know what you see.

VP

 

[wdkbeats]

This seems to be session-related bug. I'm having issues with a ton of plugins, depending on a session. My mixing projects are quite big, often with heavy plugin count. The crashes in SP8 on my machine are often triggered by Slate VTM, followed by random plugin crashes.

Edit: forgot to mention - the same very heavy mixing projects are working flawlessly in S1 7.2.3.

 

[JamesNorth]

In my case for the plugins that are causing either major crackles or processing delays (latency) it also happens in fresh blank projects in V8 when in 7.X they work fine at 64bit.

So far the 32bit processing has solved any issues I had.

I remember a similar thing a while back - maybe it was going from 6 to 7? The same processing change fixed It - just ran like that for a few months until it was solved.

In all cases previously it was a plugin update that fixed it - nothing in S1 was wrong.

 

[Vocalpoint]

This seems to be session-related bug. I'm having issues with a ton of plugins, depending on a session. My mixing projects are quite big, often with heavy plugin count. The crashes in SP8 on my machine are often triggered by Slate VTM, followed by random plugin crashes.

Edit: forgot to mention - the same very heavy mixing projects are working flawlessly in S1 7.2.3.

Fair enough - but what is your Precision set to? 32 or 64 bits?

The Slate plugins have already appeared on numerous user's lists so far - indicating those products now need some TLC from the vendor.

VP

 

[wdkbeats]

Fair enough - but what is your Precision set to? 32 or 64 bits?

The Slate plugins have already appeared on numerous user's lists so far - indicating those products now need some TLC from the vendor.

VP

I tried every possible Dropout Protection and Process Precision settings. Nothing's changed.

 

[Vocalpoint]

I tried every possible Dropout Protection and Process Precision settings. Nothing's changed.

Not aware of dropout protection being in the equation - but Precision to 32bits is key to get things to settle down.

And even then - if plugins like Slate are now having their shortcomings exposed (see the discussion to an even more stringent VST SDK specifications check in SP8) - there may be little that can be done until Slate corrects whatever issues are being seen in specific plugins.

Remember - just because a plugin appears to be a "big name" doesn't guarantee they know what they are doing when building plugins to exact VST SDK spec.

Many vendors take all sorts of liberties to get their product out there and as long as it appears to "work" in many cases - that is good enough.

AND - many DAWs simply do not have the same scanning benchmarks as Studio One/Pro does either. So you can see a plugin be just fine in one DAW and the same dies during a scan in S1/SP8

VP

 

[Number6]

Ultimately the key takeaway is if your plugin crashes then report this to the plugin vendor first. It's the plugin vendor who can more easily diagnose the issue, they have access to their own plugin source code which will show the symptoms.

They should then either patch their plugin, or log a ticket with Presonus (er sorry Fender) themselves if they believe Studio One (er sorry Studio Pro) is at fault.

It's way harder if not impossible doing it the other way around.

It's more than likely a plugin has a broken dependency, and it needs updating to keep in sync with Studio Pro, but even if this isn't the case, it makes far more sense to report to the vendor first who are in the best situation to troubleshoot.

 

[Timo]

Sonnox Oxford Inflator doesn't work in 64 Bit (Process Precision), digital distortion, sounds like a heavy bit reduction.

PSP Vintage Warmer 2 doesn't work on a bus in 64 Bit, no delay compensation, music timing is off, no processing

Changed to 32 Bit (Process Precision) and both plugins are working as expected.

 

[Timo]

There's a problem with the Stock Pro EQ when using a band in dynamic mode.

When you set the threshold and range, and observe the frequency band dynamically moving up or down depending on the range setting, there will be no audible change with a gain setting of 0.00.

However, as soon as you set the gain to, for example, 0.001 (+ or -), the dynamic movement becomes audible.

In Studio One Pro 7, this is always audible, even with a gain setting of 0.00.

 

[Vangelis]

While Using the L3 Waves plug in on the master track, the latency in recording is increasing incredibly (huge delay between playing of a note on the guitar and the sound).

 

[Vocalpoint]

While Using the L3 Waves plug in on the master track, the latency in recording is increasing incredibly (huge delay between playing of a note on the guitar and the sound).

L3 is usually reserved for mastering. Jamming it into the master bus while tracking is like using iZotope Ozone the same way - tons of overhead in a situation it was never designed for.

VP

 

[louieshowers]

Fair enough. If you say you have been at 64 bit for a long while - I am good with it.

And yes - my understanding is that all settings carry over

What is most odd however - is that if Studio One has had these setting for many years - and it has never caused any issues - until now - that can only mean two things:

1. The code that governs the precision settings area - after being stable for (presumably) years - was suddenly altered to become unstable
2. Specific plugins that "advertise" accurate 64 bit precision - are now being outed and actually do not provide what they say they do.

This condition could also be related to (or intertwined with) the changes communicated by Lukas - with the normal cadence of tightening the VST SDK once again in v8

Whatever this is - I do find it curious that all these outlier plugins suddenly "snap to their senses" when Studio Pro is set back to 32bit precision.

The cause will be one or the other - but I am very skeptical on it being #1 above.

VP

Well well well....look at this. Thoughts? I don't understand why we had this elaborate back and forth about the lack of integrity for plugin developers when it was studio one all along. Do you concede? I'm not trying to be snarky, but in a user support thread, it gets pretty tiring. This was an initial release and judging from the MASSIVE bug fixes, threads like this help people and companies sort stuff out .