As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I've been developing apps and frameworks for several years (since I was in college). Pre-Vuo projects include Kineme Quartz Composer plugins, iOS apps for education, an app that analyzes photographs of tomato slices, and software to help people with disabilities use talking keyboards.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
@Kewl, sorry, I was unclear. You told me that when you tested recently with Vuo 1.2.5 the problem was no longer happening. I jumped to the conclusion that you'd been using Vuo 1.2.4 earlier. But if not, no need to test with 1.2.4. If you were using 1.2.5 the whole time, maybe the problem was related to CPU usage by other applications.
@Philip, we just published a Vuo 1.2.6 alpha release that includes a fix for this bug. Despite it being an alpha release, the changes are few and isolated enough that — other than the new nodes added in the release — I would consider it safe to use in production.
@Chris and anyone else who'd like to be testers — we just published a Vuo 1.2.6 alpha release that includes XML/JSON nodes. We'd appreciate if you could try them out and let us know if they do what you need them to do.
The final 1.2.6 release will include much more stuff, including CSV nodes, but we wanted to get your feedback on the XML/JSON nodes sooner.
If you find any problems with the alpha release, please post a bug report. If you have questions/suggestions about the scope of this feature request (what the new nodes will/won't be able to do), please comment here. For other questions/suggestions, probably best to a new discussion thread so it's easier to follow the conversation.