System overload

I'm using 16 instrement tracks and I get the message:
CoreAudio:
Disk is too slow or
System Overload.
(-10009)
Can I get rid of this? I already have my battery settings at best performance.
I have 768 MB of Memory on my iBook G4 1.33.

Thanx CB,
I was having so many problems earlier that I brought my three week old PB back to my local Apple store where I purchased the package. They wiped the disk, reinstalled the system, tested it extensively, and returned it to me...a virgin system.
I reinstalled LE, updated it, ran the program--at this point my system had never seen a new application, plug in, sound card or driver, and there were no permission issues. Just fresh LE and Tiger updated to the moment.
I loaded the demo song, no sound, no access to inserts or instruments...Turns out the check box allowing Core Audio was left unchecked during the install. Resolving this, restarted the system loaded LE and ran the LE Demo song.
At bar 141 the system stopped and I received the message:
Core Audio:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
After this, I was able to play the song at will. Is this message a warning, designed to be turned off at critical times; is that the purpose of the check box in the preferences tab? Is the message accurate? Why won't it repeat itself consistantly? I've seen page 479.
I sometimes receive it the first time I use LE or play song, though not always, certainly not like I did before wiping my disk. Of course, in music whether performing or recording glitches like this creates unacceptable anxiety.
I have made no recordings since my last post. The quality of my recordings has been very satisfactory. I just lack confidence.
I intend to buy an external HD. Won't any such device be significantly slower than my internal 7200 rpm ATA? I'm thinking I should reserve my internal drive exclusively for Logic, right?
Regarding buffer size, it was established at 512 samples during the install and that's how it was during my recording attempts so far. It is my understanding that this is conservative--a lower setting should be obtainable.
In one forum, a user of my i/o box (Focusrite Saffire) and Logic had the buffer size set to 128 samples. I'll try this and other settings, but doesn't a lower setting tax audio engine even more?
Frequently, my transport window freezes, and neither will operate or close. I have to Quit and reload LE. All my problems are difficult to replicate, which is frustrating.
Having experienced so many problems before wiping my disk, I established a practice of doing a screen capture every time I have an issue, a practice I would recommend to those suffering "issues."
I appreciate everybody's time and have probably expanded this post too far. I really enjoy Logic and look forward to feeling better about it.
TGD
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB
Powerbook G4 1.67 Mac OS X (10.4.3) 1 GB Ram, 7200 rpm HD 100GB

Similar Messages

System Overload ...i know ..I'm not the 1st ...

_History Below_
Topic : System Overload ...i know ..I'm not the 1st ...
This topic has been archived - replies are not allowed.
Your question is not answered.
Mark as answered.
Use the "helpful" or "solved" buttons to award points to replies.
Subscribe to this Topic Back to Topic List
Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 7:52 PM
Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
Imac Mac OS X (10.5.5)
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
Imac Mac OS X (10.5.5)
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
Updated
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
Perfect. Well here are some suggestions:
1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
Try these two things and get back to us. I think you'll be very happy with the results.
It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
Let me know how this works, good luck, L
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
Thanks again
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
CCTM
Posts: 249
Registered: Mar 11, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
4feet4 wrote:
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
HTH
CCT
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
*Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Much appreciated-
(TBD)
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
And free up some room on that system drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
Pancenter
Posts: 3,306
From: Southwest U.S.
Registered: Apr 22, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
4feet4 wrote:
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Groove Agent 3 loads samples into memory so I doubt if your luck will change.
The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
Free drive space now or expect more problems than you're currently experiencing.
pancenter-
Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

_History Below_
Topic : System Overload ...i know ..I'm not the 1st ...
This topic has been archived - replies are not allowed.
Your question is not answered.
Mark as answered.
Use the "helpful" or "solved" buttons to award points to replies.
Subscribe to this Topic Back to Topic List
Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 7:52 PM
Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
Imac Mac OS X (10.5.5)
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
Imac Mac OS X (10.5.5)
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
Updated
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
Perfect. Well here are some suggestions:
1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
Try these two things and get back to us. I think you'll be very happy with the results.
It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
Let me know how this works, good luck, L
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
Thanks again
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
CCTM
Posts: 249
Registered: Mar 11, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
4feet4 wrote:
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
HTH
CCT
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
*Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Much appreciated-
(TBD)
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
And free up some room on that system drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
Pancenter
Posts: 3,306
From: Southwest U.S.
Registered: Apr 22, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
4feet4 wrote:
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Groove Agent 3 loads samples into memory so I doubt if your luck will change.
The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
Free drive space now or expect more problems than you're currently experiencing.
pancenter-
Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

