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.
Quite astonished to read that the only fixes for openGL would be to run in on the CPU instead ! Really ? No other methods ?
Since Apple's OpenGL drivers are deprecated (so they're not going to fix them) and closed-source (so we can't fix them) — no, not really. At least, nothing that would be less work than updating to Metal.
Anyway, one question, before moving Vuo completely to Molten / Vulkan / Metal which I assume will be some work, would it not be possible to test it out for small fixes like these first ?
Not in this case. Meshes are one of those things that you have to do either entirely in OpenGL or entirely in Metal. You can't do a little bit in Metal to work around the problem and keep the rest of the code OpenGL.
We're seeing similar results with a 1920x1080 Hap1 video (Gadane Fega Hap HD.mov from Hap Sample Pack One 1080p), tested on one computer. Vuo 1.2.8 is using a lot more CPU than VLC (Vuo = 101% – 125%; VLC = 25% – 58%).
As it turns out, Hap has two APIs: a simpler one that Vuo was using and a more complicated one that is apparently the fast one. With the fast API, the same video uses much less CPU (12% – 19%). We'll switch over to the fast API for the next release.
The width, height and time inputs are not in the order as they are in the subcomp file.
Yes, this is a bug. Thanks for reporting it.
This may be unrelated but…
Could you create a separate bug report and attach the composition? I don't think it's related to this bug.
upon searching it returns pages and pages of links to the manual
We intentionally made manual sections rank higher in search results than bug reports, since the manual is more helpful for people trying to learn Vuo. When you want to search only for bug reports, you can use the "Filter by content type" link in the sidebar.
+1 to Magneson's suggestion. If you can test in some other Blackmagic capture app besides Vuo, even better. That would eliminate one variable.
If for some reason you can't get both cameras working in the same composition, another option would be to have one composition receive from the barcode camera, decode the barcode, and send it to a second composition (via OSC, or by writing text to a file).