• 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

Are there no more CPU spikes in version 8? Has this issue been fixed? In version 6, the built‑in browser consistently causes CPU spikes on my system, etc...
There are sometimes spikes, when inserting plugins or turning plugins off/on.
Same thing can happen, when plugins go into, or out of plugin nap. That can cause clicks and Realtime render to fail sometimes. Turning off Plugin Nap might resolve that.
In terms of browser cpu spikes, I can not contribute much, because using it for Sample or Filesearch is pure pain, so I don't do it. Loops, Splice, Cloud is even "custumized away" at my end. I enjoy it only for Plugin Search.
 
Last edited:
Anyone have issue with tempo automation if the time signature beat duration is dotted?

For example if the time signature is 6/8 with a 1/4 dotted beat duration I'm getting various bugs in the tempo track. Not being able to consistently create or edit tempo automation - sometimes it simply won't let me. Or not being able to select multiple tempo automation points.

Only happens if the beat duration is dotted.

SP 8.0.2
Win 10.

EDIT - I've just checked this on my mac and it's the same. Looks like a genuine bug to me.

Bump on this. Anybody experience this?

It's very easy to recreate.

Create new project. Make the time signature 6/8. It should automatically be a dotted 1/4 beat duration.

Open the global tempo track. Try and click in some automation points with the mouse.

For me it won't work.

I can add automation points with the + button in the track header, but I can't then select them or edit them correctly. Particularly selecting and editing multiple automation points doesn't work.
 
Bump on this. Anybody experience this?

It's very easy to recreate.

Create new project. Make the time signature 6/8. It should automatically be a dotted 1/4 beat duration.

Open the global tempo track. Try and click in some automation points with the mouse.

For me it won't work.

I can add automation points with the + button in the track header, but I can't then select them or edit them correctly. Particularly selecting and editing multiple automation points doesn't work.

Yes I can reproduce.
I strongly suggest in future creating a separate thread to get it reproduced first, then post here, otherwise it just gets lost with a bunch of other conversations. It's also easier to send the URL to support if you create a ticket. Also please update your signature with your hardware/software specs.
 
Yes I can reproduce.
I strongly suggest in future creating a separate thread to get it reproduced first, then post here, otherwise it just gets lost with a bunch of other conversations. It's also easier to send the URL to support if you create a ticket. Also please update your signature with your hardware/software specs.

I'm never sure whether to make a new post. I try not to clutter a forum but I can see there's value in having separate posts too.

Thanks for checking though. At least I know it's not my system.

Seems a relatively serious bug - not being able to correctly automate tempo in triplet based time signatures.

I've sent a bug report and encourage others to send one so it gets visibility with support.
 
I'm never sure whether to make a new post. I try not to clutter a forum but I can see there's value in having separate posts too.

Thanks for checking though. At least I know it's not my system.

Seems a relatively serious bug - not being able to correctly automate tempo in triplet based time signatures.

I've sent a bug report and encourage others to send one so it gets visibility with support.

I've made this mistake before myself several times. For your own issues you are trying to reproduce you really need to create a separate thread for it so it can be troubleshooted first, rather than piggy back on others. Cluttering your own thread is way better than cluttering others with different conversations and issues going on, especially threads like this.

If you don't get much traction in responses on your own thread you can always post a link here asking others if they would like to join in, and if you actually find a bug you can post a link here too.

Again please update your signature with your hardware/software specs. Thx
 
Thanks to maintenance team for the update. I was so confident about the 8.0.1 that I updated to 8.0.2 in the middle of a session. It is running smoothly as I'm getting ready to mix.
 
Thanks to maintenance team for the update. I was so confident about the 8.0.1 that I updated to 8.0.2 in the middle of a session. It is running smoothly as I'm getting ready to mix.
Jeez. You are either brave or foolhardy!
I always wait at least a couple of weeks before updating, and a couple of months for major updates. I've been bitten too many times.
 
I finally installed as soon as 8.02 arrived. As usual - super solid right out of the gate.

VP
 
Its good to hear, FP8 is solid at this point. Hey, good things ahead. Maybe even some attention to address what is still needed in this great DAW, but still lacking. Once our relocating is settled on our end, I'll be looking forward to picking up version 8. Until then, congrats on keeping the roof sealed, and no rain coming in.

I'm looking forward to when actual discussions begin on integral improvements. 🏁 🏎⚙️⚙️⚙️
 
But then again - I have never seen spikes with any version of S1 to this point (since 2011)

I've seen recently when I updated from S1 5 to 8.0.0. with the same project on the same machine I've had to double buffer size and tweak dropout protection to get them of my way. (yes, I've re-opened the projects in question with v5 after performance issues with v8 -- they were still good in v5.)

not yet retested with a 8.0.1 or .2 tho.
 
I've seen recently when I updated from S1 5 to 8.0.0. with the same project on the same machine I've had to double buffer size and tweak dropout protection to get them of my way. (yes, I've re-opened the projects in question with v5 after performance issues with v8 -- they were still good in v5.)

not yet retested with a 8.0.1 or .2 tho.
Did you look which plug-ins show higher CPU load than in v5?
 
Did you look which plug-ins show higher CPU load than in v5?

one of the projects in question doesn't and didn't have like any plugins (except of two stock limiters on aux monitoring buses), so probably that's not the plugins.

let me retry with a more recent version before we dive in further.
 
one of the projects in question doesn't and didn't have like any plugins (except of two stock limiters on aux monitoring buses, a thing I saved to a template back in 4.x, I think), so probably that's not the plugins.

let me retry with a more recent version before we dive in further.
Can you update your signature please with your hardware and software specs.
 
I always disliked that part. is this required by rules now?
It makes life a LOT easier comparing specs from one user to another. Far easier then searching for a single post that may or may not contain specs (unless we are expected to memorize a users specs).

It's a one time operation and doesn't take much time at all and is helpful for everybody.
 
It's indicative at best. When you update your signature it also changes in all previous posts. Now your old posts about say S1 v7 and your old rig have a signature with SP v8 and your new rig's specs in them. How can that be helpful? :(
 
  • Like
Reactions: boo
It's indicative at best. When you update your signature it also changes in all previous posts. Now your old posts about say S1 v7 and your old rig have a signature with SP v8 and your new rig's specs in them. How can that be helpful? :(
Mostly nobody cares about old threads, and even if they did, people would have the common sense look at the date stamp of the post and realise the signature is more up to date.

Better to have one than not. It's useful to have at least something rather than nothing (are you windows or Mac?), and the amount of time you could have spent typing that last post you could have updated your signature, so you can be helpful to people trying to be helpful..or just not be helpful. "At best" is WAY better than nothing. Back to the thread eh? And please be nice and update your signature!
 
Back
Top