Solution for "Error while trying to synchronize Audio and MIDI" and "System Overload" messages

Article for those who hate Logic error windows
Seen in Logic Pro 9.1.7 on Mac OS X Lion 10.7.4
and Logic Pro 9.0.0 on Mac OS X Snow Leopard 10.6.5
Logic Pro:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
Error while trying to synchronize Audio and MIDI.
Sample Rate xxxxx recognized.
Check conflict between Logic Pro and external device.
The search in the help given as follows: overload occurs when you use a lot of tracks and a lot of effects on them, and the synchronization is lost when the selected MIDI track for recording or playback. Yes, this is all that is written in the resources. And here are useful tips that have been found:
The Bounce function allows the entire instrument track to be recorded as an audio file. This bounced audio file can then be used (as an audio region) on a standard audio track, allowing you to reassign the available processing power for further software instrument tracks. For more details, see "Bouncing Your Project."
You can also make use of the Freeze function to capture the output of a software instrument track, again saving processing power. For details, see "Freezing Tracks in the Arrange Area."
These tips - about the timing. About overload - there are no tips, except as "reducing the number of plug-ins" and "increasing latency". Zero useful tips - I got two errors in the test project with a blank audio track with no effects, MIDI drums and standard synthesizer, it was no aux buses, and the entire project was only a single plugin in the master track.
Here is the configuration of my computer:
iMac12, 2
CPU: Intel Core i5 3,1 GHz
Memory: 4 GB
And here's a project that almost immediately stops Logic, all instruments and plug-ins with the init-patch, ie not the most demanding settings:
It's sad.
When this happened the first time, I could start the project only if the empty audio track has been selected, a track specially designed so that you can at least start the project. Then, this problem has evaporated along with the changing conditions of work and I forgot about it until the last case.
I was looking for the cause of the problem in the console and the system monitor for two days, and finally I found that Logic ping to the network frequently. I remembered the exact time of occurrence of the problem, and system logs revealed that the problems began immediately, as soon as I deactivate the service of the Internet.
Solution: enable the Internet, or add a new network service on a computer with no Internet. I just created the Ethernet connection to the ip address 1.0.0.0
Logic immediately began to sing.

Hi gabaghoul
Yes, it worked for me on four different OS and Logic versions (10.6 - 10.8 and 9.0 - 9.1.6)
It does not work in some cases, hard enough to tell in which one, but you can try, it very easy: go to the net settings and create new Ethernet connection to the ip address 1.0.0.0 and connect LAN cable to the port.
Also you can try to figure out what happens in your system while Logic error occured - fot that you just start Console and search "logicpro"
Pay attention to repetitive events in a console and events with suitable timing, not so far from error
The problem may be related to the GUI or system memory, sometimes turning off Safari (or Chrome, others browsers) might help.
Message was edited by: spred

Logic error-hard drive too slow or system overload (new macbook!)

have made a few short tracks with logic with no probs. when i have tried to play the demo songs which have many tracks, i get an error msg saying hd too slow or system overload. i have a new macbook, 2.4, 2mb ram, 250 gb hd (with loads space left). airport turned off when using logic. what gives???

Samples that I am using are located on a 7200 external HD.
Is your external formatted for Mac? If you didn't buy it from a store that sells mac drives specifically, it's probably formatted for windows. You must reformat for Mac or you'll have a lot of performance issues.
I've a Macbook 2,2 Ghz Core 2 DUO with 2Go of RAM.
You should get more Ram, it's really cheap these days.
Airport is disconnected. My AUdio Buffer is 1024 in the Logic preferences.
Make sure the I/O Safety Buffer is OFF, and then set the buffer size at 256 or 512.

"system overload" in logic pro 8 on my Mac Pro with only three tracks

