Difference between revisions of "UM:Red File Format"
m (Upload page Red_File_Format) |
m (Text replacement - "|Platform:" to "|UM:") |
||
Line 1: | Line 1: | ||
<div class="manualcontent"> | <div class="manualcontent"> | ||
− | {{Template:M-Navlinks-top| | + | {{Template:M-Navlinks-top|UM:Manual|UM:Red_Support_Main|UM:Red_Properties_And_Metadata}} |
{{Template:M-Title|Format and Conventions}} | {{Template:M-Title|Format and Conventions}} | ||
Line 196: | Line 196: | ||
<p class="p_DVBodyText"><span class="f_DVBodyText"> </span></p> | <p class="p_DVBodyText"><span class="f_DVBodyText"> </span></p> | ||
− | {{Template:M-Navlinks-bottom| | + | {{Template:M-Navlinks-bottom|UM:Manual|UM:Red_Support_Main|UM:Red_Properties_And_Metadata}} |
</div> | </div> |
Revision as of 12:06, 15 October 2014
The R3D file is a 12 bit RAW format that supports high resolutions and high dynamic range images.
A full dynamic range is preserved by extracting the raw R3D data at 16 bits but we may later choose to work with 10 bit DPX files. See the section Properties and Metadata. |
The RED ONE camera can shoot at a number of different resolutions and the highest resolution shot will determine the resolution of the main Full Premium decode.
Dynamic decoding of the Red R3D raw image data.
Each resolution is defined by its size and its quality.
Full Size and Premium Quality is the maximum resolution the camera has shot and this will determine the alternative decode formats available. The 1/2 Premium mode is half the pixel resolution but the same decoding quality.
The table below show the possible decode resolutions for the RED ONE 4K camera shooting its maximum resolution of 4096x2304.
Size |
Quality |
Width |
Height |
Full |
Premium |
4096 |
2304 |
1/2 |
Premium |
2048 |
1152 |
1/2 |
Medium |
2048 |
1152 |
1/4 |
Medium |
1024 |
576 |
1/8 |
Medium |
512 |
288 |
1/16 |
Medium |
256 |
144 |
Note that a Full Premium decode of a 2K shot will have a resolution of 2048 x 1152.
Files and Folders
By convention, the R3D filename encodes some basic metadata.
The R3D filename A004_C019_0806UL.R3D encodes :
A |
The camera identifier |
004 |
The clip identifier |
C019 |
The reel identifier |
0806UL |
Year (2 digits), Month (2 digits), 2 random characters [1] |
.R3D |
The RED ONE file extension |
[1] Previously, these six characters were the GMT date (format YYMMDD) e.g. A004_C019_080612.R3D
This was recently changed to replace the day part with two random characters. This is to help prevent file paths being duplicated thus risking overwriting shots.
These random characters do not exist in the R3D file header metadata. This means we now have to conform using tapename or clipname from filename (not file header). See the Conforming with RED section. |
RED .R3D files usually come in a folder structure where each folder contains a single shot. The folder structure may appear as follows :
S:\media\projects\test1\A004_C019_0806UL.RDC\
A004_C019_0806UL_001.R3D A004_C019_0806UL_002.R3D |
The filename numerics (_001 etc.) do not specify frames. The R3D shots are split into 2 GB chunks due to the limitations of the file system used to save the files. Our application will see and import this "clip" as a single shot. |
Tapename
The tapename metadata element will be extracted from the R3D filename.
Tapename : A004_C019_0806UL
The Conforming with Red section discusses both tapename and clipname as they relate to the conform process.