cremaschi's picture

mic (@cremaschi)

Community Spotlight


  • Vuo Founder


4 years ago
7 years ago
cremaschi's picture

Cycle through list outputting inconsistent data


Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.14

CPU architecture: 

Intel x86_64

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. run the attached comp
  2. right click and fire event on yellow node "list two".
  3. right click and fire event on "go backward" port of blue node
  4. Outputted "Item" from blue node is correctly "3" - the value of the third element of "list two" node - while outputted position is 4. I'd expect this latter to be 3, it's very strange that cycling a list with just 3 elements could output a fourth position. And in any case, this data doesn't match with "Item" data.

Have you found a workaround?: 


Other notes: 

Don't know if this can be considered a proper bug, but in my opinion it's quite inconsistent and just when I simplified a task with this example realized what could be happening in a more complex comp that isn't behaving as i'd expect.


Binary Data cycle node bug.vuo2.26 KB
cremaschi's picture
mic posted a new Discussion, “node performance cost

node performance cost


i have two different algorithms that can solve a step required by a program I’m writing.

In the first idea (yellow nodes), I hold a list till a signal event hit the node, and then i make the flow continue.

In the second idea (blue nodes), I calculate generated values the first time the list changes, hold these and let them go on as soon as signal arrives.

Given the fact:

cremaschi's picture
mic commented on ooftv's Discussion, “Display video on second screen

Hi ooftv and welcome to Vuo.

"Change Windows Screen" nodes needs to receive an event to be activated and route its output to "Render Image to Windows" nodes. So, just add two event cables from "Fire on Start" and I think this will solve the external monitor position. There's a second issue in cable connecting "Change Window Screen" set to display on main monitor, and its "Render Image to Window". You shouldn't use a thin cable (event-only), but a data-and-event cable. Probably you'd need some time to read documentation, that explain all basics you need.


cremaschi's picture
mic commented on jersmi's Feature Request, “Delay node

I think that this and other FQ could be easily solved whenever "Publish Generic Ports" FQ is. So, I'd give priority to this latter.