I am running Logic Pro 8, on a 2.66 Quad Core Mac Pro w/ only 1GB of RAM. I have not had the money for the much needed ram upgrade, yet.
The day before yesterday I opened a project I had opened many times, with only three tracks - two audio and a midi synth with only a few notes. These tracks are fairly well plugin-ed up, but this Mac Pro has always eaten them up, no problems. When I tried to play the project, I got system overloads every 2 seconds, rather precisely actually. My CPU usage reads low in logic and with iStat, but suddenly it peaks to 100% on my third core and I get the system overload.
I had my buffer size at 128, so I switched it to 1024, it worked, and then I switched it back again and everything worked like it used to!
But now I have to go through this slightly illogical little procedure everytime I open a project. I have read threads here about this subject before, back I cant seem to apply them / understand them in relation to my particular situation.
any ideas?

Join the club...wait for them to patch/update it.
I've tried the various work arounds, sometimes they work temporarily, sometimes not at all.
For the overloads the most reliable "work around" is to select each track, open the VI/FX modules associated with that track, then close them, go to the next track and repeat the process. OR, if you know all the modules (VI/FX) you're using, just open each one. This will "initialize" their existance BEFORE the audio engine hits them in playback.
My guess is LP8 tries to reduce it's memory foot print and does NOT initialize all the VI/FX in a saved project that is just opened until it actually needs to use them -- a good idea one would think. However, when you do your playback and it hits the VI/FX for the first time (after you just opened your saved project) it appears the audio engine stalls waiting for the VI/FX to initialize the 1st time around and hence the overloads error. Obviously I can't prove this since I don't have access to the code, but I'm a developer and this would be my logical guess based on the evidence at hand.
I can reproduce the problem consistently:
1. Start LP8
2. Open existing project with 3 tracks (staggered to start a different times) with different VI on each track
3. Have 3 buses with a different FX on each bus
4. Do nothing other than hit Play
Overload when it hits start of 1st track VI, stop, restart, overloads when it hits start point of 2nd track VI, stop restart, overloads when it hits start point of 3rd track.
Why wasn't something this obvious caught in testing? Good question.
Rob.
Message was edited by: Rob A.

System Overload & How to get the best G4 Performance

Okay all you Logic and OSX Gurus. I need your help. I've finally made the LOGIC leap from OS9 and have hit the SYSTEM OVERLOAD wall like many of you before me.
I've been pouring over this, and many other Forums and Blogs, for about two weeks now, and have tried many of the fixes / solutions to no avail. I estimate I'm now getting about 25% of my OS9 Logic performance from Logic in OSX.
One specific case in point is this. A four minute song sketch. No tempo changes. Four midi tracks, 6 Audio instruments and 2 EFX (1 Guitar Amp Pro, 1 Space Designer that's no even being used).
I have unsuccessfully tried to Bounce this to disc for two weeks now. The AUDIO and DISK I/O Meters barely register until the GUITAR AMP PRO track brings the AUDIO METER up to about 1/3rd usage. At various points in the Bounce the G4 will completely FREEZE, and I will have manually restart.
THINGS I HAVE TRIED, and continue to try are:
- Repairing Permissions
- Trashing Preferences
- Updating MOTU Drivers
- Changing Processor performance setting - which I cannot do BTW, because my system does not seem to support this option.
- Closing all Widgets
- Freeing up more Space on my Mac OSx startup disk (I now have 78.41 Gig available on a 114.49 Gig drive)
- Run Cocktail to clean up System logs and temporary files
- FREEZING TRACKS as a temporary 'fix'. This did nothing BTW but add more strain to the CPU and I still had about 1/3rd the usage with my GUITAR AMP Plugin (and it still crashed).
- Increased AUDIO BUFFER to 1024
So, (and I guess this is really two sides of the same question)...
1) How do I FIX this SYSTEM OVERLOAD problem, and
2) How do I "optimize" my Dual 1.25 G4 in order to get the best performance possible out of LOGIC PRO?
OTHER QUESTIONS I HAVE ARE:
- Does the G4 have the processing power needed to run LOGIC PRO?
- I'm confident adding RAM will "help" (can't hurt), but am I really dealing with a RAM Problem here or, again, can these processors really handle it?
BTW - I'm not looking for an excuse to go shopping for a Quad G5 (I mean who needs an excuse... . But, I'm really trying to determine if at the end of the day I will spend money on RAM, Hard Drives, whatever..., and then still be frustrated and end up shopping.
- Are SCSI drives a problem with Tiger / Logic? These Cheetah drives are fast (10,000 RPM), reliable, and have been great drives to record on. I'm trying to do this simple bounce to one of the Cheetahs and as I said it's just not happening.
- Does the startup volume size effect performance?
- Does the amount of free space on the start up drive effect performance?
- Firewire 400 vs 800? My sample library is on the Firewire drive, and I'm thinking this does not pull a lot on the CPU as these get loaded into memory before playing? Am I right about that? It is Firewire 400.
A long letter and a lot of questions. I thank you all in advance for any answers, guidance or direction you can give. Please also let me know if there is something I HAVEN'T asked, looked at or should be doing.
Best,
Kevin
Kevin Saunders Hayes
SYSTEM SPECS
Machine Name: Power Mac G4
Machine Model: PowerMac3,6
CPU Type: PowerPC G4 (3.3)
Number Of CPUs: 2
CPU Speed: 1.25 GHz
L2 Cache (per CPU): 256 KB
L3 Cache (per CPU): 2 MB
Memory: 1 GB
Bus Speed: 167 MHz
Boot ROM Version: 4.4.8f2
Logic 7.1.1 (885)
Pro Application Support 3.1
MOTU 896 - Latest drivers
2 - Seagate Cheetah 9 gig SCSI drives
1 - Oxford Firewire (Up to 400 Mb/sec) with EXS Library
G4 Duel 1.25 Mac OS X (10.4.3)

