Jump to content

ACES workflow

Melanie Diaz

Recommended Posts

Hi there!

Using this template you will learn how to streamline ACES pipeline with Mistika Workflows. Our platform supports the latest ACES 1.3 version. 

By default, Mistika Workflows reads the source clip metadata and builds the necessary color space conversions during transcoding to different formats. In this example, we work with two formats: R3D and DNG from DJI drones.

To set the R3D media to AP0 Linear, we connect a debayer node for RED files to the folder and configure the color space to ACES. 

This is possible because RAW formats typically include the IDT in their parameters, so we only need to select ACES for them (note that the required debayer may vary depending on the RAW camera).

The DJI files don't have this option embedded, so we need to make the color space conversion during transcoding. To do this, we set the input color space (DJI D-Gamut and DJI D-Log) and then use the EXR and ProRes nodes to convert the color space to AP0 Linear and Rec709, respectively.

The output color space in Unicolor uses ACES ODT as default values. If you need custom outputs, set the option to custom and define the output Gamut and Gamma.

This is just an example workflow for the automated ACES pipeline. You can modify it to fit your needs adding new inputs, tasks and outputs.

If you need assistance, please reach out by opening a ticket on SGO Support Portal.

Enjoy Mistika Workflows!


Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.