[SOLVED] Too slow on 64-bit system

As I bought a 4g mem (a tot of 6g) I upgrade my arch to 64-bit, and it goes very very slow.
It takes several minutes (after download completed) to install some small software ( like vim ).
And top shows pacman used 97% cpu ( i5 M430 2 core 4 threads , a tot of 25%?).
Then I use vim to open a 100-line c file, it took about 5 seconds ( not only once! ).
It's much slower than my old 32-bit arch.
My new 64-bit windows has the same problem while the 32-bit windows goes well.
Would it be that 64-bit is supported but not well supported by my cpu? Or any solutions?
I don't know what information should be posted here.
If I should post any other information here, please tell me.
Last edited by zero2228 (2012-11-04 15:11:56)

Try takeing out the new stick of ram... you say a total of 6GB, so I assume you also have a 2GB stick in there.... Then see if Arch is still slow.
I am like 99.9999999999% sure that the i5 CPU works fine with 64bit.
NOTE: They Hyper-Threading of the Core-i CPU's is not a linear increase in speed. Like for my:
>Ivy-Bridge moble i7 - Kernel 3.6.5-1-grsec - Hyper-Threading enabled
->/etc/makepkg.conf set to "-j2" (two threads)
It takes ~32min's to compile the Linux Kernel
->/etc/makepkg.conf set to "-j3" (three threads)
It takes ~27min's to compile the Linux Kernel
->/etc/makepkg.conf set to "-j4" (four threads)
It takes ~22min's to comple the Linux Kernel
> 100*(1-(22/32))
[1] 31.25
So, the Hyper-Threading gives my i7-3520M about 30% more speed. Which is good. I read that the Pentium 4HT only produced 20% more speed.
Last edited by hunterthomson (2012-11-04 02:05:51)

