macOS Monterey 12.3 officially supported!

[FilterDecay]

Originally Posted by 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.

yeah i can see how hat could happen. But when i oopened a session on a macbook pro with a m1pro it was fine until I put plug ins then it was all digital hash clicks like when you overload the cpu. Thats why I am confused.

[JamesG602]

That’s likely more plug-in related, something not being compatible with M1 or Monterey. In logic I was having the same issues with certain plugins, using them would instantly overload the session, without it it was more than fine.

[Eric Lambert]

SSL Duende users take note that SSL has said that Duende is not supported in Monterey and they are doing nothing to make it so. The latest version (2) will open, but the originals (x86) and even those with the newer GUIs (v6) get the AAE error. When asked how we can migrate to the newer versions, the response was 'we're doing nothing.'

We have hundreds of sessions using these original AAX plugins, and at this point they're the *ONLY* ones that will not make the transition to Monterey according to the developer. And SSL has offered no advice for accessing those hundreds of sessions.

We went through this when they moved from hardware to software, and from RTAS to AAX, and no again into Monterey. We've spent thousands of dollars on their hardware and software, in 5 different rooms, only to get 'you're on your own.'

FWIW, I'm under the impression that these plugins *can* be updated.

With this response, SSL will never again receive a dime or any kind of recommendation from us or our partners.

[JoeTools1963]

Originally Posted by Eric Lambert

SSL Duende users take note that SSL has said that Duende is not supported in Monterey and they are doing nothing to make it so. The latest version (2) will open, but the originals (x86) and even those with the newer GUIs (v6) get the AAE error. When asked how we can migrate to the newer versions, the response was 'we're doing nothing.'

We have hundreds of sessions using these original AAX plugins, and at this point they're the *ONLY* ones that will not make the transition to Monterey according to the developer. And SSL has offered no advice for accessing those hundreds of sessions.

We went through this when they moved from hardware to software, and from RTAS to AAX, and no again into Monterey. We've spent thousands of dollars on their hardware and software, in 5 different rooms, only to get 'you're on your own.'

FWIW, I'm under the impression that these plugins *can* be updated.

With this response, SSL will never again receive a dime or any kind of recommendation from us or our partners.

That is super sad man!! That is the worst customer service I have ever heard of.

[Eric Lambert]

Originally Posted by JoeTools1963

That is super sad man!! That is the worst customer service I have ever heard of.

And the saga is just getting started I'm afraid. After a couple more attempts to get an answer of any kind, it's just a string of rude remarks and dismissive text. The company has changed since the good ol' days with Jim Motley and crew as solid teammates. We'll see where it leads -- we simply don't have the option of letting these important sessions die.

I never thought I'd see a day where SSL is difficult to deal with and AIR is an absolute dream -- a swap-a-roo from the old days -- but this has been my experience this morning.

edit: It shouldn't have been necessary but I've reached out to some old friends at SSL and hopeful that they'll be able to assist.

[Daveporter33765]

After substantial research, I concluded that the DAW software, plug-ins, and hardware drivers we rely on now support Monterey. So I bit the bullet and upgrade our Studio B iMac to Monterey last night. The installation went very smooth. I then spent a few hours testing each DAW, plug-in and piece of hardware, again, everything went well…no issues at all. Today I upgraded our Studio A iMac to Monterey and everything went equally well. After more testing this afternoon we are finding that Monterey is more responsive and “snappier” than Big Sur. So far so good!

[Eric Lambert]

Originally Posted by Daveporter33765

...Monterey is more responsive and “snappier” than Big Sur. So far so good!

I'm finding the same thing.

[JoeTools1963]

Originally Posted by Eric Lambert

And the saga is just getting started I'm afraid. After a couple more attempts to get an answer of any kind, it's just a string of rude remarks and dismissive text. The company has changed since the good ol' days with Jim Motley and crew as solid teammates. We'll see where it leads -- we simply don't have the option of letting these important sessions die.

I never thought I'd see a day where SSL is difficult to deal with and AIR is an absolute dream -- a swap-a-roo from the old days -- but this has been my experience this morning.

edit: It shouldn't have been necessary but I've reached out to some old friends at SSL and hopeful that they'll be able to assist.

Sounds to me like they need to re-code that software for the new environment. Full stop.

[JoeTools1963]

I just finished a television series on PT2021.12 Ultimate running on Big Sur.



Last week like many of us, I upgraded to Monterey.



I went to open one of the sessions today and it gave me a MISSING CODEC error. Called support to no avail. I suggested that maybe an extension switch would perhaps fix the issue.



The original was .MP4, changed the extension to .MOV and re-imported the video. Boom, problem solved.

This is where it gets weird!!

I opened up another session from the same series with the extension .MP4 still intact and it opened fine. Prior to this, the same session had given the same error. I was able to open every session in the series without issue with the .MP4 extension left as is. All had failed to open prior to changing the extension on "ONLY ONE" of the videos in the series.

[K Roche]

Originally Posted by JoeTools1963

I just finished a television series on PT2021.12 Ultimate running on Big Sur.



Last week like many of us, I upgraded to Monterey.



I went to open one of the sessions today and it gave me a MISSING CODEC error. Called support to no avail. I suggested that maybe an extension switch would perhaps fix the issue.



The original was .MP4, changed the extension top .MOV and re-imported the video. Boom, problem solved.

This is where it gets weird!!

I opened up another session from the same series with the extension .MP4 still intact and it opened fine. Prior to this, the same session had given the same error. I was able to open every session in the series without issue with the .MP4 extension left as is. All had failed to open prior to changing the extension on "ONLY ONE" of the videos in the series.

Humm Strange indeed. Can only conclude software gremlins must be screwing with your head.