And after months of using Express, and a week of
using Logic, I hadn't had a system overload until
today. Now I'm having them all the time. It wasn't a
set up change, it wasn't running on the battery, it
wasn't running software monitoring, it's set up with
512 i/o buffer, medium processor buffer. And it
wasn't brought on by number of tracks - that's for
sure. After it started happenind and I took a break &
came back, I was sitting on my couch, Powerbook in
my lap, tapping a beat in with the onscreen
keyboard.... a SINGLE instrument, mind you. NO plugs,
no other tracks of ANY kind. And it happened.
There's a lot of great, relevant and very helpful info on this forum and it all helps and it all counts. But..... so many people are suffering this when moving up to Pro 7 from either Pro 6 or Express. One expects a change in system load when a major update comes along but more and more people are reporting that simply recording 1 or 2 tracks of audio, pure, no plug-ins or EQ is causing an overload whereas in the previous version(s) this was easily accomodated. This, you may have guessed, has happened to me as well. Are we to accept in 1 version increment (albeit a major one) there is such a massive increase in demand from hardware that you cannot record a pure no-plug-in stereo track? When going back to 6.4.3 it will happily record 8 at once, let you EQ and reverb and then do another 8 AND then another. With no troble at all.
It is pointing more and more towards fundamental flaws in the programming. Did L7 come out too soon? Are we just beta testing what is pro software? We are only on 7.1.1 and 6 went to 6.4.3 but at no stage was it this bad at the fundamentals of what the App is for. I love Logic, I really do, but I think, even with all the great help we are fighting what Apple should be addressing. Not that you can find/contact/talk to or get any sort of response from them.
I have tried but have gone back to 6.4.3 until 7.1.2 or even 7.2 appears, but I'm not paying for 7.2. My £200 upgrade from 6.4.3 is now sitting on a shelf desperately wanting to use it.

Core Audio Disk too slow or System Overload message

Hi, I hope somebody can help me. I've seen the topics about this already posted, but my situation is a little different. I'm only playing back three tracks of recorded audio and two EXS24 sampler instruments. I have the Logic compressor on my bass track and thats it! My Disk IO meter shows no load at all as well as the audio meter. However, I'm still getting the core audio disk to slow or system overload message. I figure with a dual 2.7 G5 and 2.5 Gigs of ram I should be unstoppable. What's happening?
By the way I'm using Logic Pro 7.1, and my sound card is a Delta 1010 from M-Audio.
Thank You, anybody for your help!
Dual 2.7GHZ PowerMac G5 Mac OS X (10.4) 2.5 Gigs of ram

Same or similar problem to you check out my recent thread
http://discussions.apple.com/thread.jspa?threadID=245528&tstart=30
Powerbook, 512, 1GHz, 60 gig Mac OS X (10.3.6)

Disk too slow / System overload HELP?

