CoreAudio: Disk too slow - Logic Pro - Logic Pro Help
Looking for:
CS Release Notes - Join the conversation |
QF质量管理俱乐部 - 年5月31日ISO/GB 为主题活动 - 第页 - 线下活动 - Logic Pro X "Disk is too slow (Record)" Error Message
Hi, i have an early 15" baseline macbook pro. Upgraded to 8gb and today i have switched out the optical drive for a second HD toshiba gb I did this because i have been consistently coming up against the same problem recently not after an update i don't think, just randomly.
Changing projects at this point makes absolutely no difference, it still happens. If i turn the mac off and restart i get the same minutes of normal stable time on logic before any trouble. I have tried the usual buffer changes and all the classic tricks to try and get round cpu spiking but this seems slightly different as neither the HD or CPU meter seems to spike at any point during this.
I have tried disabling the sudden motion sensor…didn't help. Turning it back on…didn't help. I am not going as mad about this as i usually would for some reason haha but it is a serious problem as i need to get some tracks finished for the 21st of this month and it's not going well. Any help would be much appreciated and though i said i have tried all the classic tricks to try and stop spiking i am sure i could have missed something.
Can you put your system specs in your signature? You didn't say what operating system and what Logic version you have. Mac mini 2. The System Overload message issues go back to the first days of my reading the forum and buying the mbp. The two settings made a big difference. The Retina introduction era adds even more complexity. I was using the internal disk at the time.
I purchased an External Fw disk and immediately got improvement resulting in not seeing this error. I keep a benchmark Logic project that trips logic with the Overload error at the same place every time Once tripped pressing Return then Spacebar sees the project play fine without tripping any more?
I think plays a big part. Each upgrade results in my tweaking the benchmark project to achieve the 'Overload' on my internal disk, the external disk always performs better.
The impression I get is that something? Logic Pro X I'm finding with the current issue that it is based around the amount of time i spend working on the project…seems to be the same each time, whether i am just playing the track over and over or working on it and playing it. I get around 10 minutes before the message pops up and from that point on until i quit logic and let it settle, logic is unusable.
I think i can rule out HD as i have now got that setup as advised and have absolutely nothing on the HD meter regardless of what i do during playback. It seems to be something that is building up over time and then overloading without the ability to settle itself back down. Really frustrating! I can't see this ever being rectified as i have come up against it on a number of machines and every version of logic over the last 10 years. This has to be the number one most serious downfall to logic and it's really surprising that apple haven't addressed it…Maybe it's third party plugins?
That stopped the "overload message in my MBP Logic9. CustomMac-Hackintosh, 3. Yep, all the above have been tried. Like i've said, this isn't the usual cpu spiking issue that i and many of you have always dealt with. The Fan behaviour reminds me of VM tweaks on 'Other' laptops years back. I've not changed the VM settings on mac, advice seems to suggest leave alone, but I'm curious. When you replace the optical drive for Second HD are there any 'additional' settings you have to make regarding Virtual Memory Swap or does OSX deal with this automatically?
The mac recognised the second HD without any tweaking…plug, format and play. The fan issue is certainly unrelated to the new HD as i've been up against the near constant rpm fans since i bought the mac.
Out of interest, you know that little box you can tick to speed up a file being imported into Logic? Could this be partially responsible for the system overload messages? I'd like to know how it would be possible for this system overload issue to spring out of nowhere no updates of any kind, no new plugs ….
I need it to be clear again that this isn't the usual issue of it popping up every time it hits a new file etc and then levelling out again.. It almost appears as though it happens at an exact amount of time playing the track over and over probably around 15 minutes. What does your project consist of? Right, the issue definitely seems to now be effecting all of my projects usually when i have had these issues before it will only be heavy ones.
There were various mastering plugs across the drumwork but i have bounced each track within the drums and deleted all plugs now. Active i have: 3 copies of predator, 3 copies of camelphat, 3 copies of ohmicide and a host of un-CPU intensive verbs no space designers and delays across the board.
I have made sure to get rid of anything clearly CPU heavy and the problem persists. Tons of room on both disks. OSX gb used of and 25 used of on the rpm project drive. I might add that i am unable to bounce now for the first time ever also. There is a clicking behind the bounced track and sometimes half the bounced file is silent i imagine where the cpu has spiked during the bounce. This is truly the worst issue yet for me. I am supposed to be taking some tracks to a night in London next friday and the timing is unreal.
I would also try a new OS X user and launch your project from that one instead just to see if something is off system wise. Yeah tried that. I imagine it is a hardware fault. I think it is overheating or at least something is telling logic it is under more stress than it actually is…hence the similar time of the fail each session.
The fans steadily work their way up to full power within a minute of pressing play and the temp hits 90c normal? I've just had to send the projects i need for next friday to a friend to try and bounce for me as i can't even bounce them now without loads of pops and crackles. I'm really surprised, i never thought anything could be worse than the standard system overload i have dealt with for ten years on and off…this is truly unusable! You can post now and register later.
If you have an account, sign in now to post with your account. Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL. Click here! Disk is too slow or System Overload. Share More sharing options Followers 0. Reply to this topic Start new topic.
Recommended Posts. RawScience Posted February 8, Posted February 8, Thanks Charlie. Link to comment Share on other sites More sharing options Try turning Wi-fi off. Reduce Undo Steps in Logic's preferences. Thanks, i hadn't actually tried turning wifi off before. I'll give it a shot. How do i add my system info to the signature? Eric Cardenas Posted February 8, Click this link to your signature.
RawScience Posted February 9, Posted February 9, If it were a hardware fault, does anyone know what is most likely the culprit? DaveRobinson Posted February 9, Wireless off Great tips..
Thank you triplets RawScience Posted February 10, Posted February 10, I should add that near enough immediately when i start logic and play a track the fans kick it to max and stay that way for the duration of the session. Posted February 11, RawScience Posted February 11,
Comments
Post a Comment