<< Click to Display Table of Contents >> Navigation:  Nodes > Input > Camera RAW > RED File

 

Purpose

 

This node will load RED r3d files and set their properties before passing them to other nodes. Custom debayer options are supported.

 

Outputs

 

AV Out: A video Red RAW file with the settings applied on this node.

 

Standard properties

Object Name

Color

File

Name Convention

Lock

 

Input node standard properties

Content metadata

 

 

Debayer

Debayer

 

 

Node specific properties

 

r3d Gamma Curve, r3d Color Space: Drop-down menu to select r3d gamma & r3d color space. By default they will pass trough the original settings ( --- From File --- value) but you can force them to other values. These particular properties are RED r3d settings, but depending on the selection they will also set the gamma and gamut properties of the node and they will be displayed below.

Gamma, Gamut: As described above.

 

RED settings (ISO,  Tint, Exposure, Gain, Contrast,  Brightness, DRX, Shadow, IPP2 settings, ... ): These properties will use the r3d metadata settings by default, but they can be forced to other values by activating their respective Change parameterName buttons.

ReduceFactor: Default value is 1. You can set a division factor to make an image extraction at reduced resolution, which is  faster than extracting the images at full resolution, then reducing the resolution in posterior encoder nodes.

 

Notes about the name convention of RED files: RED .rrd files have a size limit, and when it is exceeded they are split into multiple enumerated files ( xxxxxx_001.r3d, xxxxxx_002.r3d etc.). .  This is not a problem for this node because it is specialized in this particular format, and in normal cases the metadata output by this node will also pass trough other nodes just fine, even if the Name Convention is left with an ambiguous syntax such as [path][baseName][.ext]. But certain operations such as EDL conforming are very sensitive to the correct interpretation of the file numbering and may fail if the file number syntax is not explicitly defined in the Name Convention.  If you experience conform problems please make sure to set the Name Convention to [path][baseName][_frame][.ext]  ( even if the file number is not technically a  "frame" it will provide the correct  file numbering-context).

 

Note about render performance from r3d files: In order to get the best performance, if C computer has an NVIDIA card with more than 3GB of memory, you can select Cuda New from the preferences menu in the File->Preferences->Codecs->RED decoder section. The Cuda decoder is several times faster than any of the other decoders.

 

Troubleshooting

 

When using the CUDA decoder for RED Files (File->Preferences->Codecs->RED decoder), if the RED decoder refuses to start with an error related to NVIDIA (or CUDA):

 

Install the latest NVIDIA driver supported for your GPU.  NVIDIA decoders and encoders are rapidly changing, and having an obsolete NVIDIA driver is a common cause of failure.

 

If you are using remote desktops to run  Mistika Workflows  unattended on virtual machines), make sure that the graphic session has a valid CUDA and openGL context. For example, the basic version of Microsoft RDP is known to destroy the graphics context on user disconnections. In particular, in the case of AWS EC2 better results have been observed by using Amazon own RDP via Fleet Manager.

 

You can also select a different RED  decoder different to CUDA,  (File->Preferences->Codecs->RED decoder), at least to help on troubleshooting.

 

 

Developer reference (API Rest - node/REDFile/property/[Property ID])