Copy link to clipboard
Copied
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:
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:
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!
Copy link to clipboard
Copied
I should clarify. Based on my testing:
Current release:
Display Color Management enabled - causes media thumbnails to be converted to the display space by OS display profiles. Internal conversion regarding sequence settings to Rec.709 including tonemapping is disabled. (displaying source pixels directly converted to the display.)
Source Monitor - Also shows original pixels directly but with Display Color Management enabled behaves the same as the thumbnails.
Current Beta:
Display Color Management enabled - thumbnails are still converted directly from source color space to the actual display, ignoring sequence settings.
Source Monitor - Takes whatever current opened sequence color management set up is and applies that to the source viewer so they match. This includes both Display Color Managment enabled or disabled.
Bug - When using direct SDR as management it looks like Tone Mapping method Hue Preservation is enabled for the source viewer despite picking By Channel for the sequence. I didn't see this issue when using ACEScct.
Mechanism concern:
We can have individual sequence based color management which makes sense for different deliverables and it's good to have that flexibility. But it also feels like a structural problem that there is no global management present. Colormanagement per production/project in almost all cases isn't something you decide per sequence. Would it not be better to have project based color management instead, then subsequently all sequence settings will inherit the project's settings by default unless overwritten. This would enable the entire project to be managed in a consistent manner and globally changed if needed.
Here's a mockup of what that could look like: