Premiere Pro 22.1.1 and overexposed iPhone 13 footage

[Mineiran]

I rolled it back this version I already have to use a older one just for edited Iphone 13 footage because this latest one over exposure HDR videos. 

I mean we pay for this, and this will stop next year. I had issues with this update and I will start learning another video editing tool asap to get myself free of a payed bug software. 

[Michael Grenadier]

never update immediately and if you do, make sure you don't replace the earlier version... and test the new version before you start working with it...   This is one of the strong points of Premiere...  Resolve does not allow you maintain earlier versions on your system.   I've been working with NLE's for over 30 years and there have always been issues with updates.  And these problems don't happen to everyone.  We have 3 posts to this thread and none of them include their system specs...  Updates often make greater demands on your hardware...   Not saying there aren't bugs, but really hard to tell what's going on without sufficient information.

[Mineiran]

Why this update broke mu software? Before the update this was not happening. I already have to use an old version because the newest can't handle Iphone 13 HDR wihtou overexposure the videos? I am really considering and cancel my subscripton. I pay to have a tool to help me instead of break my workflow in everysingle update. Please help!

[Michael Grenadier]

first of all, iphone footage has a variable frame rate which can cause intermittent, unpredictable issues.  Always smartest to convert to a constant frame rate before importing into Premiere.    Here's how to diagnose and fix the issue

use mediainfo to determine whether your source is variable or constant frame rate
https://mediaarea.net/en/MediaInfo/Download
if it's variable use handbrake to convert to constant frame rate setting the quality slider in the video panel to maximum
https://handbrake.fr
and here's a tutorial on how to use handbrake
https://www.youtube.com/watch?time_continue=34&v=xlvxgVREX-Y

And do some searching here about how to handle HDR footage.  

And gotta say that upgrading your iphone to was certainly part of the issue...

[Mineiran]

I am sorry, this don't work. This is a scripedt CRT C + CRT V answer since it doesn't fix the issue. 
Variable frame hate doesn't affect HDR Graphics 709/203 in our sequence. That is why I have to get the Premiere Pro 15.4.1 installed yet, because the newest one simple overexposure the footage.

As a customer that pay for a software I would like to use a single version of it. Also I don't like when updates mess it up our settings and workspaces breaking our workflow and having us stop to figure out what got changed it without letting us know. 

Test the version before release, found a bug? Postpone it. It is simple and I don't understand why this doesn't seems to be done.

[Michael Grenadier]

just trying to help since you're working with iphone footage...  We see all sorts of problems that can be traced back to vfr footage...  and yes I copied and pasted cause I've had to suggest that people check this issue so many times...  And it's solved many people's problems.  

And did you do any research on how to handle HDR footage in premiere as I suggested?   And this is what I found with a quick google (maybe took 5 seconds).

https://postperspective.com/working-in-hdr-editing-and-finishing-in-adobe-premiere/

Have you tried the suggested workflow...?  And I'm sure there are many other links to how to work with HDR footage...  

[R Neil Haugen]

Yes, the new version handles the footage fine once you understand the Color Management changes that were part of Pr2022. And unfortunately, not very well presented to the users. The FAQ here covers what changed, why, and how to work within the new options and behaviors.

Neil

FAQ: Premiere Pro 2022 Color Management for Log/RAW Media

[R Neil Haugen]

That isn't at all a "bug". They changed the color management options and default behaviors in the 2022 release.

And unfortunately, there wasn't great info about what that meant provided for most users. I totally understand your frustration. I wrote a FAQ for this forum on the issue ... what changed, why, and how to work with the new setup. Including what's broken with the current behaviors.

FAQ: Premiere Pro 2022 Color Management for Log/RAW Media

Essentially, Premiere is simply treating your phone's HLG clips as what they are, an HDR clip. And not auto-transforming them to a Rec.709 SDR timeline as it used to. So ... you simply select them in groups in the bin, right-click/Modify/Interpret Footage, and tell Pr what you want for CM at the bottom ... probably, using the Override option setting it to Rec.709.

As realistically, the vast majority of work any of us does is still Rec.709 "SDR" for some time to come.

The reason for the change is because they have to give us more CM options. HDR is coming at us, and within a year or two at the most, many 'routine' projects will assume working in HDR.

And ... any app you go to, you will need to learn that app's CM options, because most other NLE type apps already had more CM options than Premiere did. So ... learn a completely different editing process simply because you don't know how to work with the new CM options in Premiere ...

... only to have to learn the CM options in the other app to do any editing to begin with ...

Somehow, that doesn't make a lot of sense.

Being ticked off as you weren't given an easy and obvious bit of information about massive changes in the app's behavior ... that makes total sense.

Neil

[Eko Wardoyo]

thanks @R Neil Haugen , i learn many things about how adobe premiere works from your reply

[R Neil Haugen]

Most welcome.

What the options are that we have, I think we need. We actually will need more.

How some defaults are behaving ... that's not so good.

And again, I really think we users need a unified CM panel ... one panel to rule them all!   hahahaha ...

Color Management Panel UserVoice Request

One place where the app's default behaviors can be set and checked and changed, and where overrides can be handled also. Rather than running around the place trying to find everything, as it takes now.

Neil

[Eko Wardoyo]

Voted, there should be a 'simple single panel' for all of there things

[R Neil Haugen]

Thanks!

[Mineiran]

Ok, Now we some proper answers. Tha last one with a video was amazing. Thanks for your time to doing that Karl, really thank you.

I was able to follow that and I already changed the color space by interpreting the footage. Therefore I still see some color difference in my monitor between the current version and the 15.4.1 and 22.1.1 where 15.4.1 is more vivid and has more saturation than the 22.1.1 which is a bit more brighter close to washed out, due to new color space for HDR. My question is which one is correct for HDR?

Also this is a considerable change in a software, since I am not a professional, Adobe was this advertised? Regular people with basic skills like me will know about it?

Thanks

[R Neil Haugen]

Which OS are you on?

And ... whether working in HDR or not, you need to match the sequence color management to the clips. Such as if you have an HLG clip, and expect an HLG export, you would use an HLG sequence. And for non-HLG clips on an HLG sequence, use the Override option to HLG also.

Note: if 1) you have an HDR clip, 2) you have an HDR timeline, and 3) your monitor can show HDR from Premiere, the image should be if anything more "color-ful" than when shown as a standard dynamic range (SDR) clip on a Rec.709 timeline.

So to figure out your situation, we may need a more complete listing of what the color space of the clip is, what the sequence CM is, and what your monitor is, and how it can handle HDR.

Also ... here's a FAQ that goes over 1) the changes to CM options and default behaviors, 2) how to work in the new setup using images demonstrating this, and 3) some problematic issues.

FAQ:PremierePro 2022 Color Managment for Log/RAW Media

And another on monitor setup for HDR with Pr2022.

How to Set Monitors for HDR work in Premiere Pro 2022?

Neil