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.
If I take away the Hold Value nodes inside of the subcomposition (attached), it no longer hangs.
Based on port popovers in the parent composition and a Display Console Window in the subcomposition:
First event hits Smooth With Duration With Internal State node's Value and Time input ports.
Event travels through subcomposition and emerges from Smooth With Duration With Internal State node's output port.
Second event hits Smooth With Duration With Internal State node's Value and Time input ports.
Event never makes it in through subcomposition's published input ports.
I don't yet know the details of why, but I'm guessing that the subcomposition is still working on its first time executing. The second event hits the subcomposition node, but inside of the subcomposition, it's still processing the first event.
This is probably a bug involving the way that nodes in the subcomposition are scheduled to execute. Obviously it shouldn't get stuck like that.
However, I don't think the Hold Value nodes are really accomplishing anything in this composition, right? Did you add them because the subcomposition wasn't actually smoothing the data? The problem there is that the Value port is receiving values as fast as the Time port — whereas the Smooth with Duration node and other smooth nodes are intended for the Target to change more slowly than the Time.
My coworker suggested replacing textureLod with texture2D and then adjusting the input texture. The attached composition doesn't get you all the way there (don't know where the radial ripples are coming from), but maybe points you in the right direction.
Floats and integers don't need to be (and shouldn't be) retained and released. Only heap-allocated pointers need it.
A few examples of node classes that use struct instance data are vuo.data.record, vuo.osc.send, and vuo.scene.twirl. If those don't answer your question, maybe post some of your code here and I can try to give a more specific answer.