Participating Frequently

Question

Color Mismatch: Premiere Pro exports 16-bit TIFF and ProRes 4444 XQ differently from the same Raw source

Forum|Forum|26 days ago
March 10, 2026
4 replies
155 views

Hi everyone,

I'm having a serious color consistency issue when preparing files for a professional colorist.

The Setup: I have Raw footage on my Premiere Pro timeline. I exported two versions of the same clips (no effects, just the "raw" media) to send to DaVinci Resolve:

Version A: 16-bit TIFF Sequence.
Version B: Apple ProRes 4444 XQ (Render at Maximum Depth / Max Quality).

The Problem: When my colorist imports both into DaVinci Resolve and applies the exact same grade to both, they do not match. The TIFF and the ProRes have different gamma/color shifts, even though they came from the same Premiere timeline and the same Raw source.

TIFF 16 BITS:

PRORES 4444 XQ:

My Theory: It seems Premiere is applying some internal color management or NCLC tagging to the ProRes export that it isn't applying to the TIFF sequence.

My Settings:

Project/Sequence Color Space: Rec. 709.
Viewer Gamma: 2.4 (Broadcast).
Display Color Management: OFF.
Export Settings: Both exports are set to Rec. 709, but the pixels clearly don't match once they leave Premiere.

How can I ensure that Premiere exports a "pure" ProRes 4444 XQ that matches the data levels and gamma of a 16-bit TIFF sequence? Is there a hidden transform happening during the ProRes encode?

Thanks for the help!

jamieclarke

Community Manager

Hi @marjorieee - Can you navigate to the Lumetri Panel > Settings and then navigate to Sequence > Color Setup: and change that setting to “Disable Color Management”. Let us know if that helps your issue

marjorieeeAuthor

Participating Frequently

Hi Jamie,

That fixed the issue, but it points to a clear inconsistency in how Premiere handles different formats.

When 'Color Management' is enabled, my TIFF exports match the original raw footage perfectly, but the ProRes exports do not—they only match the source once I disable the setting, as you taught me.

This forces me to constantly toggle Color Management just to ensure my ProRes exports remain faithful to the original raw files and consistent with my TIFF frames. Is this a known mapping bug between sequence management and video exports that Adobe plans to fix in future updates?

jamieclarke

Community Manager

Hi @marjorieee - Thanks for submitting your bug report. We need a few more details to try to help with the issue. Please see, How do I write a bug report?

@R Neil Haugen has some good questions and will be able to help,.

Please let us know as much detailed information as you can.

R Neil Haugen

Legend

Hokay ... quick question, you have DCM (display color management) off ... is that display highly calibrated, preferably with a profile check after the calibration to check how accurate it is? Or say via a Decklink or AJA output device?

Next, you say “raw” ... but is it actually a RAW file, and if so, from what camera? If not an actual RAW file, if you just mean the original camera file ... what format/codec and color space plus dynamic range is the media?

The TIFF/16 bit file is quite possible handled as Premiere as an RGB file. I’ve not checked that in a while now ... and if so, it would therefore be encoded in ‘full’ range. Most 16 bit files are technically RGB and not YUV, and are by the specs for Rec.709 encoded in full range.

The ProRes will be encoded as a YUV file, and by the full Rec.709 specs, for Rec.709 YUV media, as “legal” range.

I would expect the colorist would normally handle the two files correctly ... but you can check the Properties for the TIFF file re-imported into Premiere. Does it show full range?

Everyone's mileage always varies ...

marjorieeeAuthor

Participating Frequently

Hi everyone,

Thank you for the detailed questions. Here is the technical breakdown of my setup:

1. Monitor and Calibration (DCM): I am working on a MacBook Pro M3 Pro (Liquid Retina XDR display). I do not use a Decklink or AJA output device; I'm monitoring directly from the GPU. I have kept Display Color Management (DCM) OFF in Premiere's preferences to avoid additional OS color layers during this technical comparison.

2. Source Media and Raw Handling: The footage is from an ARRI Alexa Mini (.MXF) recorded in Log-C. I have also experienced this exact mismatch previously with RED RAW (.R3D) files. In both cases, the source is interpreted correctly in the timeline, but the exports diverge.

3. TIFF Properties (Re-imported into Premiere): When I import the exported 16-bit TIFF back into Premiere, the properties show:

Type: TIFF Image File
Color Space: Rec. 709
Color Space Override: Off
Alpha: Straight Alpha
As noted, since this is an RGB TIFF, Premiere appears to be handling it as Full Range, which is expected.

4. The Evidence (Scopes Comparison): I have performed a side-by-side comparison using the Lumetri Scopes (Waveform Luma set to 8-bit for monitoring). I am attaching two screenshots: one for the TIFF export and one for the ProRes 4444 XQ export, both from the exact same frame on the timeline.

The TIFF Screenshot: Shows the peaks precisely at the 128/153 (8-bit) mark (around 60 on the percentage scale).
The ProRes 4444 XQ Screenshot: There is a visible lift. The highlights peak slightly higher than the TIFF, and the shadow density is shifted.

Conclusion: This confirms that even with "Render at Maximum Depth" and "Use Maximum Render Quality" enabled, Premiere Pro is re-mapping the luma/gamma levels differently for each codec.

The TIFF (RGB/Full) maintains the timeline's integrity, while the ProRes (YUV/Legal) undergoes a transformation—likely an NCLC tagging or a Gamma 2.4 vs 2.2 shift—that makes it impossible to achieve parity between the two files in a professional color grading roundtrip.

What is the official recommendation to ensure that a ProRes 4444 XQ master export matches the bit-for-bit luma levels of a 16-bit TIFF sequence?

R Neil Haugen

Legend

First, your Mac ... do you have Reference modes, and is that set to HDTV? As if not, then ... your Mac display is showing an incorrect Rec.709 image ... sorry, but that was Apple’s choice in their ColorSync utililty.

I work for/with/teach pro colorists, have for years now, and they as expected are mostly Mac geeks, right? And they are still furious with Apple over this for the entire last decade. But ... Apple will be Apple.

Second, there can be differences in Premiere’s encoding at times with some high-end files and you might be hitting this. So ... @Fergus H ... would probably be necessary to give the inner details of sorting that out.

Everyone's mileage always varies ...