I'm really hoping someone can help me out with this!:
I purchased a G4 PowerBook around six months ago, with Logic Pro pre-installed. Since then, I have mixed and mastered lots of music that was recorded on a previous system and imported. I was running multiple tracks simultaneously with tons of plug-ins and everything ran smoothly on my new Mac. HOWEVER, within the last month, my playback capabilities have been severely reduced. When I try to play back even two tracks simultaneously (with just one compressor or reverb), I get the error message, "Disk too slow / System overload."
My first reaction to this problem was to check my disk space and see how much room I had left: it turns out I have over one third of my harddrive space still available. I checked my memory capabilities and they seem to be more than adequate. I bought new virus protection, too, and ran scans to see if that might make a difference, but it hasn't. I don't understand why this is happening on a system so new. ANY ADVICE YOU CAN OFFER WOULD BE GREATLY APPRECIATED!
Many thanks.
Powerbook G4 Mac OS X (10.4.6)

It is generally not a good idea to run logic on the same drive that contains your audio files and samples. Most of the data involved with logic whether it be programs or individual audio files will be saved physically all over the place on your hard drive. At a certain point the actual part of the drive that reads the data will not be able to move around to all the little different audio files it needs to access for the session on top of running the program and whatever other software that is up. It is best to save all your audio files and samples to a fast external drive (7200rpm at least) otherworldcomputing.com has great drives that have high quality cases and the option to put any drive they have in stock into the case. (i would recommend seagate) If you are going to continue running your entire sessions off the internal drive then you need to keep up with your basic mac housekeeping. You should repair your permissions 2 times a month (use disk utility) You should buy a good directory repair program such as disk warrior. The directory is exactly what it sounds like. It keeps track of where everything is on the computer. If your directory is corrupt the computer will have to do an extra manual search to find what its looking for. If your directory is healthy your computer will make a straight shot to the file you are looking for.

"Disk too slow or System Overload"

So while I'm doing rather simple things like recording vox or even playback, the audio stops and I get the 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."
I'm running on Intel Dual Core i5 2.3's, 4 gigs of RAM with about 230 gigs of free space. I have turned the SMS already to it can't be that. Does anyone know what the problem could be?

CosmicChild wrote:
Thanks for the reply. Mind if I ...probe... you for some more info?
Too many CPU intensive VI- what is VI?
HDDs- what is that?
thanks you!
VI = Virtual Instruments. Logic software instruments or third party software instruments.
HDD = Hard Disk Drive
pancenter-

Disk too slow and system overload error

I like many other users am having problems with the "disk too slow or system overload error (-10010)." It only seems to occur during playback attempts, seeing as I recorded with no problems yesterday, and only began happening today (granted, I have not tried recording anything since this started happening). I have tried changing the buffer size (still occurs at all levels), and, as per noted in a similar post, ensuring that my computer does not at any time put drives to sleep. All my sessions are stored on an external Toshiba Canvio Connect 2.0 TB drive connected directly to my computer via USB.
My setup (I know that this is going to draw a lot of criticism) is a macbook air with 2 gb 1067 MHz DDR3 ram and a 1.4 GHz intel core 2 duo processor, running OS X 10.9.3. While I am fully aware (I promise) that these are well below the recommended numbers, I have been using this configuration since June without any problems whatsoever.

Clancy,
No problem!
I also added it to the Useful links and resources for Logic Pro X page in the tips sections....
Cheers..
Nigel

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

Hi there, I'm a professional music user and recently switched from Pro-Tools to Logic due to PT11's lack of third party plug-in support at the moment. I was looking forward to leaving behind the error messages of Pro-Tools for the supposed plain sailing of Logic. However, after installing Logic X and starting a new session with one track of audio and 4 tracks of software instruments, I'm receiving the following error message when attemping to record a part on one of the software instruments. 'Disk is too slow or System Overload. (-10010)'
I have an 8 core Mac Pro with the latest version of Mountain Lion, 16GB of Ram and a 250GB SSD boot drive (which Logic is installed on). My sessions are ran from a secondary 120GB SSD which has 110GB of free space on it and my sample libraries are streamed from another internal 250GB SSD and a 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive. My interface is a Focusrite Scarlett 6i6 USB 2.0 and my I/O buffer is set to 512.
It is completely unacceptable to me that I should be experiencing error messages with this set up and a 64 bit DAW, particularly when the session in question only has one track of audio and one instance of East West's Play engine, spread across 4 software instrument tracks.
Has anyone else experienced similar problems or have any ideas as to what the solution could be? I'd really appreciate any advice.
Cheers,
David

