Skip to main content
Alexis Van Hurkman
Community Manager
Community Manager
August 15, 2024
Question

[Now Released]: Dramatically updated color management in Premiere Pro

  • August 15, 2024
  • 29 replies
  • 43813 views

We’re pleased to bring to public beta some dramatic improvements and expansions to the color management experience, tailored specifically to the needs of the Premiere Pro editor. With the right source clip metadata, color management automatically adjusts the color and contrast of each clip in your sequence so that every source clip from every camera is converted into a shared color space for further adjustment, and then output to the color space of your choice with automated color space conversions, tone mapping, and gamut compression creating high-quality output with the correct color.

 

In this new version, color management becomes more automated, handles more formats, preserves more image data, and gives you more flexibility to choose just the right workflow for your needs, even turning it off either partially or completely if you would rather work manually using Input LUTs, Creative LUTs, and effects.

 

After installing the public beta, your default Premiere Pro experience shouldn’t seem that different from before, but there’s a lot under the hood to explore. Here’s a rundown of the new features we’ve made available when using Premiere Pro color management:

  • Each sequence’s color management is easily configurable in the Sequence controls of the Settings tab of the Lumetri panel. By default, color management works similarly to the Premiere Pro color workflows you’re already used to when using the default Direct Rec.709 (SDR) preset. Alternately, you can choose to use one of our wide-gamut color processing presets to maximize the image quality of all grading and timeline effects when using wide-gamut or wide-latitude source media. Regardless of how you choose to work, Lumetri and other effects have been made color space aware, so they work well in any preset.
  • Users who don’t want to use automated color management can now turn it off from within the same Color Setup menu. This is useful for pass-through workflows when you don’t want the color space of media being processed at all, or when engaging in traditional display-referred grading workflows using LUTs and manual adjustments.
  • Premiere Pro now automatically color manages camera raw media, including Apple, ARRI, Canon, RED, and Sony raw media formats. As long as color management is enabled, raw clips will be automatically processed.
  • The Override Media Color Space menu has been expanded to support even more color spaces for more cameras and formats, making it easier than ever to color manage media that were either recorded or transcoded to standard file formats such as QuickTime and MXF, without needing to track down the right input LUT.
  • For clips you don’t want to be automatically color managed, a new Preserve RGB setting in the Color tab of the Modify Clip dialog prevents input to working color space conversions, allowing you to manually convert clips either using LUTs or manual filter adjustments.
  • Program MonitorVideo ScopesTransmit, and Media Export all output the image as it appears after conversion to a new Output Color Space setting. While the working color space lets you choose how media is processed, the Output color space lets you choose the specific color space you want to monitor (SDR, HDR PQ, or HLG) and deliver your program to. This guarantees that the working color space never needs to be changed, while making it easy to change color spaces at any time to create multiple deliverables using the same grade (e.g., delivering both HDR and SDR versions of the same sequence).
  • Improved tone mapping algorithms and new gamut compression settings improve quality when automatically converting wide-gamut source media to standard dynamic range. Additionally, there are now two ways  of using tone mapping, on input or on output.
  • Premiere Pro color management has been improved to enable smoother interoperability and color consistency using Dynamic Link for round-tripping color managed sequence clips between Premiere Pro and After Effects whenever you use the Replace with After Effects composition command.
  • Last, but certainly not least, if you import projects and sequences created in older versions of Premiere Pro that have grading and effects already applied, these will automatically be configured to appear the same as before, while the color management will function exactly the same as before. If you decide you want to override these legacy settings and use the new color management, you can override the custom settings the sequence was set up with and choose a different color management preset (and you can use Undo if you find this was a mistake).

 

As you can see, color management in Premiere Pro has become quite a bit more sophisticated. However, the best way to experience this is by upgrading to the public beta, creating a new project, importing some media, and experimenting for yourself:

  • By default, new sequences use the “Direct Rec.709 (SDR)” preset with the output set to Rec.709. This preset is best used when most of your source media is SDR but you’re importing some wide gamut camera raw or log-encoded media as well, and will give you the most familiar color handling experience.
  • If you want to try working completely manually, you can open up the Sequence Settings and set the Color Setup menu to “Disable Color Management.”
  • If you’re more adventurous, you can change the Color Setup menu to “Wide Gamut (Tone Mapped)” to try using the wide gamut workflow we’ve created to maximize the quality of sequences using primarily wide-gamut media.

 

