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.
David, thanks for reporting this performance bug. Confirmed that we can reproduce the problem. The code is doing a lot of unnecessary work while seeking (decoding frames that are just being skimmed past).
Yes, please! My coworker tried to reproduce the crash using the steps you gave, and didn't see it — but he did get a crash if he closed the composition at the end. The latter crash is already fixed in our code under development. If you can send the crash report, we can see if it's the same bug or a different one.
Another thing you could try is to go to System Preferences > Mission Control and toggle the "Displays have separate Spaces" setting, then log out and log back in, and see how the performance compares.
To get a more objective measure of performance, you could add a visualization of skipped frames as in the attached composition.
One thing we're thinking of changing based on your comments so far — As you observed, currently you need a Resize Image to scale the image back up to the screensaver's expected size. We could change the wrap mode on the output image from "clamp" to "stretch" so you wouldn't need the Resize Image (and extra processing that it incurs). Assuming that doesn't break anything else.