Fender Studio Pro 8.1 - Discussion Thread

[Davey]

It's early days with Scaler 3.3 but I have had no crashes with it in FSP yet and earlier versions of Scaler 3 were OK for me too.
The one thing I never do with Scaler is host VSTs inside it. I just use the built-in instruments for roughing stuff out then route the MIDI to FSP tracks for the "proper" version.

In the early days of Scaler 3 there were loads of crash reports across all sorts of platforms and many of those reports seemed to be where folks had been very ambitious with using VSTs inside it. In one case a guy had about 30 plugins (instruments and fx) running inside Scaler 3 which itself was running as a plugin. Of course, it should cope with that or fail more gracefully but it did seem like tempting fate!

 

[Vocalpoint]

It's early days with Scaler 3.3 but I have had no crashes with it in FSP yet and earlier versions of Scaler 3 were OK for me too.
The one thing I never do with Scaler is host VSTs inside it. I just use the built-in instruments for roughing stuff out then route the MIDI to FSP tracks for the "proper" version.

Agreed. Nothing odd here but then again - I haven't really given it a hard workout yet.

I am monitoring the official Scaler forums as well - so far no sign of any reports from any Studio One/Studio Pro users.

VP

 

[OneBass]

The Scaler crew would be interested to hear more on this.

Are you saying Studio Pro crashes - after you walked away - and I assume the app was idle - and out of the blue - Scaler v3.3 caused it to crash? T

That seems a tad odd - if no one doing anything on the machine at the time of crash.

Can you share anymore detail?

VP

Yes, FSP has crashed at least twice when I was away from the computer. Both times FSP itself was idle, that is, nothing was being looped, exported, etc. And here is an interesting point; in both crashes Scaler was not "active" in my project. Meaning I had not created a Scaler instrument nor had Scaler on any track or explicitly having used it in any way. The crashes were sporadic, spaced apart in time, did not cause Windows to crash or restart and I have no knowledge in how to intentionally reproduce the crash.

 

[Vocalpoint]

Yes, FSP has crashed at least twice when I was away from the computer. Both times FSP itself was idle, that is, nothing was being looped, exported, etc. And here is an interesting point; in both crashes Scaler was not "active" in my project. Meaning I had not created a Scaler instrument nor had Scaler on any track or explicitly having used it in any way. The crashes were sporadic, spaced apart in time, did not cause Windows to crash or restart and I have no knowledge in how to intentionally reproduce the crash.

Can you post a screen cap from Event Viewer that shows the entire crash sequence, file listing, timestamps etc.

VP

 

[Kisnou]

Hopefully Lukas will read this.
Since a few months ago, any combination of Alt + Key (like ALT+F) now triggers actions in the context menu instead of the actual studio one shortcut. I believe a Windows update has changed the Alt key behaviour.
Now all my shortcuts which include Alt will trigger context menu actions (if the key that is combined with Alt is a letter that corresponds to a tab of the context menu).
To give an example: Alt+T which was my Transform Range shortcut now opens the Track tab in the context menu; Alt+F which was my Snap Enable/Disable now triggers the File tab in the context menu; Alt+S which was my Strip Silence shortcut, now opens the Session tab in the context menu; the list goes on).
I believe this will involve more and more users as the updates roll out to more people. As far as I am aware, Reapear has a setting to block exactly this from happening (disables the alt key from moving the selection to the context menu).

Combinations of keys like Alt+Shift still work (magnifying glass), but if you pay attention to the context menu, you'll see the selection/focus moves to it. So if you press F after using Alt+Shift, you will open the File Tab because the focus has moved there anyways.

Try it out yourself. My Windows version is 25H2 (Build 26200.8894).

 

[Vocalpoint]