As you experiment with the new color management options, be sure to share your questions or comments in this forum. We also encourage you to view the new color management documentation on our website: https://helpx.adobe.com/premiere-pro/using/color-management-improvements.html

 

Keep in mind that we’ll be continuing to bring improvements throughout the public beta period as we respond to issues reported, so details may change as time goes on.

 

We look forward to your feedback!

29 replies

Inspiring
May 3, 2025

Since this keeps coming up for me:
Will this issue realted to tone mapping ever be addressed?

https://community.adobe.com/t5/premiere-pro-beta-bugs/dramatically-updated-color-management-relinking-footage-resets-input-tone-mapping-to-default/idc-p/15257395#M5632

 

It s major pain point when you open projects which moved around and relink all the files. All the work has to be redone. 

IS there any workaround to avoid the reset of the tonemapping settings?

Inspiring
April 25, 2025

I just started playing with this in 25.3.0 build 61.

 

I notice that if I change sequence settings in the Lumetri Color panel, the color on the program monitor window (and clips on the timeline) change, but the Mercury Transmit external monitor does not change.  Is that by design?

jakew39230329
Known Participant
April 18, 2025

Can we get a log exposure and white balance slider before the first input lut for anyone still using a rec709 workflow?

R Neil Haugen
Legend
April 18, 2025

I've asked for that for years.

 

As currently, I do not recommend using transform or log->lin normalization LUTs in the Input process or the Basic tab's Input LUT slot. Because you cannot properly trim the clip into and through the LUT with corrections applie before the LUT. 

 

This is the process used by pro colorists ... as LUTs can easily clip or crush file image data.

Everyone's mileage always varies ...
jakew39230329
Known Participant
April 18, 2025

I agree. It would be helpful, i currently use them in the creative tab, or apply 2 sets of lumetri, as the basic controls are designed to work on normalized footage, but luts clip data. 

Shebbe
Community Expert
Community Expert
April 4, 2025

Hey Adobe,

 

So after radio silence followed up by the release of 25.2  almost none of the issues I repeatedly mentioned have been adressed...

 

Is this your solution to the obvious problem?

If you need to add a client logo it needs to be spot on accurate not "close enough".

The only workaround is to nest the scene referred data but with more complex edits this is impossible and just not desirable overall to always deal with nested edits as it f*cks your timeline versioning if the actual edits aren't existing in the output timeline.

 

DRT inverses are not something new, this could've been on the radar before even starting the implementation of this. If the existing DRTs aren't written well enough that an inverse is possible an alternative DRT should've been made. If that's not the goal then why still add this?

 

Nobody is going to benefit from this until it's properly addressed.

Alexis Van Hurkman
Community Manager
Community Manager
April 4, 2025

Hi Shebbe,

 

Your feedback has been received, and while we've moved forward with releasing what's been in public beta based on the broader positive feedback we've received, this is only the beginning. We're acutely aware of the tone mapping of SDR media in wide gamut and are in the process of providing a solution for this in a future release. For now, Wide Gamut is being made available for projects for which the current behavior is not a problem. Ideosyncracies such as this are why we're taking such pains to document this behavior for users, and it's why Direct Rec. 709 remains the default, available for people who need SDR to pass through the system as expected.

 

Regarding your prior observations, EXR color management is a larger issue for which there are no near term solutions, although again we're aware of this and it's on our long term road map. The other issues you'd brought up earlier are being explored internally. As always, we appreciate your detailed feedback, and ongoing improvements to color management are planned in a future release.

Shebbe
Community Expert
Community Expert
April 5, 2025

Hey Alexis,

 

I appreciate you explaining the move behind it and the plans of continuing development around this topic.

But I can't help but be concerned about it. Many times features are released and then left as is. Even if improvements are made, depending on the differences between the 'fixed mechanism' and the legacy 'broken state' present high chances of forcing backwards compatiblity to such states for sake of peoples projects not breaking.

 

It would've been more efficient to keep things that aren't fully finished out of the way until then. I wouldn't have minded at all if the improved colormanagement features would've been released without 'wide gamut tone mapped' ACEScct working space yet.

Shebbe
Community Expert
Community Expert
February 5, 2025

Hey dev team,

It's been a while since we've seen any updates around this feature set. Wondering if anything is to be expected soon.

