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.
We found the cause of the problem! Because of how our build system works, the VuoCompiler class declaration used when compiling Vuo.framework differs slightly from the header file packaged with Vuo.framework. This messes up the allocation of VuoCompiler in your Xcode project.
It's possible to reproduce the problem with a simple program that links to Vuo.framework, one that just calls new VuoCompiler(). This may run just fine under normal testing. But if you enable Guard Malloc (in Xcode: Edit Scheme > Diagnostics), it consistently crashes at the very beginning of the VuoCompiler constructor.
Thanks for alerting us to this problem, mrray. We'll have it fixed by the final Vuo 2.0.0 release.
Just as Bodysoulspirit said — The intention is that the composition is already zoomed to fit when you open it, but that doesn't always happen. I've updated the bug report's title to reflect that. Thanks for letting us know about this problem, lechbialek.
Bodysoulspirit, so far we haven't been able to reproduce this problem. But we made a change in Vuo 2.0.0-beta2 that might possibly have fixed it. Do you still see the duplicate options in Vuo 2.0.0-beta2?