Fender Studio Pro 8 Released

[thievedletter]

First is whacking it

Wouldn't that make the second step, "Having A Nap"?

[CapnLockheed]

Hey, BONES just wants to help!

Yeah, never a discouraging word from Mr. Bones......LOL!!

Have you tried restarting your computer?

I surely hope you're being sarcastic. The alternative isn't very flattering.

Maybe the problem is that your equipment is from the last century?

HAHAHA. If that were the case I wouldn't be able to run Fender Pro Studio at all smart@ss.

This thread is Soooooooooooooo KVR.

[Grizzellda]

He's also clearly using macOS and SPro v8, so if it works for him it should work for you, shouldn't it? Or a really good reason to change operating systems. Everything on Windows works perfectly, as it always has.

I don't understand what would make you think I'm on a macOS. I have never used any Apple software or hardware. I'm on Windows too. And everything works perfectly, as it always has....EXCEPT for Fender Studio Pro V8.01.

You think I'm angry? No, just a bit frustrated but not terribly surprised. My OP regarding this issue was simply to report a bug which, btw, was confirmed by a Fender mod. All I got was a bunch of snarky condescending, accusatory responses and a few potentially risky solutions. None of which I needed because, as I stated in that first post, Fender Studio Pro is not my main DAW. I was just trying report an issue which does not occur in earlier version of Studio One. All I got was a big bag of crap. Typical KVR.

@EnGee....my sincere apologies for getting your post count wrong. As to the rest of you lot, not so much. This thread was already entirely de-railed and off topic. Please feel free to get back to your deep metaphysical musings......I'm out.

I would not say the thread has derailed, we should keep on sharing experiences with any DAW, and talk about issues.

As for "deep metaphysical musings" ...I'm sure I could find something in the Urantia Book that would encourage you to calm down,...and chill out!

When I get going on a new machine with a 4k screen, I will surely report my findings here, to contribute, how it looks and performs of course. I feel that Fender Is gonna do cool things with this DAW. We will see.

[Fornicras]

If we get back to the topic:

Version 8.0.2 is out with a bunch of bug fixes:

Version 8.0.2 Release Notes (March 3, 2026):​

New features and improvements:
[Extract Notes] Dialog is now keyboard accessible
[Linux] Updated Stem Separation
[Presence] Editor design refresh
[Toolbar] Refined order of hidden elements when resizing screen
Offline Activation Guide added to installer
Improved plug-in ordering after search
Inspector menu height is now consistent

The following issues have been fixed:
[Acoustic Piano] Full fine tune is momentary
[ATOM SQ] Bank buttons are off when in editor mode using Impact
[ATOM] Black box appears at the top of Control Link area using ATOM controller knobs
[Browser] Potential freeze when attempting to split a large multichannel file
[Channel Overview] Truncated parameter is added when dragged from Control Link panel
[CLAP] Plug-in doesn't show its multi-outs
[Fat Channel] DSP buttons require double-click to open
[Mai Tai] Cutoff knob looks blurry
[Mai Tai, Presence] LFO key-scaling disabled state inverted
[Mixtool] Channel Overview shows stereo invert on mono channel
[Mixtool] Phase Invert button icon is not centered
[Mixtool] Tooltip for Phase Invert claims "Flip Channel"
[Mojito] Incorrect tooltip for Sub knob
[Mustang Native] Switching presets in a certain order creates invalid data
[Open AIR] Empty image tab still referencing Studio One logo
[Pattern Editor] Unable to edit C-2
[Pro EQ³] 12th octave spectrum analyzer issue
[Pro EQ³] Macro Controls are not working
[Pro EQ³] Volume slightly boosted in HQ mode
[Pro EQ³] Wrong automation rendering when using Freeze
[Score Editor] "Select All" shortcuts reversed
[Score Editor] First dynamic marking missing after copying tracks
[Score Editor] Layout breaks after copying exported tracks
[Show Page] Chord track scrolling is not smooth
[Show Page] Dragging setlist item to end of show causes sticky UI and redraw issues
[Show Page] Incorrect tooltip displayed for "Display" dropdown in Chord Track header
[Show Page] Undo removes Arrangement parts instead of the last added session
[Show Page] Video player disappears in Performance mode
[Vocoder] Follow & Release knobs are not centered
[Windows] Text box shows artifacts when editing in certain scale factors
Articulation playback sets document dirty flag
Auto Zoom and Autoscroll pulldown menus are too large
Automation baseline shifts based on first automation point
Channel Strip missing in Inspector for all tracks
Chord doesn't audition when applied from recommendations
Chord suggestion not showing when clicking the arrow on the first chord in the session
Duplicate channel fader in Inspector for video tracks
"Extend Left/Right" macro isn't applied to the event selected after duplication
"Extract Notes" mutes all tracks after un-solo when used on soloed track
Fade out on looped Tonalic introduces clicks on loop joints
Focus remains in ARA editor after clicking Session Page
Freezing a subfolder places the resulting track outside its folder
Frozen looped instrument part is incorrect on return trip
Full plug-in scan forced when changing time zones
Importing certain MP3 files may create empty space at the end of the event
Inconsistent scale display for pitch bend
Incorrect key signature detection in certain cases
Inserting silence less than a bar at the beginning of a session inserts a new time signature
Inspector velocity no longer allows negative values
It is not possible to remove the key from the session
Key command CTRL+ALT+SHIFT not working for certain plug-ins
Moving Events from Scratchpad to main Arrangement causes freeze
Offline Activation button is hidden when using certain language settings
Paste after dangling slur confuses note order
Popup menus are not consistent
Potential crash when drawing a shape in the Tempo Editor
Recorded takes are not placed correctly on layers
Recording preview appears in wrong pattern while recording to different track
Score shows individual tempos for imported tempo ramps
"Show channel editor" macro command does not work when state=0
Sound Variation field disappears when Note Editor is detached
Square UI glitch appears when clicking channels in Mixer
Sustain CC messages continue to affect playback after moving playhead to an area without Instrument Parts
Tap Tempo during playback resets audio position instead of following timeline
Tempo drops below minimum limit after changing time signature
Tempo track trim handle doesn't change the parameter
Timing of exports from Notion are incorrect
Two cursors appear when recording with cursor mode set to centered and Auto Zoom on full
Undo replacing instrument does not restore previous auto-generated track name
Waveform is not drawn at all zoom levels in certain sessions

