Multiframe Rendering: Expression output discrepancy between RAM preview and final render

Identifying Thread-Safe Expressions

An expression is considered "thread-safe" for Multiframe Rendering (MFR) when it is purely functional. This means the output is derived exclusively from the current time, static property values, or other properties at the exact same frame. It must not rely on external state, global variables, or values computed in preceding frames.

The Cause of Render Discrepancies

The discrepancy between RAM previews and final renders occurs because RAM previews process frames sequentially, while MFR processes them in parallel across multiple CPU cores. When an expression has a temporal dependency—meaning Frame 10 requires the calculated result of Frame 9—the parallel engine may attempt to render Frame 10 before Frame 9 is completed. This leads to non-deterministic output, often appearing as jitter or sudden jumps in position and opacity.

Why thisComp.layer Triggers Errors

A dependency on thisComp.layer triggers calculation errors during MFR under the following conditions:

• Cross-Layer Temporal Dependencies: If Layer A uses thisComp.layer("Layer B").transform.position.valueAtTime(time - frames), and Layer B is also being modified by an expression, the parallel thread rendering Layer A may access the "raw" value of Layer B before the expression for Layer B has been evaluated for that specific frame.
• Evaluation Order: In a sequential preview, the engine ensures all expressions for Frame N are resolved before moving to Frame N+1. In MFR, different threads handle different frame ranges; if a reference jumps outside the current thread's assigned range or relies on a yet-to-be-calculated property in a parallel thread, the output fails or reverts to a default value.

Resolution Steps

1. Audit for valueAtTime(): Check if your expressions reference previous or future frames. If they do, ensure the referenced layer is a static source (no expressions) or a pre-composition.
2. Flatten Dependencies: Convert complex expression-driven layers into Pre-compositions and "Bake" the expressions (Convert Expression to Keyframes) if the temporal dependency is critical.
3. Verify via Sequential Render: To confirm the issue is MFR-related, navigate to Preferences > Memory & Performance and disable Multiframe Rendering. If the final render now matches the RAM preview, the expression is not thread-safe.

Diagnostic Detail Required: Are you utilizing the valueAtTime() method to create a "follow-the-leader" or trailing effect? If so, the recommendation shifts from auditing to mandatory pre-composition or keyframe baking.