Copy link to clipboard
With Premiere Pro v 22, new features around color management for H.264 and HEVC have been introduced. This FAQ will show you how to fix clips that appear overexposed or oversaturated due to these new features. Caution: iPhone shoots HDR by default.
So why do HLG files look saturated/over-exposed in Pr v 22?
In the previous version of Premiere Pro (v 15.x), HLG media was treated as Rec.709 & the sequence created from that media also used Rec.709 color space.
In Premiere Pro v22, H264 and HEVC are color managed, and the HLG media is treated as Rec.2100. So a timeline created from HLG media in v 22 will automatically be assigned HLG color space.
However, in v 22 opening a project created in the previous version (which had HLG media on Rec.709 timeline) results in HLG to Rec.709 conversion. This causes the clips to look saturated/over-exposed in the newer version of Premiere Pro.
Note: This only happens with projects (HLG media + Rec.709 timeline) created in the previous version. Newer project files will have the appropriate color space assigned and will show the correct preview.
How to solve this issue in v 22?
You may manage the color space of the entire timeline made from HLG clips.
You may also color manage individual media files.
How to correct saturated/over-exposed previews during H.264/HEVC export?
If you have edited in an HLG timeline & would like to export in HLG, please ensure that you use the following export settings.
Please note that the Match Source presets use Rec. 709 color space & might result in an incorrect preview if used to export a sequence based on Rec. 2100 HLG color space.
For the full HDR broadcasters workflow, see this page in the Premiere Pro User Guide.
Hope this helps.
This hurts just reading.... I have a wedding I shot with three cameras that has no due date.... but I have over half of it completed editing on the old version. I'm not excited to open it up later this week.
let me know if you figure out a sketchy work around
Why would you change versions on that project? There is absolutetly no reason to!
You can keep working in 15.4 as long as you want. Any projects started in 15.4 (2021) should probably be finished in it.
You can install 2022 as a different install. Create new projects, and TEST working in it. Once you have it sorted out, then create new project files in it, use the MediaBrwoser to import the assets of old-version projects and see if they also can work in 2022. Or leave them and keep using 2021 for them.
Have you ever had a file that was created in 15.4.1 and then installed 22 and then the whole project was opened in 22 does not look like this if you would do that, you will come to the conclusion that the files that were opened in 22 are no longer in 15 can be opened
I don't need to go back to the past. I am working in the present and in the new version v.22.
But there is still no solution! Adobe when will the update finally come ???
There is an update addressing the issue coming very shortly. Sorry I can't answer any "when" questions. That said, I still would not recommend updating major projects that are in progress to new versions. Roll back and use a XML file to do that if you already did significant work in the new version. Good Luck.
Do NOT ever open files from one version in a 'higher' version. That is a user choice, with absolutely no need to do so!
Create a new project file and IMPORT the assets of the old project file into the new version project in the MediaBrowser panel.
The old version file is untouched and usable in the old version. The new version file can be tested to see if it works.
Copy link to clipboard
I'm just a mid level editor who likes to tell stories with video.
All this talk of course space and workarounds is WAY over my head.
For idiots like me, what's the best thing to do to solve this ******* stupid problem which has come out of nowhere?
Nothing at all waiting for an update, the only thing that is done when you contact adobe is that they tell you update your graphics card driver or see if there is an update error for 3 days I am writing with one of adobe, I also had an adobe employee accessed via remote on my pc what he said it is not possible to change projects that have already been opened in version 22 can no longer open in 15 that means a project started in 22 then always 22 or higher I'm so mad at adobe I have a document that has to be finished, they will hear from our producers
the person who did the update should contact me and would like to tell him something
you are the best you in the forum thank you thank you thank you why adobe doesn't say something like that!
Glad to help my friend ✌
Hi Mr/Ms Default!
Sorry for that. In my opinion, it's because it's a total hack that doesn't work in all cases and can break the sum total of all my work on a project? Just saying. That might be the case. Don't perform this kind of surgery on any working project, please use a copy/duplicate as a test.
For me, it's still a no go. XML is the way to go that is also sanctioned by engineering. So, that's the route I go.
The problem is if you open a project in 22 then you can no longer open it in 15.4 because then the file is ready
That's true... it does however prompt you to save new version as a different file name....so next time do that.
For now open the latest auto-save file on old version and hopefully it's sufficient.
Autosaves saved me so many times!
Never ever do that! That is always a user choice ... you can duplicate the file and open the dupe in the new version, or as often noted, the better choice: create a new file in the new version, use the MediaBrowser to import the contents of the old version project.
Either way, you still have the working original project file in whatever version it worked in. And a new version file to test in the new version.
As to the new color management options ... they have to bring color management choices to the app. For exactly this reason, that it would confuse some, they have resisted a long time after PrPro should have had user controls for color managment.
But with several different HDR forms out there now, they have to move forward. I've complained that spreading them around various places is inherently confusing, but ... they've done it this way as to the developers that's where users would 'think' to look for CM option.
I want a new CM panel.
Never simply "open" a project file in a newer version. That process can work but has far more likelihood of being a partial to full disaster than a different way of migrating.
Create new project files in the new PrPro version. From those project files, use the MediaBrowser to navigate to, select, and import the assets of those projects.
You have a clean proper project file of the new version, with all the assets of the old version.
And you still have the old version project file intact and usable.
Now ... test the project in the new version. If it works, great! If not, continue working that project in the old version.
Copy link to clipboard
You just saved my day and project. I was ready to throw my pc in the trashcan and pay back my costumor.
Mod note: Please do not use profanity, even if only implied. We have minors reading here.
This update watesed me one to struggle with the HLG color Problem......
Still cant get the excat color of the oruginal HLG videos....
Finally go back to the previos vesion to advoid this problem......
Copy link to clipboard
I appreciate this attempt to help, but my HLG footage is ruined when trying either of the suggestions.
If I manually set colorspace to Rec.709, the footage is blown out and oversaturated.
Whether I do it to the sequence or the video, the result is the same.
The closest I've gotten is applying SDR conform upon export, but it's still adjusting color values.
Please help... why did you guys make this so difficult for Sony HLG users??!!?!
So you have HLG footage from ... which Sony cam, and what settings in-cam?
What are you setting the clip color space to in the Project panel?
What sequence settings?
Is your monitor set to handle HDR and your OS also ?
Thank you for your help, and apologies for the lack of context. It just suprised me that my original workflow needs a revision upon updating Premiere...
Testing new HLG3 footage shot this morning, from Sony a7r3
Shot at 4K XAVC 30p 100M
Clip Color Space in the project panel is usually left as default, but today I'm trying intrepeting to Rec709 with no luck, colors aren't right. So either default color or Rec709.
Sequence settings is either derived from the video itself, matched, or using a RED 4k Timeline, or sometimes a custom timeline for social media cropped to 1920 x 1080 vertical. Either way, old workflows don't seem to work with HLG anymore.
And my monitor.. no clue.. I never used to have any issue. I use a 2014 Retina 5k iMac.
I'm a bit of a novice when it comes to the technical side of video, codecs, compression, output, etc. I've had zero issue in Premiere from 2012-today, I just want to learn and keep up with the updates. Especially because I primarily use HLG on my Sonys.
If I apply SDR Conform on export, it kind of helps, but it's still adjusting colors more than I'm comfortable with.
Thank you so much.
Copy link to clipboard
Why on earth would you make this change to PP? Now, I have to make these edits to EVERY freakin' clip???!!! Please remove this feature ASAP! I have spent HOURS trying to figure out how to fix this issue until I came across this blog. Please, please, please change it back!