Similar Messages

  • [SOLVED] mplayer says that the system is too slow?

    I've noticed that mplayer has been complaining that my system is too slow to play videos lately.
    mplayer CLI output:
    AVI file format detected.
    [aviheader] Video stream found, -vid 0
    [aviheader] Audio stream found, -aid 1
    VIDEO: [XVID] 640x352 12bpp 25.000 fps 1537.8 kbps (187.7 kbyte/s)
    Clip info:
    Software: Nandub v1.0rc2
    ==========================================================================
    Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
    Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
    ==========================================================================
    ==========================================================================
    Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
    AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000)
    Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
    ==========================================================================
    AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
    Starting playback...
    VDec: vo config request - 640 x 352 (preferred colorspace: Planar YV12)
    Could not find matching colorspace - retrying with -vf scale...
    Opening video filter: [scale]
    VDec: using Planar YV12 as output csp (no 0)
    Movie-Aspect is 1.82:1 - prescaling to correct movie aspect.
    [swscaler @ 0x89d5f50]SwScaler: using unscaled yuv420p -> bgr24 special converter
    VO: [gl2] 640x352 => 640x352 BGR 24-bit
    [gl2] You have OpenGL >= 1.2 capable drivers, GOOD (16bpp and BGR is ok!)
    [gl2] antialiasing off
    [gl2] bilinear linear
    A: 866.0 V: 866.0 A-V: 0.012 ct: 0.099 21651/21651 2% 3% 0.2% 4 0
    A: 868.6 V: 867.9 A-V: 0.763 ct: 0.099 21698/21698 2% 3% 0.2% 50 0
    **** Your system is too SLOW to play this! ****
    Possible reasons, problems, workarounds:
    - Most common: broken/buggy _audio_ driver
    - Try -ao sdl or use the OSS emulation of ALSA.
    - Experiment with different values for -autosync, 30 is a good start.
    - Slow video output
    - Try a different -vo driver (-vo help for a list) or try -framedrop!
    - Slow CPU
    - Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
    e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
    - Broken file
    - Try various combinations of -nobps -ni -forceidx -mc 0.
    - Slow media (NFS/SMB mounts, DVD, VCD etc)
    - Try -cache 8192.
    - Are you using -cache to play a non-interleaved AVI file?
    - Try -nocache.
    Read DOCS/HTML/en/video.html for tuning/speedup tips.
    If none of this helps you, read DOCS/HTML/en/bugreports.html.
    mediainfo output:
    Format : AVI
    Format/Info : Audio Video Interleave
    File size : 698 MiB
    Duration : 58mn 0s
    Overall bit rate : 1 684 Kbps
    Writing application : Nandub v1.0rc2
    Writing library : Nandub build 1852/release
    Video
    Format : MPEG-4 Visual
    Format profile : Streaming Video@L1
    Format settings, BVOP : Yes
    Format settings, QPel : No
    Format settings, GMC : No warppoints
    Format settings, Matrix : Default
    Muxing mode : Packed bitstream
    Codec ID : XVID
    Codec ID/Hint : XviD
    Duration : 58mn 0s
    Bit rate : 1 538 Kbps
    Width : 640 pixels
    Height : 352 pixels
    Display aspect ratio : 16/9
    Frame rate : 25.000 fps
    Resolution : 24 bits
    Colorimetry : 4:2:0
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.273
    Stream size : 638 MiB (91%)
    Writing library : XviD 1.1.2 (UTC 2006-11-01)
    Audio
    Format : MPEG Audio
    Format version : Version 1
    Format profile : Layer 3
    Codec ID : 55
    Codec ID/Hint : MP3
    Duration : 58mn 0s
    Bit rate mode : Variable
    Bit rate : 133 Kbps
    Nominal bit rate : 128 Kbps
    Channel(s) : 2 channels
    Sampling rate : 48.0 KHz
    Resolution : 16 bits
    Stream size : 55.1 MiB (8%)
    Alignment : Aligned on interleaves
    Interleave, duration : 24 ms (0.60 video frame)
    Interleave, preload duration : 477 ms
    Writing library : LAME3.90.
    Encoding settings : ABR
    ~/.mplayer/config contents:
    vo=gl2
    monitoraspect=16:9
    Any ideas?
    EDIT: Well, it looks like adding "ao=alsa" to ~/.mplayer/config did it. I guess that it uses OSS by default, which is apparently too slow.
    EDIT 2: If anyone else can offer any mplayer performance tips, I'd still appreciate them.
    Last edited by mrbug (2008-10-24 00:42:05)

    Perhaps. Also, in that error message, do as it says and play around with combinations of those.
    Possible reasons, problems, workarounds:
    - Most common: broken/buggy _audio_ driver
    - Try -ao sdl or use the OSS emulation of ALSA.
    - Experiment with different values for -autosync, 30 is a good start.
    - Slow video output
    - Try a different -vo driver (-vo help for a list) or try -framedrop!
    - Slow CPU
    - Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
    e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
    - Broken file
    - Try various combinations of -nobps -ni -forceidx -mc 0.
    - Slow media (NFS/SMB mounts, DVD, VCD etc)
    - Try -cache 8192.
    - Are you using -cache to play a non-interleaved AVI file?
    - Try -nocache.
    Read DOCS/HTML/en/video.html for tuning/speedup tips.
    (Taken directly from your post )

  • Logic Express says "Disk is too slow or system overload (-10010)"

    I have a brand spankin new white MacBook. It has Intel Core Duo 2.1 processors, with 2gigs of RAM, and Leopard 10.5.6 OS. I am using Logic Express 8 and every now and then I will get an error message "Disk is too slow or system overload (-10010)
    I checked the requirements for Logic Express 8 and I exceed them. Could I still need more than 2 gigs of RAM?

    I got the same problem when I was recording 10 tracks while using SW monitoring. For a short while it went OK but then twice in a row I got this message about the disk being too slow. The result was that I got a real loud noise on the headphone. But after that the recording just proceeded. I had to stop because otherwise I think the musicians would have gone deaf. However I had to continue with recording for some more hours so I tried to solve it. The following worked for me. I turned off 24 bit recording because I had the impression there was too much data being written. I also made the buffer as low as possible (32). After that I did not have a problem anymore and recorded for about 7 to 8 hours in a row.
    So I suspect that the HD is indeed too slow or has not enough cache. As far as I can see my HD has 8 MB RAM and runs at 5400 rpm. I wll ask Aple support if this could be an issue when recording large amounts of data. Note that I have 4 GB RAM and still got the problem so that is not the cause of this issue here.

  • Logic 9.1: Disk is too slow or system overload (-10010)

    After updating I kept getting this error: Disk is too slow or system overload (-10010)
    Can't go five minutes without encountering this. I'm in 32 bit mode using record via rewire. It's maddening and I am now kicking myself for updating. The song that's doing this is a song I was using working on the day before I updated. I had no problems then.
    Anyone else encountering this?

    I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
    http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
    Or, you can search the forums for error 10010.
    The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
    I hope this provides some insight.
    Chris

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

    I keep getting this error when I'm playing a song that has 16 tracks and effects on each track, but each track is frozen (!): CoreAudio: Disk is too slow or System Overload. (-10010). I'm running a G4 and have 2G RAM. Is this common? What can I do to prevent this? Thanks for any advice you can give!
    -David

    In addition to Rohan's suggestions you have more options depending on how you work and what phases of the project you are in.
    Something overlooked very often is polyphony enabled for the EXS24-some patches are set to 64 drop the polyphony to either the minimum you will need or less (if less you will notice older notes cutting out-but you can set it to the necessary number upon bounce or export). Some mono patches from sound designers are set to 32 or 64-even if you enable unison this is often worthless.
    Up your buffer size-I usually have my PBook at 512-I usually do offline editing, location recording and sound design with the book anyways.
    Export the track.
    Set virtual memory in EXS prefs to 'on' and with the largest RAM allocation-slow disk, lots of activity.
    If you use certain exs patches often but only parts of them trimming the excess off the instrument can improve performance. If you have a piano program with good samples you can initially create a lite version with 2 velocity layers and then when it is time to get things sounding good revert the instrument to the original 5 layer-obviously this makes a huge difference depending on what you are using the piano for, leave it if it is critical.
    Save the Channel strip and export as audio file while keeping the sequence in your session. Like Freezing but you can manually trim the file start position and set the bit depth. Freeze files render from the start until the last audible sample and then truncate the tails, meaning even if you can't hear it it is still pulling "silence" from disk as long as there is sound after it. Exporting as 24 or 16 bit will effectively reduce your file size by 25 (24bit) or 50 (16bit) percent. If you know you don't have to edit a performance for weeks to come exporting it will solve alot of problems for CPU.
    Someone should back me up on this one but at the moment I want to say EXSamples load into memory regardless of freeze settings-reducing your resources.
    Disable the filter (if live or playback-N/A with Freeze)-it is often not critical for some patches. The more synthetic sounds or sounds with fewer/shorter samples rely on them.
    Disable Unison.
    Most sample libraries were not recorded at 88/96k-there is no benefit in running them in sessions in these Sampling rates as far as the EXS sound quality goes.
    That should keep you busy for a while, just some tuning to up your system performance.

  • 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 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. 

  • Disc is too slow or system overload

    "Disc is too slow or system overload"
    right in the middle of a project. stupid question. what can i do? won't even play. can't even bounce it.

    Was dealing with that, among other system/disk response issues last weekend. This weekend I researched it extensively and found 2 things that, knock on wood, so far have seemed to resolve my issues. One Mac white paper suggested that when using an external drive, you must format it as MAC Extended, and NOT include journaling. This paper was dated in 2006, but the theory made sense to me, so I tried it. BTW, it also emphasizes that you NOT get rid of journaling on the main HDD of the computer. The other thing I stumbled across was a little download calls "ProKitUpdate 4.5". It is supposed to make your 'professional' apps run smoother. I also downloaded and installed that. I then set up a test with 8 inputs, recording at 48K x 24 bit (what I was doing weekend before last), and recorded for about 2 hours. During that test, I had no beachballs, no dropouts, no 'disk is too slow' errors, and as a matter of fact, no errors at all. At this point, I'm feeling more comfortable with the setup, but am still planning on some more testing before I assume the problem won't happen again.
    Charley

  • Disk is too slow or System Overloaded ERROR

    I have logic studio and a macbook pro and keep getting the following error message:  Logic Pro:  Disk is too slow or System Overloaded (-10010)  Not sure how to fix it.  Any suggestions?

    It's a bug in logic. It's been there since multicore CPUs came out.
    Try putting your fx on a bus/aux rather than on the same track as the instrument.
    That way it will trick logic into using a different core for the different tracks.
    I've seen this problem on dual quad core CPU mac pros, so it has nothing to do with your CPU performance.
    Also if your recording to the internal harddrive whilst playing back audio from it you might run into problems when using bfd2 or addictive drums or any other large sample library type plugin.
    In my MacBook pro I took the DVD drive out and put in an SSD for the OS in its place.
    I then use the internal mechanical drive for recording and samples etc.
    This solved all my issues and made everything so much snappier.
    It's dead easy to do too. Infact it works so well I'm thinking about getting a standard MacBook pro (so I can do the same thing again) instead of the retina one.
    I'd refuse to buy a retina one until I have seen logic play back  1 instance of bfd2 a few audio files whilst at the same time recording a guitar through amplitube 3. I'm not paying £2000 if it can't do that. (you'll be surprised)
    Like I said my old one couldn't do it due to the overloads you mention until I did the DVD drive swap trick.
    The retina looks good but, 1/4" thinner is one thing, but having to carry leads and adapters for everything it kind of defeats the purpose!
    I would need a thunderbolt to FireWire adapter (which aren't out yet) a FireWire 800 lead and a FireWire 800 to 400 adapter jut to plug my apogee duet soundcard in! ***?
    I'd buy a thunderbolt audio interface but their are no mobile ones. The only ones that are out are large ones for the studio (And mac pros don't even have thunderbolt)
    It makes no sense, no sense at all!
    You couldn't make it up. At least they have dropped the dongle from logic so I can plug my mouse in.
    Emagic should release a pc version again. These quarterly decade updates are getting boring!
    Where's logic X?

  • Error message!!!!!Disk is too slow or System Overload this keeps coming up?

    Logic Pro:
    Disk is too slow or System Overload
    (-10010)
    Mac book pro
    10.5.8 OX
    4gigs RAM
    recording to ext 800 firewire drive
    any ideas???

    I am just reposting my response to a similar question because I never found a solution to this problem just a work-around. I would love to know the actual solution.
    I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
    http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
    Or, you can search the forums for error 10010.
    The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
    I hope this provides some insight.
    Chris

  • CoreAudio. Disk is too slow or system overload

    Hi. I am writing you to ask something that might be simple. I am working with Logic 7 pro and with a Powerbook 15 inch, processor 1.25 and ram of 1.25. When I am reproducing some files I got the message:
    Error
    CoreAudio. Disk is too slow or system overload.
    I will appreciate any help
    My mail is
    [email protected]
    Thanx a lot.

    Hmm, I agree with David, get an external firewire drive. I think that the internal disk on your powerbook is 5400 rpm, which can be quite slow. It certainly is not the RAM if you are only running a few tracks. It will probably be the audio data that cannot be read quickly enough by the hard drive. The solution that they might have been about to give you could have been resolution and word length of the audio files you are recording, Are you recording at 44.1khz and 24 Bit? If you are recording higher, try bringing it down if you want CD quality to 24 bits and 44.1khz. Obviously when mastering it it will be dithered, but I, and pretty much everyone else here, would advise recording at 24 bits rather than 16. As for external drives, go for something like 7200 rpm (I think that's what mine are), although you will find faster and much better! I hope this helps, keep asking questions as there are many people here who are very (and much, much more than me hehe) capable of helping you out, and we're all here to learn. Good luck and all the best, Fred

  • Disk is too slow or system overload (-10010)

    Yes I have searched but I couldn't find an actual solution to get logic to stop doing this every other minute (literally). I used to think the 'smart' snap feature was the most annoying thing in logic, but this waaaaaay surpasses it.
    Anybody found a solution yet?
    Logic 9.1.0 32 bit.

    The thing to remember is that the infamous 'disk too slow' or 'CPU too slow' error messages aren't just some random bug that needs fixing. They are actually warnings that are there for a reason. You'll get them in any DAW - or any kind of audio or even video application - that needs to do a lot of disk read/writes and CPU work in realtime. There is plenty of advice out there on how to optimize your system to get it to perform as best as it can (even in the Logic documentation), but there is obviously a physical limit to how many tracks and plug ins you can use. When you hit this limit, then all the warning is telling you is that your drive or CPU are actually too slow for the task at hand. At that point, there are other workarounds (like freezing tracks, adjusting buffer and other settings, or bouncing subgroups etc) to keep you working. In some cases it might mean that your work is beyond the capabilities of the machine you're using, in which case considering getting a faster Mac and/or faster hard drive(s) is the next solution.
    Another thing to keep in mind is that Logic uses a kind of resource optimization process, built in to the audio engine. This means that sometimes you'll get a 'disk too slow' error in some part of your song, but when you play through that part a second time, you don't get the error again. This behaviour is markedly different to how other DAWs work, notably ProTools, where the disk and CPU resources are pre-allocated to guarantee performance up to a pre-defined maximum limit of tracks.. The upside of Logic's dynamic engine is that it allows Logic to squeeze out every last drop of power it can get it hands on, by not doing any processing on tracks that aren't playing audio at a given time. But the downside is that you can get CPU or disk too slow errors at seemingly random places. It can be confusing to see a disk too slow message when playing a certain passage, and then not seeing it again in exactly the same passage later.. leading to people wondering if it truly is random, and a bug. But it isn't a random bug, it's just the way Logic handles audio in an effort to get the highest track count possible at any given time.
    Btw, @ fuzznormal: While I agree with pretty much everything you said, you make it sound like a MacBook Pro's internal drive is slower than it really is. Honestly, even if you have put in dedicated SATA II cards or some kind of decent SCSI in your G4, the system buss alone on those old machines is at least an order of magnitude slower than the system buss on any current Mac.. It creates a pretty formidable bottleneck which wipes out a significant amount of any speed advantage the G4 with dedicated drives might have over a MacBook Pro using its humble internal. I (like everyone) used to have a snazzy G4 with a fast SCSI card (I think it was SCSI anyway), and there's no way I could get anywhere near as many tracks running as I can now on my MacBook Pro using the internal drive. Of course I don't usually use the internal drive for audio, but on the occasions that I've had to, it happily chugged out more tracks than my old G4 could, with very rare disk overloads.

  • Disk is too slow or System Overload. (-10010) on Mac i7

    Hello dear Logic users,
    My problem is: I use Logic pro X on iMac i7  X 3.4 Ghz with 16 GB of RAM running OS X 10.9.2. Mavericks.RME 400 firewire.Speed of hard drive jumps to 100 - 130 Mb/s. Hard drive Rotational Rate:7200
    Logic cannot play more than 60 WAV audio tracks. When I add more than 60 tracks I get error letter " Disk is too slow or System Overload " So that is wonderful that system can't run more than 60 tracks. So i did not try yet software Instruments tracks.
    Maybe someone is confronted with such the problem?Or is my hard drive bad, or maybe here should be performed specific settings on Logic?
    Any help will be so much appreciated!

    Hi
    LOGIC wrote:
    My problem is: I use Logic pro X on iMac i7  X 3.4 Ghz with 16 GB of RAM running OS X 10.9.2. Mavericks.RME 400 firewire.Speed of hard drive jumps to 100 - 130 Mb/s. Hard drive Rotational Rate:7200
    Logic cannot play more than 60 WAV audio tracks. When I add more than 60 tracks I get error letter " Disk is too slow or System Overload "
    It is generally accepted that it is not a good idea to be running audio projects from the OS drive.
    You do not mention what Bit depth, Sample rate etc. Higher sample rates mean larger files, means more work for the drive.
    CCT

  • Logic Express "disk too slow or system overload"

    Hello,
    I'm brand new to all this and have just started going through the tutorials that come on the DVD with the Mark Sitter book for Logic Pro and Express. i have a brand new MacBook Pro and can't seem to get beyond the first ten seconds of the demo song without it bogging down with an error message that reads "Core Audio: Disc is too slow or system overloaded. (-010010)". The funny thing is that the CPU meter is barely registering any activity. Any words on this for a rookie?
    Thanks.
    Darthpolski

    I found some Hard Drives that seem to be super small and FW800 with a rotational speed of 7200. They're made by a company called GTech. i think it's called the Mini. Has anyone had any experience with these for my application? I have a Lacie but was hoping to keep the system a bit more concise.
    Thanks,
    Darthpolski

Maybe you are looking for

  • Open save dialogue box wehn run servlet program

    hi, i m having one servlet file(Write_File.java).. in this prog i retrive some data form one table and write into one file(c:\\write.be).. its automatically stored tat file in server machine.. now what my issue is when i run Write_File.java, it sholu

  • Re: we do not recognize your sign in details

    Few days ago I was kicked of my skype. Trying to log in again produced the same result: we do not recognize your sign in details. Meanwhile I created a new account, but lost important contacts. The problem is that I can not access registered email ac

  • Using third party headset with Retina Macbook Pro (microphone issue)

    Good day, everyone! I have very strange issue with my Retina Macbook Pro (Late 2013) OS X 10.9.3 When I plug in my Steel Series Headset, its microphone not recognised by system and only "Internal microphone" available in Settings - Sound - Input. Hea

  • Problems Freezing

    I have been having this problem with my Macbook Pro lately. It keeps freezing on me, I can still move the mouse and iTunes still plays, but nothing else will work. I can't force quit anything, I can't change the volume, nothing. I have over 18gb of h

  • Linking po_distributions_all and ap_invoice_distributions_all

    Hello All, How would I link the two tables po_distributions_all and ap_invoice_distributions_all to get freight or misc charges that are allocated in payables or manually entered? I need to write a report that shows item#, po#, inventory_type, receiv