I beta tested for SONAR, Waves and NI (Maschine) - all great communities
-
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.1 - Discussion Thread
- Thread starter Lukas
- Start date
Hi, I'm sorry but this update is the least stable I've had since Studio One 5, constant visual glitches, crashes, the most amount of cpu spikes I've had with my M1 pro with projects that V7 handled more than fine. I hope the bug fixing and optimisation patch comes back really soon or I'll migrate to reaper...
We all have to do what's best for our own situations. FSP8 is running well for me, a lightweight low-ish track count user.
Reaper is an awesome DAW with excellent performance. I personally have an allergic reaction to the UI and have never found a theme that was both visually pleasing and fully implemented. Too many options, SWS extensions, etc. I just don't have the self discipline to stay out of rabbit holes
Geoff L. Allan
New member
I've been using Davinci Resolve since 2019. Every year we get a new major version with a ton of new features. Every year we have multiple updates to fix the issues with the new features and things that the update broke. BUT - if you don't immediately update and can hold off on new features, it's completely fine with me. Since I'm not making $100M movies or anything, I can handle the occasional problems. By the end of the cycle there is always a stable, capable version that you can continue working with.
I'm just assuming that this is now the norm for large, complex apps. I'm fine with it. I can be both an early adopter, AND continue to use the stable older version.
My songs (not sessions!) that I'm currently redoing in FSP have "_Fender8" added to the title so I don't try to load them back in 7.
For the record (no pun intended), I use a DAW like I used to use a console and tape machine in a full-up analog studio, so maybe my situation is different than some.
I'm just assuming that this is now the norm for large, complex apps. I'm fine with it. I can be both an early adopter, AND continue to use the stable older version.
My songs (not sessions!) that I'm currently redoing in FSP have "_Fender8" added to the title so I don't try to load them back in 7.
For the record (no pun intended), I use a DAW like I used to use a console and tape machine in a full-up analog studio, so maybe my situation is different than some.
Can you tell me more about "constant visual glitches, crashes, the most amount of cpu spikes" in version 8.0.1 in a seperate thread please?
Thank you very much!
Ari
The fix was a very fast response to issues. No program with all of the vst/effects/computer variations will be perfect. If Fender has this kind of focus on fixing things, well it's good enough for me. As Windows gets more complex (as does the Mac operating system), I see more stress on our computers. Just because a program can run in a minimum set, that doesn't mean a dozen vst/effects that are memory hogs won't cause issues. Most problems are related to issues to an individual operating system matched to a specific computer and a specific VST/effects or mix of VST/effects. Just because your system worked fine with one song mix, doesn't mean it will after a system update, or adding one more vst, effects. Any major program today can and will have issues due to the software tools used due to the above interactions. Life needs fixes every day, adapt or die, just ask the dinosaurs.
TheNeil
New member
Not sure I get what your point is, given that I'm describing an issue related to the core settings of the application, before one even opens a file at all.
Growing at the expense of stability isn't sustainable for any application. If 25% of the 4 fields on the Audio Device menu aren't working correctly on macOS, that seems worth raising.
Hopefully the next few updates will focus on the various issues raised here which began with 8.0.0. Then we can all get back to a nice stable baseline of the newly rebranded app.
Growing at the expense of stability isn't sustainable for any application. If 25% of the 4 fields on the Audio Device menu aren't working correctly on macOS, that seems worth raising.
Hopefully the next few updates will focus on the various issues raised here which began with 8.0.0. Then we can all get back to a nice stable baseline of the newly rebranded app.
Luny
New member
Hi.
A Studio Pro 8 support person has reproduced a graphics problem with plug-ins on his computer.
The application has been registered and sent to the developers!
Attachments
I've installed 8.0.1 and I still have problems with crackles and pops when opening all my v7 sessions that work absolutely fine in Studio One 7. The CPU monitor doesn't show any "red light" warnings but the audio is very frequently broken.
I've tried using "Save To New Folder" with a few sessions but it doesn't work, crackles and pops every 20 to 30 seconds or so.
This is a problem with v8, not with plugins or system changes because the exact same sessions in the exact same computer work fine in v7. All audio settings in v8 are also exactly the same - they were imported when I installed v8.
I want to open a support ticket but I don't even know where to start. All my old sessions just fail when playing back.
I feel like I've wasted 99€ on a piece of software that I really want to get on with but it's impossible to work with it in its current state.
So disappointing...
I've tried using "Save To New Folder" with a few sessions but it doesn't work, crackles and pops every 20 to 30 seconds or so.
This is a problem with v8, not with plugins or system changes because the exact same sessions in the exact same computer work fine in v7. All audio settings in v8 are also exactly the same - they were imported when I installed v8.
I want to open a support ticket but I don't even know where to start. All my old sessions just fail when playing back.
I feel like I've wasted 99€ on a piece of software that I really want to get on with but it's impossible to work with it in its current state.
So disappointing...
Last edited:
Vocalpoint
Well-known member
Have you tried dropping your audio device out of SP8 momentarily and then readding it?
In Audio Setup - selecting No Audio Device. Exit the dialog
Then change it back to the UAD again?
Had some weirdness like this with devices when I moved from v5 to v6 some years ago.
While V6 recognized the devices on import and everything "looked" good on the surface - it wasn't until I stripped them out and added them back in that things started working again.
VP
Be sure you do a blind listening test before moving to Reaper. It's audio engine is appalling. Used it for 14 years before I realised- blamed myself and my old ears- it was Reaper all along. See, it can't do mono througput discretely, all audio passthrough is minimum 2 channels and it's flawed. Don't take my word for it, grab an accoustic guitar track & A/B with Studio Pro. You'll be amazed. SP is magic.
Sorry but that's just BS. There is no "magic" in neither of those programs, they're both just processing a PCM audio stream without any coloring. Those DAW summing differences have been debunked countless times...
I agree though that the 2-channel processing for mono sources does not make any sense at all and (besides a higher CPU usage) can lead to audible problems with certain plugins. There is a MPL script for mono processing though.
Last edited:
3BoxesEast
New member
And so, seeing the dust settle and with the 1st maintenance release out, decided to pull the trigger and update..!
Diving in over the weekend
Diving in over the weekend
It's not bullshit. Do the test or not, use YOUR ears or don't, I don't care. If your happy with subrate audio, go for it. Just thought I'd try to help. But as always,help can go fuck itself.
Since you made me curious, I just recorded the same input in S1 as well as in Reaper simultaneously. Then I exported the files, imported them in Logic, aligned their phase, flipped the polarity on one and pressed play. Result: 100% silence. Case solved.