System Overload (LPX) - more RAM or SSD?

I am an amateur producing EDM with Logic Pro X and after a couple of tracks, I get system overload quite often.
The machine is a MacBook Pro mid-2012 (non retina) with 500GB 5400rpm HDD, 4GB ram and i5 2.5ghz.
Therefore, I'm thinking about upgrading my mac, but I have a really tight budget after spending a lot of money on plugins for LPX,
so should I get a 256GB SSD or upgrade my RAM? And if I upgrade my ram, should I take out one stick and put an 8GB in for a total of 10GB, use a single 8gb stick or 2x4GB?
Thanks.

For what it is worth.. I just got hold of a WD VelociRaptor Duo Thunderbolt 2TB for $550 off of Amazon.. and the beast really flies...
It actually clocks faster than any of my Samsung SSDs.... coming in at 389GB/sec for reads and 383GB/sec for writes over Thunderbolt... and holds steady over repeated tests I have run today... and it's 2TB folks... which is great for storing and accessing large K5 libs...
Worth a look at imho....

Similar Messages

  • Should I keep my MacBook Pro or exchange it for more Ram and SSD space?

    Hello,
    I decided to purchase a MacBook Pro 15 inch with Retina display. I thought I would just bite the bullet and get it with the upgraded 16gb Ram and 512 SSD as I want this computer to last me at least 5 years. I don't know exactly what I will be using it for but potentially I will be running a small business with it as well as using it for photos, some videos and all the other things we all use everyday. This brought the total price tag up to about $2900 before tax. Way more than I wanted to spend, but again, I plan on this being my last computer purchase for at least 5 years...and this would be my only computer...not a secondary one but the primary one.
    As I was asking the guy in Best Buy about any sales or discounts, he mentioned a MacBook Pro with retina display that was just retuned to the store by a lady that decided to go with a MacBook Air instead.  It had been opened but not used and was in perfect condition. The sales manager said he could sell that one to me for $470 off the normal price. The problem was, it was the base model and only had 8gb Ram and 256gb SSD storage. So, I had the option of buying the computer I wanted...that I know would last me for years and years, for $2,900 OR buy the base model for $1,729. What would you do?
    I decided to buy the base model as it was just to good a deal to pass up. Now, 2 days later, I don't know if I made the right decision. I know that 256gb of memory is not going to last me very long...especially considering how much more space modern software takes up nowadays...and its only getting worse. My solution is to just buy an external hard drive and store everything I don't immediately need on it. But I don't know if I'm being realistic as maybe it will be a major pain to constantly have to carry around an extra storage device. Then again, even if I had the 512 SSD model MacBook, I would still eventually run out of space and need an external drive. Has anyone else relied on an external device for their daily computing needs? Is it a major nuisance or easy to get by with?
    My bigger concern is that it only has 8gb of Ram and can NOT be upgraded in the future. 8gb ram is fine right now, especially with the flash drive and i7 quad core processor, but in a couple years, I'm afraid  it won't be enough and that ill be forced to purchase another computer. The sales manager said that because its a Mac and because of the "monster processor" that the 8gb of Ram will be more than enough for years to come. According to him, Macs require less Ram than PC's due to their operating system being much more efficient. (This is my first Mac so I'm a bit unfamiliar)
    So this is my dellima, should I return the base model and buy the one I originally wanted or should I make do with the base model and be thankful for the great deal I was able to get?
    Will the 8gb of Ram be enough in a few years? I realize that depends on what I'm using the computer for but, since I'm not sure what my needs will be in the next year, lets assume I'll be using it to run a small business as well as the typical storage of pictures and home videos, etc.
    Bottom line, will the 8gb of ram be enough to prevent the need to buy another computer for another 5 years or so or do I need to suck it up, return the base model, pay the extra $1,100 and get the 16gb of ram I originally wanted?
    Sorry for the long story, I just need some solid advice as money is tight and I want to make the right decision. I'd rather pay $1,100 extra now and not need to buy a new computer for 5-6 years than save the money now but have to buy a whole new computer in 1-2 years.  If however, the 8gb ram will still make for a solid computer in a few years, I will gladly save the money.
    Thanks in advance for your help. ;-)

    Generally (and in my opinion):
    1) do not buy any computer you cannot replace the hard drive and the RAM in.
    2) do NOT (EVER, EVER, EVER) purchase RAM or expended hard drive from any vendor (like Apple, Dell, etc).  they mark up the RAM
    purchase the lowest machine that will work for you and upgrade the RAM and hard drive down the road.    Just look at the price Apple charges for the upgrade from 4GB to 8 GB:
    Apple is charging the (4GB RAM + $100) for the 8GB upgrade.  You can easily get 8GB for $100.  later you should be able to get 8GB for $60.
    Same thing for the hard drives:
    Applis charging the price of (500GB + $100) for the 750GB drive.  I just bought a 750GB notebook drive for $99
    I, personally, would return the retina notebook for a MacBookPro that you can upgrade the hd and ram

  • Upgrade: more Ram or SSD ?

    I am using a Mac mini 2009 with 2 GB Ram Mac OS 10.5.8
    It looks like there are two options to upgrade my Mac.
    1. upgrade the Ram from 2 GB to 4 GB
    2. replace the internal hard drive with SSD
    I just want to improve the overall performance.
    Which one would you recommend?
    Thank you.

    Of course, the ultimate prize would be to upgrade both, but for overall performance, go SSD.
    The difference is so noticeable and rewarding.
    I had an early 2008 MB Pro 15" which I'd used a Cardbus SSD in the Expresscard slot for over a year. Now I have a current model MB Pro 15" which I do love, but in many respects it's no faster than my old one with the SSD.
    If you are planning to do a lot of video editing and transcoding, image editing, etc. then the SSD has less noticeable improvement and is better served by better CPU and more RAM. But if you're consuming content, using social networking, importing and managing lots of files, databases, etc. then SSD it is. Reboots, launching multiple applications, Cmd+Tab(bing) between apps are all accelerated greatly by SSD.
    An interesting idea, I've seen positive reacting to the new hybrid drives form Seagate which combine SSD with traditional HD storage. This way you still get 500GB but also, SSD and lower cost. In fact, then you could buy the RAM too!

  • More Ram or SSD?

    Dear All,
    I want to buy a new iMac but I'm not sure if I should get it with more Ram 32GB or more space in the SSD the512GB Flash Storage.            
    I'm a TV producer and I process a lot of video files in Final Cut and pictures in CCS 6, which configuration would it better in terms of efficiency and render process.
    Thanks a lot for your input.

    you asked us in a Mac Pro tower forum. We have option of doing both as needed on our own with adding RAM as needed up to 48/64GB and more, and 4 x 4TB hdd plus 2, 4 SSDs on PCIe SSD card.
    Don't they have a Fusion drive also as an option? Or SSD and hdd was an option too.
    If you get a new iMac you will need scratch disk for even CS6 it has not gone away, your media on (or in) a Thunderbolt case.
    See what www.macsales.com has to say about possible upgrades. It is easier to do with the 27" iMac.
    Tips on and benchmark tests on CS6 and probably an iMac
    http://www.macperformanceguide.com
    The iMac high-end with 3.9GHz 4-core is nice but expensive.
    For now better in cpu tests than a Mac Pro but there is something coming out in fall (October?) Mac Pro 2013 6,1 w/ up to 12-cores, 64GB.
    Right now the Mac Pro w/ 6-core 3.33GHz and 24-32 or 48GB RAM plus all the storage you need. And 24GB seems to be minimum sweet spot for CS6 though more is better and when working with a lot of large fils then even 96GB isn't 'too much.' And a couple PCIe SSD controllers (4 x 256GB SSD for 1GB/sec and 1TB storage).
    Adding 1TB of SATA3 SSD with Apricorn and Highpoint RAID to my 2009 MP
    http://forums.macrumors.com/showthread.php?t=1504491
    Real world experiences with Sonnet Tempo Pro and 2 Samsung 840 Pro SSDs
    http://forums.macrumors.com/showthread.php?t=1605500

  • Will adding more RAM reduce system overloads?

    I'm running Logic Express 8 on a mac mini (core 2 duo) with 2GB or ram. I was thinking of adding more RAM (4 or 8GB). I tend to see "system overload" errors often. Generally, rebooting seems to fix the issues. Do you think adding more RAM would make any difference? Generally I have maybe 15-20 tracks.
    Thanks

    No, unless the overload has to do with RAM, which it ususally hasn't.
    Nevertheless, adding RAM is a very good idea to help instruments with high RAM requirements like EXS24.
    To reduce system overload:
    - let Logic be the only open application
    - if necessary, raise the audio buffer in the preferences to the next higher value.
    - while playing back, have an empty audio track (or the master track) selected.
    Fox

  • The best DAW for Logic and big sample libraries... no more system overload

    I'm planning on going big and getting the Mac Pro Two 2.66GHz Quad-Core Intel Xeon, 16 GB of RAM and add two additional 1 TB drives, one for samples and one for projects. It's been suggested that I include a RAID 5 and that it will make streaming of the samples faster and also safer and more reliable for backing up data.
    With my current setup I constantly have to freeze tracks of sampled instruments or I get system overload.
    Do I need RAID or am I better off without it?

    Gabe Garza wrote:
    With my current setup I constantly have to freeze tracks of sampled instruments
    I'm not sure why you consider this a bad thing.
    Having to constantly freeze/unfreeze takes time and disrupts workflow. It's a good option to have if you need it, but much nicer if you don't.
    Johnny,
    I would strongly advise against diving straight in with 16GB of RAM. There are a lot threads around that discuss how much RAM Logic can even recognize, you should check them out. I don't remember the details very well, but I feel like 16GB was more that it can handle (maybe that was just for ESX...). In any case, don't buy a Mac pre-installed with all that memory; Apple charges way too much for their RAM, and you can find perfectly functional, guaranteed RAM from third-party sellers. I bought my Mac Pro with the base amount of RAM and have added as needed, and I recommend you do the same.
    When you play your projects, look at your CPU window.
    Look at the Audio and Disk I/O meters.
    If Audio is peaking, you need more CPU's
    If Disk I/O is peaking, a faster I/O on your hard drive is needed.
    I would also recommend doing this. Are you getting "core audio overload" messages, or another type? If you get core audio overload messages while your System Performance meters aren't peaking (or getting close to it), getting a faster machine isn't necessarily the answer. Core audio overloads are kind of tricky--some people with slower machines get them rarely, others with very fast machines get them often. If you haven't read up on this issue, I recommend you do so.
    I'm not too savvy on RAID arrays, but I have a few thoughts. How likely are you to need your PCI slots for other cards? The specs for the Mac Pro lists 3 PCI slots, which I believe means 3 empty ones, i.e. doesn't include the one that holds your graphics card. Do you expect to add a second graphics card? PCI based audio interface? Anything else like that? A RAID setup will occupy one of those PCI slots, just keep that in mind. Second, while a RAID 5 array is a pretty secure way to store your data, you ought to have an external backup drive anyway, so maybe it wouldn't be worth it ($700 for a RAID card, yikes!). Lastly, it's likely that any of the most popular 1TB drives (search barefeats.com for some articles on these) will be sufficient to do what you need them too. I don't know how involved your Logic sessions are, but I've never maxed out my disk I/O while using my Western Digital Caviar 640.

  • System Overload = Ram or CPU

    i get a system overload with sessions.
    ive got all my drums tracked out...Kick, Hi hats, shakers, snares, claps, as well as synths, strings...stuff like that.
    PLUS vocals and their effects on them.
    i keep getting a overload error and my question is this a Ram issue, or a CPU issue.
    ive got a macbook core 2 duo...so i hope its not a CPU problem.
    thanks in advance!

    Hi Tim,
    you really don't say how much ram do you have,
    you should have all you can afford at least 1 GB,
    Also I think your main problem is your internal HD
    that runs at 5400 rpm, to audio you should have
    and external running at 7200 rpm (firewire/USB2).
    While you don't have what I'm stating above,
    try to freeze tracks, to prevent those error messages all the time.
    The freeze button, it's a "snow flake" on the right of the Record or mute buttons.
    Regards,
    Jorge

  • "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 on brand new MBP 15"

    Hi everyone,
    Last week i bought a new 15" retina Macbook pro (2.0 Ghz quad-core i7, 8gb RAM, ssd). I mainly plan to use it for recording and mixing in Logic. With my previous macbook (13"  2011 model, the cheapest at that time) i got the system overload quite frequently. I bought this new 2000 dollar Macbook, and I still get this error.
    Don't get me wrong, I understand what this error means and why it's there, it's just that I thought such an expensive machine would be able to handle this easily. There is one core that it continuously spiking and 4 others are only at 15%. My overall CPU load (according to MiniUsage) is only around 15% when I get the error. Also, the fans are completely quiet.
    Is there a way to push my macbook into full processing power? Or is your advice to buy the even more expensive one? I understand that the cores are 'only' 2.0 Ghz each, but is this not enough for logic? Should I return this one if this is what I plan to do with it?
    Again, I am aware of the tricks to reduce the CPU load (split track and plugins, Low latency mode, select an empty track etc) and I know logic can only assign one thread to one core, but I don't want this to be neccesary on a brand new two thousand dollar machine.  On top of this it seems it's not pushing the CPU when it's needed.
    So I think my question is, should i buy a different system, or is this just normal for a new macbook pro? Because now I'm kinda stuck with a "bad bargain" feeling.
    Some advice would be greatly appreciated!
    Joep

    Sounds like you need to increase your buffer. Go to prefs - Audio  and increase the I/O Buffer size to the next highest setting, then keep going up if you still experrience issues.
    Remember you can use Low Latency Mode if you have a delay when recording. Shocks me that they have relegated this feature to such a obscure place, but a quick google search or peek in the manual will help you find it and use it.
    Btw, this is my backup .me account, so nvm the low level.

  • 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

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

  • Windows 8 (all versions) stop several times, bootcamp 4.0 macbook air core i 5 4GB Ram, 128 SSD

    Hello People.
    1- Macbook Air Core i 5 4GB Ram 128 SSD. mountain lion 10.8.2 (latest updates).
    2- Windows 8 core or windows 8 professional or windows 8 enterprise.
    mixed with:
    Boot camp 4.0 in a 35GB partition.
    Results:
    after complete installing the windows 8  it stops working if I install windows support drivers then stops working again.
    Then I must restart required by pressing the power button for 10 seconds.
    installing on a battery, not charging is OK and works good drivers updated, but when you plug in the charger for charging the MAcbook Air Battery , it stops working again.
    I Confused. May be a driver of

    I see that you are saying all versions of Windows 8 are failing on your system, but are you including 32-bit and 64-bit flavors?  I understand why 32-bit versions might give you grief (too much RAM for a 32-bit system to handle).  A 64-bit system might still have device driver issues.  Microsoft does not auto-magically have all the device drivers in the world that are necessary to make any system usable.  The original device manufacturers must provide Microsoft with drivers before the Windows Update servers would be able to communicate said drivers to the computers in question.
    In regards to Apple devices, Apple has not yet released the device drivers needed to run the hardware with Windows 8.  Apple has released the drivers for previous versions of Windows (XP SP2 and higher, Vista RTM and higher, 7 RTM and higher) to their userbase, but not to Microsoft for distribution through Windows Update (unless I am mistaken).  Until Apple releases a version of Boot Camp updated for use with Windows 8, they have not yet released any form of the full collection of necessary device drivers for normal device function with Windows 8.  Running compatibility mode on the Windows 7 device driver bundle via boot camp is not a fully palatable solution because compatibility mode generally is meant for application programs, not device driver services.  Therefore, partial compatibility might be gained by using the Windows 7 device drivers for Windows 8 with the compatibility mode enabled prior to install.  Unfortunately, much unanticipated incompatibility is equally likely with such a decision.
    Some parting words on the subject may be necessary for clarification: prior to the RTM versions of Windows 8, the trial versions of Windows 8 were distributed with a much wider array of device drivers than the RTMs.  This was for Microsoft's testing purposes.  Furthermore, some of the architecture used during the trial period likely used Windows 7 engines more than Windows 8 engines.  This means the Windows 7 drivers pack would have had more likelihood of working during the Beta and Release Candidate periods than during the final Golden Master period we have now entered.  Regardless, it is not recommended by Apple (our hardware manufacturer) to use another method of installing Windows on a Mac than to utilize Boot Camp.
    As Mende1 suggested, you would be wise to reinstall a previous version of Windows you may have been running.  Also, given your previous post, you will want to repair your OS X installation back to full functionality prior to the Windows reinstall.  For a reasonable timeline estimate, consider that it took 89 days from the original release of Windows 7 by Microsoft until Apple originally released device drivers via an updated Boot Camp.  That puts a reasonable ETA for the necessary Boot Camp update at January 22nd/23rd.  Even though this does not seem to apply to your situation, the discounted download for the Windows 8 Pro Upgrade will end after January 31st.
    Cheers!

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

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

Maybe you are looking for