Network issues with ATEM and Mac OS Sequoia

Raising this issue on this forum. New LAN security policies implemented in Apple OS Sequoia are wreaking havoc with all kinds of AV devices controlled via LAN networking. This includes ATEM switchers, DANTE devices, Companion, Stream Decks, etc, etc. We have now run across this on multiple forums, and have experience it trying to use Macbooks that were upgraded to Sequoia as control laptops with ATEM Constellation 8K switchers - with multiple consistant instances of the problem. Laptops still running Sonoma have no issues. Apple has published an article about the new local network security requirements for devices on the LAN. We need BMD to address this critical issue ASAP - as it will bring critical AV equipment to a halt if not corrected.

BEWARE OF MACBOOKS ON SEQUOIA WITH ATEMS!!!

https://developer.apple.com/documentati ... rk-privacy

We have found this work around and tested it - it temporarily solves the problem (until the laptop is rebooted). Go into Settings>Privacy&Security>Local Network, and turn off all the apps in the list - then turn them back on. This will clear the issue until the Mac is next booted. This will resolve Macs on OS 15.x not connecting to BMD switchers, routers, and Streamdecks via Companion. This seems to be especially true on local AV networks tied together via an unmanaged switch. Not sure if the long term fix for this needs to come from Apple, or the hardware/software makers.

This is so real and just about killed us a week ago. Not just a MacBook issue, we lost all ATEM control on a Mac mini and Mac Studio. Also Dante Virtual Soundcard. Had roll back to Sonoma 14.6 to get things working again.

Have found the same problem with my M2 Mac mini running Sequoia 15.3.2 and ATEM Software 9.6.3. The set up software would see the ATEM 4 ME Constellation I am using but would not connect. As a test, I hooked up my old MacBook Pro running Monetary 12.7.6 and 9.7 ATEM software. Connected immediately.

I tried "fbella"s method listed below and connected right away. Thank you for that. Shutting down the computer and restarting, the problem comes back.

I am going to try and roll back to Sonoma 14.6 as "michael.arman" has suggested and see if that fixes the problem. Certainly a bug in the software that BlackMagic/Apple needs to address.

People have been experiencing the same issue with Companion, and some of them have reported that it only seems to happen when they have a static ip set on the mac. It would be interesting to know if the same is true here.

If anyone is able to try this using DHCP instead, it would be good to confirm if that resolves the issue.

If it is down to whether it is using a static ip or dhcp, then I am pretty confident in calling this a macos bug, and not something that can be fixed in other software

So an update...

I reached out to Blackmagic Support via email and actually got a response in less than 24 hours. So first hats off to the BM support team.

I was given the following steps to go through in establishing a connection. I have been doing this a long time with BM ATEM's. But these steps were slightly different than what I typically do. So I proceeded with skepticism. Bottom line it worked. First time rebooting the Mac and launching the ATEM control software takes a while to find the switcher. Like 20-30 seconds. So be patient. Here are the steps:

NETWWORK SETUP
Make sure the USB cable is the only cable attached to the ATEM and connect to the computer. Be sure the Ethernet cable is disconnected from the ATEM at this time as well.

First, obtain the IP address, subnet mask, and gateway/router of the computer connected to the network. On Mac, this can be done opening the network settings of system preferences.
On Windows, pull up a command prompt (type cmd in the search bar), and in the command window type Ipconfig/all. Press enter to retrieve the information. For this example, we’ll use the following:

IP Address: 192.168.10. 100
Subnet Mask: 255.255.255.0
Gateway/Router: 192.168.10.1

Close the network settings

Launch ATEM setup, and click the configuration button below the ATEM’s name.

For the IP address, enter the first 3 Octets from the IP found from the network, but change the last octet to an unused number between 0-255. In this example we'll change the number to 50. The final IP entered would be 192.168.10.50).

The Subnet Mask and Gateway have to be identical to the network settings. Here’s what should be set in ATEM Setup:

IP address: 192.168.10.50
Subnet Mask: 255.255.255.0
Gateway/Router: 192.168.10.1

Save the new settings in ATEM Setup, and those the program. Disconnect the USB cable from the ATEM and computer.

Restart the computer. While the computer is resetting, unplug the power from the ATEM for 20 seconds. After 20 seconds, re-apply the power, then connect the Ethernet cable between the ATEM and the network router/hub.

Launch ATEM Control, and your device should be detected. If you are asked for an IP address, enter the IP address from ATEM Setup (our example is 192.168.10.50). From here the ATEM should be connected.

I'll keep checking this over the next several days to be sure nothing changes. I still gave my Mac a manual IP address. No DHCP. I have never found that to work. I'll try if I have trouble with companion.

Do you have enabled wifi ?

I have not problem with Seqoia and Atem Control station ..

But these steps were slightly different than what I typically do. So I proceeded with skepticism.

Other than the fiddly bit at the end, this is a standard manual configuration. Were you using DHCP previously? I’ve noticed unrelated DNS issues under Sequoia when returning to known networks after upgrading MacOS. It might be a good idea to “forget” networks established in prior OSes and re-establish them under Sequoia.

In my experience and that of several colleagues, Sequoia is the least stable release since 10.0, and I don’t mean Yosemite.

Good Luck

Edit: Two minutes after posting received this message from a different vendor RE a bug

The affected functionality is Sequoia’s System Settings > Security and Privacy > Local Network permissions.

After running the ATEM and network settings as BM had recommended, I was able to shut down and restart on multiple occasions with no problems. I felt confident the problem was solved. I was wrong. This morning preparing for a live broadcast I found that the iMac mini no longer recognized the ATEM on the network. Seriously, no changes, no updates, just sitting for a while with the power off to all devices.

I have never used DHCP to connect my ATEM devices and have always made sure all devices do not have the same address. Never had trouble frankly in the past. Once again, "fbella"s method works great in recovering the connection.

I will reconnect with BM support for any final advice but I will likely go back an operating system until APPLE/BM figure this one out.