- Posts: 135
- Joined: Sat May 04, 2019 4:11 am
- Real Name: Ashley Thomas
Mon Apr 21, 2025 8:59 pm
I notice Davinci Resolve Fusion expressions (SimpleExpressions) always run even when a node is no longer producing any output.
For example, if the current frame (playhead location) is outside the node's Fusion Keyframes Editor (KE) segment span, the node's expressions still run. Outside such, the node should be deemed "off" or "disabled" per the manual (page 1377, see below). The manual describes how segment spans can be used to optimize out nodes when they no longer need processing but it seems expressions are not part of that optimization.
This means that nodes in a comp which have no functionality for lengthy periods of time cause a significant performance burden.
While I can see how Davinci Resolve cannot predict a node's expression does not have programmatic effect outside the node's KE segment spans, it seems most likely the node and its expressions are inert at such a point in time.
Regardless, if outside of a segment span, the expressions should not be called. If one needs expressions to run outside the span, they can be hosted within a node that is active at the desired times (i.e., where playback is within the node's segment spans).
Is there a reasonable way to disable a node's expressions, prevent Lua expression stack setup, and the call, for a given expression, for given periods within a comp's timeline where that node is seemed inert/disabled?
Davinci Resolve Manual (February 2025). page 1377, "Trimming Segments":
I'm on Davinci Resolve 19.1.4 Build 11. Thanks.
For example, if the current frame (playhead location) is outside the node's Fusion Keyframes Editor (KE) segment span, the node's expressions still run. Outside such, the node should be deemed "off" or "disabled" per the manual (page 1377, see below). The manual describes how segment spans can be used to optimize out nodes when they no longer need processing but it seems expressions are not part of that optimization.
This means that nodes in a comp which have no functionality for lengthy periods of time cause a significant performance burden.
While I can see how Davinci Resolve cannot predict a node's expression does not have programmatic effect outside the node's KE segment spans, it seems most likely the node and its expressions are inert at such a point in time.
Regardless, if outside of a segment span, the expressions should not be called. If one needs expressions to run outside the span, they can be hosted within a node that is active at the desired times (i.e., where playback is within the node's segment spans).
Is there a reasonable way to disable a node's expressions, prevent Lua expression stack setup, and the call, for a given expression, for given periods within a comp's timeline where that node is seemed inert/disabled?
Davinci Resolve Manual (February 2025). page 1377, "Trimming Segments":
* SimpleExpressions are always executed even outside of node's segment ranges (tested using Text+)....
Trimming the segments of effect nodes instead modifies the range of that node’s effect in the
composition. Outside of the trimmed region, that effect node will behave as if it were disabled.
TIP: Shortening the duration of effects nodes can optimize processing. ... trimming ... will effectively prevent it from rendering and consuming either memory or processor time until needed. ...
I'm on Davinci Resolve 19.1.4 Build 11. Thanks.