A lot of the issues I've once mentioned seem to be still in place. Here's another quick summary of the things I observed.

 

- The kink in the tone mapping of ACEScct to display.

 

- Lumetri Curves in ACEScct have undesireable effects when messing with start and end point of the curve. (Lift/Gain) Probably because the curves tool uses clamping internally and the range is not aligned to ACEScct black and 'white'.

 

- Film Dissolve used to become yellow in the highlights. Looks like this is fixed!

 Another more general issue with Film Dissolve I spotted is that the transition curve seems weird. As if the first/last frame in the transition has a value of 10% already compared to a smoother fade start/end seen in Cross Dissolve. You can really see the B image jump into view instead of fade.

 

- Dip to Black does not map to the working space black point in ACEScct causing negative values at the bottom end.

Should be aligned when using 'Color Space Aware'. Even better would be internal conversion to linear for exposure style fade to black!

 

- Several combinations of Direct/ACEScct per channel or other DRT settings map to higher than display brightness. Not sure if this is intentional. (Seen in Lumetri Scopes but verified with EXR export to AE.)(Maybe time for a color info panel in PR?;))

 

- No inverse DRT for 'roundtripping' display referred image data for ACEScct workflows making use of sRGB/Rec.709 images in such a workflow impossible.

 

- S_OCIO_Transform and fnord OpenColorIO plugins still break the image when used in Direct SDR and are redicolously slow in Direct SDR and ACEScct. Image seemed to not break anymore in ACEScct though.

 

- EXR color management support is missing. We can disable the auto linear conversion in source settings but cannot convert ACES2065-1 or ACEScg to the working or display space.

 

I really hope many if not all of the above are adressed before we see a release.

Participant
January 29, 2025

Hi.

 

I am seeing colors differ between 32 bit and 16 bit float render paths. I am using Metal on macOS. The 16 bit image is greener. I first noticed this in PP v25 and it is also present in the beta.

 

Thanks

Adobe Employee
January 29, 2025

Hi @loren_9744 ,

Please share more details,  if possibe please share the media and project file to check

 

Thanks!

Participant
January 29, 2025

Hi,

 

I have sent you a dropbox link to a video file that will exhibit the problem in any project.

 

Thanks

SpaceCherryFilms
Inspiring
November 25, 2024

The latest update 25.2, when i add a lut to a clip the colors go haywired.  This happens when im using Wide Gamut (toned mapped), when its in direct 709 the lut works as intended

WINDOWS 11, AMD 3900X, 96GB RAM

 

 

 

 

 

R Neil Haugen
Legend
November 25, 2024

The LUT is probably designed for a Rec.709 space. As it works as expected with a Rec.709.

 

But when you go to a wide gamut sequence space, that LUT cannot work. As it's now getting applied to the wide gamut data. Remember, in wide gamut working space, the grading controls are applied in that space before the transform to display space.

 

Totally expected behavior. LUTs need to be used for the precise gamut they were created in.

Everyone's mileage always varies ...
SpaceCherryFilms
Inspiring
November 26, 2024

Ok that makes sense, thank you.

 

BUT in Davinci Resolve, with Color Space Transform,  I decide when the transform happens.  Im able to convert the color space to rec709 then apply the LUT at end of the node tree.  There needs to be a way I can convert the ACES to rec709 color space with the lumetri settings so i can apply a rec709 lut so I can get my intended results.  I prefer to not having to roundtrip for color grading if possible. 

 

 "If" Premiere wants to catch up to Resovle with color management, there needs to be an option for people who want more control to when color space transform happens

R Neil Haugen
Legend
November 12, 2024

@Alexis Van Hurkman 

 

When we apply Lumetri presets as a Source effect on a clip, where are they processed? Before working space transform or after?

Everyone's mileage always varies ...
Adobe Employee
November 12, 2024

Hi @R Neil Haugen ,

All effects are applied after working space transforms. This is true for both Source effects and Timeline effects.

 

Thanks,

Chetan Nanda

R Neil Haugen
Legend
November 12, 2024

Thanks for the reply, Chetan.

 

And as I also asked about how the RAW plugins, such as for BRAW and ProResRAW are handled, could you give the specifics on those? 

 

I use the Autokroma Studio plugin, though many use the standard BlackMagic Freebie. And the rather limited ProRes RAW plugin also.

