Skip to main content
Inspiring
January 24, 2023
Released

QuickTime gamma shift [Prevent color shift on export from premiere on MACOS]

  • January 24, 2023
  • 40 replies
  • 20975 views

A common issue I've seen here. When exporting a sequence from premiere the color shifts dramatically in the majority of playback programs. Quicktime, Vimeo, Youtube etc. VLC works fine but not everybody is using VLC. Makes for lots of wasted time on color grades.

 

Comments from Adobe below

This is an issue we (Adobe) are aware of. The best desciption of this issue is in this article and the related video: 
https://www.todddominey.com/2021/01/24/why-are-videos-washed-out-on-the-mac-exploring-quicktime-gamma-shift/

 

A feature for handling this issue - adjustable Viewer Gamma - has been added to Premiere Pro v24 and is explained in this documentation: https://community.adobe.com/t5/premiere-pro-ideas/quicktime-gamma-shift-prevent-color-shift-on-export-from-premiere-on-macos/idc-p/14186643.

 

Fergus

40 replies

Fergus H
Community Manager
Community Manager
April 10, 2023

An update to Premiere Pro that makes this issue easier to handle will be coming later in 2023. We will update this thread with more information when it is available. 

 

Regards,

Fergus

R Neil Haugen
Legend
February 10, 2023

That Vimeo from Baselight is one look at the issue. It's not necessarily accepted as an accurate view, though, by many of the other folks out there in color management. One significant misreading is typically cited. Whether by Steve Shaw at LightIllusions or others.

 

That video assumes that the original Rec.709 standard from many years ago is still the entire standard. But it hasn't been for years! Not since flat-panel digital monitors replaced CRT monitors. The digital monitors had a very different image from the 'native' digital signal. They therefore required either the additional spec of a display gamma or a change to the camera transform process.

 

Adding a display transform to the Rec.709 standard was thought simpler.

 

Bt.1886 was appended to the Rec.709 standard years ago. And the traditional broadcast/network/streaming processes for years now have included the expectations below for Rec.709:

  • sRGB primaries
  • camera transform of 1.95
  • display transform of 2.4 (dark room viewing) or 2.2 (bright room viewing) {added as Bt.1886}
  • 100 nits screen brightness in moderately-dark-room grading

 

This workflow was the accepted manner of working with NCLC tags of 1-1-1, and the monitors were carefully calibrated and profiled to the above display specs. It's what both Resolve in "auto" mode and Premiere Pro applied to Rec.709 files.

 

Apple chose to return to the original Rec.709 spec and ignore the Bt.1886 appended specification. Think of this as "the real Rec.709," ... but Apple changed that years ago. And applied throughout professional workflows.

 

Until ... ColorSync reverted.

Everyone's mileage always varies ...
malbutnotbad
Inspiring
February 10, 2023

Been dealing with this for years. Best I've figured out is to make sure directors and clients use VLC to do their official reviews (esp if reviewing color). Not ideal, but I've got nothing better! arkalmed is on to the real fix there, just need to make engineers aware of it.

Known Participant
January 24, 2023
Does anyone even answer here?
Known Participant
January 24, 2023
What codecs did you use ? What software to play the file ?

You could try to export with AfterCodecs Exporter for Adobe CC https://www.autokroma.com/AfterCodecs

there is a free 500 frames trial, or H264 is free when resolution is < 720p
supersimplesmitty
Participant
January 24, 2023
Well just updated to premiere 2020
guess what still not fixed..

Already using the Lut for some exports.. mainly doing commercial billboards, and using that is usually fine. But this still is a big problem adobe. thanks
Inspiring
January 24, 2023
You guys and gals (and the Premiere developers too!!) should watch this video explaining the problem to the dot.
Made by the guys from Filmlight (I assume they know what they're talking about):

https://vimeo.com/349868875

So what Premiere Pro is missing is the correct NCLC tagging of QT files during render/export.
Inspiring
January 24, 2023
Colour shift on export in 13.1.5 is indeed 100% unfixed on an iMac Pro running Mojave. Try again adoob. And enjoy my money in the meantime, isn’t it great?
Known Participant
January 24, 2023
Allow me to save your lives. I can't believe this took as much searching as it did to find an OFFICIAL FIX FROM ADOBE for this issue (until they can figure out how to unbreak it again). Adobe's own version of this video should have been sent out by Adobe to all users of Premiere Pro the second they discovered this issue. Why it wasn't is beyond me. Well, not really because Adobe is both so amazing at enabling us to do what we do, but so utterly abysmal at fixing things that won't work. Enjoy: https://www.youtube.com/watch?v=t61b6Nk-YPw&list=PLA05pELl8mMiABtsCSEB4XdivVupnYcyc&index=5&t=229s

I do want to add one important fact: Today I married the final sound and color on a project. The color was delivered to me via prores HQ from my colorist, who graded in Resolve. There was NO NEED to apply this LUT to my final export. I double checked my export against what my colorist gave me, and there was no shift in color at all noticeable in either premiere pro or using quicktime player.

So the BIZARRE thing about this color shift issue is that it only seems to happen when you use Premiere to grade our projects. Which is super weird since Adobe can't seem to export the color we create with the very tools they provide unless we use this LUT as a fix.
supersimplesmitty
Participant
January 24, 2023
After updated to 13.1.5 this is definitely not fixed for a 100% not fixed!