MacOS 13.4.1

[Obsidian Dragon]

Updated my MacOS from 13.4.0 to 13.4.1 on my Intel and Apple Silicon Macs yesterday and ran some quick sessions (not a deep dive) through Protools 2023.6. Everything that worked before looks good so far, no obvious issues for this OS update (mostly security fixes).

[gthm]

Thanks for the heads up! Downloading now

[audiogamble]

This morning I decided to update my M1Max machine. The computer behaving unexpectedly afterwards. Many peripherals wouldn't connect. I could open pro tools sessions, but the songs didn't sound anything like how I left them, and delay compensation was broken. I fixed it by booting once into safe mode, and then booting normally again. Now everything's working as expected.

PSA for anyone else who runs into a similar issue.

[littlesicily]

After updating to 13.4.1 Pro Tools will no longer link with Eucon for my S1!

[mgoorevich]

Works perfectly here. My specs are in the signature below.

[littlesicily]

Originally Posted by mgoorevich

Works perfectly here. My specs are in the signature below.

I see you are on intel. I’m on m2 silicon.

[BScout]

Try, this: with ProTools and a session open, press the Eucon button in ProTools to turn it off, then quit Eucxontrol running on the computer, then restart Eucontrol, press the Eucon button in ProTools and hopefully the status light will go to green.
Then you can refocus to ProTools and add it to the Application whitelist in Eucontrol.

[littlesicily]

Originally Posted by BScout

Try, this: with ProTools and a session open, press the Eucon button in ProTools to turn it off, then quit Eucxontrol running on the computer, then restart Eucontrol, press the Eucon button in ProTools and hopefully the status light will go to green.
Then you can refocus to ProTools and add it to the Application whitelist in Eucontrol.

Thank you. Tried those steps and no luck. Eucon status light still off. I was on the phone with Avid support for close to an hour today. They *think* that when I boot PT in Rosetta, the S1/Eucon doesn't share a similar IP address. Not sure why that would be the case as it links fine with PT boots silicon native.

[its2loud]

Did you allow accessibility in the system prefs?

Try running Eucon under Rosetta and make sure when you updated to Ventura that you still have the correct Eucon Ethernet port selected in the preferences.

[littlesicily]

Originally Posted by its2loud

Did you allow accessibility in the system prefs?

Try running Eucon under Rosetta and make sure when you updated to Ventura that you still have the correct Eucon Ethernet port selected in the preferences.

Yes, accessibility allowed and verified by Avid tech.

The computer shipped with Ventura 13.4.0, but when I updated to 13.4.1 is when the problem started. I don't even change any settings and S1 works with PT Native, not Rosetta. I also toggled the system Eucon Workstation "network interface" from "ethernet" to "Thunderbolt Ethernet" and no luck.