Prores 4444 (from PC)

Do you have questions about Desktop Video, Converters, Routers and Monitoring?
  • Author
  • Message
Offline

marcelo.brandt

  • Posts: 6
  • Joined: Wed Dec 07, 2022 1:47 pm
  • Real Name: Marcelo Brandt

Prores 4444 (from PC)

PostMon Jan 23, 2023 8:57 pm

Hey guys,

So, I have this film I need to deliver in Prores 4444 XQ. Its HDR (1000nits P3-D65 ST2084) and I'm working on Davinci Resolve. I exported a DNxHR 444 12-bit and then converted it to Prores 4444 using Adobe Media Encoder. When I import both (DNxHR and Prores) back to Resolve, the Prores version looks a bit brighter. If I import them to Premiere, however, they look identical. What is going on? Can I 'trust' Premiere? Thanks in advance!
Offline

marcelo.brandt

  • Posts: 6
  • Joined: Wed Dec 07, 2022 1:47 pm
  • Real Name: Marcelo Brandt

Re: Prores 4444 (from PC)

PostThu Jan 26, 2023 4:06 pm

Already solved! It was a matter of full/video range
Offline

Andrew Kolakowski

  • Posts: 9209
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Prores 4444 (from PC)

PostSat Jan 28, 2023 9:24 pm

Premiere is bit crap with limited vs. full range setting- it has hard coded (sometime bad) rules for different codecs. You can't easily overwrite range on import either which is annoying limitation. There may be changes coming soon.
Older Premiere was reading ProRes444/XQ as full range which is not good default behaviour.
If I'm correct 2023 version changed it, so it's better now.
For DNxHR is still expects full range (instead of reading DNxHR private range flag), but Resolve default DNxHR 444 export is limited, so this is how things go wrong between these 2 apps.
Resolve reads DNxHR headers correctly, so it always imports files properly (unless headers are not set/set wrongly).
Keep all ProRes files always limited range unless there is some special case, but then clearly state (file name etc.) that file is full range.

Return to Post Production

Who is online

Users browsing this forum: Bing [Bot], mzperx and 38 guests