Everyone's mileage always varies ...
Inspiring
November 10, 2024

I just tried the new color settings and I love that there are finally better options to work with LOG video in Premiere.

 

But I somehow just can't get my colors / gamma to look like the DVR conversion at all.

The sequence color space is rec709. I'm sure I'm doing something stupid / wrong here, but why can't i get the contrast to look "correct" or like it should look compared to DVR or the images I took on the same day.

 

If I apply about 90 on the contrast slider and use +1EV on the sequence setting it will look more similar but it still isn't quite there with more fiddeling.

But I feel like I'm doing something wrong here, because the gamma just doesnt seem correct.

 

Thank you for you help!

 

Afternote:

I mainly work on smaller commercial video projects, where it kinda doesn't matter how I create the video as long as the end results look good (and are done fast). So this missing featureset is what mainly held me back from recording everything in LOG formats and finally not have blown out skies (or without masking). Since working with LOG with input luts was always a major pain to get it look "correct".  

 

 

Shebbe
Community Expert
Community Expert
November 10, 2024

It is true that Premiere Pro's tone mapping does not have much of a preferential rendering and 'beefy' contrast going on compared to others but your DVR example looks quite 'overcooked' and I doubt it is a correct 'conversion'. Feels like a lot of contrast and saturation was added on top.

 

DaVinci uses a per channel style tone mapper by default. You can set Premiere's to "By Channel" to get a more similar look. You can try the Brightness & Contrast effect to add contrast if you feel like the range of Lumetri's sliders are too limiting. The brightness slider is the equivalent of Offset in DVR and contrast is the same as that of DVR too if "Use S-Curve for contrast" is disabled.

 

Keep in mind that the Shadows and Highlights sliders in DVR are spatial effects. Premiere/Lumetri do not have such operations in their grading tools.

Do you really think something is broken? What does DVR look like without any adjustment at all? Just fully disabled color management and a single CST node converting Rec.2020/N-Log to Rec.709/Gamma 2.4.

 

If it's still a big difference one of the two softwares may have a faulty N-Log transferfunction in place...

Inspiring
November 11, 2024

Thanks for your quick reply. As for it being overcooked - yes this is very true. That's why not I'm not fully happy with the DVR conversion either. But I'm not that experienced in the Danvinci color controls - I just wanted to brighten the dark region a little and yeah... I recorded the scene intentionally darker, so I could capture everything from the sky.

 

Here is the same scene in DVR. My target is a gamma of 2.2 since that historically worked best for me.

 

 

Going via the intermediary color space is closer to what I want to archieve. But does this mean it does something non standard behind the scenes? 

What catches me offguard here is that, apparently Gamma 2.2 doesn't mean the same thing in both programs. Using viewer Gamma 2.2 in Premiere Pro needs a conversion to gamma 2.6 in DVR to get a visually similar brightness. Anyways, that's not my main concern here. 🙂

 

But would it make sense than for me to basically create a LUT (which gives me a closer gamma) I apply in the input section, to "fix" this for me?

quote

Keep in mind that the Shadows and Highlights sliders in DVR are spatial effects. Premiere/Lumetri do not have such operations in their grading tools.

By @Shebbe

I've already noticed that these won't stick in the LUTs I exported from DVR. 

After I get the look correct in Premiere, I wanted to test, whether it would work, if I applied those spatial effects in DVR in the intermediary color space and exported it back as NLOG. Basically for "more difficult" scenes.

 

quote

DaVinci uses a per channel style tone mapper by default. You can set Premiere's to "By Channel" to get a more similar look. You can try the Brightness & Contrast effect to add contrast if you feel like the range of Lumetri's sliders are too limiting. The brightness slider is the equivalent of Offset in DVR and contrast is the same as that of DVR too if "Use S-Curve for contrast" is disabled.

By @Shebbe

Thanks for mentioning that. I tried that out and it does look very similar if it is set by channel.

 

Overall the conversion in Premiere Pro does look a lot better than it used to for me. Last time I tried the NLOG workflow in Premiere Pro I had to deal with a lot of off color and burnt out hightlights. Which kind of caught me offguard and made me not use NLOG for the time being.

 

 

Participating Frequently
November 6, 2024

Non ho trovato molto chiare le indicazioni per impostare i vari parametri o disabilitarli.