@lechbialek, I've split off the part about a Touch Bar node into a separate feature request.
I'll be discussing with the team to come up with a rough estimate and see if we have any questions for you. Then we'll open these feature requests for voting.
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.