Removing Grain > Caching the Result >

# Caching Frames Remotely

You can use a Slave Rendering machine to cache frames in the background as you work, or Burn to submit a caching job.

NoteDegrained frames cannot be cached using Incinerator.

If you want to cache remotely to a user-defined location, you must enter a BrowseD file path in the Degrain Cache field. See Project Settings. For example, in Linux, a valid BrowseD file path can have the following structure: <IP address>:/mnt/storage/<project_name>. In Windows, it can be <IP address>:\F:\storage\<project_name>.

In Linux, to cache remotely using absolute file paths for a user-defined degrain cache location, you must create a shared NFS mount point on the Slave Renderer or Burn. In Windows, you use a UNC path for the Windows Slave Rendering machine, or use a Samba path to create a mount point on a Burn node.

To perform background caching using the Slave Renderer:

1. Display the SlaveRender menu. See Rendering Shots as You Work.
2. In the SlaveRender panel, toggle the On/Off button to On.
3. In the Degrain Only panel, toggle the On/Off button to On.

   When the Apply Degrain button is enabled in the Degrain menu, degrained frames are cached after you navigate to another shot.

NoteTo render degrained frames using the Slave Renderer, set the Degrain Only panel On/Off button to Off. Graded frames with Degrain will be rendered in the Renders Full Home destination.

To cache using a Burn node:

1. Display the Backburner menu. See Submitting a Remote Render Job.
2. Enable the Degrain Only button.
3. Click Burn.

   When the Apply Degrain button is enabled in the Degrain menu, the degrained frames are cached.

NoteTo render degrained frames using a Burn node, disable the Degrain Only button. Graded frames with Degrain will be rendered in the Renders Full Home destination.