cwilms-loyalist's picture

Somehow I missed your response but am SO glad to hear it's coming in Vuo 1.2.6... if you need any alpha/beta testers I can do a little testing with my planned project. :)

My initial need will just be to have my project read a datamatrix code with a camera, extract a 4-digit code from the delineated text string and then use that 4-digit code to find the appropriate replacement text in an XML file for displaying on screen.

Kewl's picture

Play Audio File + Send Live Audio = micro pauses

Kewl's picture

So, I have a audio visualization composition that uses the Play Audio File and Send Live Audio nodes and while playing, from time to time, not at any specific regular interval, the audio will pause for a few tens of milliseconds (10? 20? 30?) as if the rest of the composition was catching up with the audio.

Anything in particular I should be looking at to solve this? It happens in the last few versions of Vuo and in macOS 10.11 and 10.12, and the audio interface seems to make no difference (Built-in, RME Fireface UC).

marcin's picture

I finally got it after a long debugging session. :)

Once you add ImageGenerator filters, any published inputs will receive a new value every frame, even if they only hold a simple Integer values. To make if work like without ImageGenerator filters, the input values must be tunnelled through a HoldValue node.

Pianomatic's picture

Rotations get muddled through combining transformations


Vuo version: 

Fixed in Vuo version: 

OS version: 

  • Mac OS 10.11

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

Open attached composition and run it. Observe the three rotating cubes:

The orange cube has a random rotation which is applied via a Combine Transforms node.

To its left, the purple cube receives the same rotation as a quaternion via a Make Quaternion Transform node.

And to the right, the blue cube also receives the same rotation, this time converted back to Euler angles, via a Make 3D Transform node.

Have you found a workaround?: 


Other notes: 

All three cubes should, I believe, be moving in unison. Although the orange cube rotates correctly using the Combine Transforms node, the rotation gets muddled somehow when it's extracted from the combined transform and passed onto other nodes.


Binary Data Quaterion headache.vuo7.18 KB
marcin's picture

Jaymie thank you for a great response. The trick I was missing is holding option key while connecting a port to published inputs, that way it becomes an event-only port.

I've solved my issue, but this one thing seems a bit strange for me - once I've added ImageGenerator ports to your jstrecker.showCounterWindow composition, the "Increment" port is triggered every frame. Is this some kind of limitation? I was thinking about using this "Increment" port as a button in VDMX to send events.

marcin's picture

Thanks Jaymie, I've used your hack - it works fine for replacing 1.2.4 with 1.2.5.

cwilms-loyalist's picture

Turns out I ended up having to go a different route after all. The Select Latest node was working great for my test still images but as soon as I got into video sources it was no longer suitable for selecting my sources (since video is a steady stream of images it's always being chosen as the Latest source). However I ended up using the 8 input Select Latest to output the number of the source on my Select Input node and used combination of compare numbers, math node and a True/False node to split the output to the proper Select Input node. Seems to be working well now.

I was even able to make a "Take" button along with a "Dissolve" and "Cut" button to select what transition type I wanted between the current video source and the one coming in. Super smooth transitions and live video even at 3360x1080 resolution output!!! Amazing!

jstrecker's picture

If you just want the event from Fire Periodically to go into the subcomposition, you can make an event-only published input port. In the example below, I created the published port by dragging a cable from the Count node's Increment input port, holding down Option to make it event-only, and dropping it onto the published inputs area. Each time Fire Periodically fires, its event goes into the Show Counter Window node's input port, and inside the subcomposition, goes to the Count node's increment port.

If you also want to send the data from Fire Periodically, you can publish a Real (number) published input port, as in the example below. In this example, each time Fire Periodically fires, its event and data (the seconds since the composition started) go into the Show Number Window node's input port, and inside the subcomposition, go to the Format Number node's Value port.

jstrecker's picture

Your composition uses a node that is new in Vuo 1.2.5 (vuo.event.changed2), but VDMX b8.6.1.1 (the latest version) only includes Vuo 1.2.4.

I've attached a version of the composition that opens in Vuo 1.2.4. (It substitutes the old vuo.event.changed in place of vuo.event.changed2). That should work in VDMX b8.6.1.1.

If you want, there's a hack you can use to enable VDMX to run Vuo 1.2.5 compositions. See How do I use Vuo 1.2 with VDMX5 b8.5.0.7?.



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.