Removing Grain >

# Caching the Result

Degrain operations use caching of input images to manage the intensive processing requirements imposed on Lustre. If the Apply Degrain button is enabled, a degrained shot is automatically cached when the shot is initially played back after a Degrain operation. You can also use the Slave Renderer and Burn to cache frames. See Caching Frames Remotely.

The Degrain menu does not have to be visible for Lustre to continue caching frames.

You can cache the filtered frames created using the CPU. Once cached, Lustre can recall cached frames during future playback in both CPU processing and GPU acceleration mode. See GPU Acceleration. (If any parameters are changed, GPU acceleration must be disabled and images must be reanalysed in CPU mode to update and re-cache the frames.)

When configuring your project in Lustre, you also define the location of cached frames using the project settings. Degrained frames can be cached in a sub-directory of the Scans folder or a user-defined degrain cache file location. See Project Settings and Rendering Settings.

Only one instance of a frame can be cached in a shot, even if it is used in multiple cuts. If the cached media is saved as a preset, then you can load the cached media into the shot in a different cut. See Saving and Loading Degrain Presets.

#### Topics in this section

- Caching Frames from Wiretap
- Caching Frames Remotely
- Clearing the Cache