Ah! Maybe it just me zoning out a bit. I was trying to get the values from a X/Y position within a layer. Thought I had done it with that node before, but maybe I misremembered :)
When sending OSC string-messages to MA3 lighting consoles (www.malighting.com) over localhost at least, using more than one message input in the "Send OSC Messages" node leads to unexpected results at the receiving end. When using more than one input, it seems they are enclosed in parentheses () which are then not read as multiple addresses/values by the receiver. Further, the parenthesis are in some messages replaced with the number 4 for some reason.
Have you been able to reproduce the problem?:
●●● — Yes, the problem occurs consistently when I follow the steps above
Have you found a workaround?:
Using one "Send OSC Messages" per message produces the intended result.
Other notes:
I'm not sure if the problem is according to the MA implementation of OSC or if it is on Vuo's end. They are extremely rigid about implementations sticking to the spec, so if there are different conventions for implementing OSC, they might have gone for the strictest approach.
I also can't discover MA as an OSC Device from Vuo.
