12. Troubleshooting

What if you run into problems using Vuo? This section describes some common problems and how you can fix them. If you need help, you can always check out the additional resources on the Vuo Support page.

12.1. Helpful tools

The Vuo Editor provides several helpful tools for troubleshooting:

  • Show Events mode lets you watch the events flow through your composition. You can turn it on and off with the Run > Show Events and Run > Hide Events menu items. In Show Events mode, trigger ports are animated as they fire events. Nodes turn opaque as they’re executed and gradually become more transparent as time passes since their most recent execution. Using Show Events mode, you can see if certain parts of your composition are executing.

  • Port popovers let you inspect the data and events flowing through individual ports. A port popover pops up when you click on a port. If you want to keep the port popover open for a while, for example to look at several port popovers at once, click on the popover. While the composition is running, the port popover shows several pieces of information that can help with debugging:

    • Last event — The time of the most recent event through the port, and the average number of events per second.

    • Value — For data-and-event ports only, the most recent data through the port.

    • Event throttling — For trigger ports only, whether the port enqueues or drops events.

  • Node descriptions tell you how the node is supposed to work. The node description appears in the lower panel of the Node Library whenever you select the node in the Node Library or on the canvas.

When watching data with the Display Console Window node, you can use the Allow Changes node to filter out repeated data.

There are nodes to help with troubleshooting, too. One is Display Console Window, which shows a text window that your composition can write text on. You can use Display Console Window to observe values that are hard to see in port popovers because they’re changing too rapidly. To find other nodes that can help with troubleshooting, search the Node Library for debug or troubleshoot.