Wave node (vuo.motion.wave) needs offset input port like QC LFO patch

Feature Requests
,
1

If I get to learning how to edit nodes myself this should be an easy enough add…

Means you can have two objects moving in sync but offset on the wave value. Workaround is to do math on the output and clamp the result (boring).

2

Yeah, it’s easy to create an Add node to offset the time before you send it to the Wave node, but it would be handy to have that built-in since it’s so commonly used. I’ll try to add that in the upcoming release.

3

yeah adding to the time before it hit the node was something I tried but I’m not sure I understand how the time input actually works. In QC its a continuous (event free) flow of a real value (dynamic or static). Is it the same in Vuo? What is the typical way to wire this if you wanted three LFO nodes 120º out of phase with each other? What “Time” patch do you use? Fire Periodically set to 1/1000s? Or wire Render to Scene’s “Requested Frame Port” to every LFO?

4

Unlike QC, in Vuo time is explicit. The Requested Frame output of a Render Scene/Layers to Window or Fire on Display Refresh node contains an ongoing timestamp. Connect that port to the Wave node’s input port.

I’ve attached a composition showing how you’d make a three-phase oscillator in Vuo.

three-phase-oscillator.vuo (4.75 KB)

5

Thanks, Steve. With the Fire on Display Refresh node how does it know which Window it is assigned to in a composition with two or more Windows? I assume multiple Display windows refresh independently of each other (so potentially at different rates) being a multithreaded runtime?

6

Currently Fire on Display Refresh fires in sync with the system’s main display (the one with the menu bar). Multiple instances of that node fire independent events at nearly the same time.

7
  • Like

thx

8

Added in Vuo 1.2.