MartinusMagneson's picture

Magneson (@MartinusMagneson)

Groups

    MartinusMagneson's picture

    Is noise functions random per editor/app startup?

    My mac had an unfortunate meeting with a switch in my luggage in the overhead compartment of a plane, so I can't check this myself at the moment. I suddenly got to wonder if Vuo has the easiest noise looping workflow available, by animating a circle at the input of the Make Gradient Noise node. What would be neat if that is the case, would be to have a seed input for this node, so that it's not only easy - but repeatable.

    Should I feature request this, or does noise generation work in a totally different way?

    MartinusMagneson's picture
    Magneson commented on Dust's Discussion, “iterating color with layer copies

    Iteration in Vuo works a bitt differently in Vuo than in QC. The easiest way to create a list with multiple different values is to use the Build List node:

    MartinusMagneson's picture

    Don't feel dumb! Learning new skills are rarely not frustrating!

    You only need the event signal on the first nodes (the convert ones). The nodes attached downstream from those will get the event signal through the previous nodes.

    MartinusMagneson's picture

    Not quite. As long as an input port doesn't receive a signal (like for instance as a plugin in Resolume), it doesn't generate an event. If you move the event cables over to the convert nodes it should work. Event cables should be added to the first node after an input port. You don't need the rest of them as the events then flow through the rest of the nodes.

    I assume the convert nodes popped up automatically, and inserted the event cables after, which I understand would be confusing. That would perhaps be something for Team Vuo to look into (Jean Marie)? It's a feature, not a bug though.

    MartinusMagneson's picture

    It seems like you only have a fire on start node. This only triggers one event when the composition starts. You'll need a fire periodically or fire on display refresh node connected on one of the ports receiving values to calculate it. Since events always flow from start to end, you'd only need one connected (shift-drag for time output ports) to a port of the calculate node in your first example.

    Pages