Hi, that is very interesting and promising that you have it working, thank you for replying.
Ports used on AtemOSC are 3333 in 4444 out, same in OSculator. In VDMX I am not actively using any OSC, but attached what ports each apps lists in use, seems like VDMX creates a port 1234 on its own. It lists the 3333 and 4444 ports as Output ports. These disappear when I close AtemOSC and Osculator respectively.
I tried on all machines, including the local one after learning that you could make it work also locally. Whenever I launch VDMX, on any machine on the same network, within 1 second, AtemOSC stops working. I turned of WIFI on the separate VDMX machine, and relaunched VDMX, then I had no problem of course, VDMX loaded, and AtemOSC kept working. But the very moment I turned on WIFI on this machine again, AtemOSC stopped responding.
Once I restart AtemOSC, it runs fine for hours. It is only the bootup of VDMX that glitches. So it’s not a showstopper, but would like to either solve this or report a bug.
All apps + Mojave latest version.
