useful design's picture

It work! Thanks. It also helped me realise any values coming into the loop from outside seem to need Hold Value nodes on them in the same way to stop spoof values getting in and messing with the first item of the iteration. Wow that was very helpful because that's weird first-element-in-list-is-wrong thing has been bugging me for days now!

I'm adding an example comp for those who come after me. If we remove the "bottom" and " Hold Value nodes and wire those values directly into the loop we get a "Hello World!" text image in the list of layers.

Hold Value nodes very important for loops..vuo

useful design's picture

I'm noticing a bunch of this kinda thing. Have a Process List which is fed a list of numbers that get converted to a list of Text Layers.

The first layer says "Hello World!" — obviously not receiving the data even though it's wired directly to the Process Item port of the Process List node. When I cut it all out into a stand alone comp to log a bug it starts working correctly.

So then I set up a counter inside the loop and bring in some constant values for a text position calculation from outside the loop and the "Hello World!" appears.

Then I delete the outside wires just leaving the real values and it works, no "Hello World!". So this must be something to do with events getting inside the loop from before hand and loading up the first iteration buffer before it has been passed the real data — or something?! I'm pretty sure it's to do with outside wires coming into the loop.

jstrecker's picture
@jstrecker commented on @alexmitchellmus's Feature Request, “AVDepthdata support

Thanks for the suggestion, @alexmitchellmus. Opened for voting.

jstrecker's picture
@jstrecker commented on @cremaschi's Bug Report, “Inconsistent video input size

It could be that your video source is providing non-square pixels, and Vuo handles them differently than QuickTime Player. When Vuo detects that the video source has non-square pixels, Vuo asks the video source to provide square pixels. Maybe that's happening to begin with, and then QuickTime Player is asking the video source to switch back to non-square pixels.

We may send you a demo app to check if that is indeed the problem. Or if you know of some other way to check, let me know.

useful design's picture

Why does this smoothing composition work but not as a sub-composition?

I've unrolled a loop to process 25x 2D points to smooth their changing values. Takes a list and has a common duration, uses Smooth with Inertia node inside.

I loaded some data that is just a flip-flop of two sets of five (X,Y) points and it draws ovals centred at these flip-flopping points and smooths between them fine.

pbourke's picture
@pbourke posted a new Bug Report, “Warp image node number parsing bug.

Warp image node number parsing bug.

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.12

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. See attached project.
  2. Swap between "mapper.data" and "mapper_new.data" on the input the the warp image node, one works the other doesn't.
  3. But the data is basically the same except for numerical formatting.

Compositions: 

AttachmentSize
Package icon Archive.zip1.75 MB
pbourke's picture
@pbourke posted a new Discussion, “download
useful design's picture

Using a Addition node on the Which input of the end point Get From List node is not really helping, doesn't seem to do what I thought it would do adding 1 or -1 to the result.

Pages

Welcome!

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.