Error code (-10010) - why??

Hi James A..I have been working with Apple on this problem for a year and am at the end of my rope.

This is a Sudden Motion Sensor trip alert. Laptops have sudden motion sensors..your computer does not..neither does mine..Imac 2.93 ghz i7 , 16 gig RAM. Problem is I get the messages 20 to 30 times a session.

I spent 1 1/2 weeks on the phone with Pro Aps Tech..top level. He had never seen anything like it..Apple just replaced my HD and an optical drive which stopped working..transfered my files and I have even bigger problems..with files all gone grey with no way to retrieve them.these are my Bounce, Freeze, and Audio Files.

I am a tad upset as there are about 50 songs there..or about 1 1/2 years of hard work. I sure hope that my Time Machine Backups are working better than the rest of this machine I bought..but I'm not going to try anything else on this POS...which BTW checks out fine..lol

What are you using for I/O?

OK, if you don't have a sudden motion sensor, you should take out that bit of the sentence in the error message and read the rest, because that is what is happening: you are overloading your Mac with your Logic project. And believe me, it is not too hard to overload ANY Mac using Logic, you need to know what uses lots of CPU and what doesn't.

1. Having an SI track selected during playback. Puts the SI in "Live mode" which is much more CPU intensive. Have an audio or aux track selected instead.

2. Any flexing or other realtime pitch alteration to audio is CPU-intensive. Use Freeze, or Bounce-in-place when done

3. Some synths use a LOT of CPU, very much depending on the patch. Reverbs (Space designer) are CPU hungry, as are multiband compressors. Don't forget many 3rd party synths/samplers have their own effect section, using the synths built-in effects can make a synth patch much heavier on the CPU too.

Also, a system disk that is too full (less than ± 25 % of its' capacity free) can tax the CPU, as the "dumping to disk & retrieving from disk" of RAM content becomes harder for the system.

4. Also, if you use the system disk as audio file/recording disk, you're doubly taxing it (RAM writes and reads to that same disk - that is why a separate disk for recording is recommended, to avoid "traffic" on the system disk). You should Freeze Instrument tracks that need lots of CPU, that makes a difference too.

5. And don't forget the buffer settings: set it to 512 or 1024 when playing back, and set the process buffer range to Large.

6. Also, when audio recoring is done, set all audiotracks to No Input.

Freezing:

http://documentation.apple.com/en/logicpro/usermanual/index.html#chapter=9%26sec tion=16%26tasks=true

I dont wish to hijack James's thread Eriksimon..

Everything you say is very true and important in workflow.

Two questions if you don't mind.

Why would we be getting the SMS message instead of the System Overload message?

If we get this message with 2 or 3 simple tracks running live (few if any pluggins) do you believe something else might be wrong?

Thanks

Mshark

MShark wrote:

Why would we be getting the SMS message instead of the System Overload message?

If we get this message with 2 or 3 simple tracks running live (few if any pluggins) do you believe something else might be wrong?

1. If you read carefully you'll see that the system overload message is still there. It says "sudden motion sensor blah blah, or the disk performance is not sufficient to read or write all audio tracks, or the system wasn't able to process all data in time. One single message, with three separate possible causes - it is because of reason A, or B, or C. You don't have A? Then it must be reason B or C.

Or - important word...

2. Yes. But what that "something else" that "must be wrong" is, I cannot possibly begin to even guess at. I'd have to be behind the keys of the machine in question to be able to investigate it and say something useful about it. I don't think this can be sufficiently troubleshot over the phone or via fora.

I do have an appointment at my local Apple Store to meet with someone who uses Logic.

I can read but it seems from my research in this and other forums that this message isn't that common like say..

10011.

I guess Ive done everything I can think of and that I glean from these pages here..

also getting frozen track warnings on unfrozen tracks which take 3 clicks to cancel..and my HD meeter almost pins every time I start the sequencer. I dont get it..I Just want to record..lol been doing this 2 step for a year.

Thanks for your help

Mshark

via fora

Hi, I get this same message with some projects that have worked well before.

"Disk is too slow or System Overload.

(-10010)

The Sudden Motion Sensor may have parked..."

Example I have a project where is 270 tracks (audio 200 & instruments 40 and 30 midi tracks) with many plugs. There is no hiccups or errors at all. Then another project I can´t play even 9 audio track without (-10010) error. Both projects are in the same external HD.

Sometimes saving the project with a different name will solve the issue, sometimes not. Next time you open the project, the problem will come back. Very annoying.

I have now iMac 3.4GHz i7 with 16GB RAM running latest updates (10.7.3 and Logic 9.1.7) and external 7200rpm Firewire 800 hard drive for samples.

Never happened with 13" 2009 MBP and OSX 10.5.8. I really wish we get a solution to this problem.

I still get this after a couple of years..a computer change to the same model as yours and 20 calls to apple logic support. I think it may be my tascam IO but not sure yet..LMK if you ever figure it out..lol

Hey MShark. First I want to apologize my English, I hope you understand.

Sometimes I save the "influenced" project with different name and copy audio files to new place (inside the new project folder). It do not matter if the new project folder is in the same HD as the "influenced" one.

Sometimes I make a new empty project and import everything from the "influenced" one. (This method works better for me)

With both ways I could work for a while, at least until I have to open that project again. But when the problems starts again, I do one of the above. It takes some time to wait until Logic copies the audio files, but at least you can continue working.

I had two projects, which give me that error code (-10010) all the time. I finished those and now my other projects seems to work (knocking wood).

Greetings from North

Tomi (T.V.B)

(I had to change my username because the new business account)