Just as a quick followup....
After doing a little research online it seems the Scarlett is one of those USB2 devices that has issues with how Apple changed their implementation of USB when they released Macs with USB3 interfaces and put this updated implementation into Lion and later Mountain Lion... and that this is probably why some people have major issues like the OP is reporting and why other's do not. It depends on the hardware/OS X version combination as to if this issue rears it's ugly head.
Oddly enough some Win 8 users are also reporting similar issues with the Scarlett for much the same reason.
The March 2013 Scarlett OS X drivers are intended to 'alleviate' this issue but Focusrite have stated it is only to 'alleviate' in some instances and not completely fix the problem for everyone who has it,.,..
However, the good news is that Focusrite have released some beta drivers (v1.7b2 and later b3) which seem to work better for some people than the last official release...
Mac Only.
General stability/logging improvements:
- Improved audio stream syncing
- Fixed bug which results in occasional inaccurate timestamps
- Improves sample rate switching
- 18i20 stream formats now switch automatically
- Fixes Forte streaming at 176.4/192kHz
You can find them here..
http://beta.focusrite.com
Note: These beta drivers again seem to only alleviate the issues for some people and not all but it has got to be worth giving them a try I would think...

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

Hello all,
I'm running a G4 PowerBook, with 1.67 GHz, and 1.5 GB DDR SDRAM. My Logic set-up is Logic Pro 7 and a Motu 828mkII.
My present Logic project contains 7 tracks, with EXS24 through 6 tracks and Sculpture through the last. The instruments were triggered through a midi keyboard.
While trying to score a short film, I keep running into the following error:
CoreAudio: Disk is too slow or System Overload. (-10009). The error happens while recording and during playback only. There are times when I do not recieve the error message, but playback is terribly jerky and I'm unable to clearly see exactly where I am on the timeline.
I have searched for similar errors on this site and cannot seem to find an answer. I imagine the solution is changing the way I have my I/O setting in the CPU usage. Am I on base?
I'd appreciate any help,
Kris

Hey Cyril and 25G's,
Well I went out and bought a OWC Mercury Elite Pro Firewire 800 with Oxford 912. I transferred the EXS Factory Sample files to the OWC drive. Then I deleted the EXS Factory Sample files on the OS hard disk. Then I created the alias for the Samples and placed the alias back in the Logic file under Application Support on the OS hard disk.
The alias' seem to be working because the Logic project works. The only problem is that it is still terribly jerky.
The CPU is maxing out while the I/O meter is not responding at all. Could this be the clue to my problem?
(Also, Cyril, call me stupid, but I cannot find the Virtual Memory portion in the EXS Preferences.)
Thank you for all your help. (I am a bit slow myself when it comes to Logic and the proper steps to de-bugging a problem. So, very detailed explanations are appreciated)

Disk is too slow or System Overload.

I was working on a project that had a little over hundred tracks, and got this error. I thought that it was understandable, as I had many tracks(even though I was only recording one), so I started a new project to record it, with only one track. But I still got this error when I was recording one track, with no other tracks in the project! How can I fix this?
Here's the complete message:
Disk is too slow or System Overload.
(-10008)
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.
I run this on a 27" iMac with 8GB ram and 7200rpm, which should be enough to play and record many tracks.

ArnsteinK wrote:
so I started a new project to record it, with only one track. But I still got this error when I was recording one track, with no other tracks in the project!
But you didn't shut down Logic or (sometimes best) restart your machine in between ? Often, data gets left in memory and it hasn't had any particular command to clear it otherwise - a lot of allocated memory can be still considered as 'used'.
Well, maybe, but that aside,
ArnsteinK wrote:
I run this on a 27" iMac with 8GB ram and 7200rpm, which should be enough to play and record many tracks.
- hopefully you're not doing that just using your internal computer's drive - if you have, you've been lucky so far.
If you're into Logic it is a well established fact that this message can appear for so many different reasons and its not possible for me to know what goes on with your machine - there are plenty of articles on this forum and LogicProHelp as well as the very concise and accurate (but not always as explanatory as I'd like it to be) stuff on this Apple website.
That's all I can offer at the moment until we have some more technical information, in which case there are others here that may have particular insights as well, so you're gonna have to take it from there because there is no one answer.

Disk is too slow or system overload error with Logic 9.1.4

