Pianomatic's picture

Nodes with two list-inputs set to Colors are a mile long

Status: 

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. Create a node with two list inputs, such as Select Latest List
  2. Set the data type to Color

Have you found a workaround?: 

Attach a cable to one of the list inputs (note: not the list item inputs) and it goes back to its usual size.

jstrecker's picture

After some investigation, I created a bug report for the Smooth with Duration you encountered: Composition freezes with certain structure of triggers + feedback loops. See the part about a workaround.

I don't have a very good answer for your question about timeframe for fixing the graphics-related crashes, sorry. For the past several months, we've been working on features/fixes that were originally planned for Vuo 1.3 and releasing the smaller or more self-contained ones in the 1.2.x versions. Since the graphics changes are complicated, they're still planned for Vuo 1.3. I expect that will be some months away.

root's picture

Composition freezes with certain structure of triggers + feedback loops

Status: 

Vuo version: 

Steps causing the bug to occur: 

@casdekker reported a problem with their composition:

In the subcomposition are two Smooth with Duration nodes which animate the start and end of a lineair gradient. A few seconds after starting the main composition the 'Position' of the Smooth with Duration nodes stops. (Again, it runs for the first couple of seconds) The 'Time' that is being put into the Smooth with Duration node is still running. The 'Target' is not reached and I tried it with both the 'Time' coming from within the subcomposition and from a published input port.

When running the subcomposition as a composition on its own, everything works fine.

We pared down the Smooth with Duration and surrounding nodes to a fairly simple composition that reproduces the problem:

In investigating the problem so far, it looks like Vuo is not correctly scheduling some nodes, resulting in a deadlock. Something about the structure of the two Fire Periodically nodes, Random Start/stop, and Smooth with Duration is throwing it off. (Yet slightly different feedback loops work.)

Since the problem happens in a top-level composition, it's not directly caused by subcompositions, but could show up when refactoring composition parts into subcompositions if the subcompositions end up with different event flow than the original nodes.

Have you found a workaround?: 

Insert a Hold Value node:

Screenshots: 

Compositions: 

AttachmentSize
Binary Data TriphTest5.vuo2.51 KB
Binary Data TriphTest5-workaround.vuo2.55 KB
jstrecker's picture

Ack. Thank you for reporting this bug, @Philip, and sorry it's getting in your way. We'll get it fixed.

jstrecker's picture
@jstrecker commented on @Salvo's Discussion, “Track Skeleton with multiple users

@Salvo, does the attached composition do any better? It has all the Filter Skeleton nodes sharing the same Receive OSC node instead of one for each.

I also removed two of the camera nodes, since you just need the one, though that wouldn't be causing the delay.

jstrecker's picture

@unicode, thanks for pointing out this inconsistency. Scheduled for work.

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 Questions and Answers

Ask a Question


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.