CPU spike, Disk is too slow or System Overload -Logic Pro X Yosemite
Hello all,
I've been digging for a while and have yet to find a solution to my problem.
I recently upgraded my system and I've run into a frustrating snag.
I'm getting a "disk is too slow or system overload" error message, when pretty much nothing is going on in the session.
I first started seeing this in a dense session from my old computer that I brought across to see how my new computer would handle it in comparison. Initially it worked and then I started to get the error message at different points in the song, and not necessarily the same spots, or even CPU intensive sections.
I tried freezing, bypassing, taking plugins off, etc.. that didn't work. I was able to bounce from the session without any problems, so I just did an export all on all 60 tracks just to test them free of plugins in a brand new session. I brought the tracks into a clean session without any plugins on the tracks, buses or the master. Drum roll......still getting the **** error message, there's very little processing happening, and then there's a giant spike one of the 24 cores and the disk i/0 and then the message. So weird!! And incredibly frustrating, as I'm now seeing this pop up in other sessions. I've only recently started working off of my new set-up and this error has me worried that I just dropped a big chunk of cash only to be handcuffed by this glitch. Please help, I've got work on the go, and I'm afraid that this could pop up at any moment.
My new computer is a
Mac Pro (Late 2013)
2.7ghz 12 core Intel Xeon E5
64GB ram
1TB internal flash drive with 600gb free (I have Logic and NI and most of my software installed on this drive)
Thunderbolt 2 Lacie 5big configured to raid6 with about 5 tb free (this is my audio record drive and where my samples/loops and extraneous software lives).
I'm running Yosemite 10.10.1 and Logic 10.1.0
I have an apollo twin for my soundcard also thunderbolt
As far as I can tell there shouldn't be any hang up speed wise anywhere in my set-up, but then again this is a new upgrade for me, and I'm not familiar with any of the pitfalls. I have two composer friends who have seen this issue with similar set-ups and none of us have been able to figure it out yet.
Hopefully one of you has the answers, or at least some idea. Please let me know if anyone else out there has come across this issue in the current OS and Logic X, any insight would be helpful.
Thanks!
N8
Logic Pro X, OS X Yosemite (10.10.1)