-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
atem Blackmagic Design not connecting #348
Comments
Presumably the same issue as bitfocus/companion#3143 |
oh yeah. I keep forgetting that issue is specific to intel macos.. |
Hey I think this is actually NOT specific to intel macs... I believe this is only true for certain chips. Someone else posted on the same thread I started they where using an M4 mini and had the same issue. I can't confirm this, but will be able to in the next 2 weeks. We should some M4 mac minis coming in. I'll be able to throw companion on one of them and find out. OP of this thread didn't mention specs... I can assume it's an M4 though? I would recommend as a fix to this issue, OP turns on and off the local network permission for companion. This is the only fix I've seemed to find. Even if it's enabled to start wtih, turning it on and off again seems to fix it... I wish it would just stay fixed though |
This bug is also manifesting on my client's new system with 2 brand new M4 Pro Mac minis running all the latest software as of 22 Jan 2025 and macOS 15.2. Both Mac minis are connected directly to the ATEM Television Studio 4K8 via ethernet and can control the ATEM via ATEM Software Control. My older M1 Pro MacBook Pro can connect to the ATEM Television Studio 4K8 through Companion. So this confirms what you all have already observed. Any ideas on a timeline to fix this bug? This client wants to start using this and a 2nd studio with the same setup starting next week. 😅 |
@Lukeb873 I was able to enable local network permission for companion to get it to connect again on the M1 iMac we were using so thanks for pointing me to that setting. I have not been able to verify if the setting holds through a reboot yet. |
@meonlylouder and @jefferyhartman I would HIGHLY suggest reading through bug#3143. This talks about the local network permission being turned on and off and how it fixes it. However if you're adjusting ANY local network permission even if it's not companion it fixes it. This does NOT hold on reboot from my tests. You have to enable and disable it everytime the computer restarts. |
Everything was working great for a few months and then it wasn't. Likely due to a imac OS update as that is the only change I know about. Currently cannot connect, just shows connecting in Companion Connections. I've tried toggling the connection off and on, changing the IP address, updating Bitfocus companion, updating atem switcher firmware(and downgrading to a couple of different versions but nothing seems to work). I can connect to the ATEM control software from the same computer and control the switcher just fine and am using one ethernet cable to connect the switcher to the computer without a network switch. USB cable to the switcher is unplugged so I'm controlling it via network. I've selected the GUI interface to be on the same network as the switcher but tried the other options as well.
Currently running:
MacOS Sequoia 15.2
Bitfocus Companion v3.4.3
ATEM 9.6.3
Any other thoughts?
Support Bundle is attached.
iMac_companion-config_20250107-1504.zip
The text was updated successfully, but these errors were encountered: