To have the scanned footage and renders stored on a separate storage location, the Scans Full Home and the Renders Full Home must be explicitly defined as a separate location. On Windows, an example of this separate location could be a shared folder coming from a remote file server, and mapped to the local drive G:\ under the films\myfilm folder. On Linux, a corresponding example would be a directory exported from a remote file server, and mounted on the /mnt/fileserver/ NFS mount point under the films/myfilm directory.
Directory: | Windows Folder: | Linux Directory: |
---|---|---|
Project Name | H:\<project name> | /mnt/md0/<project_name> |
Scene |
H:\<project name>\ <scene name> |
/mnt/md0/<project_name>/<scene_name> |
Library |
H:\<project name>\ <scene name>\Library |
/mnt/md0/<project_name>/<scene_name>/ Library |
Where you create sub-directories to store original footage |
G:\films\myfilm\ <scans folder> |
/mnt/fileserver/ films/myfilm/<scans_directory> |
Where Lustre creates sub-directories for render files | G:\films\myfilm\grd | /mnt/fileserver/ films/myfilm/grd |
The following table shows the sub-directory structure that CEV_ProdName_CEV creates for renders. The structure differs depending on the Render Place option specified when rendering. See Specifying the Destination for Local Render Files. For the sake of simplicity, in this table, G:\...\ represents G:\films\myfilm\, and /mnt/fileserver/.../ represents /mnt/filesever/films/myfilm as shown in the first table in this section.
Directory: | Windows Folder: | Linux Directory: |
---|---|---|
Where sub-directories of the renders are located. |
G:\...\<render mode>\ |
/mnt/fileserver/.../<render mode> |