Skip to main content
Participating Frequently
March 26, 2026

Color Management Bug: color changes despite same settings

  • March 26, 2026
  • 3 replies
  • 24 views

I have footage from a Ronin 4D 8K camera which continued to look overexposed despite the raw footage having no such problem. Talking to the camera team, they said that the D-Gamut/D-log color space allowed for proper exposure on the footage while Rec.709. 

No matter what I did in Lumetri though, the footage continued to look overexposed and I couldn’t even get it to look raw, due to the default Rec. 709 Media Color Space in Lumetri. 

I started to get somewhere when I changed the color space of the source clip in the Effect Controls to D-Gamut/D-Log, like this:

r/premiere - Color Management Bug: color changes despite same settings

With that setting in Effect Controls, the footage finally looked like its normal Raw self. Once I had it looking that way, I achieved the perfect look by just turning on Color Manage Auto Detected Log and Raw Media. I wanted to try it manually as well, and so when Auto Detect was checked off, if I overrode the Lumetri Media Color Space and made it ARRI LogC3/Wide Gamut3 (that’s the media color space that just really worked!), I had the same exact look as Auto Detect - which seemed to confirm to me that it was the right setting. This moment I have in screenshots below, but then as soon as I clicked on a different clip to try to replicate the results, these same settings created an entirely overexposed picture! And when I went back to this clip, it was also overexposed (Auto Detect or manually added) (screenshots below). 

Any guesses for how to fix this issue? Leading up to this point I worked in the comments of another post, here is that for context

D-Gamut/D-Log applied in source effect controls and default Rec.709 in Lumetri (see effect controls below picture and Lumetri to the right):

r/premiere - Color Management Bug: color changes despite same settings

D-Gamut/D-Log applied in source effect controls and Auto Detect turned on (perfect!):

r/premiere - Color Management Bug: color changes despite same settings

D-Gamut/D-Log applied in source effect controls and ARRI LogC3/Wide Gamut3 applied in Lumetri (perfect and identical to auto detect - which confirms that's the right way):

r/premiere - Color Management Bug: color changes despite same settings

D-Gamut/D-Log applied in source effect controls and Auto Detect turned on afterwards, now totally overexposed:

r/premiere - Color Management Bug: color changes despite same settings

D-Gamut/D-Log applied in source effect controls and ARRI LogC3/Wide Gamut3 applied in Lumetri afterwards, now totally overexposed:

r/premiere - Color Management Bug: color changes despite same settings

    3 replies

    R Neil Haugen
    Legend
    March 27, 2026

    You don’t include any sequence setting there … and that is an inevitable part of working video media. The Sequence CM tells Premiere what transform to use for the monitor, and for any exports from that sequence.

    Clips can have different CM applied in different sequences, that’s a strength of the new system. But can be an issue, like a ton of other things in color management, if you don’t know it’s a potential issue.

    Everyone's mileage always varies ...
    Participating Frequently
    March 27, 2026

    Yes, once I solve this issue that is my next step! Determining colorspace of the both the Multicam Source Clip for soundsync and then the sequence that goes into when I’m actually cutting. These settings and picture issues, however, are all in the source monitor, only looking at the original media. Nothing changed from me having the right look on this clip to it going overexposed and unable to reach that good luck except for me clicking on a different clip and back to this one - those settings which briefly yielded what I wanted now do not. 

     

    I just sent the file to Ian who commented below!

    R Neil Haugen
    Legend
    March 27, 2026

    You will not see the final, export ready image of the clip in the Source monitor, as that is source state, not after the display transform to whichever color space you set in the sequence.

    So understand, to see the clip ready to export, you must have it on a sequence in the Program monitor … with the sequence color space set to your expected export need.

    Everyone's mileage always varies ...
    IanB_360
    Community Manager
    Community Manager
    March 27, 2026

    Hi ​@Zachary29825943vx85 
    Welcome to the Premiere community. Thank you for taking the time to report a problem. Could you share one of the files you're having an issue with? You can email or DM me with a link to anything you have to share with us. 

    Here to help.  

    Ian

    Participating Frequently
    March 27, 2026

    Just sent it to you over email, thanks!

    Participating Frequently
    March 26, 2026

    Computer Specs:

    Apple M2 MacBook Pro; MacOS Tahoe 26.2; GPU; Bus: Built-In; Total Number of Cores: 10

    Premiere Version:

    26.0.0 (Build 72)

    Footage:

    Ronin 4D 8K Camera; stored on HDD external drive, ProRes (RAWHQ)