●○○○ — Not much; I'm just letting you know about it.
Steps causing the bug to occur:
Reported in 127 alpha 1 was that no finished playback event was sent, trying to cycle through a list of movies now I'm getting the finished event, but I'm getting a crash after 2 movies played or after the lists wraps at position 1 again)
Create any minimal setup to send OSC messages with Vuo (my example composition is attached)
Open some other application to see what messages Vuo sends (I have tested with Osculator and with VDMX)
All messages sent from Vuo comes 3 times to receiving application
Have you found a workaround?:
You can see from my screenshot, there is minimal example composition which sends one number to OSC output when screen is clicked. (There is input console of Osculator open, which shows all incoming OSC messages with time stamps. So all numbers coming from Vuo, comes 3 times with almost same time stamp. (So, before that screenshot I have clicked 3 times, but 9 messages have been sent). I have tested same with VDMX and with couple of much more complex OSC out compositions, but now I just narrowed this down to find a reason why my OSC "bus" is so full of messages.
This is annoying, but I don't know how to work around it. I have problem with too much OSC traffic which makes, my OSC receiving VDMX behave less responsive, so fixing this bug would cut the traffic to third.