Studio One 4.5 Cpu Spikes Crazy
05-03-2020, 03:06 PM
Hey there,
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
_______________
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
_______________
Studio One 4.5 Cpu Spikes Crazy Craft
One of the FL Studio devs talked about that in some detail, why it's potentially problematic to move between various software and assume that what's called a cpu usage meter in various places are actually measuring and displaying the exact same thing the same way in all of them.
Cpu Spikes Windows 10
- Is Studio One 4.5 More Cpu Friendly House; May 29, 2017 CPU Multicore Usage in Studio One. I have found that Studio One seems to handle multi cores quite well here at my end. I have found a similar situation to Bbd's case. For a session that is not too demanding, one core seems to take the load while the others have it easier.
- I'm running Studio One Artist 3.2 on an HP laptop - Intel i7 6500U 2.5 GHz 8GB RAM. If I run one instance of Presence with the GrandPiano.sound, the CPU meter reads 30%. If I use more than one instance of Mai Tai, the CPU meter spikes and hits 100%. I really love the look and feel of Studio One, but it's basically unusable for me.