cremaschi's picture

Another possible solution, with a "Spin off event" technique:

cremaschi's picture

I got the same hiccup; gone away introducing a different source for events that load images. Try this:

Mechanica's picture

Ah, interesting. Thank you for the taking the time to check out my subcomps.

Bodysoulspirit's picture

Periodic Check Image URL Events seen / frame drop


Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

Not sure this is a bug, or related to to my old hardware.

I want to check every 0,5 seconds if an image has changed, load it, and apply a rotation to the layer.
It has an Allow changes after the fetch image to update events down the node chains only if the image changed.

However, on the rotation animation, I'm seeing a frame drop every 0,5 seconds, from 60 to +/- 55 FPS.

Since I have an allow changes node that block events, I guess the choppy rotation is because of the frame drop from loading the image into the composition ?

Is it because of my hardware ? Or something else ?


Have you found a workaround?: 

Nopynope. Since the image name stays the same even if the image updates, I don't know how to load the image into the composition only when changed.



Package icon Periodic Check Image Events.zip3.84 KB
tapetenstrahler's picture
tapetenstrahler posted a new Feature Request, “Ableton LINK integration
cremaschi's picture


in Vuo 1.2.8, when an event triggers an input port of a subcomposition, it flow through all the input ports. In Vuo 2.0, it flow only through that input port. If you run side by side your comp in 2.0 and 1.2.8 with "show event" activated, you'll have clear how this impacts on it. In 1.2.8, you can clearly see that all nodes are continuously triggered. In 2.0, you clearly see that only ones connected to "time" are triggered, and whole parts of the composition never run.

I tried connecting with an event cable "time" to other parts of the composition - quite randomy, without really dig into what it does as it's not that simple. This way i got the comp to behave more similar to the original one - animates, even if perhaps at a lower fps. I bet that reasoning better about what nodes of the comp should really run every time the comp is triggered, will drive you to the result.

regards michele

jstrecker's picture

Yep, it's a good idea in general to remove unnecessary triggers.

When testing with your subcompositions, my coworker encountered a problem related to the Process List node whose Finished Processing output port isn't connected to anything. It appears to be a new problem in Vuo 2.0.0 (starting with beta1). Workaround: publish the output port or, if you don't actually need the output, delete the node. We'll work on a fix.

jstrecker's picture
Jaymie commented on George_Toledo's Discussion, “vuo 2.0 sdk

Because that's the only way developers can distribute command-line utilities that macOS 10.15 is willing to run, now that Notarization is required.

jstrecker's picture
Jaymie commented on George_Toledo's Feature Request, “Specify size of Image Generator Window

Nope, there's not currently a way to do that. I've promoted your question to a feature request. I'll open it for voting after checking with the team on how long it would take to implement.

jersmi's picture



Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion

Browse Feature Requests

Suggest a Feature

Browse the Composition Gallery

Share a Composition

How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.