Disk to slow or system overload

Hi there Folks,

 

I have a really annoying situation with Logic going into spinning ball mode for what I can see as no apparent reason. I have 22gb Ram , a xeon quad core and plenty of free space on both my boot drive and my samples/libs drive.Screen Shot 2020-07-09 at 09.39.04.png Screen Shot 2020-07-09 at 09.38.39.png

I seems really odd that this should happen as I my CPU monitor tells me that I'm at 83% idle. I'm wondering if it could be because I think that some of my sample libs are on my boot drive and some are on my audio libs drive. Both are SSDs so run pretty speedily. Any thoughts would be HUGELY appreciated as I'm on a deadline at the mo and really don't need this to be happening. Occasionally it seems that on the logic CPU graphic that i do get a spike in one of the cores which can glitch it out although I haven't notice this happening recently. Thanks in advance

I suspect you're using Rewire, hence the Live Mode.

If you're mixing, change Multithreading to Playback.

Any reason for the -756 samples? Did you measure that?

Hi triplets,

 

I am measuring that as it goes through my mixer and soundcard and that holds the latency in check. Im actually tracking though and that's when it happens.. So going to playback only my cause a problem?? I dunno.. Do all my sample libs need to be in the same drive?..I've had a few issues before and some of them( one or two) have remained on my boot drive and I wonder whether that could cause an issue?

You're tracking with buffer at 1024 and 45ms roundtrip latency??

I don't think anybody can track like that.

Ive got the Delay compensation set to that that (Ive calibrated along to click) as I listen through my Focusrite Saffire Peo and don't monitor the output of logic channel( set to (no output) that i'm recording into. ITs so that i don't glitch out with the software instruments that I'm running. Omnisphere primarily. I do quite alot of work with both software instruments running and live stuff. What would your suggestion be ..I am able to play in sync as My interface does all the summing of signals.. That said there may be a better way..

I'm not a big fan of messing with that Delay Recording slider. I leave mine at 0 samples and mess with the buffer and other settings.

Can you put the buffer at 64 when you play Omnisphere?

Hi triplets... Ive seemed to sort the issue with the system too slow.. i found out that i had two symlinks in the application support folder sendings signal path to my audio drive. Then i had two versions of Onmisphere in that folder .. so i reckon that had led to confusion. Ill try the 64.. but the problem that Ive had is that as Im recording often through my mixer AND then through my interface the signal arrives at logic late.. and so when i play back the timing is off and out of sync. Ill try though now as you say and see what happens. thanks for your help mate.. Really helpful.

So I've sorted out the latency issue and that is SOOO much better with your set up having the samples at 0 whilst tracking. But the issue of the SBOD still remains.. when ive even got a really simple set up ... itll spin for 20/30 secs then I get a disk too slow or system overload error message.. Im using two ssds so that shouldn't be the issue and it happens with even a totally minimal set up. i.e 4 audio tracks and nothing more.. v. odd.. Ive just reset the NVRAM...but it still remains..??

Have you tried running First Aid from the Disk Utility on the drives?

I haven’t. I’ll do that.

Im using two ssds so that shouldn't be the issue

 

What brand? What connection? How are they formatted?

They are both Samsung Evo and I think formatted extended journal or something similar as I recall. Long time ago now!

Are you still on OSX Sierra?

I am on Sierra. Its been fine until recently. Been on Sierra for a while now. I used the dosdude Sierra patcher toool to run it on my macpro. 2008. ive just reset the NVRam. Still did it so did the SMC and that seems to have been ok so will see how that goes. I’ve also started a new track without a template adding the various elements of my standard template one by one to see if either Kontakt or Omnisphere might be the culprits. Kontakt seems to be behaving at the mo.

Remember there's a point where a quad-core from 2008 can't keep up anymore.

So keep the CPU window in Logic floating so you can see what's peaking.

Its doing it really badly ( spiining ball for 10-30 seconds on pressing play).. Also qutting randomly sometimes now with only two Software instruments loaded.. I'm wondering whether it may be a RAM issue.. Ive got the buffer set to 256 so that i can also do some guiatar tracking but With two Pizz instruments, one instance of Stylus RMX loaded and a few audio its shouldn't be taxed at all. I've reset the NVRAM and the SMC..Ive got plenty of space on both my boot drive and my audio drive where all the samples are.. Soo frustrating.. thanks for any extra help there may be out there.. You are all true legends!!! Does anyone know where I might be able to find a legit copy of Logic 10.4.6 so that i can maybe do a reinstall.. No other apps are getting the spinning ball..as far as Im aware.

Does anyone know where I might be able to find a legit copy of Logic 10.4.6 so that i can maybe do a reinstall.

 

Legit copies are only available thru the App Store.

You need High Sierra for Logic 10.4.6

ok..So could i get a copy of 10.4.3 there or something that will suit Sierra?

Might Logic somehow be corrupted.. I'm just trying to figure anything really as I'm on a deadline at the moment and its pretty frustrating. Thank you trips for your help btw..

... sorry and if i go to update in the App store will it just update to the latest version of Logic that will work with my 0SX?

... sorry and if i go to update in the App store will it just update to the latest version of Logic that will work with my 0SX?

 

If you bought Logic originally, you can update to the latest version your OS will allow for free.

So as an update.. re installed what I thought was a less corrupted version of Logic.. Still happening!!! when I look at my iStat data logic is running at 249% but my system is still 70% idle.. and still it goes into a hang. What weirds me out is that from a system that 1 year ago was behaving and managing these workloads with no issues.. present tune has 10 instances of Kontakt and a couple of others... then a few bus sends (3) and a couple of other plugins but it stills goes into prolonged spinning balls and hangs...22gb of RAM should easily be able to handle this i'd have thought.. Is it maybe something that Im doing wrong with the Kontakt memory server that isn't allowing it to access the full RAM?

here are a couple of screenshots as to what's going on under the hood...It seems like only using 3gb for Logic but other background ops are pushing that up to 19gb so only 3 gb spare.. Could that be an issue maybe and I therefore need some more RAM?.... but im still getting the disk too slow or system overload.. 2 ssds are doing all the work . Both seem to be functioning properly having tested them. Pulling my hair out a little here... deadline coming on Monday and still struggling..

Why don't you just run Logic and nothing else and see what happens?

So Ive dropped everything else.. i.e Chrome and mail etc..but I also read that having a display that was scaling can also somehow create issues. So I've dropped it back to what its supposed to be and so far so good.. have you heard of this being an issue?

Sooo.. that doesn't work!!! Just went back to the problem child track and even with allotter apps off.. its still the same.....mmmmm!!

So maybe it's an issue with Kontakt and its memory server?

Pretty sure you don't have overloads with Logic's stock plugins?

yep i did think that and have turned it off.. Ive also just turned off a cloud server called BT cloud and got rid of it as id heard that could cause CPU issues and at the moment we seems to be ok.. thank you soo much Trips for all your help.. your a legend!!! really really appreciate it.

Ive also just turned off a cloud server called BT cloud

 

Yup, cloud based stuff can create issues. I avoid them like the plague.