who here has figured out how to gamma correct for quicktime from premiere?

[Paz Derien]

Really? No one? Do you not care because you just don’t use quicktime player or care about others who use quicktime? Do you just hope people don’t use safari? I am seeing documentation everywhere about this problem and no clear workflow fix at the encoding level….strange….

[Alex Udell]

At a cursory level….

if you know what the offset is supposed to be….

could you nest sequence apply a gamma correction tool of you liking….

then submit that nested sequecne for encoding in AME?

Alex Udell
Editing, Motion Graphics, and Visual FX

[Phillip Todd]

I am still on FCP 7 and am trying to decide on Premiere CS6 or FCPx (I do a lot of multicam). All this to say I do not know the problem but have read about the issue (if this is the right issue)

From:https://www.eoshd.com/content/8612/mac-avchd-gamma-issues-the-fix

topline:

“The fix

In Premiere Pro, the specific part of the Fast Color Corrector you need to apply the fix with is the Output Levels.

Keep the Input Levels at 0-255 but change the Output Levels to 15-235.”

Let us know if it works for you.

Phillip Todd
Cinematographer

https://vimeo.com/philliptodd

[Gabriel Regalbuto]

If I remember right, there was a gamma shift out of FCP as well, and the fix was (with QT 7) to check a preference in QT to “Match FCP gamma adjustments.” QTX did not offer this fix.

As for the multi-cam, I stick with FCP 7, not wanting to mess with FCPX and frustrated with the inability to collapse multi-clips in Premiere or get any usable EDL out (Premiere won’t reference the source code) to conform. If you don’t need that functionality, the multicam tools in Premiere are workable.

[Phillip Todd]

Thanks Gabriel

[Jeff Brown]

“Keep the Input Levels at 0-255 but change the Output Levels to 15-235.”
I think this will make the problem worse?
If you are targeting web playback, can you (rename) use the file as an MP4 instead of MOV? and use HTML5 playback … AFAIK, there is no fix at then encoding level, because this is a bug in QuickTime (on Windows, a bug that has not been fixed in maybe 5-6 years or more?). As you have seen, your clips look fine in VLC player. I bet they also look fine in Safari on Apple products? Unless this is somehow unrelated to the h264/QTime issue we Win users live with.

wish I could be of more help,
Jeff

[Isaac Viejo]

Same problem here. When I export my project (edited in All-i from 5D MarkIII) from Premiere CS6 everything looks ‘brighter’ in any format I try.
There is even some issue with Magic Bullet Looks. The preview image looks brighter as well, so I cannot use it at all in Premiere… In After Effects is not a problem if I use Color Management… but then, when I export the picture is washed-out again…
I am on Mac… so it is not just a windows problem…

Isaac Viejo /StudioKrrusel/
Editor / Motion Graphics / VFX / Color Correction / Design
https://studiokrrusel.com

[Ivan Myles]

A couple of years ago I spent an extended period of time trying to resolve this problem. I ultimately concluded that the issue is caused by QuickTime color management. Trying to compensate by adjusting gamma or RGB output levels in Premiere Pro creates new problems when the output file is viewed in other video players.

Going back to the original post, instead of exporting an H.264 file directly from Premiere Pro, create an intermediate file using a non-Apple uncompressed codec. Then use QuickTime Pro to encode the intermediate file to H.264.

Of the standard Premiere Pro CS6 codecs, AVI None seems to produce the least washed-out colors in QuickTime. The video might look a little different in other players, though. Also try AVI V210 10-bit YUV or Uncompressed UYVY 422 8bit.

[Ivan Myles]

After further assessment it appears the process described in my previous post no longer works; H.264 files exhibit significant gamma shifts when viewed in QuickTime.

I was able to resolve the issue temporarily using either of the following methods:

a) Change QuickTime Visual Settings to Transparency: Blend-100%, and then Straight Alpha. The new settings cannot be saved in MP4 files, but can be saved in MOV format (although QT sometimes has trouble playing these altered MOV files).

b) Position the QuickTime window on the desktop so that part of it appears on two different monitors simultaneously (i.e. straddle the two monitors). The H.264 file will look fine when the QT window sits partly on each monitor. The video returns to looking washed-out once the QT player is moved entirely to either monitor.

For reference, here are the steps that were taken to troubleshoot the issue:

– exported NLE output files from Pr-CS6 using the following codecs: AVI-None (RGB-8bit), AVI-V210-422-10bit, AVI-UYVY-422-8bit, AVI-BlackMagic-444-10bit, QT-None (RGBA-8bit), QT-JPEG2000, QT-422-10bit, QT-422-8bit, QT-BlackMagic-RGB-10bit, QT-H.264

– encoded the NLE intermediate files into H.264 MP4 and MOV formats using QuickTime Pro

– opened the H.264 files in QuickTime and took TIFF screen captures of select frames; also opened a few of the files in VLC player 2.0.4 and Windows Media Player 12

– compared the NLE output files, encoded H.264 videos, and TIFF screen captures to the source video using the color scopes/waveform analysis tools in Pr-CS6

– tried four different versions of QuickTime Pro for Windows (7.7.3, 7.7.2, 7.6, 7.5.5)

– uninstalled VLC media player and FFD Show video codecs from the computer

– lastly, uninstalled all CS6 applications

For the most part there is relatively little difference between each NLE output file and the source video. The encoded H.264 files look OK in Premiere Pro and non-Apple media players, but appear washed out when viewed in QuickTime.

[Ivan Myles]

I just viewed over twenty H.264 test files that looked washed out on my video production computers, and all files looked great when played in QuickTime on a Windows computer without Adobe Creative Suite (including H.264 files exported directly from Premiere Pro).

Until recently I used different computers for video production and encoding. The QT gamma/contrast issue became significantly worse shortly after loading Creative Suite onto my encoding rig.