I find performance to sometimes be unpredictable. I assume that some nodes are not processed on the GPU? It would be great if the Vuo node documentation could include whether a node is rendered on the GPU or CPU.



Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro


●○○○ — Up to a few days of work


●○○ — Appeals to current community

Implemented in Vuo version: 


I can give you an overview

jstrecker's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
Waiting for more information from reporter

I can give you an overview right now of the nodes that benefit from GPU acceleration. To be clear, these nodes do the bulk of their work on the GPU, but still use the CPU some to manage the GPU. Going by node set:

  • vuo.image — the nodes that render or filter images (but not nodes like Fetch, Find Barcode, or Sample Color)
  • vuo.layer — the nodes that do the final rendering to a window or image
  • vuo.scene — the 3D object filters and the nodes that do the final rendering to a window or image
  • vuo.screen — Capture Image of Screen
  • vuo.shader — all nodes, though all the processing happens in the final render-to-window-or-image node
  • vuo.video — for certain codecs such as H.264

manuelmitasch, does that cover the information you'd like to have added to the documentation? Or do you have further questions about performance? If further questions, it might help if you could give some examples where you have found performance unpredictable.

Thank you for the overview.

manuel_mitasch's picture
Submitted by

Thank you for the overview.

It seems like basically all image processing is done on the GPU. Good to know. I believe my performance problems came from this bug (https://vuo.org/comment/3693#comment-3693) and using high quality blur on a Mac mini with no dedicated GPU.

I just tested a couple of examples with all kinds of nodes and it seems my performance issues are gone in the new 1.2.4 version.

Feature status

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Community voted
  • Scheduled for implementation
  • Released in Vuo 1.2.6

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for.

Read more about how Vuo feature requests work.