Studio One 4.5’s take on groups is so much better, with customizable track grouping that works precisely like Pro Tools (if you want it to). Many of these new features in version 4.5 are a direct result of user feedback, which highlights an important point: PreSonus seems to listen to their user base. Many different processes can be responsible for high CPU usage, and there’s no one-size-fits-all fix. To find specific advice, get the name of the process from the Processes or Details (a more specific view) tab of Task Manager, then search online for support threads on the topic. A Subreddit for Users of Studio One r/StudioOne is an educational tool. Please post anything related to Studio One; compatible hardware and software, synths, VSTs, controllers, etc. Questions about effects, getting a certain sound, troubleshooting, general or specific production questions and the like are welcome. Microsoft.NET Framework is one of the most popular application development platforms and programming languages. C# and ASP.NET frameworks are used by millions of developers for building Windows client applications, XML Web services, distributed components, client-server applications, database applications, and so on. I've been using Studio One 3 for about 8 months now. No major issues, and I've updated the program many times since then. However, since I updated to version 3.5, I have been getting random CPU spikes to 100% out of nowhere. I may have a constant 30% or so, then it will just spike to 100% for a.
Studio One 4.5 Cpu Spikes Crazy Math
Studio One 4.5 Cpu Spikes Crazy Games
Cpu Spikes Windows 10
using Mixbus since v02 and only recently jumped to v06. Really enjoying it so far.
Mixed the first session in it (about 30 tracks imported but boiled it down to about 16 tracks that were actually mixed, added a single Midi Instrument (the Drum Mic’A Sim via Kontakt) - used the typical mixbus workflow, added a few plugins here and there but went not super crazy with it.
My system meanwhile did. Macbook Pro went pretty noisy (and stood like that), the mixbus system usage display in the upper right corner showed something between 60 and 80 % sometimes 90+. Mac Activity Monitor showed about 130 % (and more) cpu usage. Even switched to 'all available processors' in preferences/general/DSP CPU utilization.
I understand that Mixbus uses higher amounts of CPU but I was wondering that such an average session size hit the limits so quickly. (btw: apart from the good idea to limit oneself to a certain amount of tracks: fan noise can be quite a challenge to listen to while you actually want to listen to your mix )
anyway, here are my questions, maybe some of you have (had) similar experiences or workarounds to share:
- plugins: is it generally possible to disable them (not just bypass them but really take them from the cpu system for the time being (like in Pro Tools)
- same about tracks: when deactivated, are they still using cpu? (in that session I kept all the unused tracks but deactived them)
- I already switched buffer size to Large Session (biggest option in the preferences/audio/buffering), are there more ways to improve system response and or avoid overload that I’m possibly not aware of?
( I know in the start session window you can choose buffer size, is this a different approach?)
- would there be an advantage to use the 32 Bit Mixbus 6 version instead of the 64 Bit?
- I’m aware that I’m using quite an old system (see below) for the whole thing but nothing on the website or manual speaks against using this setup.
Thanks for some insight.
Best regards
Tapeworm
___________________
System:
Macbook Pro early 2011 2,3 GHz, i5, 16 GB RAM (OS 10.9.5), stock HDD (SSD update is already planned),
Interface: Echo Audio 4 (for this session), normally Focusrite Saffire Pro 40
Computer connected to a second Screen plus Bluetooth Mouse
_______________