Pt 2022.5?

[jeffro]

Originally Posted by zoff

I'm getting an Activation dialog and apparently the activation process is not finding the correct iLok. iLok2 is showing on the list of License Locations but all my licenses are on iLok3.

Update: I seem to be having an iLok problem.

I'll follow up directly. Mind if we split this off to a new thread?

[XJENSEN]

Originally Posted by off the wall

I still see the same exact Mojave info as 2022.4:



macOS Mojave

With the qualification of Monterey 12.3 we will no longer be testing macOS Mojave, however it is expected to work at this time.

Yes, 'expected' to work (whatever that means in AVID terms). But no longer supported.

[off the wall]

Originally Posted by XJENSEN

Yes, 'expected' to work (whatever that means in AVID terms). But no longer supported.

Gotcha, what I was trying to say is that there is no change from 2022.4 to 2022.5. That is exactly what it said on the last release.

[Eric Lambert]

Originally Posted by gives

It’s almost entirely comprised of bug fixes from the previous release according Avid.

G

It does seem that the beach balls have gone away after this update. I now only see them when saving the session.

And it's tough to say because it varies from session to session, but I *think* scrolling and moving notes/audio is also faster and smoother.

So far so good.

[Dizzi45Z]

Thank you Avid for this 2022.5 release.

So far, not a single crash on this new version and things just feel more stable overall. I was previously getting 5-8 crashes a day and then on top of that, the licensing issues were requiring me to shut Pro Tools down 3 times a day. I was dreading working in Pro Tools this last month. So thank you for getting this .5 release to us sooner rather than later.

All major issues are now resolved for me and I can feel creative again. Yay!

[M2E]

I keep getting a pop-up saying:"The HW device is at a different sample rate from the open session."
I never use to get this before. Just wondering if I'm the only one.
What could be causing this?

Thanks, Marc

[Daveporter33765]

Originally Posted by M2E

I keep getting a pop-up saying:"The HW device is at a different sample rate from the open session."
I never use to get this before. Just wondering if I'm the only one.
What could be causing this?

Thanks, Marc

The message you are receiving is telling you that the sample rate selected for your project does not match the sample rate that your audio interface devise is currently set to. For example, if the sample rate of a project is 44.1 kHz (a choice made when the project was started) and the audio interface is currently set to 48 kHz (could be a choice made from the audio interface control app or the audio interface sample rate changed on its own when your DAW or some other audio software or connected hardware caused the audio interface sample rate to change) there will be a sample rate mismatch and you will receive the message you referenced.

[Franklyn]

Originally Posted by Daveporter33765

The message you are receiving is telling you that the sample rate selected for your project does not match the sample rate that your audio interface devise is currently set to. For example, if the sample rate of a project is 44.1 kHz (a choice made when the project was started) and the audio interface is currently set to 48 kHz (could be a choice made from the audio interface control app or the audio interface sample rate changed on its own when your DAW or some other audio software or connected hardware caused the audio interface sample rate to change) there will be a sample rate mismatch and you will receive the message you referenced.

I get this message only if my interface is used by another app. If not, it normaly changes the SampleRate without the message

[docric]

2022.5 stable here after 1 full day... no "ILM/PT license" issues, although prob due to uninstalling Avid Link completely.

[Emi]

Originally Posted by docric

2022.5 stable here after 1 full day... no "ILM/PT license" issues, although prob due to uninstalling Avid Link completely.

That´s the first thing I do, even before I start pro tools for the first time after updating.