Sampletank 3.01 CPU usage with 16 instruments loaded - Samplitude vs Studio One vs Reaper
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Yes ALL ST FX are enabled. Playing back a similar 16 midi track project in Samplitude Pro X uses 70% during playback and around 60% idle.
These are multi-out projects. S1 idles between 50-60% but I haven't created a 16 track midi project to test yet.
These are multi-out projects. S1 idles between 50-60% but I haven't created a 16 track midi project to test yet.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
OK I made a quick 16 midi track project in S1 all ST3 all FX enabled. CPU fluctuates between 60-70% during playback.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
- KVRist
- 118 posts since 17 Apr, 2005 from DFW, TX
Go to Options -> Audio Setup and disable Multi-Processing and see if that helps to lower the CPU usage.
resistance is futile. Check my latest mix: viewtopic.php?f=14&t=532758
-
- KVRAF
- 1612 posts since 18 Feb, 2011 from Salt Lake City, Utah
kbaccki wrote:Reaper does "anticipative FX processing" amongst other things to pre-buffer audio processed through FX chains. This pre-buffering decreases CPU load dramatically, but is not useful for live streams, obviously. As such, I believe reaper automatically turns off anticipative FX for any track being monitored live, so that you get the... er... live processing of the FX. I'm sure it also optimizes FX bin processing in general -- even if a track is being monitored live, if you're just idle then there's nothing to process, right? So reaper can quietly ignore ST3 plugin if it knows it's not feeding it MIDI. Other DAWs may take a more brute force approach -- i.e., just give everything in the audio graph a CPU time slice, whether or not any audio/MIDI is being fed through the graph. That would explain the huge disparity.
Try this: go into reaper options and disable anticipative FX. Is there a difference at idle? If it's the same CPU, then it must be something else, like not giving CPU to FX that are not doing anything.
Reaper contains lots and lots of options for optimizing engine I/O, threads, buffering, etc. They spent a lot of time in that area compared to some other daw vendors, IMO.
EDIT: I'd pop the ST3 demo into reaper myself... but, well, you know the deal...
Soon....
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Turning off multi-processing makes no difference.blizzard wrote:Go to Options -> Audio Setup and disable Multi-Processing and see if that helps to lower the CPU usage.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- KVRian
- 1355 posts since 27 Oct, 2009
Have you checked the actual CPU load in the task manager. Reaper shows CPU usage differently than other DAWs. For example, on my system, 10% in Reaper equals 40% in Ableton.
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Thanks I will have to try that.izonin wrote:Have you checked the actual CPU load in the task manager. Reaper shows CPU usage differently than other DAWs. For example, on my system, 10% in Reaper equals 40% in Ableton.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
OK so the task manager is showing between 12%-14% during playback. So it's a bit worse but still better.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
-
- KVRian
- 1355 posts since 27 Oct, 2009
What does the task manager show when you run Sampletank in Samplitude and Studio One? I know that Reaper has the best engine. In my experience it's usually about 10-20% better than other DAWs.
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
Since my computer is not the latest model, maybe I should switch to Reaper after all if it is so efficient I tried it before, but it seemed less intuitive than other DAW's, too complex
Have you tried it in Mulab? It is a tiny DAW (18MB if I remember correctly) and there is nothing to install. Just wondering...
Have you tried it in Mulab? It is a tiny DAW (18MB if I remember correctly) and there is nothing to install. Just wondering...
- KVRian
- Topic Starter
- 1028 posts since 11 Jun, 2004 from London
Hmm thats interesting.izonin wrote:What does the task manager show when you run Sampletank in Samplitude and Studio One? I know that Reaper has the best engine. In my experience it's usually about 10-20% better than other DAWs.
Samplitude is showing 20% in the task manager vs 66% on the Samp DSP meter.
Studio One is showing 11% in the Task manager vs 79% (fluctuating) in the S1 performance monitor.
Although in Samplitude it seems to vary depending on the amount of CPU cores I make active.If I set it to 2 or I'm getting 20% in the task manager and around 50% in Samp DSP meter. But if I set it to 8 cores, the DSP manager and the task manager are both around 60%. So the more cores I enable the higher the CPU.
Although this does seem to be a SampleTank specific issue. I created a similar 16 midi part project using Kontakt 5 with built-in effects and CPU usage (4 cores enabled ) is 12% in Windows Task Manager and 12% Samp DSP Meter. Also, it's worth noting that SampleTank doesn't have any settings for utilising CPU cores, whereas Kontakt does. In the Kontakt project I'm utilising 2 cores in Kontakt. So maybe that's the reason for lower CPU usage.
Asus Z97-A| i7 4770K|32GB DDR3|Samsung 850 Pro 512 SSD System|Crucial 960gb SSD A/V|Crucial 960 SSD Samples|GTX 960 2GB|RME Raydat|Windows 10 x64, Philips 40" 4K
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
My Samplitude/Sequoia Tutorials are here :
http://www.youtube.com/kraznet
- KVRAF
- 23103 posts since 7 Jan, 2009 from Croatia
izonin wrote:Have you checked the actual CPU load in the task manager. Reaper shows CPU usage differently than other DAWs. For example, on my system, 10% in Reaper equals 40% in Ableton.
Actually Ableton is a bit wrong in this regard... It doesn't show actual CPU usage at all. https://www.ableton.com/en/articles/why ... y-monitor/
I reckon similar case might be with Samp and some other DAWs too.
-
- KVRAF
- 2448 posts since 12 Sep, 2004
Always cross check w/ windows task manager (which itself isn't necessarily 100% accurate)... Or Activity Monitor on OSX (or "top" command line).. Every daw does there own computes differently.
You need to limit that rez, bro.