[Grizzellda]

Wow, you are tuned in it seem's, to the evolution of this app! Keep us informed!

Sure, I wanna keep current with FSP!

Also, BONES likely should too!!!

[BONES]

Yeah, I installed it earlier and it forced a reinstall of my audio I/O driver for some reason. There's nothing in it that will affect me but it's good to see them fixing bugs.

[osiris]

I haven't tried this but somebody was impressed enough with the stock reverb to do an entire YT vid on it.

[BONES]

The new one? Yeah, it is pretty impressive but who doesn't already have half-a-dozen impressive reverb plugins? And most of my newer plugins have their own impressive reverbs, so I hardly ever need a standalone one anyway. I mostly use Adam Szabo's Solaris or Valhalla's SuperMassive and they were both free, which is my preferred price for effects.

[Resonant- Serpent]

Fender is definitely faster on the draw when it comes to updates compared to Cubase. Cubase v15 is the buggiest software release I've seen from anyone in quite a while. Back on Studio Pro for a few days now, and have yet to hit one glitch. Hooking the ATOM back up made it feel like an old friend.

[Igro]

Fender is definitely faster on the draw when it comes to updates compared to Cubase. Cubase v15 is the buggiest software release I've seen from anyone in quite a while. Back on Studio Pro for a few days now, and have yet to hit one glitch. Hooking the ATOM back up made it feel like an old friend.

Totally agree with you on Cubase. I feel it's slowly dying with those new developers applying new stuff on top without updating the base. Everything seems old in this DAW.

[stanft]

[..] I feel it's slowly dying with those new developers applying new stuff on top without updating the base [..]

Ah cool. You have insights? Or is this just a random guess?!

[Igro]

[..] I feel it's slowly dying with those new developers applying new stuff on top without updating the base [..]

Ah cool. You have insights? Or is this just a random guess?!

Sure. Search my posts here and on Steinberg forum. Check their latest post about Cubase CPUs handling, the audio engine problems and so on.

[teilo]

Just installed 8.0.2, upgrading from 7.2. The CLAP crashes and UI problem are gone. Previously, some UIs didn't show correctly, and certain CLAP plugins would crash S1 the moment they opened, notably Surge XT. I think the crash was related to multi-outs.

[BONES]

I've never had either of those problems, my crashes always occur when I'm closing a project, which is something they seem either unwilling or unable to do anything about.

[lfm]

[..] I feel it's slowly dying with those new developers applying new stuff on top without updating the base [..]

Ah cool. You have insights? Or is this just a random guess?!

Sure. Search my posts here and on Steinberg forum. Check their latest post about Cubase CPUs handling, the audio engine problems and so on.

Already Cubase in 2015 were having problems navigating their own project files.
- I found a workaround for that one, in my case doing track templates
- but it showed differently for people having archived/disabled tracks that was not easy to fix
- not fixed as Cubase 10 came 2019, so I stopped at 9.5

But when at 2s past every up-hour of Windows I had some event that restarted the entire audio engine on Cubase Pro.
- 7 threads restarted and if recording then it would abort that recording
- so having to look for up-hours when starting recording
- but even Cubase Elements just gave a small "pop" as did StudioOne, Sonar, Reaper etc

Cubase is a patchwork so agree fully they just stack things on top. I did not trust it in the end.