FWW: I am on Windows 10 (not for long now but all my ALT commands work just fine. And I have at least 20.

VP

 

[freddiphin]

Agreed. Nothing odd here but then again - I haven't really given it a hard workout yet.

I am monitoring the official Scaler forums as well - so far no sign of any reports from any Studio One/Studio Pro users.

VP

There are from slightly earlier in v.3:

Scaler 3.2.1 Fender Studio Pro 8

I did a clean re-install of Scaler 3.2.1. Now it seems to crash both Fender Studio Pro 8.0.2 and Studio One 7.2.3 every time I try to add Scaler as a plugin to a new project or open a project which includes Scaler as a plugin. I also tried it with Cakewalk Sonar and it works fine, no crashes...

forum.scalermusic.com

Scaler 3 keeps crashing Fender Studio One

What happens is I make a song in FSO, Scaler 3 is on a track. Then when I go to open that song later, it crashes and says that it failed to open and gives the reason, “Created Device: Scaler 3” I have rescanned plug ins, no help It either crashes with that message or freezes when I try to open...

forum.scalermusic.com

Issues with Scaler 3.1.2 VST3 (or VST2?) and Studio One

Hi, when loading a Studio One Pro 7 song (project), S1 crashes and restarts. Upon restarting I got the following message in Studio One: “The following actions could not be completed: create device: scaler 3” I checked, no dump files were created for this crash for whatever reason. All I...

forum.scalermusic.com

But perhaps you meant 3.3 specifically

I am definitely having (random and not dependably replicable) issues and also with Ableton, so perhaps it's something in my system.

 

[Vocalpoint]

Yes - I was referring to "early" days for v3.3. Even I had issues with previous iterations of v3 - dating back to 3.1 and earlier.

What the Scaler devs are doing over there - is bizarre considering I have seen Studio One in use in some of their previous v2 vids.

I am on v3.3 now and won;t be going back - but if there were early issues - I would expect them to start showing any day now.

VP

 

[freddiphin]

Yes - I was referring to "early" days for v3.3. Even I had issues with previous iterations of v3 - dating back to 3.1 and earlier.

What the Scaler devs are doing over there - is bizarre considering I have seen Studio One in use in some of their previous v2 vids.

I am on v3.3 now and won;t be going back - but if there were early issues - I would expect them to start showing any day now.

VP

Bizarre is right. I don't really get trying to turn Scaler into a full multi-track DAW style app. It is only the scale/harmony functions that I personally use as a tool. Certainly not as an instrument or platform on its own. And given this comparitively light use of it by me I find it even more odd that it has issues. I found v.2 totally unproblematic and ended up paying for the upgrade to 3 for more stuff that I don't use and more problems. BUT, that is my problem, mostly. It "feels" like not an FSP issue

 

[Vocalpoint]

It "feels" like not an FSP issue

It definitely is not - whatever is going on over there - is on them

And I agree on the design choices for v3. If I want a Scaler DAW I would have asked for one.

I too would never host instruments or mess around like I see in their videos. It's almost as if these guys are trying to convince us NOT to use a DAW.

But most of this "multi-track" nonsense has no utility in the real world. I would never be loading up Scaler with a bunch of VSTs - only to mute them all down and add them all again to the actual tracks I intend to use/keep within Studio Pro.

VP

 

[Kisnou]

FWW: I am on Windows 10 (not for long now but all my ALT commands work just fine. And I have at least 20.

VP

Well, that's great, but I'm sure the majority of people out there have windows 11. What is Fender/Presonus going to do about this issue?

 

[Vocalpoint]

Well, that's great, but I'm sure the majority of people out there have windows 11. What is Fender/Presonus going to do about this issue?

Might be a good idea to see if anyone else can concur with your observations first.

Can't imagine that only you would suddenly be experiencing this.

And it appears you have an optional (out of band) update installed as well - the current standard Windows 11 25H2 Production build for July 2026 is:

Build 8894 is only required if you are running one of 14 very specific Dell branded laptops - which had issues:

"This update addresses an issue affecting a limited number of devices with an Intel Innovation Platform Framework (Intel IPF) driver that could cause changes in performance, power consumption, or system behavior after installing recent Windows updates. A limited number of Dell devices that were temporarily prevented from receiving the July 2026 security update KB5101650 can now install this OOB update. This OOB update is only recommended for devices affected by this issue. If your device is not affected, no action is required."

VP

 

[Kisnou]

Might be a good idea to see if anyone else can concur with your observations first.

Can't imagine that only you would suddenly be experiencing this.

And it appears you have an optional (out of band) update installed as well - the current standard Windows 11 25H2 Production build for July 2026 is:

View attachment 3775

Build 8894 is only required if you are running one of 14 very specific Dell branded laptops - which had issues:

"This update addresses an issue affecting a limited number of devices with an Intel Innovation Platform Framework (Intel IPF) driver that could cause changes in performance, power consumption, or system behavior after installing recent Windows updates. A limited number of Dell devices that were temporarily prevented from receiving the July 2026 security update KB5101650 can now install this OOB update. This OOB update is only recommended for devices affected by this issue. If your device is not affected, no action is required."

VP

I installed an optional update trying to see if it would fix the issue, that's why.. It didn't. Other friends in Win11 have the same issue right now, I reported it to support and also to Lukas, but I also did a deep research into this, not even Claude/Chatgpt can help me, it seems like it's a Windows problem

 

[Vocalpoint]

I installed an optional update trying to see if it would fix the issue, that's why.. It didn't. Other friends in Win11 have the same issue right now, I reported it to support and also to Lukas, but I also did a deep research into this, not even Claude/Chatgpt can help me, it seems like it's a Windows problem

Fair enough.

Just seems reasonable that somebody - anybody - in here - would notice this. Pretty sure there are hundreds of Win 11 users in here.

v8.1.1 has been in the wild for a week now

VP

 

[freddiphin]

It definitely is not - whatever is going on over there - is on them

And I agree on the design choices for v3. If I want a Scaler DAW I would have asked for one.

I too would never host instruments or mess around like I see in their videos. It's almost as if these guys are trying to convince us NOT to use a DAW.

But most of this "multi-track" nonsense has no utility in the real world. I would never be loading up Scaler with a bunch of VSTs - only to mute them all down and add them all again to the actual tracks I intend to use/keep within Studio Pro.

VP

Amen to all of that!

 

[Kisnou]

Fair enough.

Just seems reasonable that somebody - anybody - in here - would notice this. Pretty sure there are hundreds of Win 11 users in here.

v8.1.1 has been in the wild for a week now

VP

To be honest I didn't notice at first, I thought I was misclicking something.. I started having this issue a few months ago, then I thought it was an isolated problem on my pc, did some research in the last couple of days and just now I decided to report it. I'm guessing some of the latest Win11 updates introduced this as an accessibility feature. If there's anybody out there on a Win11 pc please share your experience regarding this matter, thank you.