Skip to main content
Known Participant
November 26, 2021
Question

HDR iPhone footage - After Effects dynamic link only using Color Space: Rec. 709

  • November 26, 2021
  • 3 replies
  • 3322 views

I'm using Premiere Pro v22.0.0 and After Effects v22.0.1 all my HDR footage from my iPhone 12 Pro.

 

The Premiere Pro timeline is set for Rec 2100 HLG and exports as 10-bit fine using H.265 (software encoding only) for smaller file size.

 

However, when creating a dynamic link with the iPhone footage to After Effects it uses Rec. 709, I have tried interpreting the footage within After Effects:

 

Project Panel > Interpret Footage > Color Space Override > Assign Profile: Rec.2100 HLG W203

 

But when I right-click the linked footage in Premiere Pro and select Properties, it still only shows Color Space: Rec. 709. 

 

This means the exported video changes colour/brightness when reaching the linked footage section.

 

Is there any way to get the linked footage to match the rest of the footage? Thanks.

This topic has been closed for replies.

3 replies

Participant
December 10, 2024

I'm kinda (very) late at this, but i just found the perfect solution: go to the footage in your project explorer in after effects right click on the Rec 2100 footage > interpret > main > color tab > override media color space > rec2100 HLG 203 > ok, then go to file > project settings > color > working color space > rec 709 gamma 2.4.

BOOM!

Participant
June 9, 2024

Hey, I've had the same problem. Did you find a fix?

R Neil Haugen
Legend
November 26, 2021

I would go to the AfterEffects forum in the links on this page and ask. I think I know what you should try, but that's still a bit of a guess.

 

Over "there" you'll get a very quick and accurate answer. And if you do go over there, how about posting back the answer you get to here?

 

Neil

Everyone's mileage always varies ...
PG73Author
Known Participant
November 29, 2021

Thanks Neil, I posted in the After Effects forum as suggested but have not had a response yet. Perhaps it's not something anyone has an answer to, rather Adobe need to fix the issue. 

Ann Bens
Community Expert
Community Expert
June 9, 2024