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.
We’re actually going to be doing a poll soon to ask you / the community for your input on how Vuo’s development should be funded. We’re considering changes to how much / how often people have to pay for Vuo, to try to get a lot more people using Vuo and helping fund its development. Stay tuned :)
Nooooo! :p Can you think of anything different between when it works and when it doesn't? For example, you had more applications running / more CPU load when it didn't work? Have you tried breaking down the composition into smaller pieces to try to narrow down the problem?
@Bodysoulspirit, the iTunes music library is in a special (Apple-specific) XML format called a property list — which is convenient for some purposes, but unfortunately not for locating items in the XML.
Possibly we could enable the Make Tree from XML node to detect if the XML is a property list, and if so, turn the keys into element names and the values into content.
Anyone else interested in using the iTunes file or other property lists in Vuo?