atemOSC
atemOSC copied to clipboard
SteffeyDev
Not Connecting
Hiya- I've d/l the latest version of AtemOSC and installed it on my 2012 Macbook Pro Running Catalina
ATEM Software connects, using default network address.
When I attempt to connect ATEM OSC, it tries five times, and gives up.
I've also tried a couple of earlier versions, in case it has moved away from 2012. Still no joy.
Any suggestions?
What is the "default network address" that ATEM software control uses? Sounds like a network issue, could be a firewall preventing atemOSC specifically from accessing the network.
Hi-
I mean the default IP address. The software opens, the graphical interface is functional. ATEM OSC opens, and tries to connect to the switcher, but fails.
Screenshot attached.
WDC
On Tuesday, June 1, 2021, 07:02:43 PM PDT, Peter Steffey @.***> wrote:
What is the "default network address" that ATEM software control uses? Sounds like a network issue, could be a firewall preventing atemOSC specifically from accessing the network.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Screenshot didn't make it, you'll probably have to post it on GitHub directly instead of using email
Thanks for your help, Peter
The IP address that my MacBook uses to communicate with the switcher is the default under the Atem Software Setup. I know that it is correct, because the software shows up!.
192.168.10.240, in this case.
I assumed that the Atem OSC would use the same IP address. Both softwares are running directly on the Mac.
I believe that Atem OSC should communicate right away. Instead, it tries to hook up five times, and stops.
What am I doing wrong!?
Bill
I have very little control over the connection process, I just pass off the IP to the same function that ATEM Software Control uses and let it handle the connection. Only thing I can think of is maybe you have some sort of application firewall that is blocking atemOSC but not ATEM Software Control from connecting to that IP. You can always try "re-installing" atemOSC by deleting the app and then dragging it from a fresh DMG, maybe that will help.
Hi Peter Thanks for reply... I have tried reinstalling but get the same issue. I have checked my firewall and it is not Blocking the program My Mack is operating on Mojave 10.14.6
Hope this helps
On Sun, Jun 20, 2021 at 11:44 AM Peter Steffey @.***> wrote:
If none of that works, what MacOS version are you running?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/SteffeyDev/atemOSC/issues/223#issuecomment-864573268, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNOLQLWAX2SDYR6LAP7QWDTTYEELANCNFSM454ZNDLA .
-- Cheers, Danny
I'm having this same issue after upgrading from atemOSC 3.1.4 to 4.2. It used to connect without a problem, but now, even though ATEM Software Control connects without a hitch, atemOSC fails in every case.
Update: More specifically, my ATEM Mini is connected via USB only — no ethernet. I was able to downgrade to atemOSC 3.1.6, and atemOSC connected to my ATEM without an issue on 192.168.88.255. Moving back to atemOSC 4.2, the connection couldn't be made when entering the same IP.
So something changed between version 3 and 4 that breaks direct connections over USB. I'm on MacOS 12.4, if that helps, but I don't think that's the issue, since atemOSC 3.1.4 connects just fine.
Further update: As it turns out, in v3.1.4, atemOSC seems to search for the connected ATEM regardless of the entered IP address, at startup, and finds it. To reproduce: •open atemOSC, it connects to ATEM. •now enter a random IP address, hit enter; atemOSC now cannot connect to ATEM. •now quit atemOSC, then reopen it. The previously entered random IP address is still listed, but atemOSC connects successfully to the ATEM!
This approach does not work on atemOSC 4.2.0.
Thanks for the details. I'll have to spend some time to investigate what I changed in the code that may have caused this issue.
No worries Peter I’ve moved on to another solution thnx for the effort
On Mon, Jul 25, 2022 at 10:01 PM Peter Steffey @.***> wrote:
Thanks for the details. I'll have to spend some time to investigate what I changed in the code that may have caused this issue.
— Reply to this email directly, view it on GitHub https://github.com/SteffeyDev/atemOSC/issues/223#issuecomment-1194884631, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNOLQK36OY6IM2P3QMHIWLVV5BHHANCNFSM454ZNDLA . You are receiving this because you commented.Message ID: @.***>
-- Cheers, Danny