Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

Steps causing the bug to occur: 

  1. Set up some layers and an "is point within layer" node and some way to react on it.
  2. Publish the "Rendered Layers" input port(s).
  3. Connect layers to "Combine Layers With Transform" node.
  4. Publish layer output from "Combine Layers With Transform".
  5. Store to node library
  6. Create a new composition
  7. Use the newly created node from the library, and connect it to a "Render Layers to Window" node.
  8. Observe high resource usage through the activity monitor.

How did the result differ from what you expected?: 

High resource usage.

Have you found a workaround?: 

Connect "Rendered Layers" output port from "Render Layers to Window" to a "Hold" node before connecting to desired input port in custom node.

Other notes: 

Publishing layers directly without the use of a "Combine Layers With Transform" node will warn about a feedback loop, and prevent connection without the hold node.

Compositions: 

AttachmentSize
Binary Data RenderedLayersBug.vuo1.37 KB
Binary Data RenderedLayersWorkaround.vuo1.66 KB

Comments

Thanks. I see the problem,

smokris's picture
Submitted by
Status:
Waiting for more information from reporter
»
Accepted

Thanks. I see the problem, though I'm not yet sure what the solution should be. I've marked this bug report accepted, and I'll discuss with the team.

In the meantime, using Hold Value outside the subcomposition is a good workaround.