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

Solved One day back and around 30 crashes so far.... (EDIT)

OP - Create the simplest session you can with a plugin that consistently causes crashes. Post the details here for potential repros and submit the session with a step-by-step to support. Attach a dump file to your support ticket if possible. Add a list of plugins that FSR crashes with if applicable.

This is the only way to help narrow things down, ultimately finding the source of the problem.

NOTE: My plug menu option was also set to advanced. I have switched to basic to see if I can replicate your reported problem.
 
I see it the same way for the most part, especially in a DAW that doesn't sandbox plugins, like Studio Pro. When this DAW crashes it is impossible for us users to say just from the crash, wether the cause is the plugin or the DAW.

I just can't agree to this:


As an experienced alpha and beta tester you should know that DAWs approach plugin handling very differently. For example, Reaper goes many extra miles to make even the crappiest plugin, with code that doesn't properly follow the plugin protocol, like VST, to work. The same is true for some other developers.
So just because a plugin works in DAW X and Y but not Z, doesn't mean it was coded properly. It only means that DAWs X and Y handle it broader, over the limits of the protocol.

I say that as a plugin developer.

And this is 100% true.

But I also think, that was not, what Lukas was trying to do here.
Yes DAWs handle plugins differently. But it has been my experience that if a plugin is coded poorly (or is in early beta) issues tend to be consistent across DAWs. Just because a DAW crashes with a plugin when others don't it doesn't mean the DAW was coded properly and the plugin wasn't and around we go. Yes there is a lot of slop in the VST spec and sometimes interpretations can vary from developer to developer.

