macOS Monterey 12.3 officially supported!

[JamesG602]

Originally Posted by glasswing

I get mine mid April - 128 RAM/2TB HD. Maybe you should start a new discussion and keep us all up to date. I think there are a LOT of soon to be Mac Studio owners here. How much RAM are you using? I'm curious about your setup. Thanks!!!

Mine is the base Ultra, which has the 48 core GPU, and 64GB RAM, 1TB HD.

In the HDX forum I started a thread!

[DerrickC]

Originally Posted by paul_g

Yes, but before you just upgrade, double check all your drivers for your 3rd party interfaces, etc, and 3rd plug-in's.

For example, UAD is not Monterey compatible yet.

Good reminder! Though it’s true that there are reported cases where UAD works with Monterey, I’ll probably wait till it’s officially supported by UAD.

Thx!!

[TimNielsen]

Some asked about Stratus and Symphony, and sadly no, they, along with R4 for me refused to work in 12.3. Pheonixverb Surround and R2 Surround work though. I hope they fix those soon, hard for me to work without those.

I just installed everything on a new Ultra, so far it's a great machine, but ProTools under Rosetta actually eat up MORE resources than my decade old Mac Pro 5.1. Comparing the Netflix demo session, my old machine runs it with less overall CPU percentage. Avid needs to be working on M1 support. From what I can tell they appear to be in zero hurry to do so.

[itsjustmeee123]

It looks like Antares auto-tune pro is falling behind and isn't compatible with Monterey yet so unless someone else has been able to make it work, I'll have to hold off updating my OS.

[Eric Lambert]

Originally Posted by TimNielsen

I just installed everything on a new Ultra, so far it's a great machine, but ProTools under Rosetta actually eat up MORE resources than my decade old Mac Pro 5.1.

That really surprises me. All that horsepower, dropped down to 5,1 levels. I'd heard from some others that their M1 MacMinis, which have less power than the Studios, were outpacing their older 5,1s by a solid margin. I wonder what, specifically, is bringing down your Studio.

[JamesG602]

Pretty sure there are some issues with the cpu meter in protools, always have been, specifically more so on the Studios.

[caseystone]

anyone reading Tim's post here, see update on this thread (spoiler, GOOD NEWS!):


https://duc.avid.com/showthread.php?...63#post2630663


EDIT: maybe not good news!

[FilterDecay]

Originally Posted by Eric Lambert

That really surprises me. All that horsepower, dropped down to 5,1 levels. I'd heard from some others that their M1 MacMinis, which have less power than the Studios, were outpacing their older 5,1s by a solid margin. I wonder what, specifically, is bringing down your Studio.

most people arent actually pushing these machines. Synthetic dverb tests dont really tell the full story.

[FilterDecay]

Originally Posted by caseystone

anyone reading Tim's post here, see update on this thread (spoiler, GOOD NEWS!):


https://duc.avid.com/showthread.php?...63#post2630663

but what changed tho? Why was he getting 5.1 cheese grater level performance first and now not? Does that session have plug ins in it? I had a fresh protools install no plug ins and it ran well aside from the memory issues. As soon as I installed fabfilter then it took a crap.

[JamesG602]

Reading through, he was getting “lower” performance according to the CPU meter, but in actuality the session was running fine. Again, on these new mac studios and protools there seems to be some very misleading info given out by the protools cpu meter.