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.
Bodysoulspirit, so far I haven't been able to reproduce this. If you are able to make it freeze again, could you please go to Activity Monitor, select the Vuo process, go to the gear menu and select Sample Process, and attach that sample here?
Joe, see here for the list of known issues with community nodes in Vuo 2.0.0-beta1.
While your crashes did occur during the loading of installed nodes/subcompositions, based on my testing so far, I would guess that they're not connected to any particular node or subcomposition. (I did briefly test smokris's Stochastic Camera Blur and did not get any crashes.)
Here are test results for all nodes in the node gallery, as of today, in Vuo 2.0.0-beta1.
I only checked if the nodes could be installed and run with their default inputs without crashing. I didn't check if the outputs are correct.
A few times while testing, Vuo (the editor) crashed. However, none of these crashes were consistently caused by any particular node. The "composition crashes" noted in the table below are consistent with a particular node.
One possible difference is that Vuo renders using Retina resolution when possible, whereas QC doesn't (it always renders low resolution). So the performance difference might be because the shader is trying to run at twice the resolution (4 times the number of pixels).
If you add a Divide node to divide the width and height each by 2 before rendering, is the performance more equal?