Hi Cliff, I think everybody can sympathize with wanting to get up and running as fast as possible. There are two things that come to mind based on what you've just written. If you're running on a fresh install, Spotlight will certainly spend a bunch of time indexing any drives connected to the machine including the internal drive. That might be the cause of initial CPU load if you just installed the OS and tried to run Pro Tools early on.
More importantly, did you follow the Intro to Pro Tools system setup instructions including turning off Spotlight indexing for recording drives? Speaking of which, are you trying to record to an internal drive? Slau On May 12, 2014, at 5:21 PM, Cliff Isaksen <cliffisak...@gmail.com> wrote: > Hi! > > Yeah, I sort of did that today... Two days ago I deleted the Machintosh HD > and started fresh on MountainLion, and today I reinstalled Mavericks over a > pretty fresh ML, so that's probably the next best I could do.. :) > I'm on a MacBook Pro 13>>, mid 2012, 8 GB ram and 2,9 Ghz processor, if I > remember correctly... > Well, the thing about the CPU usage has baffled me too... I remember before > going back to ML, the Activity Monitor in Mavericks told me that Pro tools 11 > was using somewhere around 129 % CPU, and that shouldn't be possible... It's > a little bit better today, but still when I checked, PT used 71 %, Kernal was > doing something funky that used up over 50 % and MSD (think it's some kind of > Spotlight indexing) was using over 60 %. > The only explanation I can think of, is that my processor probably has multi > cores and that each core might be counted as 100 % of CPU. So if I have 4 > cores, I might have a total of 400 % CPU available... Or? Well, as you may > correctly have gathered already, I haven't googled too much about processors > and stuff yet... > I really just wanna get down to business as soon as possible, and lay down > some funky tracks with great music, and not have to deal with all this > frustrating stuff before getting started with the real deal! :) > Thanks a lot for all your help, it's highly appreciated! :) > > > 12 May 2014 kl. 23:10 skrev Slau Halatyn <slauhala...@gmail.com>: > >> Cliff, >> >> Have you tried to reinstall Mavericks from scratch and only install Pro >> Tools? It doesn't make sense that the program would make your system gun its >> fans. Which machine are you on? Also, I'm sorry, but how does a process take >> up 120% or was that just an exaggeration? >> >> Best, >> >> slau >> >> On May 12, 2014, at 5:28 AM, Cliff Isaksen <cliffisak...@gmail.com> wrote: >> >>> Hi guys! >>> I have run into some issues, and I really need some suggestions from >>> someone who's not just as new as myself to the world of PT and >>> controllers... :) >>> The Problem is this: PT 11 works pretty fine together with the Digi 003 >>> driver for 11, but PT 11 also eats up over 120 % of my Mac's CPU, so the >>> fan starts running only after 1 minute after booting PT up, and after that, >>> it's more or less unusable... Tried all I can think of, but nothing seems >>> to work for fixing it. >>> So I'll have to use PT 10, and I can't get the PT 10 driver for the Digi >>> 003 to work in Mavericks. Can only get the driver for PT 11 to work. >>> So I downgraded to MountainLion again, and tried installing both PT 10 and >>> the 003 driver for PT 10. Now everything seems to work on the 003, but >>> sound from the Mac, including VoiceOver, can't be played through the 003, >>> and that is a huge problem... I can only playback audio from PT through >>> the 003 and nothing more. Everything else comes out of the internal >>> speakers, and VO also lags a lot in PT 10 now. By the way, PT 11 still >>> rapes my processor in MountainLion... Still uses over 120 % CPU... >>> I'm about to give up, and I think maybe I'll just have to upgrade to >>> Mavericks again, and run PT 10 without using the 003 at all... >>> Sorry, this got long, but I'm just out of ideas, and obviously too much of >>> a new be to fix this myself... >>> Any good suggestions? >>> Thanks in advance! :) >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Pro Tools Accessibility" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ptaccess/MjpRdtYaWq4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> ptaccess+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ptaccess+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
