The system usage window is at the top right corner.
WTF?!
This is running on a Macbook Pro quad-core i7 with 8GB RAM.
I was getting this error every time I was using a plug in last night.
So I shut it down and tried finishing the mix today but it's still happening.
My HW buffer size is at 512.
I get this same issue with my projects, curious to read about some workarounds (2.8 GHZ i7 MBP here). Using an external FW Drive as well.
Honestly the protools recommended system configs are ridiculous- they want me to turn off spotlighting on my internal drive? It's like they expect me to do nothing but run protools on my comp. I use my comp for everything- video, photos, audio and more. Close iTunes and safari? That's ridiculous too, plenty of other DAWs work fine with them open. Get it together Pro Tools!
i experienced the same thing on a rock solid system .....that was PT 10 1.0 an,d it was a joke !! don't know about after the last update , but all i know is that this version is a joke !!
Yes my system is rock solid , offline, Windows 7 32 , dpc latency 40us, RME fireface 400 , i 7 920 cpu was at 3 % !!!
Also turn off the airport, you don't need that to be on when you are working in PT
To me this is just a ridiculous assumption, why the hell should I not need to be connected to the internet when I'm working in Pro Tools? I have composing/ mixing sessions open throughout the day, while I am multitasking and answering emails, updating things, researching and browsing the web, etc. Using my computer. I don't feel like I should have to disconnect from the internet any time I need to work with audio- again, so many other DAWs work fine with AirPort on- Pro Tools as the industry standard needs to fix this and get with the times.
Not trying to harp on your comment specifically, just really frustrated that Pro Tools requires these parameters to work efficiently.
I get this same issue with my projects, curious to read about some workarounds (2.8 GHZ i7 MBP here). Using an external FW Drive as well.
Honestly the protools recommended system configs are ridiculous- they want me to turn off spotlighting on my internal drive? It's like they expect me to do nothing but run protools on my comp. I use my comp for everything- video, photos, audio and more. Close iTunes and safari? That's ridiculous too, plenty of other DAWs work fine with them open. Get it together Pro Tools!
/rant
Set up a different user if you're having problems.
Without finetuning the op's settings for him, difficult to say what's wrong...but something is wrong, a well set up rig doesn't do this.
But hey...if people think switching daws is easier for someone, the op should go ahead...personally I'd rather fix my rig!
__________________
<Shameless Plug>
If I've ever helped you with a technical problem or provided you with advice you found useful, you can more than repay me by checking out, and maybe buying a couple of songs, by a singer I'm working closely with. It would be much appreciated!
I don't use PT full time, but, I've had to use it the past couple weeks (9.0.6, OSX .7.4). The same thing happens to me all the time with next to nothing loaded. Last. night I started mixing a small song and bam, CPU error with the CPU meter not breaking a sweat, buffer at 1028. I was wondering if upgrading to 10 would solve this but apparently it doesn't.
Sent from my iPad using Tapatalk
__________________
Dave recordla.com www.myspace.com/dbwproductions
Logic 9.1.8, DP 7.24, PT 10.3.2, Reaper 4x, Apogee Symphony, professional 4room studio great for songwriters and producers.
when i had this , the first thing i "rechecked" is the setting and cpu distribution , then i thought ok it's waves , tried with softube : same , tried then with stock plugin , same .....
Also had some crash (app closing)
Ican run 600 track in sonar (same rig )
I do fully loaded sessions with VTM and run an app to record and post in youtube and my rig is chilling :
:::::: look at the cpu distribution ..up right
....PT is out of my rig since ....with zero regrets , i wanted to instll it beacuse of my students ....
I get this same issue with my projects, curious to read about some workarounds (2.8 GHZ i7 MBP here). Using an external FW Drive as well.
Honestly the protools recommended system configs are ridiculous- they want me to turn off spotlighting on my internal drive? It's like they expect me to do nothing but run protools on my comp.
that's right they do
once your rig is properly set up, it should run like a watch. Mine does.
Quote:
I use my comp for everything- video, photos, audio and more. Close iTunes and safari? That's ridiculous too, plenty of other DAWs work fine with them open.
then use one of those other DAWs if it such an inconvenience to close iTunes and Safari, and turn off spotlight.
The system requirements are there for all to see. If you do everything they say and you have a problem, you have a legitimate beef and cause for tech support
If you decide on your own which requirements are "silly", don't expect any sympathy when you have the very issues you were warned about.
If your car's manufacturer recommends you put high-test in your gas tank and you notice that diesel fuel is cheaper, and use that instead, who is to blame when your motor dies?? Come on Ford, get it together!
many people set up a separate user for Pro Tools. When you log in with that user, everything is set up as per the requirements. When you are done with Pro Tools, you can log back in as your other user with all your interrupting crap turned back on if you like.
__________________
.
“What you ask about is music. What you like is sound. Now music and sound are akin, but they are not the same.”
— Confucius
those pictures were from the night before.
the next day, i launched the same session, turned off itunes, and safari and it was still happening.
i'll try again later tonight with spotlight disabled as well and see how it goes.
but the thing is.. it's only THIS session that's acting up. i've never had this problem until this session.
i usually dont get that error until my CPU is around 30%.
and i dont even have a bunch of vst open and running. i have none actually.
only mixing plug ins.. and not alot neither as you can see i'm only using 5-7% CPU.
Since it's just that session giving you problems, maybe that session is corrupt. Have you tried creating a new session and importing all data from the session in question?
If your car's manufacturer recommends you put high-test in your gas tank and you notice that diesel fuel is cheaper, and use that instead, who is to blame when your motor dies?? Come on Ford, get it together!
quite a stretch on the analogy there, I don't think having your airport on or iTunes/ Safari running with PT open is at all equatable to putting diesel in an unleaded engine (something that would permanently damage your car/computer). Wouldn't you be frustrated if you couldn't run your air conditioning and radio at the same time, when tons of other cars do that just fine?
I'm on protools out of necessity, having migrated from Logic when I needed to move to what most everyone is using, and it's been constant issues for me- it's absolutely horrendous when using Virtual Instruments and just seems really clunky and inefficient- I guess I just expect more out of the DAW that the majority of the industry uses. I'm on a top of the line MacBook Pro from a year ago and it won't run smoothly.
I don't want to turn this into another hijacked/derailed Gearslutz thread so I'll stop here- I am however interested to see if anyone has anything to offer as far as a workaround/ solution. it's just frustrating that the industry standard DAW is so buggy and inefficient, and it's clearly not just me experiencing this.
I am however interested to see if anyone has anything to offer as far as a workaround/ solution.
You have been offered a solution - follow the manufacturer's requirements to the letter, at least for the User that you log in with to use Pro Tools.
Pro Tools is one of the most stable DAWs out there if you do what they say.
If you decide on your own their requirements are "ridiculous", well then you are on your own. Ridiculous they may well be, but they are what they are, and they are the solution to most problems.
Perhaps on some 'moral' level you are 'in the right' that Pro Tools ought to be as forgiving as other DAWs about having a bunch of extraneous conflicting items on your machine.
But for whatever reason, it isn't.
So you have a choice, you can be "in the right", or you can have a stable system. Which do you prefer?
Honestly the protools recommended system configs are ridiculous- they want me to turn off spotlighting on my internal drive? It's like they expect me to do nothing but run protools on my comp. I use my comp for everything- video, photos, audio and more. Close iTunes and safari? That's ridiculous too, plenty of other DAWs work fine with them open. Get it together Pro Tools!
Sorry my friend ... but if you want to use PT you must use the Avid Config. Spotlight is a major problem. it polls your drives all the time. Airport on is an issue. no internet on production computers running PT.
yes, you are right. other programs ala Logic work better when these things are turned on. but not PT.
virtual instruments in PT are an issue as well ... this is an audio program, with other features.
Logic and other programs are Midi sequencers with Audio features ...
just my .02
john
i have had most problems with PT. and most of them are related to these issues ... be patient, do it by the book.
__________________
Macpro 2.8 (2008) / OS 10.6.8 & 10.8.3 / 10gb memory
MacBook Pro 2.16 / OS 10.6.8 & 10.7.5 / 2gb memory
Logic 9.1.8 / Aurora 16 & Lynx AES16e-SRC / PT10.3.4 on SL and 10.3.5 on ML
Without finetuning the op's settings for him, difficult to say what's wrong...but something is wrong, a well set up rig doesn't do this.
This is such BS, sorry. Maybe on an HD system but I would challenge you to run this software on a native system. It shoots out errors ALL DAY LONG even AFTER you do all the recommended AVID tweaks.
So what do you do AFTER youve done all the AVID stuff??? Thats right, you sell it and get far away from it.
Same montra of " Its somethin with your system" I call BS for this excuse for piss poor written software.
Protools HD or HDX, whole diff story. I bet your setup if fine. On a native setup, give it a try and report back
This is such BS, sorry. Maybe on an HD system but I would challenge you to run this software on a native system. It shoots out errors ALL DAY LONG even AFTER you do all the recommended AVID tweaks.
So what do you do AFTER youve done all the AVID stuff??? Thats right, you sell it and get far away from it.
Same montra of " Its somethin with your system" I call BS for this excuse for piss poor written software.
Protools HD or HDX, whole diff story. I bet your setup if fine. On a native setup, give it a try and report back
We've got 7 Macs running native systems here as edit systems for pre dub conforms running happedy doody all day long. VIs are a problem - but outside of that with the right set up they're solid.
We've got 7 Macs running native systems here as edit systems for pre dub conforms running happedy doody all day long. VIs are a problem - but outside of that with the right set up they're solid.
What I/O's are you using?? Yes VI's do suck on Tools for sure
What do you mean by NATIVE, are you talking the Protools Native with the I/O box or using your own I/O with it and just the Protools software?
What interface are you using? And what are your buffers at? Do you have any old plugins in your plugin folder? I rarely get those errors and when I do its usually because I'm opening a new plugin while its playing (In a session that already has a ton of stuff going). I mix 80-100+ track sessions all the time with no problems. If native PT was that bad I would be using something else. Also I almost always have Firefox open. I'm usually on this site or checking email while PT is bouncing a mix. I do have my airport turned off and use a ethernet connection for internet with my MacPro so maybe that helps.
__________________
MacPro 2.8 "Nehalem" quad, 12gRam, Osx 10.7.3 | Cubase 6.5, Logic 9.1.6, Pro Tools 10.2, DSP-Quattro, Bidule | SSL AlphaLinkAX, SSL MadiExtreme 64 | Api 3124+ , Focusrite Isa-428, Distressor, dbx-160x | Adam P11a's , Ns-10's , Avantone's | to many plugins and VI's to list | lots of mics as well
This is such BS, sorry. Maybe on an HD system but I would challenge you to run this software on a native system. It shoots out errors ALL DAY LONG even AFTER you do all the recommended AVID tweaks.
So what do you do AFTER youve done all the AVID stuff??? Thats right, you sell it and get far away from it.
Same montra of " Its somethin with your system" I call BS for this excuse for piss poor written software.
Protools HD or HDX, whole diff story. I bet your setup if fine. On a native setup, give it a try and report back
I have...and I do.
I'm not saying PT is as good for VI stuff as logic or others..but he should be getting better performance than this. I do on a dual core laptop!
Would be difficult to sell and get away from for most of us - we make our living on it!
I have HD native and non-HD native. Same deal. HD makes no difference for VIs really.
The system usage window is at the top right corner.
WTF?!
This is running on a Macbook Pro quad-core i7 with 8GB RAM.
I was getting this error every time I was using a plug in last night.
So I shut it down and tried finishing the mix today but it's still happening.
My HW buffer size is at 512.
I dont understand what is going on.
Try unchecking "Ignore errors during playback....}.
You can also play around with the buffer sizes but mileage vary...
I run PT10 with wireless and safari running and rarely have a problem.. Forget about VIs though. Get Logic or Abe live for that.
Cheers
J
__________________
••••••••••••••••••••••••••••••••••••••••••••
Beer... Now there's a temporary solution - Homer J
Make sure you have less than your available 8 cores selected (you have a quad core with hyper threading and Protools will see it as having 8 cores in the playback engine settings)
Try 7 cores at 99% each. That is what I use and it is totally stable. I have an i7 iMac (pre thunderbolt). It also has SSD for system drive and internal SATA HD for audio, so I don't know if the SSD helps real-time performance of Protools (probably not).
I do need to have HW buffer at 1024 for intensive mix session or any mix sessions that use Slate VCC, VTM or Lexicon LXP reverb plugins though.
New Reply 
Facebook
Twitter
LinkedIn
