AlexMSlinin Posted June 15, 2011 Share Posted June 15, 2011 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. Link to comment Share on other sites More sharing options...
triplets Posted June 15, 2011 Share Posted June 15, 2011 Are you recording to the system drive? If yes, get another internal HD for your projects. Link to comment Share on other sites More sharing options...
AlexMSlinin Posted June 15, 2011 Author Share Posted June 15, 2011 Are you recording to the system drive? If yes, get another internal HD for your projects. No, I am already using a separate internal HD for recording. Any ideas what's causing this suddenly? Link to comment Share on other sites More sharing options...
triplets Posted June 15, 2011 Share Posted June 15, 2011 Do you have other drives connected thru FW or Time Machine? Link to comment Share on other sites More sharing options...
David Nahmani Posted June 15, 2011 Share Posted June 15, 2011 When you play the project, what do your CPU and HD meters (in the transport bar) look like? How big is your system drive and how much space is left available on it? How big is the drive where your Logic project is saved and how much space is left available on it? Link to comment Share on other sites More sharing options...
AlexMSlinin Posted June 16, 2011 Author Share Posted June 16, 2011 When you play the project, what do your CPU and HD meters (in the transport bar) look like? How big is your system drive and how much space is left available on it? How big is the drive where your Logic project is saved and how much space is left available on it? David, typically the meters are fairly low during playback, but when the error occurs the HD meter starts peaking. I'm only recording one track at a time, by the way. The system drive has over 100GB free, and the audio files drive where the project is saved has over 200GB free. Plenty of space in both cases, I think. I've only observed the problem during recording audio, not during mixing, playback or using software instruments. The only thing I can think of that changed from when I was recording vocals previously to this time is the update into 9.1.4 from whatever the previous logic update had been. My system is about 3 years old and I've never really had any major problems. This issue has come up from time to time in the past, but usually closing down Logic and restarting, and/or a reboot solved the problem. Link to comment Share on other sites More sharing options...
Homina Posted June 18, 2011 Share Posted June 18, 2011 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. 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 saw that message for the first time recently. Since I'm running a MacPro and not a laptop, it made no sense, at all. Turned out to be a flaky bay-controller card in a RAID. If you're already using a separate record drive, I'd suspect some kind of hardware problem, an inconsistent connection or component failure of some kind. My RAID drives all passed individual hardware tests, and I had to ID the problem via elimination. Replacing the RAID bay stopped the message. Link to comment Share on other sites More sharing options...
Zu Posted June 18, 2011 Share Posted June 18, 2011 I'm using a mac pro 3.0Ghz quad 24GB Ram OS X 10.7, system drive 500GB that came with the computer, 1TB Hitachi and 2 samsung 1TB Raid1, Digi 002 audio interface and i couldn't even play a project in 44.1 Khz with a few audio tracks and 3 virtual instruments. I'm already really upset because i've spent 2 entire days trying to fix that and I didn't. I think i've tried everything such as changing the buffer size on logic, i've tested the hard drives, i've changed the projects from drive to drive if it works, I've replaced the hard drives don't no how many times and changed his position and without any result, stills the same. The funniest thing in Pro tools everything is fine. Someone to help would be greatly appreciated!! Link to comment Share on other sites More sharing options...
triplets Posted June 19, 2011 Share Posted June 19, 2011 RAID drives only make sense for video, where you need bandwidth. For audio, they actually perform slower than a regular setup. Link to comment Share on other sites More sharing options...
Zu Posted June 19, 2011 Share Posted June 19, 2011 LOL, for me makes sense, if you ever use instruments like vienna or even omnisphere you knew the difference, for eg. loading a patch is so much quicker and stable. But still the problem doesn't come from the drives they are fine. I've already tried to disable the sudden motion sensor and stills the same. Thanks for replying but solutions would be so much appreciated. Link to comment Share on other sites More sharing options...
Zu Posted June 19, 2011 Share Posted June 19, 2011 I've received a song yesterday to work on it with just 15 audio tracks (no processing on it) and i'm still receiving that message. PLEASE HELP would be greatly appreciated! Link to comment Share on other sites More sharing options...
Zu Posted June 19, 2011 Share Posted June 19, 2011 I start to delete tracks from some projects and some of those after a few tracks deleted it worked fine but others I've left just 1 audio track (no processing) gives me the same message. PLEASE HELP Link to comment Share on other sites More sharing options...
David Nahmani Posted June 19, 2011 Share Posted June 19, 2011 RAID drives only make sense for video, where you need bandwidth. For audio, they actually perform slower than a regular setup. +1. I suppose you're using a stripped RAID (RAID 0)? Their seek time is typically longer than that of a single drive, so your audio performance will actually decrease (when compared to a single drive). Also keep in mind that a RAID 0 decreases your storage reliability (compared to a single drive). I highly recommend working with single drives when doing normal audio production. Try this: 1) Open the project. 2) File > Save As a new project, onto a single drive. Make sure "Save Assets" is selected at the bottom of the Save As window. If you don't have any other single drive then use the system drive for now - it's far from being ideal but will at least allow us to test whether or not the RAID is the issue here. Link to comment Share on other sites More sharing options...
Zu Posted June 19, 2011 Share Posted June 19, 2011 Thank you very much for replying!! Yes sorry my bad i did a stripped RAID Set (version 2.0). When I try to save the project into another drive I got this message in some audio files: I/O Error Result code=-36 File= name of the file here Link to comment Share on other sites More sharing options...
Zu Posted June 20, 2011 Share Posted June 20, 2011 When I play it stills the same… The only reason i find is the update i've made of OS X for 10.6.7. It started gradually and now just play's 3 or 4 sec. But the weird thing some projects everything is fine (with processing). Link to comment Share on other sites More sharing options...
mavdime Posted June 20, 2011 Share Posted June 20, 2011 I was having this error a lot recently. I had bounced down a whole lot of software instruments in my Logic project, and when I would hit play the HD i/o meter would go crazy and playback would stop and I would get the disk error/sudden parking sensor error message. I figured out what was happening in my case was that Logic was trying to read too many bounced regions at the same time and this was putting strain on the hard drive buffer. I fixed it by going through my tracks and stripping silence on all of the bounced tracks so that there weren't masses of visible regions on there that had no audio data, but that Logic was wasting resources reading nonetheless. Worked like a charm for me... maybe relevant/ helpful to you Good Luck Manny Link to comment Share on other sites More sharing options...
David Nahmani Posted June 20, 2011 Share Posted June 20, 2011 When I try to save the project into another drive I got this message in some audio files: I/O Error Result code=-36 File= name of the file here Hmm Was your RAID formatted for Mac OS X Extended? Link to comment Share on other sites More sharing options...
Zu Posted June 20, 2011 Share Posted June 20, 2011 Mac OS Extended (journaled) Link to comment Share on other sites More sharing options...
Zu Posted June 20, 2011 Share Posted June 20, 2011 Thank you for replying Mavdime, but mine is differente because I started a song 1 week ago from scratch with just 2 tracks of stylus rmx, I've recorded 3 voices, 2 bass tracks and and 1 piano track from vienna insruments and in that day nothing happened but 3 days after and i was using the project just to play to get some more ideas and it started stopping giving me that message. What i dont understand is that I started a new song yesterday with more virtual instruments and I've recorded some audio tracks and everything is working fine until now. Some old projects that I've made with less memory (10GB) now I couldn't play them, gives me the same message and when I open some projects sometimes gives me the error -39. I dont have any more ideas to fix it and actually I'm not the only one but probably could be because of the Logic update to 9.1.4 or the OS X to 10.6.7 that I've made. Link to comment Share on other sites More sharing options...
Zu Posted June 20, 2011 Share Posted June 20, 2011 I'm still having problems in projects that I didn't have...If I try to copy a midi region no problem but if i try to copy an audio file the waveform doesn't appear but some of those I can listen but some regions doesn't copy anything even if I do one by one. PLEASE HELP Link to comment Share on other sites More sharing options...
David Nahmani Posted June 20, 2011 Share Posted June 20, 2011 If I try to copy a midi region no problem but if i try to copy an audio file the waveform doesn't appear but some of those I can listen but some regions doesn't copy anything even if I do one by one. How do you copy your audio file? Link to comment Share on other sites More sharing options...
mavdime Posted June 20, 2011 Share Posted June 20, 2011 Zu, I have also had strange issues like this where one day a relatively small project was working perfectly and the next it was not.... after countless hours trying to work it out I ended up starting a fresh project and importing the instrument tracks into that project using the logic import function.... not really a solution I know, but it worked, and saved me a lot of bother in the end Maybe if nothing else works just try starting a new project with a different file name and just import the files... so you can go back to making music : ) Cheers Manny Link to comment Share on other sites More sharing options...
moda Posted June 21, 2011 Share Posted June 21, 2011 Last week, I opened up a project that I've been working on for six months. 60 tracks, half of them frozen. My MacBook Pro would have an occasional CPU overload, never an issue with my LaCie 750GB eSATA external drive. Now, I'm receiving the same HD error as the rest of you guys. Crazy... Running Logic Pro 9.1.4 on 2007 MacBook Pro w/ 3GB RAM Logic running on 500GB 7200 RPM internal drive Projects and sound library running on LaCie D2 Quadra 7200RPM eSATA HD Link to comment Share on other sites More sharing options...
Zu Posted June 23, 2011 Share Posted June 23, 2011 I've tried holding opt and drag the region, or with shortcuts. Sometimes work sometimes not, meaning the same file(s). Link to comment Share on other sites More sharing options...
rpalagy Posted June 30, 2011 Share Posted June 30, 2011 All people asking things like "are you using an external drive" and "how much free space on your drive?", etc. are missing the point. I used to use a G5 with 10.4.11 recording to an internal SATA 7200 drive (OBVIOUSLY NOT THE SYSTEM DRIVE!) and I could do at LEAST 20-24 tracks of audio PLUS several reverbs AND some audio instruments without errors. THESE SAME SESSIONS trigger the 10010 disk too slow error on a new i5 MacPro AND my new i5 Quad Core IMac with Logic 9.1.4 and 10.6.7 every few bars! APPLE YOU BROKE SOMETHING!!!! C'mon, this many of us can't be ALL missing something! Link to comment Share on other sites More sharing options...
n6smith Posted June 30, 2011 Share Posted June 30, 2011 Something I have noticed is that, on my system, while I am not seeing any real changes to the frequency of HD overload or too slow messages.. I am getting CPU overloads occurring, seemingly at random. I can start the exact same song and get lots of spiking... Stop and start it again and little or no spiking... start it again and get many spikes again... This with a song that has only three tracks (2 midi and one audio) Looking at the activity monitor shows nothing unusual other than Logic is using around 50% of CPU... when it is spiking a lot and about 40% when it isn't... Which is somewhat odd as it shouldn't be anywhere near that level given the lack of tracks I am using. My Mac is pretty clean in terms of other things running in the background so I don't think that is the issue.. Reloading an 'errant' song sometimes causes the CPU usage to drop back to 5% which is much more like it... Loading another, older song which has 30 tracks, Midi and audio mixed.. and no issues at all.... For me this occurs more often when starting Logic in 64bit rather than 32bit.. Something, somewhere and somehow is draining things... on a random basis.. Going back a couple of versions and this issue disappears... so for me it seems to have cropped up with 9.1.3 and 9.1.4 Just sharing my own experiences.. Yours may vary! Link to comment Share on other sites More sharing options...
hypnotik Posted June 30, 2011 Share Posted June 30, 2011 got the same problem.............on a SSD drive!! logic is a joke....lo(l)gic mac pro nehalem 2009 /16 gb Link to comment Share on other sites More sharing options...
Principal Skinner Posted July 5, 2011 Share Posted July 5, 2011 Ditto to the orig post - I did a software update yesterday to Logic 9.1.4... and am now seeing this error message for the first time on a Macbook I've had for over 2 years and on an arrangement I've been working on for months (and no, I haven't added any more plug-ins, audio files etc. to the arrangement) A bug with 9.1.4 perhaps? The irony is I only updated to get rid of bug on previous version that didn't allow you to change the 'bar position starts at...' in the Sync preferences. Link to comment Share on other sites More sharing options...
seo Posted July 10, 2011 Share Posted July 10, 2011 "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." Damn I got this error too I didn't get it with logic 9.1.3 so I'm wondering if it might have something to do with logic 9.1.4. I couldn't even close logic and when I tried to shut down my mac nothing happened and I had to turn it off manually by holding the power button down.. anyone else had that problem? I hope someone finds a solution soon. Link to comment Share on other sites More sharing options...
thekish Posted July 12, 2011 Share Posted July 12, 2011 is there away to revert to 9.1.3? I have this same problem after updating to 9.1.4 Obviously this is frustrating. I hope a fix is found soon. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.