OK, with the NVIDIA GeForce GT 750M, I'm seeing patterns emerging past [a seed of] a hundred or so. So, I'm using a shorter sequence of 67 seeds but randomly flipping and inverting the images.
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.
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.
