Most compositors these days have experienced the pain of trying to pull a key, denoise, or blur an image with negative pixel values - the artifacts are ugly, and require a lot of jiggering to get around the issue which can be time consuming and hard to track. With the test instructions, Nuke setups, and footage we provide you, we’ll be asking you to perform operations with and without the Gamut Mapping algorithm, and note your findings. Did it make your work easier? Did you notice any adverse effects? Do you still prefer another workflow?

This info is also located in the READMEs in the provided zip.
 
Testing Instructions:

We know your time is valuable - so we have provided you with both text based and quick select options throughout the form. The more information you give us, the better we can make this tool!

The questions in the form will be based around the footage - the names of which should match the Read Nodes / Backdrop labels in Nuke, from left to right across your screen.

Nuke Specifics:

Before you start, here are some details about the way the provided Nuke script(s) are set up for you to double check:

- Nuke or NukeX or Nuke Non-commercial, tested on version 12.2v3
- Color management set to OCIO
    - ACES 1.1 Config
    - Viewer set to ACES - Rec. 709
    - Working space set to ACEScg

In the GamutCompress Node itself, there are a few options (see screenshot in the nuke_README):

Power: affects the curve used to determine the amount of compression in the algorithm - we will be asking you to test each setting and choose your preferred option.
Direction: The algorithm is invertible, so you can choose between forward or inverse**.
Method: Depending on your Nuke version and hardware, you may want to choose Blink (GPU or CPU) or pure Nuke (for Nuke NC which does not include Blink). All implementations should yield identical results.

** Note on inverse: we are providing the inverse as a proof of concept, but it will not be a workflow we will be recommending in production. Please feel free to test it out, and reach out with questions/concerns or if you'd just like more information on invertibility.

Each section is divided up into relevant footage - multiple choice answers are required, but most text fields are optional. Please fill it out as time allows - the more concrete feedback you can give, the better we can make this tool. We have kept the questions/prompts vague so as not to muddy the waters - we would like your honest opinions following your typical day to day workflow.

Thank you for participating!

- Carol Payne, Matthias Scharfenberg, Nick Shaw, & the ACES Gamut Mapping Working Group Members