Pro Tools 2023.3 is out

[Eric Lambert]

Originally Posted by bernstudios

anyone running 2022.10 and 2023.3 on the same M1 machine without problems?

I'd shy away from doing this if possible. As PT versions start to get further apart, things like preference files begin to deviate and PT may not like swapping back and forth. i.e: 2023.3 adds some components to the Pref file which 2022.10 won't understand. It may work fine until one day you alter one of those parameters that are unique to 2023.3, then it creates trouble.

Unless they reference different (bespoke) pref files, but I don't believe that's the case.

[Daveporter33765]

Originally Posted by Eric Lambert

It was definitely a problem back when PT was a 32-bit app and it couldn't work with more than 4GB oF RAM (not enough to get all plugin into memory that first time), but since PT11(ish) it should be able to load everything in without issue. Unless you have overall RAM limitations. How much RAM do you have?

Regardless, your comment about loading 1/2 at a time is a solid workaround. I'm just saying that it *shouldn't* be necessary with as far as PT is concerned.

I had to trash preferences after the 2023.3 update because I was not seeing several plugins. When I restarted Pro Tools Studio it crashed half way through validating my extensive plugin library several times. I had to resort to moving half my plugins out of my plugin folder and then starting Pro Tools. Then close Pro Tools and return all the moved plugins back into the plugins folder before restarting Pro Tools. Everything was fine after I set all my preference settings.

[Fishbone]

Just find out that Plugin Alliance silently released AAX Apple silicon native versions of almost all Lindell and NEOLD plugins alongside with a couple of other odd balls. Sweet!

[JFreak]

My apologies for using the word "retarded". It is not such a strong word here. I promise to try to remember this in the future. Sorry for the upset everyone, it was unintentional.

[thin ice]

Nice one Janne. It is too easy to get caught out these days, when there is no real intent.

[K Roche]

Originally Posted by Eric Lambert

I've had PT open for hours on end and there's no hint of such issues. I've not even heard of this from anyone else. I'd guess it's an unfortunate but unique problem, seemingly related to hardware/software interaction.

Yep it turns that at his facility there are multiple PT systems
Quote : Ok, I found the culprit(s). More my fault than anything else. On the way off chance that someone finds themselves in the same boat here's the scoop. Normal Pro Tools updates leave the i/o section and the peripheral sections untouched. I believe that was the case on my first install of 2023.3. On the second install, the peripheral setup was wiped out. So one of my midi devices (the Faderport) was sending out midi data that Pro Tools didn't know how to handle. Softsynths would just get this barrage of midi data and that turned into distorted, regurgitating noise, and ultimately into feedback. I merely had to rebuild the peripheral section and everything got rock solid.

[fredrikalpi]

Too many bugs with PT 2023.3: shortcuts only appear as QWERTY even if your system is set on AZERTY. Several plugins won't work (Empirical Labs Arousor and Big FrEQ, as well as Two-Notes Torpedo Wall Of Sound, amongst others). I went back to 2022.9. Seems wiser at the moment, until all these bugs are solved by Avid and plugin developers.

[Sardi]

Originally Posted by fredrikalpi

Too many bugs with PT 2023.3: shortcuts only appear as QWERTY even if your system is set on AZERTY. Several plugins won't work (Empirical Labs Arousor and Big FrEQ, as well as Two-Notes Torpedo Wall Of Sound, amongst others). I went back to 2022.9. Seems wiser at the moment, until all these bugs are solved by Avid and plugin developers.

A plugin not being AS native is not a bug.


Sent from my iPhone using Tapatalk

[Jay_uk]

Originally Posted by JFreak

My apologies for using the word "retarded". It is not such a strong word here. I promise to try to remember this in the future. Sorry for the upset everyone, it was unintentional.

Maybe 'Tardy' (slow/latecomer) was on the tip of your tongue, it has the same Latin derivation. I can see how it may differ in other Countries. It was unintentional and context is everything.
back to topic...

[RobertDorn]

Originally Posted by Jay_uk

Maybe 'Tardy' (slow/latecomer) was on the tip of your tongue, it has the same Latin derivation. I can see how it may differ in other Countries. It was unintentional and context is everything.
back to topic...

Yes, back to topic. Pro Tools is finally out of beta stage for silicon native. And now opens as silicon native by default instead of under Rosetta2. Big hand for all third party developers who were super fast in porting their plugins to AAX silicon. For all developers that have had silicon native versions of their AU/VST3 plugins for almost 2 years now and still need to find the time to do the same thing again for AAX: understandable. Eventually, the real latecomer here has been AVID