Hey there, troubles with AtemOSC and VDMX.
I’m using AtemOSC, a tiny app to remote control a Blackmagic Atem Mini on one computer (MBPR Mojave) running Ableton Live, Osculator and AtemOSC. This works fine by itself.
The sequenced Atem Mini HDMI signal is then grabbed into VDMX on a second computer (MBPR Mojave). This also works fine when up and running.
However, everytime I launch VDMX on this second computer (or even a third computer), AtemOSC immediately stops working. The app still shows connection to the device as online, the log shows nothing wrong, it just… stops working, OSC messages never arrive, nothing more happens in the log.
Restarting the AtemOSC app (quit, launch) solves the situation temporarily. So generally I’ve figured the startup sequence is VDMX first, then AtemOSC, but this is a hack, and I’m worried there are deeper problems waiting. Anyone got any idea why this would happen? Does VDMX do some OSC network thing upon start, does it “grab” the ports from AtemOSC, can I disable this, perhaps a preference I haven’t caught on to? Or have I misunderstood OSC somehow.
I’m not using VDMX or any other app for any other OSC traffic. The Live -> Osculator -> AtemOSC -> Atem device is the only OSC activity on the network.
Happy to hear thoughts or other experiences.