root's picture

Team Vuo (@root)


  • Vuo Founder
  • Team Vuo
root's picture
root's picture
root's picture

API documentation says library file extension is optional, but it's actually required


Steps causing the bug to occur: 

On ARToolkit node github repository, @mic reported that adding the library libAR.a to a module's dependencies as "dependencies" : [ "AR" ] doesn't work, but adding it as "dependencies" : [ "AR.a" ] does. This contradicts the documentation, which says that either should work.

For some libraries (those within Vuo.framework?), both options do work. Team Vuo should either allow both options for all libraries or fix the documentation.

Have you found a workaround?: 

Include the file extension.

root's picture

UV texture coordinate math expressions in 'Make Parametric Grid Mesh' node

(Created on behalf of @unicode from Make Parametric Grid Mesh node doesn't conform to documentation.)

Add input ports U Expression and V Expression that allow specifying arbitrary UV texture mappings independent of the mesh's shape in XYZ space.

Examples of how this would be useful (details here):

  • scrolling an image around a curved surface
  • wrapping world-map images of various projections onto a sphere


Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses


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


●○○ — Appeals to current community
root's picture

Composition freezes with certain structure of triggers + feedback loops


Vuo version: 

Fixed in Vuo version: 

Steps causing the bug to occur: 

@casdekker reported a problem with their composition:

In the subcomposition are two Smooth with Duration nodes which animate the start and end of a lineair gradient. A few seconds after starting the main composition the 'Position' of the Smooth with Duration nodes stops. (Again, it runs for the first couple of seconds) The 'Time' that is being put into the Smooth with Duration node is still running. The 'Target' is not reached and I tried it with both the 'Time' coming from within the subcomposition and from a published input port.

When running the subcomposition as a composition on its own, everything works fine.

We pared down the Smooth with Duration and surrounding nodes to a fairly simple composition that reproduces the problem:

In investigating the problem so far, it looks like Vuo is not correctly scheduling some nodes, resulting in a deadlock. Something about the structure of the two Fire Periodically nodes, Random Start/stop, and Smooth with Duration is throwing it off. (Yet slightly different feedback loops work.)

Since the problem happens in a top-level composition, it's not directly caused by subcompositions, but could show up when refactoring composition parts into subcompositions if the subcompositions end up with different event flow than the original nodes.

Have you found a workaround?: 

Insert a Hold Value node:



Binary Data TriphTest5.vuo2.51 KB
Binary Data TriphTest5-workaround.vuo2.55 KB