SteffeyDev / atemOSC

Control ATEM video switchers over the network with OSC messages
http://www.atemosc.com
202 stars 32 forks source link

atemOSC lost connection mid-event, lost all connected switchers #260

Closed STP-Rob closed 7 months ago

STP-Rob commented 2 years ago

I recently had an issue with atemOSC losing connection to my ATEM switcher during an event. I had established connection with my switcher, and OSC commands were successfully being communicated to my switcher through atemOSC. I am not sure exactly when the issue occurred (I discovered it after the event -- my operator was able to take over my ATEM manually), but I discovered atemOSC lost connection to my Switcher, and had wiped all information for connected switchers in the left-hand window -- the only option I had was "Add Switcher".

I have not been able to replicate this since. And upon quitting and restarting atemOSC the switcher information came back and was able to reconnect with my ATEM. I haven't been able to find an issue listed here that describes atemOSC wiping all connected switchers after successfully connecting to a switcher.

I'm running atemOSC 4.2.0, with ATEM Software Control 8.7. My computer is an iMac -- running macOS, version Monterey 12.2.1

SteffeyDev commented 2 years ago

Thanks for reporting. atemOSC is not technically "wiping" the configuration, it is simply failing to correctly render the list (which is why restarting fixes). I've seen this before, specifically in #225 when the app it started on login, and it has something to do with UI rendering order that I don't understand completely. I'm sure I'm just missing some edge case.

If you do see this again, can you copy and attach the logs from the bottom panel? I should probably export those logs to a file for better archiving and debugging, maybe I'll include that in the next release.

STP-Rob commented 2 years ago

Thanks for following up and letting me know! I'll make sure to copy any logs for your reference if I have this happen again.

c434techteam commented 2 years ago

I wonder if this is related to the same thing as my issue #259 but it is hard to say for sure.

SteffeyDev commented 7 months ago

This should be fixed in version 5.