Resolume Forum

For me at least. Running 5.1.2 on Win 10.

Play a clip on any layer. Set the Layer Opacity to zero. Click [X] Clear All Layers.

The clip appears to have been cleared from the layer but its play-head continues to move. Only when you increase the Layer Opacity again does the clip get ejected. Resolume is still reading the file as evidenced through Process Monitor.

Same for the [X] Clear Layer.

Just tried to recreate this, but works as expected on Mac and PC. Clips eject regularly, regardless of the layer opacity. I also tried routing the layer to a slice, as that puts the layer in a slightly different state internally, but still nada.

Any chance you can recreate this from a blank composition?

to recreate, set the transition time to something not 0.
like this

Gotcha. Thanks for jumping in.

What happens is that we optimise Resolume so that layers at 0 opacity (and that are not routed anywhere), do not render. This saves a big chunk of processing power. It doesn't matter how many layers you have on standby, only the actually visible layers count towards your total rendering capacity. This will let you create comps where you have certain clips ready to go under a fader, without having to "pay" for them on each frame.

An unexpected side result is that apparently because the layer is not rendered, the layer transition is also never completed. It continues its timing, but doesn't eject the clip at the end.

The only actual drawback I can think of is that the OSC output doesn't match the actual state. Visually, there is no perceivable difference I can think of.

The more I think about this, the more I think the layer is actually cleared and the clip is actually ejected, but the active clip status is just not updated.

Interested to hear what comes of this.