I have am running Logic 9.1.4 on a MacPro 2 X 2.8 Ghz (Intel) with 8GB of RAM running OS X 10.6.7.
I recently updated to Logic 9.1.4 and was trying to record one track of vocals on a session on which I had previously worked on a few weeks earlier with no issues.
But today I got this error over and over again:
Disk is too slow or System Overload.
Occasionally I would get the message below with the error, but not always:
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.
I don't have a lap top and tried a few fixes found here (buffer size increase ,rebooting etc.). Again, I recorded several tracks of vocals on other days with absolutely no problems. But today couldn't record more than a few seconds at a time without getting this error. The only difference I can think of is that I updated to the latest version of Logic 9 (9.1.4) rather than whatever the previous Logic 9 version was.
Any help at all would be greatly appreciated.

ISSUE RESOLVED!
So after messing around with this for over 4 hours today, I think I have resolved the issue.
The issue seems to have been primarily with my main vocal track, which was frozen while I was recording a harmony vocal. The main vocal track was actually made up of about 20-30 take folders which I had swiped to make one good take. I was hoping to take a good hard listen at my swipes during mixing once all recording was done, so I had never merged into one audio track. Besides, like I said, this track was frozen so I figured it was already playing back as though it was one audio file.
So I just merged all the takes in this track into one file. Counterintuitively, unfreezing about 10 tracks also seemed to improve performance in the meters. Which makes me wonder whether I should use freezing at all? Both these things together seem to have made all the difference.
In the process, I also learned how to run Logic 9 in 64-bit mode, although this (at least by itself) didn't seem to make any difference other than making AmpliTube inoperable.
So the lesson here: don't have too many take folders going at once. And freezing tracks with take folders doesn't seem to come close to being the same thing as playing back one single merged audio file.

I just installed Lion and the newest version of Logic express 9 (9.1.5) and every time i playback audio I get this error message: [Disk is too slow or System Overload. (-10010) . Never had any issues before now...

I just installed OSX Lion (10.7.2) and updated to the newest version of Logic express (9.1.5) on a macbook and every time I playback audio I get this 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]
Never had any issues before now... any ideas?

Have a look into the Preferences folder (YourUserFolder/Libraries/Preferences/) and trash all Logic preferences.
You'll have to setup the program again.
cheers
rob

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.

"LOGIC PRO X: Disk is too slow or System Overload. (-10010)" This is the message that I was having since two weeks ago with my Logic 9. I updated two days ago to Logic X and I am still having the same problem.
I recently formatted my computer. In other words, I'm not using too much memory of my HD. My Memory Ram is 8GB.

dandotcraig wrote:
A week before logic X comes out it starts bugging out... i deleted a bunch of stuff on my HD and cleaned up everything... didnt fix anything... then logic x came out and I though oh i better update that will fix everything... and im still having the same problems... its rediculous.
Umm,, no offence... but what is ridiculous... is you didn't troubleshoot the original problem but instead you assumed it was a LP9 problem so you updated to LPX which is still in its early days and is likely to be less stable than LP9... rather than more so!
So.. Here's the thing....
LP9 was working fine and then stopped working normally according to you. Therefore what changed at the time LP9 stopped working normally?
Here are just a few ideas to think about.. for around the time this started..
Did you update Logic Pro 9... OS X... Drivers for Midi/Audio or other connected devices?
If you did, did you then restore from a backup you made prior to these problems occuring and what happened when you did so? (assuming you do make backups of your system?)
Did you install any new Apps on your Mac?
Did you add a new Hard Drive? How is it formatted?
Did you start recording or creating music in a different way to how you used to before the problem started?
Have you started using a different SI or FX plugin or plugins.. More or different FX for example.. Did you install a new version of a plugin?
Is all your software legal? (Have to ask because some people install all kinds of illegal plugins and whatever else.. and have no idea how the 'cracks' work or what they might affect/mess up/conflict with in the process)
Have you looked at the System logs to see if anything is happening out of the ordinary when you get these messages?
Have you looked at OS X's Activity monitor to see if any app or routine is kicking in hard when you get this issue?
Basically, you need to think about and look for what changed... because something apparently changed to suddenly cause these issues...given you said you didn't have them until a certain timeframe and some of the questions above, I hope, will get you thinking..
....and maybe a few of the others here will come up with other ideas and suggestions to help you...
Good luck and let us know how you got on...

System overload

Similar Messages

Maybe you are looking for