Skip to main content
Participant
October 16, 2023
Open for Voting

Freeze and Cache Comps

  • October 16, 2023
  • 0 replies
  • 158 views

Just like how you can "freeze" the rotobrush effect on a layer, I would love to expand the current cache system to allow us to Pre-Render/Cache a comp and "Freeze" or "Lock" it so that cache doesn't get deleted/purged the same as any other random cache files that are generated.

 

I envision it looking like a button seen next to the "Enable Motion Blur for all layers in this comp" button. Pressing the button would offer up some options like processing the cache in the background, locking the comp so no one can change anything accidentally causing the cache to be purged, storage location of the cache (same place as all the other cache, different folder, contained with in the project file, etc. etc.), expiration options (cache expires after a certain date, or after the app is closed,  etc.), resolution options (create the cache at different resolutions), multiple states toggle (add the ability to store/cache multiple versions of the comp that we could toggle through).

 

The current method of rendering and importing a file or the render/replace with proxy method can generate a lot of files that "permantely" take up space, and the process of rendering and swapping in can be a bit tedious, especially when using master properties. I think a careful expansion of the current cache system would speed up everyones workflow by reducing a number of steps and help reduce project bloat and clutter.