Project Management > Recommended Directory Structure for Projects > 
Scanned Footage and Renders Stored Separately from Project Home
 
 
 

In this example, the Project Home is defined in Windows as the H:\ drive, whereas in the Linux version it is defined as the /mnt/md0/ mount point.

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.

Windows Folder: Linux Directory: Description:
H:\<project name> /mnt/md0/<project_name> Project Home directory.

H:\<project name>\

<scene name>

 /mnt/md0/<project_name>/<scene_name> Scene directory.

H:\<project name>\

<scene name>\sacc_data

 /mnt/md0/<project_name>/<scene_name>/sacc_data Directory where most metadata associated with the scene is stored.

G:\films\myfilm\

<scans folder>

 /mnt/fileserver/ films/myfilm/<scans_directory> Directory in which you create sub-directories to store original footage.
G:\films\myfilm\grd /mnt/fileserver/ films/myfilm/grd Directory in which Lustre creates sub-directories for render files.

The following table shows the recommended sub-directories structure for scans. 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 previous table.

NoteIf you decide to store half-resolution scans in a different location from the originals, the project directory structure must be identical in both locations and must include the root directory of the project. For example, if the Project Home is defined as V:\Data\Lustre_project\My_movie, the Scans Full Home could be defined as W:\mnt\San\Lustre_project\My_movie\ and the Scans Half Home could be X:\Lustre_project\My_movie.
Windows Folder: Linux Directory: Description:
G:\...\<scans folder>\<shot name> /mnt/fileserver/.../<scans_directory>/<shot_name> Directory in which sub-directories for different resolutions of the scans are located.
H:\...\<scans folder>\<shot name>\<resolution> /mnt/fileserver/.../<scans_directory>/<shot_name>/<resolution> Directory in which the actual scans are stored. Half- and full-resolution scans should both be at this level, in different directories. The directory name must consist of the resolution expressed in numbers with a lowercase x in between. Example: 2048x1556. If you generate proxies in Lustre, the proxies directory is created automatically.

The following table shows the sub-directory structure that Lustre 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.

Windows Folder: Linux Directory: Description:

G:\...\grd\

<shot name_grdxx>

 /mnt/fileserver/.../grd/<shot_name_grdxx> Directory in which sub-directories for different resolutions of the renders are located when using the Normal or No Wedge Render Place option. In the example, xx is the grade number.

G:\...\grd\

<shot name_grdxx>\

<resolution>

 /mnt/fileserver/.../grd/<shot_name_grdxx>/<resolution> Directory in which the actual renders are stored when using the Normal or No Wedge Render Place option. The directory name corresponds to the resolution of the render files, for example, 1280x1024.
H:\...\grd\<grdxx> /mnt/fileserver/.../grd/<grdxx> Directory in which the actual renders are stored when using the One Sequence Render Place option. In the example, xx is the grade number.