Logic 9 "Disk too slow or system overload"

[Onfireee]

I'm having some major problems regarding large session files on my Mac Pro. With my current specs, I feel like I shouldn't be getting these problems. Maybe I'm just confused as to the root of the actual problem. Anyone willing to help me out?

Specs:

Processor: 3.07 Ghz Intel Core i7
Memory: 24gb 1066 Mhz DDR3
Internal HD: WD Black Caviar 1TB
External HDs: 2 TB WD (for session files)
1 TB WD (for all my virtual instruments)

Error Message:

Disk is too slow or System Overload.
(-10010)
The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time.

[pinkheadedbug]

What's your buffer size? Try creating an empty audio track and selecting that before starting playback.

I've had some similar issues, mostly with Kontakt when it is loaded with a big library like NI Abbey Road Sixties drums or something similar.

Also, are you running in 32bit or 64bit mode?

[jimmymio]

Originally Posted by pinkheadedbug

Also, are you running in 32bit or 64bit mode?

When I get this msg i know that it's time to switch from 32 to 64 bit.

[silveradio]

there is a simple solution: trash the logic preference file in your library. navigate to user/library/preferences/ and trash this file: com.apple.logic.pro.plist

make sure you have saved your work and closed Logic first.

this should fix your error! i had this problem the first time on a location shoot where i was recording a band's live performance, this was the solution after trying multiple hard drives.

[Onfireee]

Originally Posted by pinkheadedbug

What's your buffer size? Try creating an empty audio track and selecting that before starting playback.

I've had some similar issues, mostly with Kontakt when it is loaded with a big library like NI Abbey Road Sixties drums or something similar.

Also, are you running in 32bit or 64bit mode?

I am running in 64 bit mode, both my CPU and logic 9 itself. As for buffer size, I've tried every one with the same result unfortunately. I've also looked into Apple's page regarding the error and how to fix/evade it with no success.

Originally Posted by silveradio

there is a simple solution: trash the logic preference file in your library. navigate to user/library/preferences/ and trash this file: com.apple.logic.pro.plist

make sure you have saved your work and closed Logic first.

this should fix your error! i had this problem the first time on a location shoot where i was recording a band's live performance, this was the solution after trying multiple hard drives.

Unfortunately, this didn't work for me :( The file reappears every time I open Logic, and the error continues.

I'm wondering though... Is it possible that my CPU or Logic isn't utilizing the full amount of RAM in my system? I recently maxed out my RAM (from a previous 6gbs) in an effort to correct the error with no success either. When I monitor the I/O and threads in Logic, it doesn't seem to be evenly distributed across all 8 threads... Not entirely sure how that works.

[pinkheadedbug]

Few more questions --

-- what interface are you using? Have you tried removing the interface and playing through the built-in outs?

-- what's on the tracks you are playing, and is any of it running in the 32-bit bridge?

-- trying running Utilities>Activity Monitor and Utilities>Console to get a clearer idea of what's going on

-- again, try this: create a new audio track with nothing on it, and select this track before trying to play back. Make sure it is not armed. Does this make any difference?

[starseed]

I believe it is the exact message from the motion sensor as you suspected.

MacBook Sudden Motion Sensor

[Manfrensengensen]

logic 9.1.6? internal HD or External? may make a difference.

[pinkheadedbug]

Mac Pro doesn't have a motion sensor.

[grooveminister]

Does anyone know where this motion sensor is located?
Is it inside of the 2.5" drives or on the mainboard?
I´ve got a Mac Mini Server and have had this message too.

But it seemed to me that the message would be displayed anytime when a disc was busy and didn´t deliver audio data fast enough...

[Nu-tra]

Disarm all input tracks that aren't being recorded.

[pianoman]

Originally Posted by Onfireee

Specs:

Processor: 3.07 Ghz Intel Core i7
Memory: 24gb 1066 Mhz DDR3
Internal HD: WD Black Caviar 1TB
External HDs: 2 TB WD (for session files)
1 TB WD (for all my virtual instruments)

Error Message:

Disk is too slow or System Overload.
(-10010)

Amazing.

Message to me: keep the computer reasonably lean. Even buying a beast of a machine appears to be no guarantee. I hope your problem gets solved.

[Onfireee]

Originally Posted by pinkheadedbug

Few more questions --

-- what interface are you using? Have you tried removing the interface and playing through the built-in outs?

I'm using an Apogee Ensemble. For about a month, I left the ensemble at my other guitarists throughout the duration of tracking our EP. In that time I used his Apogee Duet 2 and my backup EMU 0404 with the same problems.

Originally Posted by pinkheadedbug

-- what's on the tracks you are playing, and is any of it running in the 32-bit bridge?

It only happens in sessions with extensive tracks. The first example, is a short film I'm scoring which has a large Kontakt multiple-instrument and many plug-ins both 32-bit bridge and native 64. I'm sort of mixing/recording at the same time as I go on that one. So I thought it was just my CPU not having the 'huevos' to handle it.

But then on the other hand... I have a session for my band that has 42 audio tracks, no midi and no plug-ins at all (all premixing/mastering stage). Yet I still recieve the error.

Originally Posted by pinkheadedbug

-- trying running Utilities>Activity Monitor and Utilities>Console to get a clearer idea of what's going on

Here's screenshots of both minitors and those programs with Logic open while the error occurs. The threads don't seem to evenly distributed in logic, and my computer doesn't look like it's working very hard according to the activity monitor

Computer Tech pictures by Onfireee - Photobucket

Originally Posted by pinkheadedbug

-- again, try this: create a new audio track with nothing on it, and select this track before trying to play back. Make sure it is not armed. Does this make any difference?

