Problem
Render cache invalidation occurs after harmless project changes, causing previously rendered sections to recalculate.
Solution
Root Cause / Diagnostic:
Placing global adjustment layers, unrendered audio track effects, or unconstrained master timeline plugins above edited clips causes every upstream edit to invalidate the downstream render cache. The cache engine perceives global changes and dumps pre-rendered frame data.
Actionable Fix:
1. Scope adjustment layers strictly to individual clip segments rather than stretching single continuous layers across the entire master timeline.
2. In DaVinci Resolve or Premiere, switch render cache mode to "User" and manually flag only locked, finished composite segments for caching.
3. Perform a minor edit on an adjacent track to verify that cached render indicators remain blue (valid) on unrelated clips.
Pro Tip:
Never place global adjustment layers across your entire timeline until the cut is 100% locked; localized adjustment clips prevent accidental project-wide cache invalidation and save hours of re-rendering.
Placing global adjustment layers, unrendered audio track effects, or unconstrained master timeline plugins above edited clips causes every upstream edit to invalidate the downstream render cache. The cache engine perceives global changes and dumps pre-rendered frame data.
Actionable Fix:
1. Scope adjustment layers strictly to individual clip segments rather than stretching single continuous layers across the entire master timeline.
2. In DaVinci Resolve or Premiere, switch render cache mode to "User" and manually flag only locked, finished composite segments for caching.
3. Perform a minor edit on an adjacent track to verify that cached render indicators remain blue (valid) on unrelated clips.
Pro Tip:
Never place global adjustment layers across your entire timeline until the cut is 100% locked; localized adjustment clips prevent accidental project-wide cache invalidation and save hours of re-rendering.