User-defined changeability of sequencing effects in Color Mode (Clip - Group - Sequence)

1 reply
14 views
Translate

Hi Adobe team!

I’ve been enjoying the new color mode in many ways, but the biggest issue I have at present is that the order in which effects are implemented is, by default, Clip → Group → Sequence. I would like the ability to change this on a per group basis, or at the very least, on a per clip basis, giving the ability to have the sequencing go Group → Clip → Sequence.

The issue is that when you first bring footage in, the main move for most editors (myself included but I work in an agency and this workflow is shared) is to first apply a standard LUT onto log footage to get it closer to a Rec 709 color space (or whatever the project calls for). Then, corrections are applied after this, so the 2nd effect is changing the luminance and chroma values after the LUT has gotten it into a more general area of acceptable contrast and color rendition.

HOWEVER this is still relevant if someone is taking something from log footage all the way to final look. It would be great to have a first layer, that could apply to a group, where a first pass on log footage gets the whole group to a more contrasty and saturated place (compared to log) before dialing that in on a per-clip basis.

As it stands, if I apply a LUT or effect to a group and then go back and want to fine tune it, I’m actually affecting the colors on the original clip without the LUT / effect on it, which means those changes are sometimes affecting values I can’t actually see in front of me, and which are maybe visible on the new HUD, but are not visible in normal scopes on the side (which I personally always keep on screen when doing color work).

Before it is mentioned, I am well aware that you can add some standard LUTs for many cameras to change their color under the “Color Management” window before any effects are added, but these options are very limited, and for new cameras/color profiles where Adobe has not yet included the LUT or just generally for more flexibility as mentioned above, this feature would be very helpful.

This would (I believe) put us back into a similar workflow that Lumetri had, where you could load in a LUT under the first panel (Basic Correction → Input LUT) and then move on to editing the colors in front of you. I appreciate Adobe’s unique approach to color and a lot of the elements in the new color mode are great, and in some cases a bit faster, but this feature really is key to controlling what the final color on any specific image is and to making adjustments on the image in front of you.

R Neil Haugen

Legend

First, a correction … most of the color management options for tonemapping at the top of Premiere’s CM panel ... are not LUTs … they’re algorithms. LUTs are certainly useful but they also are about guaranteed able to break the image if the exposure/contrast/sat are not what the LUT is expecting.

And if that transform LUT clips or crushes data, as applied prior to everything else, you cannot get that data back. This is why most colorists prefer if possible to work from the algorithms now in Resolve and Baselight … and also in Premiere. They do not clip or crush data.

Personally, never trusted putting a LUT in Lumetri’s Basic tab slot, I always used log->lin transform LUTs in the Creative tab slot, so I could then use the controls of the Basic tab to trim the clip into the LUT as necessary.

Which is the same processing chain then as in Resolve, when applying a LUT to a node, then doing corrections in that same node. As Resolve always processes any LUT applied in a node after all other operations in that node.

Second, is the view of the image after the algo’s identical to any LUT you’re using already? Of course not. Like LUTs the algos are built as a starting point … and all the camera makers give you a number of LUTs for every camera. So you’re already picking a specific starting point then working from there.

The algo’s are just the same, really. A slightly different starting point, like a different Sony LUT for example. Except the algos don’t clip or crush.

Translate

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.