For each project, you can now define the folder structure and media files that are generated at render time. You can use the default path structure defined in the RenderNaming section of the init.config file. Or you can customize your renders by modifying the fields in the new Render Naming menu in the Project settings. Use Tokens (words representing values) to customize the folder location and file names based on the default values.
You can also create project templates with a customized render naming structure. If you create a project template named "default", newly created projects will automatically use the render naming structure defined in this template instead of the default path structure in the init.config file.
Render Naming menu
The following tokens can be used for rendering:
Note: You must include the brackets when typing a token in the render path field.
You can also define the padding of the file name (i.e the number of digits used for file numbering) for any render mode.
<NormalPadding string=".%06d" /> will generate a six digit file like this: filename.123456.dpx.
It is possible to remove the "." to create a file with only a frame index (no filename), like the default padding value of the One Sequence render mode.
If you type an invalid token and press enter (or select another path field), Lustre will highlight the invalid token to warn you about the error.
Also, after modifying a render location field, if you want to revert to the default location defined in the init.config, press the CTRL key and click on the field you want to reset.
Starting in Lustre 2012 Extension 1, each grade saves the current render naming path associated with its render mode every time you start a new render, submit a render job to Burn or the Slave render. This means if you modify a render naming path for a new grade, and you load a previous grade that has a different rendering path for the same render mode, Lustre will be able to link the grade to its previously saved render path. The render naming paths are saved in the file called <grade name>.renderinfo.
To use the new Render Naming convention, there is a new option -9 which allows you to enter the absolute render path along with the supported tokens you wish to use. You must also provide the command-line renderer with the same render naming structure that is entered in the Lustre application in order to view the media files rendered at the expected location. Below is a sample command line render:
./render -s SD_scene -g grd01 -r full -o dpx -1 / /mnt/StorageMedia/projects/LOCAL -2 / /mnt/StorageMedia/scans -3 /mnt/StorageMedia/renders -9 / "[RENDERS_HOME]/Normal/[SCENE]/[GRADE_NAME]/[REEL_NAME] / /[RESOLUTION]/[UID][ORIGINAL_FILENAME][GRADE_NAME]" -I ".%06d"
Note: if you do not use the -9 option, the command-line renderer will generate media files in the legacy location (prior to 2012 Extension 1). If you wish to view the files rendered with the legacy command line strings, the Render Naming fields need to have non-defined (ie. blank) fields. Also, make sure to write the render naming path and padding value between quotes (" ").
Command-Line Renderer Test Mode
It is now possible to use a new Test mode with the Command-Line Renderer (-H). In this mode, no media files are written.
./render -s SD_scene -g grd01 -r full -o dpx -1 / /mnt/StorageMedia/projects/LOCAL -2 /mnt/StorageMedia/scans -3 / /mnt/StorageMedia/renders -9 / "[RENDERS_HOME]/Normal/[SCENE]/[GRADE_NAME]/[REEL_NAME] / /[RESOLUTION]/[UID][ORIGINAL_FILENAME][GRADE_NAME]" -I ".%06d" -H
Rendering to the Wiretap Server
When rendering to a Wiretap destination, ie. <wiretap_server>@wt:/stonefs…, the clip names are not affected by the Render Naming convention. However, the naming of the Media files will be affected if the Wiretap Render option is enabled (i.e. media files in this case are written to a shared location as unmanaged media).
Even if it is recommended to create new projects when upgrading to a new version of Lustre, you can still use a project created in a previous version. Since there are no Render Naming settings in a prior version, Lustre 2012 Extension 1 will load legacy projects with blank Render Naming fields. If you render grades from old projects, the files will be generated with the legacy render structure. In Lustre 2012 Extension 1, users can update the old project and define the Render Naming options, if needed. But in this case, the old project will no longer be compatible with the previous version of Lustre.
It is also possible to copy grade files from an old project into a new project created in 2012 Extension 1. In this case, rendering will generate files with the new Render Naming paths and Lustre will be able to display the rendered media in Print view since Lustre saves the current Render Naming path to the <grade name>.renderinfo file each time you start a new render.
Lustre 2012 Extension 1 introduces a new way to organize presets based on the Grade bin workflow. In previous versions, all Presets were saved in the "presets" folder located in the home of the application. Since all these presets were seen in all projects by all users, it was sometimes difficult to find presets. You can now organize your presets in the following ways:
It is possible to define the Global Presets location in the init.config file. The default location is in the "Autodesk" folder.
Note: Previously, the Global Presets folder was located in the home of the application. If you want to re-use this content, you must define the previous location in the init.config file or move the Global Presets folder to the Autodesk folder. Moving the files will prevent this content from being used in previous versions of Lustre.
Project-based Grade Bin and Presets
When creating a new project, you can define where the project Grade Bin and Presets folders are located from the Rendering menu. The default location is inside the project home folder.
Note: the user interface of the Project / Rendering menu has been updated to support the new options.
User-based Grade Bin and Presets
When creating new user settings, you can define where your Grade Bin and Presets folders are located from the System & Menu page. Default location is located inside the user home location.
When you enable the Presets button, the Grade Bin is replace with the Presets Bin of the current menu.
The Presets bin is available from the following menus:
Grading / Curves / Secondaries (Geometry, Gmasks & Tracker). To access the Keyer presets, right-click on any of the Diamond keyer colour presets (R/G/B/C/M/Y/Sh/Mid/Hi) or on the HLS keyer mode (Hue/Lum/Sat).
Note: In the Flame Premium configuration, the default location of the Denoise Lustre import / export is located in the Project Preset folder.
In addition to the Global / Project / Scene and User Presets Bins that are locations defined by the system or the project / user, it is possible to create presets that are saved with the source media files, the same way in which the Marry grades work. This is useful since presets can be used in any project that uses the same media files. When you navigate to a shot in the timeline, the Presets Bin for Marry shows you, for the current menu, the available presets for the current source footage.
In the User Management / Display & Interface, there is a new option to set the cursor type:
You can toggle between the three cursor type with the CTRL + Enter key.
Flame Premium: New Location for Full / Half Scans
When creating a project in Flame Premium with the "Create Lustre project" option, the location of the Scans Full / Scans Half is set to the following location:
<current Standard FS volume>/<project name>/
Lustre stores the following in this location:
