Processor overload

I have an I5 processor with 8 Gig of ram. Lately my CPU overload warning has been poping up regularly. When I open the task manager I find several (as many as 6) Adobe reader processes going even when I do not have any Adobe files open. It appears to me that I open a file and close it, but that for some reason Adobe is not closing down. I click the "end process" buttion and they close and the processor goes back tot normal usage levels, but this is a pain to do several times a day. Can someone tell me why these processes continue to run and take processor capacity when they are not in use? And more importantly how do I fix it?

Apple has a problem that they have not addressed. With all the new Plugins that are now available they consume a lot of memory. Apple has not come up with a answer to stop overload messages. Adding ram will not solve your problem. The best thing you can do is run your computer and Plugins in 64bit mode. This will help you relieve some of the memory issues. We can only hope Apple will release a new version of Logic that will allow the Plugins to feed off of your ram.
I'm running a dual quad with 10 gig of ram and i still have the same issues, APPLE ARE YOU LISTENING!!

Similar Messages

  • Fcp video stutter and processor overload

    I'm editing on Intel MacBook Pros and on one I'm encountering (after downloading a series of software updates) a slight stutter with Quicktime files played in Final Cut Pro. The other machine is fine (and didn't have the updates). Both run FCP 5.1.4. and the latest Quicktime. Just playing out clips pushes the processors past 100 percent. I've used the disk utility. No other programs are open. Desktop is clean and I've got plenty of hard drive space. Any help?

    Both run FCP 5.1.4. and the latest Quicktime.
    Does that mean QT 7.4.5?
    If so they are not compatible and you will need to go back to a previous version of QT.
    Search for "pacifist" and you will find posts to help you

  • "mds" & "mdimport"  processor overload on Activity Monitor

    I use the MenuMeters application to help monitor for system slowdown. Lately (perhaps since 10.4.9?), the processors have been sky high & the Activity Monitor shows "mds" & "mdimport" at user, root & unknown levels as culprits. Despite force quit, repair permissions, reboot, reset PRAM, these beasts keep coming back. What am I missing & what can I do. Thanks fo any input!
    Quicksilver2001+ 1.33GigaDual/1.5g RAM   Mac OS X (10.4.7)   Powerbook G4 1.3G/1.25g RAM

    Hi
    They are to do with Spotlight, see this forum:
    http://www.macusenet.com/mac-system/37712-tiger-mdimport-and-mdsync.html
    Steve

  • Sample Rate problem as well as CoreAudio overload and anyone using DFH?

    I've only switched from Pro Tools to Logic Pro recently and am confused about a lot of things. I am running Toontrack DFH Superior with 7 audio tracks and one more software instrument track. I keep getting message about sample rate problem and something about conflict betwwen logic and external device. The only device I use is a M-Audio 49e MIDI controller and the M-Box, and I am running these on a Quad PowerMac G5 wih 4 GB RAM... I've tried to adjust the setting here and there, but none of them seem to work... Please help!

    Often MIDI driver conflicts and processor overloads, or bottlenecks too. Freezing, removing old drivers, if you really are running Jaguar and if it is actually installed from those days then it is time to do a fresh install and maybe use Panther or Tiger. Panther can be found really cheap these days. As far as old drivers you don't use for any audio or MIDI interfaces you once used with your sytem, are there any? If so which ones? You may be able to direct yourself to your old driver uninstall by looking at the receipt of whichever driver you no longer use. Also, Jaguar was just really good at getting this message to come out, in my experience. Some plugins require alot of MIDI I/O or CPU power, some of NI's stuff really (momentarily) spikes on MIDI data input.

  • IPod Touch 4G Not Turning On or Connecting to iTunes

    I have no idea why, but my iPod Touch will not turn on. When I press the Home button, it will show the low power screen (but only when connected to a USB cable). Holding Home does nothing. Holding Home and whatever the button on the top is results in a brief white flash, then it goes completely black. It won't show up in iTunes, and I've tried everything I can find on Apple's Support pages. I've tried plugging the iPod in both before and after starting up iTunes, I've tried holding the Home button down before plugging it into the USB cable, and I've tried changing where the USB cable is plugged into the computer (despite it being the same port I've used for the past four months, with no real problems).
    I'm not sure what, if anything, else I can do, but any help would be greatly appreciated.

    I'd tried soft-resetting several times (had a similar thing happen before, and that always worked). Don't know why, but I tried holding the Home button while plugging in the USB cable today (had tried it yesterday, with no luck, but I figured why not try again) and it seems to have worked. Read in another post about it shutting off for about 24 hours because of processor overload, but since I usually don't have more than one app running at a time, even in the background, I didn't think that could be it. Clearly I was wrong. Thanks for the assistance, though.

  • CPU spikes - what's the latest?

    I posted a question about this in another thread but haven't heard anything back yet - and am desperate for answers so figured I'd try again!
    I've just started having a big problem with CPU spikes, seemingly out of the blue.
    After having had no problems (that have affected my workflow at least) since updating to Logic 8 when it first came out, the last 2 songs I've worked on have both started having repeated CPU spikes. In both cases the songs (which have for the previous couple of weeks been running fine as I've worked on them) suddenly seem to reach some kind of critical mass and stop at least 4 or 5 times in the song (with a processor overload) making it impossible to mix. The spikes themselves appear to occur every 10 seconds or so.
    Though the songs have previously been fine during sections with many tracks, plugins and instruments running, once this starts happening even the most sparse sections can suddenly no longer play without overloading.
    In the past, bouncing any instruments to audio or freezing processor-intensive tracks would clearly lessen the load and allow the song to play without a hiccup, but it seems once this starts happening that any attempts I make to pare the song back barely help at all. Even if, in between spikes, the song is running with about 25% max on the CPU meter, when a spike comes both processors momentarily max out and stop the track.
    Strangely, with the latest song, even reverting to previous versions (ie from a few days ago when I was having absolutely no problems of this kind) the computer can suddenly no longer cope with the spikes (which I assume have been happening all along but haven't affected playback before now). Weird but true.
    I've tried disabling all audio unit plug ins in AU manager, setting all channel strip inputs to no input, running the song using Core Audio rather than the MOTU 828 and repairing permissions with DiskUtility.
    Today I tried a clean install of 10.5.3 and 8.0.2 on a new drive (no 3rd party plugins or ANYTHING apart from Logic and OSX installed) - still with exactly the same result.
    I've even tried copying all the audio from the arrange into a brand new song, adding the plugins and routing to busses track by track, all the while keeping an eye on the CPU meter. As soon as I've sent just a couple of tracks to aux channels and added only 3 or 4 instances of Channel EQ and Compressor I notice the spiking begin. It's clear that by the time I've finished the setting up of the song the spikes will be maxing out again.
    I realise I'm running an old machine (ie Dual 1G G4) but it has, up until now, been working spot on under the current system (I've been using 10.4.11 and hadn't updated to Leopard until today cos I haven't wanted to upset the delicate equilibrium!)
    Thankfully I've found a clunky workaround by copying the song on to my Macbook and running that in my studio - a lifesaver but not satisfactory. (I can see the spikes on the Macbook too but playback isn't affected).
    I've been using Logic forever and know this behaviour (and unresponsiveness to all my troubleshooting attempts) isn't normal!
    I've seen the threads from a few months back but am wondering is anybody else out there still having similar issues? Or has anyone had them and solved them?
    Please help!
    Cheers
    Duane

    The latest? It's still spikes constantly here. IMHO, I think there is an issue with-in LP 8 itself with symetric multi-tasking to more than one core... evenly distributing the load between cores. It's hit or miss with me & completely un-predictable and random (the CPU spikes). I've tried all the same quick fixes or work-arounds, of which none seem to make any difference at all. Even setting core audio buffer to 1024 & disabling safety buffer.
    Oddly I do find it interesting that on my system anyway, Ivory 1.7 & Atmosphere 1.2, once initially instantiated on an inst track, will consistently evenly distribute between both cores (I have a dual core machine)... and never spike the CPU, no matter how much polyphony I use on either one, with the core audio buffer set to 128. There has to be something the way these two virtual synth plugs are coded differently, to utilize an even symetric threading or distribution to multi cores. -> I am no computer wiz tech head by any means, but this is the best way I can explain it.
    Fresh clean install of OSX Leopard 10.5.4 / 2.5GB Ram / LP 8.0.2 / Digi Core Audio 7.4 / Digi 002R

  • SPDIF optical audio input problem

    having got over the audio stutter problem by upgrading to 10.4.5, i discover that there is a part 2 to the audio faults on the last g4 powerbooks.
    i've been trying to record from DAT via the spdif input, but after a random amount of time, the apps stop recording with a processor overload error, or worse, something very similar to the looping audio problem previously thought cured.
    If i try and record via line in analogue - there is no problem.
    I'm not really streesing the CPU - i've been forced to try and use simple recorders like quicktime and boom recorder , trying to keep it simple and reliable at this stage.
    any ideas?
    Powerbook G4 17" 1.67 DL 512mb   Mac OS X (10.4.5)  
    Powerbook G4 17" 1.67 DL 512 mb   Mac OS X (10.4.5)  

    But when I plug the output of the Radio Shack controller into the audio input of the iMac, it captures only one end (my end) of the conversation.
    Where did you previously connect that output, when it works properly?
    Is it coming over only on the left or right channel?
    You may be able to control the audio input more precisely using the +Audio Midi Setup+ utility (in the Utilities folder).

  • Macbook Upgraded to Yosemite, now Logic 9 stalls

    I have an older macbook pro (2009) that was running fine on Mountain Lion with Logic 9. I upgraded to Yosemite, and now Logic 9 stalls when playing songs, gives me "processor overload" errors when playing songs that used to run fine on Mountain Lion, and keeps playing songs even when the stop button is pressed, only after about ten or fifteen seconds will it do the command I enter (stop, pause, etc.)..... My question is, until i can afford a new mac, will I save on processor power by purchasing a stereo digital audio converter instead of using the internal one? Im thinking my mac isn't fast enough or powerful enough to run yosemite AND logic, as is evident by the amount of errors I am experiencing. (BTW, this was done with a fresh install on a clean drive I had security erased, so there shouldn't be any extension conflicts, I loaded up logic first to see if i would keep getting the processor errors and I do.) SO, my choices are to reinstall Mountain Lion, or to buy a digital stereo audio converter. Will the converter transfer all of the processing from the internal CPU to the converter , and if so, will it be enough so that Logic will run smoothly?
    Thanks for any help,
    Ivan

    Well, I got rid of Yosemite, erased my drive, and loaded up mountain lion PLUS installed a SSD per the Apple referred dealer, and the Mac clocks like a champ. HOWEVER, Logic is STILL stalling on the "stop" button, whether I use the space bar or the transport, and no other buttons or commands fail. It seems to stop whenever I load it up with a new process (add a reverb, delay, softsynth, etc.), but if I am normally playing back a track, it works fine. It seems to get worse as the session goes on (first ten seconds, then twenty, then thirty, the last time I had to leave it completely and it went on for five minutes.).  When it's ready, it runs through the commands I've pressed one at a time in rapid succession. First it will scroll to the next plug in preset (per the "next " button I pressed when it first jammed), then it will stop (because I pressed the "stop" button) then it will start again (because I tried pressing the spacebar after that) then it will do as many of the commands as I pressed, about two per second, until the last command I entered is completed, and if I press the spacebar an even number of times, it will simply start playing again. Ever heard of something like this?
    p.s. would you recommend a new MOTU (I've always liked them) or have you heard good things about the Native Instruments digital stereo I/O? Or the Apogee? I think I'm going to just buy a whole new system, I'm getting more soundtrack work and as fun as trying to fix problems are and as much as I'm learning, It;s probabaly time to throw away the duct tape and bubble gum and step up. Mac even offers special pricing for college students. I get a whole twenty bucks off a new mac. Oh, thank you, mighty apple.
    Thanks for your help. You guys get points or something for answering questions, right? Does that turn into anything tangible, like software or discounts, or is it like a status thing (I'm an online poker player, and we get pretty vicious during tournaments even though there's no money, everyone wants first place).
    Ivan

  • SSH changes vs future firmware update

    Hullo, I have made some changes to WD My Cloud via SHH: I disabled ipv6;I stopped two services through crontab (S85wdmcserverd and S86wdphotodbmergerd)etc, according to http://blog.cloud-client.info/?p=1365 In case of future firmware update and I perform the installation will the changes done be overwritten?Would be advisable to accept the update in the future? Thank you in advance.     

    Indeed, an answer from a user that has experienced the aggravation of firmware updating and vowed never again will he update; unless he has two clouds (one to update and the other to keep as backup). yes... once you update your firmware, all changes will be lost and if you had store script files in the /usr/local/sbin directory, they will be gone too... In a sense it is a good thing because if you had done a lot a changes, this reverts your device back to original factory state. Now I have heard rumors that if you by pass too many firmware updates and decided to upgrade from, lets say 3.04 (which happens to coincide with my current version) to the latest firmware 4.xxx which is probably 6 update versions ago, your device will be bricked. They say, the customers that runs and replies in this forum, that you will need to upgrade your firmware one by one until you reach the latest version. The other rumor is that many have updated their firmware to the latest version to find that nothing works, speed is slower, usb connections don't connect and of course drop outs are more frequent. Then there are those who says "I've upgraded and everything is fine", but that particular user probably has 5MB of data on his drive. Now here is what I suggest. 1. Always have another copy of your data which has nothing to do with firmware updates. Never ever copy your data to the Cloud device and erase the original unless you have another copy somewhere else. If you don't have another device and don't wish to buy another device, either leave the original on your original drive and use the Cloud as your backup, or subscribe to one of the free or paid online storage to keep a backup copy, but don't rely on the online storage as your only copy either, since places like Megaupload may disappear overnight and your only copy may be in the hands of the FBI.2. if you upgrade your firmware, it is better to have another Cloud for a 3rd backup. That way if something fails (and it would feel like it expecially when it goes white light on you), you have another device to use while the other one is being RMAed.3. If you have stopped the scans from occuring, the first thing that happens after an update is a flurry of activity from your Cloud trying to catch up on its scans and you might get locked out. So be prepared to SSH into it as soon as it lets you which is way way after the white light stays on for several hours (speaking from experience). 4. Once you SSH in, be prepare to repeat the fixes that you applied to your last version. For four years (or more), I haven't seen a switch to turn off the media scans although in version 3.04, they actually turned off the scans automatically dues to processor overload and it had a message on the UI telling me that the scans has been stopped and in order to restart the scans you must reboot (I didn't reboot for 6 months). You can skip firmware upgrades as I have without too much problems. Although they have fixed a couple of potential security threats, none of them should potentially affect you since you are behind a router. Although eventually I expect that I will have to upgrade my firmware simply for the reason that the matching iphone app will require the latest version. Perhaps on that day, I will sell my Cloud and move on to a more robust NAS. Good luck..  edit: the/bin/sh /etc/rc2.d/S86wdphotodbmergerd stop /bin/sh /etc/rc2.d/S85wdmcserverd stop  are not permanent changes. If you reboot the Cloud, those two process will restart. The update-rc.d commands will disable the processes until you upgrade the firmware.  

  • Problem counter (Frequency)

    Hi,
    I have a DAQ card 6024E. I want to measure a frequency between 10 and 500Hz, (from a propeller) approximately. The signal come from a inductive-sensor. When I put the signal on the PFI9 input (ctr0 gate) and I use the DAQmx "CI Frequency" (1 counter measure) I get sometimes good measure and sometimes wrong measure (0,3 Hz or 2MHz for example).
    So, Please you can help me, where is the problem?
    Thanks
    Franco
    this is mi VI
    Attachments:
    FREQUENCY 1.vi ‏21 KB

    Hello,
    I already answered to your question on the french forum but I also answer here for english people who have the same problem.
    There are a few problems in your VI. The detailed help specifies that you don't need to connect the divisor input when you choose Large Range with 2 Counters in the measurement method of DAQmx Create Channel (CI-Frequency). Moreover, you don't need the DAQmx Timing (Implicit) function in your VI. However, you'd better add a Wait Until Next ms Multiple in your while loops in order to avoid a processor overload which would slow down your computer.
    So I changed a few things in your VI. Please find it in attachement. I saved him in LabVIEW 2009.
    Please let us know if you succeed to read your frequency measurements.
    Best regards,
    Jérémy C.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Travaux Pratiques d'initiation à LabVIEW et à la mesure
    Du 2 au 23 octobre, partout en France
    Attachments:
    FREQUENCY (modifié LV2009).vi ‏14 KB

  • G5 Fans going berserk with Leopard

    I installed (clean install) Leopard yesterday on my G5 PPC. All went really well and I put the machine to sleep for the night.
    When I went into my office this morning it had woken up at the fans were going berserk, never heard them so loud. It was unresponsive and I had to force quit by holding down the button on the front.
    Anyone know what is causing it or having a similar problem?
    Thanks

    There are many threads on this issue regarding processor overloading and overheating with Macbooks. Here is one thread:
    http://discussions.apple.com/thread.jspa?messageID=5718200&#5718200
    My experience:
    it seems to have something to do with some sort of excessive processor load. I have MenuMeter installed, and it shows one of the processors running flat out at 100%, and then the load switches to the other processor. This would certainly create some heat. Also, open Activity Monitor, click on the CPU tab, and look at the CPU usage LED display at the bottom and you will see the full processor load switching from one side to another. Interestingly though, Activity Monitor doesn't show any processes that are taking up a significant amount of CPU. I have the problem even after a restart before starting any applications, and with no startup items enabled. This one has me puzzled, but the other symptoms noted in this thread sound similar.
    By the way, I get the same overload/overheating problem with only a newly created user and nothing else running. I am not running Time Machine and Spotlight is not indexing.
    This is a serious problem and due to the load, the battery time on my MBP is now limited to less than an hour on a full charge. I am also concerned that the constant heat load will not be good for my MBP.
    The only solution I see right now until Apple fixes this problem with an update: revert back to 10.4.10. Since I run my MBP on battery during frequent flights, my MBP is for all practical purposes unusable with 10.5. Needless to say, I am disappointed that I have shelled out the money for Leopard and cannot use it.

  • OSX error ID -8796

    Anyone explain this to me?
    It occurs on a MBP 2Ghz with OSX 10.4.8 after starting Digital Performer 5. 11. Not related to processor overload or low RAM. Plist trashed and preferences deleted. It is making DP very unstable, and occurs after opening some of the windows and commands (like Tracks window and Sequence window) or openng a new project. I have posted a similar request on the MOTU forums, but no one can explain this, so far.
    MacBookPro   Mac OS X (10.4.8)   Digital Performer 5.11

    Followup:
    I now have reactivated all arabic, chinese, and Japanese fonts that I had turned off in Font Book, then I have re-started the computer and DP. The errror code message has changed to ID -39, but the instability stays the same.
    I am wondering if I have moved or deleted any fonts, but cannot recall having done so.
    The mystery goes on.

  • System overload . Just right processor clips. Left one almost at zero.

    Sorry, if this has been asked before, but I did not manage to find a way to look for thread titles and there´s thousands of posts containing my search items!
    Here´s my problem: I get the System overload message: "Audio engine was not able to process all required data in time (-10011)", which is in my case understandable, cause I´m running very many EXS an reberbs.
    But:
    1. My system performance shows, that the right processor is doing allmost all work, while the left processor is just at 10 %.
    Why is this?
    I remember a trick in Logic 5, where U could ballance the processor-work by using an I/O-plugin an bypass this. This way some of the work was handled by the other processor. Are there any similar tricks in Logic 7?
    2. I´m working almost without audio tracks and with many EXS-plugins.
    Even though I set everything in a way, that my hard-disc should have a lot of work (Buffer Size 1024, fast disc, etc...) the system performance shows zero activity, but the Audio clips.
    What´s wrong?
    Thanks for your help!

    Hi Felix, bin zwar nicht Sonther, antworte aber trotzdem mal:
    Denke es reicht, wenn Du einfach mal den 10.4.9 Combo Installer drüber installierst...wie Sonther schon erwähnt hat !
    Logic brauchst Du deswegen nicht gleich zu deinstallieren.
    Einfach mal ausprobieren...
    Aber ob es an 10.4.9 liegt, warum die Prozessorlast nicht gleichmässig verteilt wird, bezweifel ich. Logic müsste das von sich aus eigentlich selbst machen.
    Ich arbeite zur Zeit noch mit 10.4.8 auf men Mac Pro, da hab ich immer ne
    gleichmässige Auslastung aller 4 Kerne.
    Könntest aber mal den Node-Trick ausprobieren.
    Logic Node auf dem gleichen Rechner installieren und in Logic Spuren auf den Node verteilen( vielleicht kannst Du damit den 2 Kern benutzen).
    Wurde von Leuten schon auf den G5 quad Macs gemacht, bevor nur 2 von den 4 Kernen von Logic benutzt werden konnten.
    MfG

  • Playback Jumps as if processor is overloaded

    I just uploaded an HD clip from my Sony HDR-HC3 camcorder in 1080i format at 29.97 fps into iMovie 6.0.3. I followed all previous trehead advice. Nevertheless when I play in preview mode or full screen, the video portio skips while the audio track plays smoothly. I took it into the store and a Creative transferred the file and it played fine. It creates the impression that iMovie and my processor are overloaded.
    To test this further, I tried exporting the clip to QuickTime with a medium quality compression. It played continuously but the quality was poor and it took 20 minutes to compress a 22 second clip into 64MB.
    How do I get iMovie to play without jumping? Sometimes I get a mesage saying "HD playback at 1/8 speed" but Help does not explain what this means.
    Thanks for your guidance.
    Patrick

    Noticed it only happens on my secondary monitor; on the primary, it scrolls just fine. Got any ideas on how to fix this?

  • Is core audio overload error a ram issue or a processor issue?

    I have a macbook 2ghz with 2gb of ram, external 250 gig 7200 rpm lacie hard drive. I am running ivory pianos, superior drummer 2.0 and waves plugins. I get the core audio overload a lot. Its really annoying. I have disabled airport and shut down all programs. All unused tracks have no inputs. I am thinking about buying a new macbook with 4 gigs ram(my macbook can only handle 2) but wondering if it will even make a difference. Am I getting it because I only have 2 gigs of ram? I will be really upset if I purchase a new macbook and spend a ton of money and it still happens. Any suggestions?

    I noticed it happens when I mix.
    Not when recording though.
    Upon loading a project the first time accessing a resource hungry effect or plug-in, the core overload pops up. When the problematic section has been successfully played once, the problem doesn't reappear.
    As such, It really doesn't bother me. I figure it's some sort of caching issue. It's annoying, but never affected my work.
    Similar experience for you?

Maybe you are looking for