This can happen if events are not flowing through your composition often enough or quickly enough. Here are some things to check:
Is each trigger port firing events as often as you expected? Check its port popover to see the average number of events per second. If it’s firing more slowly than you expected…
Check the node description for the trigger port’s node. Make sure you understand exactly when the trigger is supposed to fire.
Check for any nodes downstream of the trigger port that might take a long time to execute, for example a Fetch Image node that downloads an image from the internet. Change your composition so those nodes receive fewer events. (See the section Common patterns - “How do I…”.)
Check the trigger port’s event throttling, which is displayed in the port popover. If it says “drop events”, try changing it to “enqueue events”. (See the section Buildup of events.)
Check the event throttling of each other trigger port that can fire events through the same nodes as this trigger port. If the other trigger port’s event throttling is “enqueue events”, try changing it to “drop events”.
Is each node receiving events as often as you expected? If not…
Check if there are any event doors that might be blocking events between the trigger and the node. (See the section Event walls and doors.)
Is the composition using a lot of memory or CPU? You can check this in the Activity Monitor application. If so…
Check if any parts of the composition are executing more often than necessary, and try not to execute them as often. (See the section Common patterns - “How do I…”.)
Export the composition to an application. When run as an application instead of in the Vuo editor, compositions use less memory and CPU.
Quit other applications to make more memory and CPU available.
Run the composition on a computer with more memory and CPU.