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.
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.
What would be an example of a situation where this would be a better solution than the proposed Target Framerate?
Not sure if better, but maybe a couple different ways of looking at it. I would assume jersmi 's method would result in lower system overhead in total, considering fewer (duplicate) frames. As someone that deals with broadcast equipment a lot (looking at you Blackmagic), along with Powerpoint that does exactly this, I can hardly say I'm a fan of the approach.
With a "get system refresh rate" you can easily divide it with any integer to get a subdivision of the framerate. That way you can not only trigger at half framerate, but also get every fifth frame for instance - for less important/time sensitive tasks.
While the time output ports don't output the exact same time for Display Refresh vs Divide set to 1/60 (which I hope is not a big deal)
This is just the info overlay rounding up
Can you explain how that would make it easier ?
If using Fire Periodically 1/60 will always output the same no matter the display no ?
Fire periodically will fire at a set rate, but if it will sync up to your display output rate is something different. This is probably why your older iMac stutters as well. If system framerate is set to 75Hz, and you fire at 60Hz, these only match up every fifth frame. Then it can be a bit hit and miss when you get sync. This is probably why jersmi wants system setting control, and is why I think a get "system refresh rate" would be neat :).