Gamma shift on exports with Prores and H264 with Quicktime

Forum|Forum|5 years ago
April 25, 2020
2 replies
5697 views

Hey everyone.

Im using the latest Premiere Pro.

Are they gonna fix this problem any time soon? It has been years since we all are having this problem and the only response from Adobe it's "Hey, professional calibrated monitors works well..." but, hey, Adobe, de you know that the vast majority of your clients are not grading on professional monitors, and are probably using iMacs, Macbooks and PC prosumer screens? And most of them are not high end professionals? What happens with educational envionments? Why do we need to have this problem on Premiere when DaVinci Resolve (free software) and FCPX (a $300 lifetime license) are not having this issues?

I just want to make an edit, grade it and export what I'm seeing on Premiere monitors. Is that so hard Adobe? Why insist on not patch this kind of issues, or at least give the option?

F.

This topic has been closed for replies.

A

Andy 1968

Inspiring

It is not a bug!

Unless things have changed DaVinci resolve will have the same problem by defualt.

Does you rendered image look fine if you drop it back into the Premiere Pro timeline?

You video will look different if broadcast and played back on someone's TV. Is that a bug or is there a difference between YUV and RGB? Video frames that look awesome on your computer screen will look washed out when you print them on paper because the RGB will be converter to CMYK.

You can change a few setting in DaVinic Resolve or add a adjustment layer in Premiere Pro. All software will have color space issues. It is normal. It is not a bug.

https://youtu.be/K7EGNJop_HE
https://youtu.be/nN2XlWWd26Y
https://youtu.be/7kjZZNT5js4

Kizzume

Inspiring

It IS a bug. Again, this wasn't a problem with Premiere v12 and earlier, and it is NOT an issue in DaVinci Resolve, I've tested it multiple times--it's what made me almost swtich to DaVinci Resolve--the only thing that kept me from switching to Resolve is that their AAC encoding sucks and sounds like a 96kbps mp3, and it can only be adjusted to 192kbps in options instead of 320kbps like every other program can. I have to choose between gamma issues with Premiere or sound issues with Resolve.

In Premiere, doing the adjustment layer makes it look darker than the original. None of the awful workaround answers that people have been giving actually work right--the LUT makes everything darker than the original, and the adjustment layer gamma adjustment also makes everything darker than the original. I just want the output files to look the same as the original files like it did in v12 and earlier and like it does in DaVinci Resolve.

If Adobe didn't artificially block people from installing earlier versions, none of this would be a problem to begin with. Shame on me for upgrading my computer. V14 runs slow as molasses when editing as well (it's like editing on my old computer in v12), and people have complained about that, and the problems all started in v13--the panels not staying where one puts them, crashing issues, slow editing, and the gamma issues. It's why I never upgraded to v13 last year, I tried it for a while, and swtiched back to v12, but in 2020, Adobe took away people's choice, you can only go back one version number now.

Obviously something has changed between v12 and v13 when it comes to gamma. I want v12 behavior (as well as DaVinci Resolve behavior), not this new "adjust your monitor correctly and you won't notice the problem" behavior.

A

Andy 1968

Inspiring

Well, I'm rather embarrassed at this point, but it ends up that this problem I've been having is PURELY about bitmap images. The entire time I've been focused on my intro of my videos, assuming that the same problem existed on the rest of the footage, but it actually doesn't. When I import an older completed video that has that intro looking the way it's supposed to (from v12 and earlier), when I re-render it (or view it in Premiere without color managemenet), it looks fine. No gamma shift at all.

It's only when I try to render a bitmap image (or view it without color management) that it pumps up the gamma. So there's a problem, but it only affects imported bitmap images. Is there a reason for this, or is THIS the actual bug?

Thanks for your discussion and input on this.

I am glad you were able to do more advanced trouble shooting and find the actual problem. It might be a bitmap bug. That being said if you use an adjustment layer to compenstate you shouldn't need to use any luts. The gamma filter and proc amp filter should be enough to compensate for the gamma shift. As I stated there might be a bitmap bug in the newsest version. You can file a bug report.

Kizzume

Inspiring

You're totally right. In version 2018 (v12) and earlier, this was never a problem.

I made a thread about this problem, and I'm so annoyed with someone who basically keeps giving the argument "if you have your monitor properly calibrated to industry standards, you wouldn't notice the problem". I even gave examples of what happens, and the only advice I'm given besides that guy telling me that if I adjust my monitor so 8,8,8 looks the same as 0,0,0, I wouldn't notice the problem, is to use either an LUT or a gamma adjustment layer to cover up the problem.

A helpful thing to be able to see the image in the Premiere interface/monitor the way it will actually render as a finished product, is to go to Preferences, General, and uncheck "Display Color Management". Yeah, it doesn't look as good, but at least you'll know how bad it will look when it actually renders/exports as a finished video.

Attached are images showing what the images are supposed to look like, and the color values of each section, and what Adobe Premiere does to the same images in the render/export.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded