2023.12 update frequent CPU overload errors

[its2loud]

What is hard to understand is why would you be against a possible warning that there may be an issue with 2023.12?

.

because the OP's "warning" is useless and baseless since it provided absolutely zero system info and we don't know if all if it's an issue with 2023.12. No scenario info, no plugin info, no info whatsoever what the OP was doing when he/she got the error message.
That's not useful to anyone. How is it helpful at all? If a lot of folks were posting these types of messages about 2023.12, that might be cause for concern and a reason to dig deeper. Without any pertinent information about the situation, it's absolutely useless to anyone wanting to upgrade to 2023.12.

It's not unreasonable to ask folks reporting any errors to provide important, supportive information about their computer, OS, hardware, etc, etc, etc. So that anybody can do a quick comparison to see if they might be affected as well. That would be useful.

[alexthemusicbloke]

Shefi, what system are you on? OS?

Any specific plugins where it seems to become an issue?


Just trying to get the ball rolling with help for the OP.

[coolbass]

People are being treated very unkindly on this forum by some who think they have to act as forum police. Why? This used to be a friendly place.

[midnightrambler]

Originally Posted by coolbass

People are being treated very unkindly on this forum by some who think they have to act as forum police. Why? This used to be a friendly place.

^^^^^^ this

[K Roche]

I have just started using 2023.12 (3 days now) on my intel iMac system listed below --- but so far no CPU overload errors.

I also checked several other 2023.12 threads no CPU issues reported in them either

There have been some potential bug reports but CPU overload is not one of them

The only issue I thought I had was with Buss color coding but turns out it was pilot error and inexperience with Import I/O settings

[ejsongs]

i reached out to Barry Rudolph, (whom I trust implicitly when it comes to this stuff) and this was his reply:




I have not upgraded myself yet because the update is calling for Monterey 12.7.1 and I'm on 12.5.1. But im not in a rush anyway so i'll get around to it at some point to see for myself.


Ej

[Darryl Ramm]

What is the point of all this? Many of us here are running fine on 2023.12 with no problems, with in many of our cases lots of third party plugins. All reported on DUC, all findable with a search. What is the point going out and polling folks who have not even tried it?

Of course if anybody has a problem and can give useful details then that is great. Even better open support cases if you have useful info, and that has more chance of leading to fixes for us all, I've opened around 6 cases for Pro Tools bugs in the last year, several currently in engineering hopefully getting worked on.

If anybody finds CPU errors and can finger specific plugins then that is useful to everybody. I don't see how anecdotes of a problems with no details, or folks who have not even used the new release give any useful information to anybody.

[Shefi]

As mentioned in my previous post, My system is Mac Studio M2 Ultra 128GB, Mac OS 13.5
I am happy to inform that ALL cpu overload errors DISAPPEARED after going back to version 2023.9
Who are you Darryl?
What makes you think you are better than any other user of this forum?
When I see a post that I cannot say something productive about - I keep my mouth shut.




Sent from my iPhone using Tapatalk

[Darryl Ramm]

You posted about a common ordinary every day issue... CPU errors happen frequently with Pro Tools updates, and are typically plugin related when they do. And I assumed you did not know what to do since you had rolled back Pro Tools without trying any usual/useful troubleshooting steps. So I made the mistake of assuming you might be after help, what a mistake.

You can post all you want on DUC, and folks can reply to your posts and point out they are not that helpful or not the best way to go about solving the problem you are seeing. If you don't want to listen that's fine, but hopefully it will help other users. And yes I know that was your intent as well, great intent, had you just spend a few tens of minutes doing some additional testing you could have proven it was was/was not a plugin issue, or maybe even fingered the exact plugin and that would have been very useful to folks. And had it not been a plugin issue then even more important to know that.

You tried a Pro Tools update, it had a CPU problem, rolling back to the previous version fixed that, little surprise there, what would be expected with wait for it... a plugin compatibility issue.

[ZoeMusic]

Originally Posted by Shefi

As mentioned in my previous post, My system is Mac Studio M2 Ultra 128GB, Mac OS 13.5
I am happy to inform that ALL cpu overload errors DISAPPEARED after going back to version 2023.9
Who are you Darryl?
What makes you think you are better than any other user of this forum?
When I see a post that I cannot say something productive about - I keep my mouth shut.




Sent from my iPhone using Tapatalk

Hey Shefi, sorry to hear you are having this problem. While I think both sides of this discussion could have taken a different approach (one with a little more patience and the other with a little bit more info) I Must say from my experience with 2023.12 I am really surprised to hear you are having this issue. I have a similar computer to yours (take a looks at my specs) and I have found Pro Tools 2023.9 and 2023.12 to be the most stable versions I have ever used since Pro Tools 9. Neither version have caused me cpu spikes/overloads and I have over 300+ plugins, all up to date though. I am also a heavy user of VI"s. I have been working with PT 2023.12 6-8 hours a day since it's release with no problems at all except a possible Mac fullscreen (spaces) issue that I have reported here in another thread but it is unrelated to this issue. My guess is that your problem may be a plugin issue. Don't give up on your quest to find out whats causing the problem. There are a lot of good benefits in upgrading to 2023.12. Especially if you are mixing in Dolby Atmos like I am. I can understand if you are working on a project and need to quickly revert back to PT 2023.9, but when you get some time, I believe it would be in your best interest to do some more trouble shooting to find out what's causing the problem.

Keep us posted....