And its sucks the life out of your hard disk.
(Also, disabling HyperThreading is such a stupid recommendation I won't even go into it. Perhaps only if you're a Cubase user because Reaper has no problems with HyperThreading for example... in fact it uses it to its advantage.)
Right, it was the OS drive, it was really horrible in my case, probably the disk wasn't that performing as well so that didn't help. Anyway, switching to SSD has been instant happyness.
Guy here adamant reaper is better with it off.
What ssd have you put in for C drive?
Hey Guys!
So i might have been a little quick to judge because after a few playbacks the deopouts stop and it happens only during the first few playbacks .. so i am guessing its fine, has anyone experienced the same? asking out of curiosity.
Thank you all for your replies!
It seems the Steinberg recommendation to turn off HT only applies to old versions of their software too.HT had issues early on (cca 2007-2008), especially at the very lowest latencies (OS-side thread scheduling issues, which might still be there to certain extent), but times have mostly changed. If you're not using latencies below 128 samples, feel free to leave HT on. At least for Reaper.
6. Disable Hyper-Threading if your CPU supports it (e.g. Intel i7) and you use older sequencer versions than Cubase 7 and Nuendo 6
It seems the Steinberg recommendation to turn off HT only applies to old versions of their software too.
Hey guys!
So i have recently upgraded my PC to the following specs I7 8700k 64GB RAM and disks as follows 128GB 860 EVO (OS and Cubase), 500GB samsung 960 NVMe pro SSD (Heavy Libraries), 3TB Hitachi drive 7200 RPM (2nd drive for heavy libraries), and two WD RED 3TB disks 5400RPM for all the rest of the libraries.
Now i have upgraded my machine so i could stop freezing tracks and stop from my disk usage to get to %100 however after a brand new PC upgrade i ran into this problem again and i thought that more RAM could basically solve this issue (RAM is at only %50).
I use many libraries in the projects and the heaviest one being loaded from the SSD (Orchestral), i have set my General preload buffer to 60k and it has helped but i still have them in times .. what are possible solutions i can have?
Ain't that the truth. I find that Spitfire libraries tend to be very hard on my CPU and RAM. They don't want to let go when I try to delete the track they're on, or shut down my DAW. Don't have this problem with any other libraries.There's no average. Different libraries have patches of different complexity, so this will impact CPU/disk usage differently.