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.
Walking across the stage at their convocation ceremony is a symbolic moment in the lives of graduating students. For the families and friends of graduates at Loyalist College, that moment has been made more visible by the addition of a graphics system engineered by Chris Wilms (Chris (@cwilmsloyalist)).
The problem was that every event that went into the subcomposition would go through your "Data" node through Take from List and hit the Set Target input port of Smooth with Inertia. The Target port is supposed to get an event only when you want to change the target, not every frame. The purpose of the nodes I inserted between the Data published port and the "Data" node was to block all events to "Data" except when the target is supposed to change.
Yes, here's a fix. I was going to propose inserting an Allow Changes node into your subcomposition, between the Data published input and the node labeled Data, but that node doesn't work on lists yet. So instead I added another published input to the subcomposition to detect changes.