I stopped using pro tools after 17 years because of this exact thing. Randomly getting cpu overloads. I’ve tried everything you could think of and it would even mess up while tracking with no plugins and it would do it in random spots while working paid sessions. I finally moved over to logic and never had any issues like that. Pro tools users need to be computer wizards instead of just work on music like it should be.
12 years for me and I will never use Pro Tools again on my system for the same reason. There's always something happening where it *just stops working for no reason* after being great for months. No changes to the system. No updates to any apps. All variables exactly the same and then it just stops working. I'm on Windows and Studio One, Cubase, Reason and Wavelab all work flawlessly. Pro Tools is nothing but a headache.
thank you! i recently upgraded to a new PC that was *supposed* to be much stronger than my last one, but kept running into this problem when i went over 48 tracks. PERFECT solution!!
EMILY< YOU'RE A ROCKSTAR!!! I've been dealing with this for the last few years as track counts and plugin usage increased in my sessions. I just wrote it off to having an old computer that couldn't handle it, and would close sesion and reopen, and if that didn't work; quit Pro Tools and reopen. What a time saver!!!!! Thanks for this tip!!!
@@emily_bowie Thank you! Your tips are really useful. I've been using PT since version 5 and you come up with stuff I just never ran across. I had no formal training so had to use the manuals, but there's too much to memorize in those. Ha ha.
For Pro Tools is a vengeful goddess. One must not taunt Pro Tools. Her DAE error can smite you with the greatest of ease and while in one moment you bask in her glory, the next, she will destroy you and force one reset, to the next. Yay, speak softly in her presence and pray that today, the day of your important drum tracking session with a famous drummer, that she smiles upon thee. For if you forsake her glory, your buffer size shall not save you from the wrath.
What if you’ve done everything possible and it still happens and then when you hit play, it doesn’t play. And blinks with stop and play buttons at the same time?
I love your little studio:) Soo, I have run into this issue for quite a while now. and , yes you can fix the pops and clicks with that trick, however, not the running out of cpu error. That being said, what the heck causes the disk cach issue in the first place. I went litterally years without a problem, using the same pro tools update. It's driving me crazy and it's hard to type in a straight jacket. I have gotten no luck at the Avid forum either.
After the new versions 2023.9 this happens on everything that worked fine. Plus they managed to triple loading times! Back to Ableton, Bigwig and Studio One again!!
im not getting any static noise, my pro tools just stops working n sez cpu overload...ive tried every trouble shooting thing from closing background apps to turning off wifi wtf...changing the buffer size does help with playback/mixing, but i cant record with that buffer size n it creates a dramatic delay impossible to record properly with...wen i put it back to the normal buffer size, i get a cpu overload in the middle of recording again...ive freed up disc space on my comp, etc...nothing seems to fix it n i dont understand y as my pro tools was working 100% fine a month ago n nothing changed to my knowledge...i will try just changing that disc playback cache size to c if that helps...mine was set to 4gb n i keep having problems...wut do u recommend i change it to now to try to alleviate this situation? also does it need to b on dif things for recording vs playback? thanks so much for ur help as pro tools wont even respond to me without paying for a yearly subscription even tho i paid close to 600$ for their product, wild! thanks again emily! 🙏🙏
Got a new Mac super charged (super expensive) Still getting the cpu error telling to to adjust my buffer size What wit dat? Very frustrating to have 100s of gigs of ram and a million core processor and still be dealing with this in 2023 almost 2024
Im using a 500$ cpu and still get this sometimes with barely anything running, check my cpu on the side and im using like 15 % with no spike happening what so ever
Yeah its a good idea, either Set the Cache Disk or Buffer Size.. or maybe you can also try to solve it with a lil upgrade on your computer,, like change the processor, disk drive, RAM.. i think thats a perfect way, and it works!
nah not always. I have a brand new m2 MacBook. CPU load is literally less than 10%. Just cause pro tools tells you there's a cpu overload issue doesn't mean your cpu is actually overloading. It's a software issue
@@jasonhebert1656you right, but i think the software issue its like only 5 or 10 % issue,, RAM and Processor still the biggest one issue for me. intel,M1 and M2, even M2 pro i’ve been tried all of ‘em. But still, Once you go for the huge spec you have one step to safe the overload cpu
@@stanleymanuhutu3800I have 96GB of RAM and an M2 Max processor. I never had a single CPU interrupt when I was running Windows on an 2015 era i7 intel professor and 16GB of RAM. Pro Tools on the M1/M2 Mac is simply a poor product. I have had zero issues on the very same machine using Logic Pro, Ableton Live, or FL Studio. It is a entirely a Pro Tools software problem. Funny how it’s also the most expensive of the bunch.
Is it possible that a session is just corrupt? I just got a session sent to me and no matter what I choose I can't playback. My brand new Mac is using less than 10% of the cpu load so it's clearly not a hardware issue. This session should be nothing for it
The hack I use is simply changing the HW Buffer Size from one value to another value, then clicking OK. Another nudge that seems to work. Honestly, I can't wait until Luna maturates so I can get off of pro tools. And if Universal Audio isn't sensitive to their user community, I'll move to Logic Pro
i never got this issue until i updated to Sonoma.. i can have a session with only 4 audio tracks, and 2 aux’s. ℹ constantly get the error in every session now, and I’m working off a 2 year old Macbook Pro, An External SSD, & Pro Tools Ultimate, It Makes Me Angry, Because I Spent A lot Of Money On Good Hardware To Avoid Issues Like This. Before One Of You Smart Asses Try To Be Condescending About My Chosen Hardware, This Just Recently Started Happening To Me, I’ve Thrown Heavy Workloads At My Computer With A Regular Hard Drive, And Didn’t Get Errors. I Think Updating The Plugins Could Be Effecting It Also. I Run Into The Same Issues On FL Studio Too, And I Have All My Sound Bank’s And Virtual Instruments On My SSD. It Sucks Because When I Pirated/Stole Software And Plugins, I Had No Crashes. Now I’m Thousands Of Dollars Invested, And Can Barely Mix A Session Because Of The Constant Crashes. I’m Building My Next Computer
Wow that’s crazy! I’ve been using protools and iMac for years and always had to restart everything, I’m practically a expert when it comes to Apple products Imacs especially but eh..what is this “command” thing you mentioned? what’s that all about??
I stopped using pro tools after 17 years because of this exact thing. Randomly getting cpu overloads. I’ve tried everything you could think of and it would even mess up while tracking with no plugins and it would do it in random spots while working paid sessions. I finally moved over to logic and never had any issues like that.
Pro tools users need to be computer wizards instead of just work on music like it should be.
I’m about to switch over to Logic Pro x too I just got this error but I don’t have time to deal with it
@@turnpiketony97 only got the error once? That’s a blessing. But that’s true we need to be able to make music not trouble shoot software
Been going through this since last December. I then upgraded my laptop and it still happens. It’s a point where protools stopped launching
@@Ziddy_Mortal that sucks, it’s a waste of time
12 years for me and I will never use Pro Tools again on my system for the same reason. There's always something happening where it *just stops working for no reason* after being great for months. No changes to the system. No updates to any apps. All variables exactly the same and then it just stops working. I'm on Windows and Studio One, Cubase, Reason and Wavelab all work flawlessly. Pro Tools is nothing but a headache.
thank you! i recently upgraded to a new PC that was *supposed* to be much stronger than my last one, but kept running into this problem when i went over 48 tracks. PERFECT solution!!
EMILY< YOU'RE A ROCKSTAR!!! I've been dealing with this for the last few years as track counts and plugin usage increased in my sessions. I just wrote it off to having an old computer that couldn't handle it, and would close sesion and reopen, and if that didn't work; quit Pro Tools and reopen. What a time saver!!!!! Thanks for this tip!!!
Same thing was happening to me. And I would close the session and reopen. So glad that’s over! Thanks for watching and commenting, David!!
@@emily_bowie Thank you! Your tips are really useful. I've been using PT since version 5 and you come up with stuff I just never ran across. I had no formal training so had to use the manuals, but there's too much to memorize in those. Ha ha.
Wrong
Its 349am in the morning. And I had this problem. And it worked. Thank you so much! Likesd and subscribed ❤❤❤
Thank you! That did the trick. No fun dealing with stop and start when recording and editing an audiobook.
Excellent!!
For Pro Tools is a vengeful goddess. One must not taunt Pro Tools. Her DAE error can smite you with the greatest of ease and while in one moment you bask in her glory, the next, she will destroy you and force one reset, to the next. Yay, speak softly in her presence and pray that today, the day of your important drum tracking session with a famous drummer, that she smiles upon thee. For if you forsake her glory, your buffer size shall not save you from the wrath.
Nice, never thought to make a vid about it. Changing the buffer back and forth also works
So, here was the answer after so many years!
THANK YOU!❤
Always used normal, but not anymore, thanks EB!
Excellent, thanks so much, Friend!
What if you’ve done everything possible and it still happens and then when you hit play, it doesn’t play. And blinks with stop and play buttons at the same time?
I don't know if that's a common issue with a Mac? But so far my PC hasn't experienced it yet. I appreciate the tip in case it does.
Thanks
Hi I have a quantum computer with Pro Tools, I still get CPU overload after i put 4 audio acoustica plugins.
I love your little studio:)
Soo, I have run into this issue for quite a while now. and , yes you can fix the pops and clicks with that trick, however, not the running out of cpu error. That being said, what the heck causes the disk cach issue in the first place. I went litterally years without a problem, using the same pro tools update. It's driving me crazy and it's hard to type in a straight jacket. I have gotten no luck at the Avid forum either.
After the new versions 2023.9 this happens on everything that worked fine. Plus they managed to triple loading times! Back to Ableton, Bigwig and Studio One again!!
Or! U can similarly just change to any other buffer size, switch back to 1024 samples and hit ok. Also works!
You are so intelligent and you have the best video for this issue I hope it works for me ! 🎉❤
Good video, thanks for the tip! However, why does that help? What technically is adjusting the cache amount doing when we change that? Thanks
im not getting any static noise, my pro tools just stops working n sez cpu overload...ive tried every trouble shooting thing from closing background apps to turning off wifi wtf...changing the buffer size does help with playback/mixing, but i cant record with that buffer size n it creates a dramatic delay impossible to record properly with...wen i put it back to the normal buffer size, i get a cpu overload in the middle of recording again...ive freed up disc space on my comp, etc...nothing seems to fix it n i dont understand y as my pro tools was working 100% fine a month ago n nothing changed to my knowledge...i will try just changing that disc playback cache size to c if that helps...mine was set to 4gb n i keep having problems...wut do u recommend i change it to now to try to alleviate this situation? also does it need to b on dif things for recording vs playback? thanks so much for ur help as pro tools wont even respond to me without paying for a yearly subscription even tho i paid close to 600$ for their product, wild! thanks again emily! 🙏🙏
Got a new Mac super charged (super expensive)
Still getting the cpu error telling to to adjust my buffer size
What wit dat?
Very frustrating to have 100s of gigs of ram and a million core processor and still be dealing with this in 2023 almost 2024
My pro tools does not have “disk playback” option what’s up with that?
I’m definitely gonna try this
Would having a hdx system cure this?
Thank you for this video lol it was very frustrating getting these got it to work on much appreciated
Im using a 500$ cpu and still get this sometimes with barely anything running, check my cpu on the side and im using like 15 % with no spike happening what so ever
Never thought of that! Thanks Emily!
Thanks so much for checking it out, Michele!
You saved my life thank you!
And, also there change decay to 512 and after rechange to 1024. Will click ok. Always im this make. Because it is problem in old driver sound card
YOU SAVED MY LIFE ! Thank you so much
thanks so much.. that tip was worth money...for real
I love that TN cassette shirt. Totally want one now haha
You the GOAT‼️💯
Yeah its a good idea, either Set the Cache Disk or Buffer Size.. or maybe you can also try to solve it with a lil upgrade on your computer,, like change the processor, disk drive, RAM.. i think thats a perfect way, and it works!
nah not always. I have a brand new m2 MacBook. CPU load is literally less than 10%. Just cause pro tools tells you there's a cpu overload issue doesn't mean your cpu is actually overloading. It's a software issue
@@jasonhebert1656you right, but i think the software issue its like only 5 or 10 % issue,, RAM and Processor still the biggest one issue for me. intel,M1 and M2, even M2 pro i’ve been tried all of ‘em. But still, Once you go for the huge spec you have one step to safe the overload cpu
@@stanleymanuhutu3800I have 96GB of RAM and an M2 Max processor. I never had a single CPU interrupt when I was running Windows on an 2015 era i7 intel professor and 16GB of RAM. Pro Tools on the M1/M2 Mac is simply a poor product. I have had zero issues on the very same machine using Logic Pro, Ableton Live, or FL Studio. It is a entirely a Pro Tools software problem. Funny how it’s also the most expensive of the bunch.
Is it possible that a session is just corrupt? I just got a session sent to me and no matter what I choose I can't playback. My brand new Mac is using less than 10% of the cpu load so it's clearly not a hardware issue. This session should be nothing for it
Thanks sis
Thanks for the tip!
Thank you very much
Thank You 🙂
Thank you! This was driving me crazy!
Bangin Emily, thx much. First time here, won't be the last. Much appreciated.
So glad you stopped by!!
Like a boss!!! Really useful thanks!!!
Thanks so much, Agustin!!
Thanks!
Thanks for the support, friend!!
THANK YOU EMILY APPRECIATE THAT TIP WORKING IT OUT NOW :-)
Big thank you Emily!! I appreciate this wonderful video.
Thanks so much, Friend!
Thank you mumie.
Thank you😅
Omg thank youuu
worked for me !
Muchas gracias eres un ángel
Right on point ! Thanks.
The hack I use is simply changing the HW Buffer Size from one value to another value, then clicking OK. Another nudge that seems to work.
Honestly, I can't wait until Luna maturates so I can get off of pro tools. And if Universal Audio isn't sensitive to their user community, I'll move to Logic Pro
THAINKS ALOT
Very cool. Thanks.
This help me Thanks so much
thnkx
awesome
Thank you !!!!
i never got this issue until i updated to Sonoma.. i can have a session with only 4 audio tracks, and 2 aux’s. ℹ constantly get the error in every session now, and I’m working off a 2 year old Macbook Pro, An External SSD, & Pro Tools Ultimate, It Makes Me Angry, Because I Spent A lot Of Money On Good Hardware To Avoid Issues Like This. Before One Of You Smart Asses Try To Be Condescending About My Chosen Hardware, This Just Recently Started Happening To Me, I’ve Thrown Heavy Workloads At My Computer With A Regular Hard Drive, And Didn’t Get Errors. I Think Updating The Plugins Could Be Effecting It Also. I Run Into The Same Issues On FL Studio Too, And I Have All My Sound Bank’s And Virtual Instruments On My SSD. It Sucks Because When I Pirated/Stole Software And Plugins, I Had No Crashes. Now I’m Thousands Of Dollars Invested, And Can Barely Mix A Session Because Of The Constant Crashes. I’m Building My Next Computer
Wow that’s crazy! I’ve been using protools and iMac for years and always had to restart everything, I’m practically a expert when it comes to Apple products Imacs especially
but eh..what is this “command” thing you mentioned?
what’s that all about??
😄
GRACIAS ME SIRVIO
seems to only works for mac
Whoa, has anyone ever told you that you look a lot like RUclipsr Ashleigh Burton?
Where'd you get that cap Emily Bowie?! It looks good on you. I want to buy one for my wife!
It’s a Municipal sport utility hat.
1:36 is what u came for
A minute and 32 seconds to finally show me something that didn’t work 🤦🏾♂️
Hope your day gets better.
I like it. Who'dda thunk?
Easy breezy
ok but WHY THIS HAPPEND
👏🏻👏🏻👏🏻👏🏻👏🏻🔥🔥🔥🔥🔥