I'll give you an example. Resizing Rob Papen's plugins requires them to be reloaded for the change to take effect (other developer's plugins have dynamic resizing). When changing the size of an RP plugin a dialog box is generated that lets the user know the plugin must be reloaded.

Closing that dialog box instantly crashes FSP here. However in every other DAW I have installed the crash does not occur. So who is to blame? Rob Papen or Fender Studio Pro? If I report the issue to RP they will likely blame FSP and if I report the issue to FSP support they will almost certainly blame the plugin. This battle between DAW and Plugin has raged on since the first day they coexisted and the end user is left in the middle, often frustrated.

As for Lukas' intention he went right to: "You haven't mentioned which plug-ins you're using when these applauses [sic]. Have you temporarily suppressed suspicious plug-ins from a copy of your session to see whether the crashes?"

So it was apparent to me that he was instantly trying to blame (several) plugins without consaidering that FSP might be the cause. Hence my post.

I love FSP very much, it's my main DAW but my point has been that automically blaming muliple plugins may not be addressing an underlying issue that might be within FSP. I'm not saying FSP is definitely at fault I'm just saying that it can't be ruled out.

I want FSP to be as rock solid as possible when running the hundreds of plugins I own so it would be in everyone's best interest to look at the whole picture just not the part that fits the company narrative when chasing down bugs.
 
Arggghhh I've reported this issue before There is something wrong with the forum software. It keeps changing words I have typed into my posts (and I don't think I'm alone). It removes words and letters, it adds words. It's maddeningly annoying.

In the post above "apparent" what changed to "some" and "requires" was changed to "require".

Also spell check stops working after a certain point.
 

Attachments

  • FSP.png
    FSP.png
    7,9 KB · Views: 7
Arggghhh I've reported this issue before There is something wrong with the forum software. It keeps changing words I have typed into my posts (and I don't think I'm alone). It removes words and letters, it adds words. It's maddeningly annoying.
The few times that similar stuff happened on my machines, I found Copilot running stealth in the background. Disable in gpedit.msc or registry, then end task instance in Task Manager and test again.
 
I love FSP very much, it's my main DAW but my point has been that automically blaming muliple plugins may not be addressing an underlying issue that might be within FSP. I'm not saying FSP is definitely at fault I'm just saying that it can't be ruled out.
I only tend to lean more towards the plugin angle for the simple fact that Studio One/Pros VST engine has been running hot now since 2009.

If this DAW was 3 years old - I might be a lot more skeptical. But after 17 years I find it difficult to believe that the DEV team over there would go out of their way to subterfuge their highly tuned plugin engine - just for kicks

That said - given what I have seen lately (say the last 4-6 months) and what I am now sensing is an actual general disturbance in the "force" with FSP - I agreed with you. I am fully able to now admit that there actually might be something wrong internally with the v8 engine.

There have simply been too many instances of odd plugin behavior reported both here and elsewhere on other forums (where it was deathly quiet before) for it to mere co-incidence - especially when compared with Studio One v7.2.3 - which was a model of stability.

I only say this because over here - there are 200 plugins, always have been 200 plugins and are ONLY 200 plugins.

These are the same 200 that I have used for the better part of a half dozen years - and only when I crossed over to FSP v8.x - did any of these stalwarts start acting weird. Now - it doesn't happen often - but when it does - I have never been able to pin down the cause.

This kind of analysis was non-existent in the S1 7.2.3 days and prior....and I have way too many diagnostics logs these days from FSP than I have ever had.

VP
 
Last edited:
Yes DAWs handle plugins differently. But it has been my experience that if a plugin is coded poorly (or is in early beta) issues tend to be consistent across DAWs. Just because a DAW crashes with a plugin when others don't it doesn't mean the DAW was coded properly and the plugin wasn't and around we go. Yes there is a lot of slop in the VST spec and sometimes interpretations can vary from developer to developer.

I'll give you an example. Resizing Rob Papen's plugins requires them to be reloaded for the change to take effect (other developer's plugins have dynamic resizing). When changing the size of an RP plugin a dialog box is generated that lets the user know the plugin must be reloaded.

Closing that dialog box instantly crashes FSP here. However in every other DAW I have installed the crash does not occur. So who is to blame? Rob Papen or Fender Studio Pro? If I report the issue to RP they will likely blame FSP and if I report the issue to FSP support they will almost certainly blame the plugin. This battle between DAW and Plugin has raged on since the first day they coexisted and the end user is left in the middle, often frustrated.

As for Lukas' intention he went right to: "You haven't mentioned which plug-ins you're using when these applauses [sic]. Have you temporarily suppressed suspicious plug-ins from a copy of your session to see whether the crashes?"

So it was apparent to me that he was instantly trying to blame (several) plugins without consaidering that FSP might be the cause. Hence my post.

I love FSP very much, it's my main DAW but my point has been that automically blaming muliple plugins may not be addressing an underlying issue that might be within FSP. I'm not saying FSP is definitely at fault I'm just saying that it can't be ruled out.

I want FSP to be as rock solid as possible when running the hundreds of plugins I own so it would be in everyone's best interest to look at the whole picture just not the part that fits the company narrative when chasing down bugs.
Again, I totally agree with your general statement. Neither ist FSP innocent everytime nor a plugin at fault at all times. I would never argue against that. It has to be inspected on a case-by-case basis.
My point simply was, that seeing a plugin working in other DAWS is not necessarilly proof of proper code, as you put it. Seeing a plugin working in DAW x but not y, only allows us to state, that DAW x and the plugin have a better communication. Wether that's based on proper code or a more forgiving DAW is impossible to say.
You said, "I'm not saying FSP is definitely at fault I'm just saying that it can't be ruled out." and you're absolutely right. Full stop.

That Lukas asks for the plugins is simply context. The op mentioned the crashes in connection with plugins. That doesn't tell wether plugin or DAW is the cause, it is the situation in which the crashes appear and understanding the situation helps narrowing down the cause.

In a real world scenario, when someone breaks their leg and says "I fell 20m", then that is enough to give that person a personal treatment to curate their leg. But when we want to prevent this from happening again, we need to know where and why he fell. Nobody wants to instantly blame the person by asking that. But to understand the circumstances that led to the fall.
 
I believe this could be because of other software or hardware or some third party VST.
It is very unusual to get so many crashes in a day.
 
  • Like
Reactions: AAV
I believe this could be because of other software or hardware or some third party VST.
It is very unusual to get so many crashes in a day.

That was my reaction too. So many crashes is more than likely down to a specific combination of components, and the only way to identify the culprit is by removing components until stability returns. That doesn’t mean directly that either FSP or a specific plugin is faulty; just that that combination is a problem for some reason. Once the offending combination is identified, then the devs (at both/all implicated companies) have something to work on.

It’s worth considering that the problem may be caused by another program that isn’t directly in the FSP-plugin chain.
 
  • Like
Reactions: AAV
Please excuse my edits to your post, I'm hoping you might be able to clarify what is going on...
The last 24 hours has been pathetic. I can't freeze a track and get back to the midi unless I keep the instrument active now? Complete lockup if I do that. I'm saving before loading any plugin now because it feels like Russian roulette otherwise. Crash after crash.

Cheers
When you say "Keep the instrument active", are you referring to freeze options dialogue in the image below?

Screenshot 2026-11-16 095336.png


I am trying to reproduce what you describe and thought it might be worth unpacking some of the issues you highlighted.
I am not getting crashes and maybe I am not following what you are doing to cause the prog to crash.
I am on windows so this may be something specific to Mac computers.

Can you help and break the issue down into steps to reproduce please?

Kindest regards
 
Thanks for the comments. Regarding the freeze problem, I haven't yet revisited that, but I had a problem with preserving the unfrozen instrument state if I removed it. (i.e. All the boxes checked in the options). I couldn't get the unfrozen instrument back to midi like I always used to be able to. I will re-check that.

Regarding the plugin issues.. I have posted earlier in this thread that I've found the problem. It has nothing to do with any particular plugin as far as I can tell. The solution was to switch the plugin menu preference from "Basic" to "Advanced" - and that solved it 100%. Every plugin selected now loads and behaves perfectly in "Advanced" menu mode. In "Basic" menu mode every plugin crashes out the program instantly upon selection.

Preferences - Advanced - Console - Plug-In Menu

So for me, just that one alteration to the preferences has solved it 100%, and overall the program is now rock solid. 12 hour session yesterday with plugins everywhere without any crashes, thankfully.

Perhaps it's just a Mac thing. Perhaps it's a Studio Pro 8 thing. Perhaps neither. Maybe it's just me... But I've used Studio One since version 4, and never had to use the advanced menu option because I've always sorted my plugins into categories - the folder view (which is the "basic" mode for the plugin menu, and quicker for me...)

I don't know anything about code, but it's an easy problem to reproduce if it is not just my setup, right?
 
Regarding the plugin issues.. I have posted earlier in this thread that I've found the problem. It has nothing to do with any particular plugin as far as I can tell. The solution was to switch the plugin menu preference from "Basic" to "Advanced" - and that solved it 100%.
Can I ask exactly what "basic" would do - or why anyone would need to make that choice?

Until this specific thread - I was not even aware of this setting - let alone changing it.

VP
 
Perhaps it's just a Mac thing. Perhaps it's a Studio Pro 8 thing.
I can only say that i tested this with a bizzare random chain auf over 30 plugins and got no Crash.
Windows Version, latest Studio Pro release.
 
Please excuse my edits to your post, I'm hoping you might be able to clarify what is going on...

When you say "Keep the instrument active", are you referring to freeze options dialogue in the image below?

View attachment 4285

I am trying to reproduce what you describe and thought it might be worth unpacking some of the issues you highlighted.
I am not getting crashes and maybe I am not following what you are doing to cause the prog to crash.
I am on windows so this may be something specific to Mac computers.

Can you help and break the issue down into steps to reproduce please?

Kindest regards
Thanks for the help. I've just managed to get an instrument back from the frozen state, with all boxes checked on freeze, so it would seem to be OK now. I think my system was in turmoil with all the crashing out maybe... I will repost if I get any more info. or if it starts doing it again. Fingers crossed.. cheers
Can I ask exactly what "basic" would do - or why anyone would need to make that choice?

Until this specific thread - I was not even aware of this setting - let alone changing it.

VP
It just means that the plugin menu just shows the folders you have customised in the browser... So you can categorize, like "Reverb", "Dynamics", etc across all vendors and disregard the embedded plugin 'type'... when you have hundreds of plugins, it helps, and presents submenus over mouse hover instead of folders - it's quicker, thats all
 
@redgazza
cool let's hope you are good to go and that things work as you had hoped.

Just in passing I had always assumed that the second tick box "Remove Instrument" was a guillotine. If that box was active there was no way to retrieve the instrument. I will need to check, sometimes assumptions are way off.

It might be cool to mark the thread resolved if you are happy.

Kindest regards
 
@redgazza
cool let's hope you are good to go and that things work as you had hoped.

Just in passing I had always assumed that the second tick box "Remove Instrument" was a guillotine. If that box was active there was no way to retrieve the instrument. I will need to check, sometimes assumptions are way off.

It might be cool to mark the thread resolved if you are happy.

Kindest regards
It just removes the instrument from the session, but as long as the "preserve instrument track state" is also checked, it will come back. I successfully did a freeze earlier with some drum tracks, and they unfroze fine, back to the instruments, but then it created a load of empty FX channels that were being sent to by the instruments... weird. Never used to behave like that.. But it's easy enough to delete those. I think the new "freeze FX channels" function might be complicating a few things.... the drum tracks were sending to other FX before being frozen.. oh well.
Yep, I'll mark as resolved, thanks... once I find out how to do that. As long as it's not crashing, I'm good. Cheers
 
Back
Top