2022.12 - for me the worst version since years

[JFreak]

You have a badly behaving plugin installed. You mentioned SSL so try to move it to unused folder and try again. It may be any plugin that gets loaded into memory, you don't need to instantiate it in a session to wreck havoc.

Originally Posted by nstu

I am not very often complain about Pro Tools. I was very happy with the last updates and also try to have clean install, still one OS behind and plugins all up to date...
(Mac Studio, 12.6.3)

2022.10 was once of the very stable versions for me...could not think of any errors.

This changed totally with 2022.12 (rosetta). - yes I trashed pref, re-start Mac, checked my plugins...and did not change anything at all with my setup.

This first thing was I can't activated SSL UF8 as a HUI device. Pro Tools crashed or hangs with beach ball when I hit save in the HUI pref. Need to restart, need to create a new clean session, activate Midi Input device, SAVE, QUITE PT, RE-Start and then I could saved the HUI device without beach ball..very strange

Next...just by clicking trough a session without playing - pro tools hangs....beach ball

Next...editing inside ARA Melodyne (my first try with the ARA system)...pro tools hangs...logical after 30 min of editing at the last note....auto save was on every 2 min....so again beach ball....re-start pro tools....the session load fine from the auto save back up but all melodyne work was gone...(yes I have the last update of melodyne). This was the last thing I needed to revert back to 2022.10.

I know this .12-version is half an update half an beta for native...thought it would more beta on the native side.

What really hit my nerve that I don't get a error message....just beach ball every time until I hard close pro tools.

Thanks to backups to get back fast to a stable and working version.

Just for interests, anybody with same experiences?

[Eric Lambert]

Just to highlight the above comment because I feel that some people don't realize this: take every plugin in your plugin folder into consideration. They can cause issues even if your session doesn't actually open and run audio through it. Just having it in the folder can be enough to trip up PT. It's a good idea to do regular checks to make sure that you're running the latest/greatest version of all of them. It can be laborious, but it can also make all the difference between a smoothly running PT app and a nightmare of crashes and stalls.

Truly, I've been through it so many times where one silly plugin I never use is so old and out of shape that it brings down my whole system. Finding that they offer an update that puts wind back in its sails changes the game and the sluggishness and crashes vanish, all because of that one silly old plugin.

[hurdy gurdy]

Originally Posted by Eric Lambert

Just to highlight the above comment because I feel that some people don't realize this: take every plugin in your plugin folder into consideration. They can cause issues even if your session doesn't actually open and run audio through it. Just having it in the folder can be enough to trip up PT. It's a good idea to do regular checks to make sure that you're running the latest/greatest version of all of them. It can be laborious, but it can also make all the difference between a smoothly running PT app and a nightmare of crashes and stalls.

Truly, I've been through it so many times where one silly plugin I never use is so old and out of shape that it brings down my whole system. Finding that they offer an update that puts wind back in its sails changes the game and the sluggishness and crashes vanish, all because of that one silly old plugin.

I don't have every plugin ever written but I've never had to do the remove-add plugin routine with this latest version (plugins that are qualified though). BUT, when I've exited PT sometimes I get the "PT quit unexpectedly" mumbo jumbo. Wait second.. come again? I quit PT but PT is telling me PT quit me Nevertheless it's been a real fast and solid experience with this whole M1 native business

lb.

[BigBadBill]

Originally Posted by Eric Lambert

I'm surprised to see this. It's been one of the best versions for me and my coworkers (we're running OS Monterey). It has a few issues but every version of PT has had a few issues. I'm sure those problems are real, and probably frustrating, it's just not happening here.

I have to agree here, 2022.12 is dead stable for me running Monterey on an M1 MBP MAX.

[11miles]

I am on imac 2017, big sur and 2022.12.
Cant complain really

[nstu]

Just want to thank you all for your feedback, tipps and experience.

My "problem" is, when I have really good functional version of pro tools (2022.10) with all plugins up to date (and I can say for myself, I don't have so many third party plugins...and than perform an update of pro tools with these kind of results I got...that should not happen (with any kind of software) in my view...I know, this is easy to say.

Maybe I should try update MacOS and all the others things again...but I don't think it is worth for me yet. The work with Melodyne as a plugin feels better to me, but that is just again a personal preference.

I am happy that I can go back to a working system and don't have to stress myself. I will wait until pro tools will be complete native as well all of my used plugins. Than I will do for sure the one-by-one testing of all plugins.

[dominicperry]

On the recommendation of someone here I bought MacUpdater.
https://www.corecode.io/macupdater/
I'm using version 2, and you need the Pro Version of Version 2 (about $35, one-off) to get the plugin updater, but it's been really good. I just run it every few days and it tells me what needs updating, including plugins. It's capable of doing the upgrade itself with a single button press for some apps - e.g. Reaper and for others it prompts you to open the AppStore and for others it's a manual update - sometimes it will have info about the release and sometimes not. Anyway, it makes life much easier. It occassionally knows about beta versions out in the wild which you can't actually download, but that's pretty rare. No nags, no subscription, you just have to buy the right version to get plugin info.

Ironically, although there was a recent update to 2.3.3 I didn't realise there was a new Version 3, so I'll check that out now. EDIT: Version 3 is Ventura only - so that's why they didn't tell me. Smarter than I thought!

Dominic

[thin ice]

Mac Updater has really helped me keep on top of a big plugin folder with all the latest versions. You need the Pro version to scan aax plugins though.

[thierryhenry]

You're a legend for this. Just downloaded MacUpdater and it says 41 of my plugins were in need of an update.

Pro Tools 2022.12 has been crashing for me a lot and this is possibly a big cause. Thank you.

[nstu]

Originally Posted by dominicperry

On the recommendation of someone here I bought MacUpdater.
https://www.corecode.io/macupdater/
I'm using version 2, and you need the Pro Version of Version 2 (about $35, one-off) to get the plugin updater, but it's been really good. I just run it every few days and it tells me what needs updating, including plugins. It's capable of doing the upgrade itself with a single button press for some apps - e.g. Reaper and for others it prompts you to open the AppStore and for others it's a manual update - sometimes it will have info about the release and sometimes not. Anyway, it makes life much easier. It occassionally knows about beta versions out in the wild which you can't actually download, but that's pretty rare. No nags, no subscription, you just have to buy the right version to get plugin info.

Ironically, although there was a recent update to 2.3.3 I didn't realise there was a new Version 3, so I'll check that out now. EDIT: Version 3 is Ventura only - so that's why they didn't tell me. Smarter than I thought!

Dominic

Very helpful and thanks for sharing. Will try this within the next days.