Event firing inconsistant

Steps causing the bug to occur

  1. load attached composition
  2. run, counting to console window will start at 100 and either go up or down in twos. You’d think it might average out to stay at 100.
  3. run it again and see if it behalves differently
  4. rinse and repeat

How did the result differ from what you expected?

no sure. maybe count averaging around 100 with 2 increase events and 2 decrease events per second.

When did you first notice this bug?

Following the documentation on Event firing (4.3.4 Multiple triggers) and expanding on the demo composition. This may be the ‘correct’ behaviour but it is inconsistent on execution.

Other notes

  • Vuo version: 1.0.1
  • macOS version: OS X 10.10

count up-down.vuo.zip (959 Bytes)

@useful_design: each Fire Periodically node is firing its own event at roughly the same time. A node can only process 1 event at a time, so when 2 events come in at roughly the same time, 1 event gets processed and the other event has to either be dropped or enqueued until the node is available.

The Fire Periodically nodes default to drop events. Right-click on the Fired port and change Event Throttling to Enqueue — then you’ll get consistent results.

There’s more info in the Controlling the buildup of events section of the manual.

Ok that makes sense, thank you, Steve. So it seems like which ever event is dropped, Vuo consistently drops that event of the two events every time it evaluates. But at another runtime it may drop the other event each time. Seems to be random but whatever it starts with it sticks to. How would you delay an event by a set number of frames (not sure what Vuo calls each screen-draw) or a set time period? I looked for a Delay node but nothing.