• 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!

Fender Studio Pro 8.0.2 - Discussion Thread

The plugin delay compensation while using sidechains into busses simply doesn't work and the whole chain is going out of sync. It's reported and confirmed by the support, but I would assume to see a high priority on such an issue. A correspondig thread can be found here. PDC is an absolute crucial aspect in the signal chain.

In reality - something only ever becomes a high priority if a VERY large swath of the total user base actually uses said function ("sidechains into busses".)

I myself do not. Probably many others do not either.

While I totally understand that this is an issue for you - that alone does not make it a priority in any way.

VP
 
^

Well I use it, and perhaps more users than you think. So I'd like to see that as high priority, so I guess that's at least one extra person. Sidechain is of course one of the most important features of recording and professional recording after all, but yeah, being able to press record may be slightly more important.

Perhaps we should settle this out in a gladiator arena and then the Devs can make this decision based on which one user shouts the loudest.

p.s. I'm Sparticus and so is my wife.
 
While I totally understand that this is an issue for you - that alone does not make it a priority in any way.
The aspect that the compensation of plugin delays (latency) is not fully consistent is an issue in my opinion and not a minor one. But you are right that's just my very, very personal opinion, no need to agree with that.
Some real world examples: gating, ducking, sidechain compression, selective frequency ducking like sidechaining a bass with the bassdrum and a lot more applications. If you do it from a track to a bus than you might have a problem. Of course there are workarounds if you know what you shouldn't do in V8.

Beside this, a lot of things got fixed which is great and the timeframe of the release intervals is fast. 😃
 
Not seeing that behavior anywhere here. And I do not even use a graphics card.

FWIW: Did not see this behavior in any of the two prior versions either.

And no mention of any fixes in the Release Notes.

Not exactly certain this is a bug or more of an environmental issue on your DAW - specifically.

VP
No, it’s not related to my setup. I see this bug in all the YouTube reviews I’ve watched about FPS8. When a plugin is added or opened from the channel view, it opens instantly. But when it’s opened from the mixer or the inspector, there’s a delay - and this happens with absolutely all plugins.
 
When a plugin is added or opened from the channel view, it opens instantly. But when it’s opened from the mixer or the inspector, there’s a delay - and this happens with absolutely all plugins.
Just tested this - on both the mixer and Inspector from 3 client sessions this morning - literally as fast as I can click the plugin tile in a mixer channel and again in the Inspector- the plugin appears instantly. I tested a variety of plugs from Fender, Waves, u-He, Spectrasonics, Komplete Kontrol etc...

No delay, no gaps, no freezes. Trust me - if this did happen here - I would notice.

See my signature for gear and OS in play. Would be good if you filled out your signature as well.

VP
 
The aspect that the compensation of plugin delays (latency) is not fully consistent is an issue in my opinion and not a minor one. But you are right that's just my very, very personal opinion, no need to agree with that.

Well - delay compensation can be a complicated scenario and has a lot to do with the plugins in play - your hardware and especially your audio interface.

You did not list any of your gear so I have no idea what you are working with. Until we can get a bead on your hardware - this is hard to troubleshoot.

VP
 
Well - delay compensation can be a complicated scenario and has a lot to do with the plugins in play - your hardware and especially your audio interface.

You did not list any of your gear so I have no idea what you are working with. Until we can get a bead on your hardware - this is hard to troubleshoot.
No sorry, this is has absolutely nothing to do with a system setup or audio interfaces.
And there is no need of troubleshooting my setup, I have the confirmation from the support that it exists and can be reproduced on their side. I have a simple test with only 2 internal SPro plugins which, of course, I've sent to the support. :) the support is great, fast and friendly as always.
I was only a bit sad, that it couldn't be solved in the first two updates and I would love to work with V8. Maybe I've sounded a bit rude and I'm sorry if this was the case. But as I've written earlier, in my very personal opinion, it's a crucial part of audio production.
 
And there is no need of troubleshooting my setup, I have the confirmation from the support that it exists and can be reproduced on their side.

Fair enough.

Hopefully this gets addressed at some point.

VP
 
No, it’s not related to my setup. I see this bug in all the YouTube reviews I’ve watched about FPS8. When a plugin is added or opened from the channel view, it opens instantly. But when it’s opened from the mixer or the inspector, there’s a delay - and this happens with absolutely all plugins.
I just tested this myself and while it isn't 0ms instant it's only a few ms to open with a mouse click from any location. What I will say is I think people thought it was bugged after they changed from double click to single click opening. I complained about this myself at the time because it felt like they left the opening times and only changed the click vs double click round so that single click was delayed to the speed of a double click.

They must of listened because it's almost instant now within a few ms when I just tested it with 8.0.2. Seems fine to me.
 
More than enough people complained and provided information about PDC over the years from the old forum etc. In 2015 S1 V3 didn't just have close synced side chain communication across channels, it was perfectly in sync every single time. Unlike other DAW's were you had to at least change attack and release times to get a more coherent groove interaction. The very same perfect sync midi out to midi in also had. Any cross track or channel interaction had perfect PDC and then for what ever reason it never worked the same again and still doesn't. Around the time Drop out Protection was added is when it happened. Since then it's kinda worked and kinda hasn't worked over various versions.


