...
| Table of Contents | ||
|---|---|---|
|
Setup
Here your can define which setup file should be used. This controls which Global Config to load and edit.
Global Config
Default values
First let’s have at look what default config value you can set:
label | key | description |
|---|---|---|
Element-Number padding | element_number_padding | Set the number padding for the naming convention. |
Framecount for Filmstrip | filmstrip_length | Set the frames used for the preview filmstrip in the ingest view. No matter the length of the sequence, the filmstrip length will be this many frames. |
First frame of Sequence | first_frame | Set first frame of a sequence when transcoding a file sequence. Some VFX studios start with the common 1001 frame. |
Thumbnail Frame of Sequence | thumbnail_frame | Set which frame of a sequence should be used for the thumbnail frame |
File path definitions
...
| Info |
|---|
This is the part where you define your naming convention and file path structure |
This is where you set the naming convention and file structure on disk.
You need to define the file path patterns so the software knows where to store the elements file data. These two path patterns are the most important path patterns that the transcoding template will use.
Types of path patterns
Which path patterns will be used depends on the output format and the transcoding templates setting for each library. There are two types of path patterns.
| Info |
|---|
In transcoding template you can set this with the option: Type of output file |
Single files
Movie files or single textures files without frame count.
...
Cory process of a movie filemy-movie-file.mov -> fire_000023.mov
Sequence files
Renderings or sequences with frame counter.
...
Use '#' for the frame counter. The default frame count padding is 4.
Path Patterns
...
You can create a so called path pattern. A pattern is assembled by placeholder values. These values get resolved into the actual value on ingest/render time.
...
This might look a little bit weird at the beginning, but this system gives you full control over how to assemble your naming convention. You will see the benefit of it in a second.
Example: resolution
Our source image is an image of a flame with the resolution of width 1920 and height 1080.
We create a path pattern to define the naming convention of the resolution folder as followed:
...
If we create a library transcoding template that creates a thumbnail preview for our elements, we can overwrite the path value <colorspace> by another value. For example: srgb
The path pattern for this transcoding template gets now resolved to: abc_1920x1080_srgb
...
Example: category
Let's create a path pattern for defining the naming convention for folder of the element.
Create a new path pattern:
element_name : <category.base.name>_<element.number>
...
| Info |
|---|
Why should we use the base category? We want our library to be sustainable and be as static as possible for many years. That is why you should decided to store the elements in the base category folder |
Path Values
...
Path values are used to resolve the values of the path patterns depending on the element that will be ingested or rendered. Some values are known once we actually know the data that we want to ingest, others values can be set by you (custom values). The custom values can be overwritten in the library and the transcoding templates.
Predefined path values
The predefined values are used as placeholders in the path patterns. They are divided into separate predefined groups that will be commonly used. For each group you can access the sub-keys.
...
Example
If you want to get the width value of the source element you ingest, you access the group resolution and the sub-key width in the path pattern like this: <resolution.width>. This will resolve the source image width value for you.
Example: element
Path of element that we want to ingest:/some/path/to/file.%04.exr
It is a sequence of OpenEXR files that contain a picture of a flame.
The first frame of the sequence is 1001 and last frame is 1042.
Each image has a resolution of width 1920, a height of 1080 and a pixel aspect ration of 1.
In the library there are already 22 fire elements.
...
description | predefined value | example resolves to |
|---|---|---|
source image width |
|
|
source image height |
|
|
image pixel aspect resolution |
|
|
source elements file extension |
|
|
Frame counter for a sequence |
|
|
output sequence first frame |
|
|
output sequence last frame |
|
|
number counter of this element |
|
|
readable name for flame category |
|
|
unique ID for flame category |
|
|
readable name of the base category for flame, based on the hierarchy category tree |
|
|
unique ID of the base category for flame, based on the hierarchy category tree |
|
|
Custom path values
These are the values that you can define. These custom path values get resolved in the path patterns.
...
server : /path/to/server
library_name: my-element
If you use path patterns that reference path values you have to make sure that these values exist in the path values section. If something can not be resolved because values are not defined, the ingest or rendering of proxies will fail and you will see an error message.
Overwrite pattern & values
The server path or the folder where the library data is stored might chance for each library.
Overwriting path pattern and path values is based on the concept that you only need to overwrite values for each library, which reduced the complexity and misalignment of the file structure.
...