Serato Studio General Discussion

Forum
 Serato Studio General Discussion
Macbook Pro 2016 poor performance
Talk about anything Serato Studio, music production, plugins and supported hardware

Macbook Pro 2016 poor performance

Oli Griffiths 12:19 AM - 20 September, 2019
Reposting this from serato.com

* Step 1
Play a project on a 2016 Macbook Pro 13" with 16GB ram, 2.5GHz processor.

* Actual Result
Notice how laggy the UI and overall computer is.
Switching to chrome and scrolling or moving between tabs is slow AF.
Adjusting faders or otherwise clicking around the serato UI is slow AF.
The machine becomes basically unusable when playing back and it's impossible to adjust controls within studio. Frame rate is about 2fps at best.

* Expected Result
It's not laggy.

* Workaround
Buy a faster machine.

It also takes 10+ seconds to even open the project
I am only using one VST (Serum) for about 4-5 instruments, and a bunch of samples for everything else.

This is happening on 1.3 (and all previous versions).
Oli Griffiths 2:22 PM - 1 October, 2019
Hey, just an update on this.

I went through some optimisations for Serum splice.com and www.reddit.com

Basically I reduced the oscillator quality in general settings down to draft, and reduced my unison counts down to < 10, seems to have helped a lot.

One thing I don't understand is after pausing serato, the CPU stays at 150% load for a good 20 seconds before dropping off. Is this serum still doing stuff but producing no audio? like long tail reverb?
Serato, Forum Moderator
Phil C 10:55 PM - 6 October, 2019
Nice one Oli, sounds like you got some good results.

My only question would be whether the CPU stays high for 20 seconds when Serum is not in the project or is this specific to the use of Serum?

That might point to the cause of the high CPU...
Oli Griffiths 11:00 PM - 6 October, 2019
Yeah if I switch to another project the CPU drops down www.dropbox.com

It's weird that the CPU is still being pegged when the project is not playing, like something in the background is still processing even when nothing is happening...