Unfortunately, It made no difference in either of the sessions.

[Onfireee]

Originally Posted by Manfrensengensen

logic 9.1.6? internal HD or External? may make a difference.

Logic 9.1.6. Sessions are on external, OS is on internal (obviously haha). Also, I have another separate external to house my virtual instruments when they're in use.

Originally Posted by pinkheadedbug

Mac Pro doesn't have a motion sensor.

Exactly. I'm baffled.

p.s. thanks for all the quick responses everyone. This has stunted my workflow for a long time and your help is invaluable!

[Onfireee]

Originally Posted by Nu-tra

Disarm all input tracks that aren't being recorded.

I always do.

[fabriciom]

Either your HDD or your CPU cant handle the load. I also get occasional reads/seeks on my HDD and I get the same error. This does not happen on my SDD drive. So its either something to do with the HDDs not being able to keep up or the buffer gets full and has to wait for the disk to seek and get data. I have 2 drives with 7200 rpm and cant have a project with more than 20 audio tracks. On the other hand if the project is my SSD drive I have gone up to 50 audio tracks with absolutely no problems.

P.D. The load meter in logic barely show any action the HDD, but when it stops with the error you see a huge spike in the HDD load meter.

[degas]

Originally Posted by fabriciom

I have 2 drives with 7200 rpm and cant have a project with more than 20 audio tracks. On the other hand if the project is my SSD drive I have gone up to 50 audio tracks with absolutely no problems.
.

Weird. I have a Mac Pro early 2008 with a standard WD FW400 disc.
Gone 80+ tracks many times without problems.

[bugscoe]

I'm wondering if this is a 9.1.6 thing?

Since upgrading, I've been occasionally getting this message as well on a Mac Pro 6 Core machine.

I haven't had the chance to try it with a different session to make sure. I just know it started happening with the new update.

[Onfireee]

Originally Posted by bugscoe

I'm wondering if this is a 9.1.6 thing?

Since upgrading, I've been occasionally getting this message as well on a Mac Pro 6 Core machine.

I haven't had the chance to try it with a different session to make sure. I just know it started happening with the new update.

I just recently upgraded myself, but it was happening throughout the duration of 9.1.5.

[Onfireee]

Anyone have any other ideas?

[dankin]

Does it only happen the first time you play a project? Or does it happen randomly while you are working?

[valis]

Originally Posted by degas

Weird. I have a Mac Pro early 2008 with a standard WD FW400 disc.
Gone 80+ tracks many times without problems.

2008 mac pro and have done 60+ tracks with internal 7200rpm (I do put samples on another drive). Something else is afoot imo.

Also pmset only affects the OS based controls, individual drives can have their own timeout even if they're not listed as 'green' drives (green drives just tend to be more aggressive about power saving states and can even have variable spin rates). Some models may have utilities (like WD specifically) that allow you to tune the power saving states as well as things like TLER, which can also affect read/write performance as consumer drives can take ages to recover from an error and that can affect performance as well.

Lastly I would wonder if there's a sub in the proximity of the computer? Vibration can affect performance even without triggering motion sensors.

[Onfireee]

Originally Posted by dankin

Does it only happen the first time you play a project? Or does it happen randomly while you are working?

Randomly while working.

[Onfireee]

Originally Posted by valis

2008 mac pro and have done 60+ tracks with internal 7200rpm (I do put samples on another drive). Something else is afoot imo.

Also pmset only affects the OS based controls, individual drives can have their own timeout even if they're not listed as 'green' drives (green drives just tend to be more aggressive about power saving states and can even have variable spin rates). Some models may have utilities (like WD specifically) that allow you to tune the power saving states as well as things like TLER, which can also affect read/write performance as consumer drives can take ages to recover from an error and that can affect performance as well.

Lastly I would wonder if there's a sub in the proximity of the computer? Vibration can affect performance even without triggering motion sensors.

I've considered getting a sub, but there isn't one for the time being. I'm really at my wits end trying to solve this... I have no idea how to fix this.

[valis]

Pay someone who can help you, or take the machine to a knowledgeable Mac shop.

[Padje]

Getting the same message. It's driving me crazy.

6 core macpro, used the terminal commando. Very irritating. Any solutions, ideas, anything in the meantime ? THanks in advance

[matt thomas]

I'm pretty sure the problem is your external drives.

you are using a firewire interface, and firewire drives to stream samples, and a firewire drive for session files, all on the same firewire bus.

Put your external sample drives inside your machine, and stream them from there. Then you should be sweet

edit: Just noticed this thread is over a month old. To the guy who bumped it, what is your setup?

matt

[Padje]

Originally Posted by matt thomas

I'm pretty sure the problem is your external drives.

you are using a firewire interface, and firewire drives to stream samples, and a firewire drive for session files, all on the same firewire bus.

Put your external sample drives inside your machine, and stream them from there. Then you should be sweet

edit: Just noticed this thread is over a month old. To the guy who bumped it, what is your setup?

matt

Just wanted to ask if it was a reply on my last post or not. Clearly not :-)
My setup is 6 core mac, 10.6.8 , Logic 9.1.5, SSL alphalink with madiextreme card. O, I wish somebody could solve this one, very annoying. It started to pop up 2 weeks ago, not to often, but today, way to often. I disabled sms in terminal, but no difference.

[matt thomas]

hmmm. that's not so obvious.

External drives?
Streaming samples?
sample rate?
number of tracks?

matt

[Padje]

No external drives, all internal.

1. Startup
2. Recording
3. Samples
4. Backup

Sample rate project I'm working right now is 44.1kHz, not more than 25 tracks and 8 aux.

I've been way higher with higher sample rate without troubles. This is a relative new bug to me.