OK I noticed this last week with Beam v1 but waited until yesterday in the studio to confirm the issue also happens with the v2 beta. If I enter any address into the ArtNet IP address is is sent to the loopback interface, regardless of which interface on my system has that particular subnet. In the attached packet capture screen shot you can see I’ve entered the address of my WiFi interface (en0 192.168.0.219) in the box in Beam but the DMX traffic is still appearing on lo0. The odd thing is when I changed the IP in Beam to a completely random and unused number on the WiFi subnet, the traffic disappeared altogether, no DMX packets in lo0 or en0 or anywhere that I could find.
Have I found a bug or am I doing something so obviously wrong I’m not seeing it? It certainly explains why I had so much trouble getting the Capture demo to work reliably, and why I haven’t yet been able to get my Vuo app to see any Art-Net messages.
Screen shot is of the beta but can confirm this also affects 1.5.2