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 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.
Estoy practicando para ser competente en español. Si publicas en el foro en español, trataré de responder en la misma manera.
Alastair (@usefuldesign), since there are significant design changes coming in the next major release (thanks to suggestions from you and others in the community), let's reassess after that: is wire tracing still a problem, and if so, how would rainbow cables or other solutions work out with the new design?
Yeah, the current Filter Skeleton node uses NI mate's "Basic" OSC mapping, which is just positions. NI mate also has a "Basic + Orientation" mapping that includes rotations. In your composition, maybe you could calculate the rotations from the joint positions using Make Quaternion from Vectors.
@ou, I've turned your question into a feature request, since Vuo doesn't currently have any blob tracking built in, and that would be a great addition.
In the meantime, you may be able to use some external software that tracks blobs and sends OSC data to Vuo. One that I have heard of, but not tried myself, is KVL_Kinect_Tracker.
To implement a blob tracking node in Vuo, we're considering integrating a piece of software called OpenPTrack. Since OpenPTrack can output UDP messages, an alternative to this feature request would be Send and receive data via TCP and UDP. It would be more general-purpose (support communicating with other things besides OpenPTrack) but would mean you'd have to handle the UDP messages from OpenPTrack within your Vuo composition, rather than having a node that converts them to tracking data for you.