James Wiltshire from the Freemasons F9 audio did a promo video of his favourite feature from his favourite DAW's about the very subject of how Studio One's perfectly synced side chains were at the time. No other DAW could do it and every other DAW company needs to take note. His very words at the time and one of the reasons I switched from years of Cubase clunkety clunk to Studio One V3. Even Steve Duda told them in 2015 your PDC is borked. The posts still on the Xfer forums.

As much as this looks like I am complaining I'm not. I'm simply telling you what others have already mentioned and some back story of how I got on the S1 train. I use S1 still today but V6. I have the latest Fender ofc but I have never been so turned off by a DAW as this one is atm. Hopefully I get back on the love train with it because I enjoy using it. Slipping and sliding tracks under and over is normal practice for me so that bit I don't care about, it's the real time playback of out of sync tracks via PDC that's the issue.

I'm not saying I have golden ears but I am willing to bet a lot of people never even noticed because in most cases the PDC for plugins is a couple of ms to zero. Obviously it would be nice to see it work like it used to but here we are in 2026.

Once upon a time you could only ever get a side chain or ducking in most DAW's to react in sync by adjustting attack and release times via both channels. It was a constant back and forth making changes etc. S1 V3 was always perfectly in sync every single time with internal and third party plugins so attack and release times became nothing more than shaping tools reacting on the perfect sync of the side chain. No other DAW was capable of this at the time. I wish they would go back to that.
 
Last edited:
More than one person can now reproduce this bug:
 
They must of listened because it's almost instant now within a few ms when I just tested it with 8.0.2. Seems fine to me.

This is like "within a few ns" for me. The plugin appears instantly.

VP
 
No, it’s not related to my setup. I see this bug in all the YouTube reviews I’ve watched about FPS8. When a plugin is added or opened from the channel view, it opens instantly. But when it’s opened from the mixer or the inspector, there’s a delay - and this happens with absolutely all plugins.

For me, creating an instrument track and clicking on the plugin on that track, the first time it takes a second or two for me depending on how resource heavy the plugin is. Then it gets cached into memory, and when I try to open again using the same method it's nearly instant.

"But when it’s opened from the mixer or the inspector, there’s a delay"

Trying this afterwards... yup there is a delay of about a second compared to opening it on the track. The difference is quite noticeable although it's hardly a workflow killer.
 
Not for me. Plugins open instantly from mixer or main arrange page for me in FPS8. Even big ones that are resource heavy. I love the single click too. You have got to get used to it though at first.
 
I love the single click too. You have got to get used to it though at first.
Would like to have the option to change it. It's anoying and against/oposite the logical way to open something.
 
For me, creating an instrument track and clicking on the plugin on that track, the first time it takes a second or two for me depending on how resource heavy the plugin is. Then it gets cached into memory, and when I try to open again using the same method it's nearly instant.

"But when it’s opened from the mixer or the inspector, there’s a delay"

Trying this afterwards... yup there is a delay of about a second compared to opening it on the track. The difference is quite noticeable although it's hardly a workflow killer.
So it's a bug, and they haven't fixed it. For me, it's critical. I work quickly and very often doubleclick because I think the plugin didn't open.
 
So it's a bug, and they haven't fixed it. For me, it's critical. I work quickly and very often doubleclick because I think the plugin didn't open.

Well I don't know, if it's always been like this then it's a feature request.
If it hasn't, it could be labelled as a performance bug (up to the devs).
But then apparently some people can't reproduce (but I can).
Can you please update your signature with your spec's in order to make easier comparisons (it appears those who can't can't repro aren't on Windows 11 for instance, not that this is a smoking gun), and I suggest you create a ticket with support.
 
Just tested this - on both the mixer and Inspector from 3 client sessions this morning - literally as fast as I can click the plugin tile in a mixer channel and again in the Inspector- the plugin appears instantly. I tested a variety of plugs from Fender, Waves, u-He, Spectrasonics, Komplete Kontrol etc...

No delay, no gaps, no freezes. Trust me - if this did happen here - I would notice.

See my signature for gear and OS in play. Would be good if you filled out your signature as well.

VP
In this thread also already confirmed this bug. It's just that with my workflow, it's very noticeable, and this made me give up on the 8.
 
Well I don't know, if it's always been like this then it's a feature request.
If it hasn't, it could be labelled as a performance bug (up to the devs).
But then apparently some people can't reproduce (but I can).
Can you please update your signature with your spec's in order to make easier comparisons (it appears those who can't can't repro aren't on Windows 11 for instance, not that this is a smoking gun), and I suggest you create a ticket with support.
Updated! It seems that it really isn't the case for everyone, but as I wrote above - I saw this in FSP8 reviews on YouTube and was very surprised. At the same time, everything opens as it should through the channel overview, so it doesn't seem to be an issue with the plugins or the system.
 
Back
Top