DNxHD legal range vs. full range

Forum|Forum|7 years ago
May 27, 2018
3 replies
3590 views

I export video footage from Resolve to MOV DNxHD full range. When I import this file in to Premiere 2018 (maybe 2017 but I need to work with 2018) the blacks are crunched and without details. Premiere probable expects legal range but I need to export it from Resolve in full range because I need to import it also to After Effects but there it would be incorrect because After Effects expects full range.... this is absolutly insane......... It would be grate if I would be able to definy whether imported footage in premiere is in full or legal range ..... how is it even possible that one company cannot make to work its products the same way................

This topic has been closed for replies.

Correct answer R Neil Haugen

Colorists I know say when working with PrPro and AfterEffects with Resolve, leave Resolve's media cokor options set to auto. Do NOT set to either data or video levels.

They will always come into Resolve properly, and into PrPro.

In AfterEffects set the cir management so they appear correctly

Neil

R Neil HaugenCorrect answer

Legend

Colorists I know say when working with PrPro and AfterEffects with Resolve, leave Resolve's media cokor options set to auto. Do NOT set to either data or video levels.

They will always come into Resolve properly, and into PrPro.

In AfterEffects set the cir management so they appear correctly

Neil

Everyone's mileage always varies ...

E

Edouard Jeanjean

Participant

Hi,

For years, and even on DaVinci Resolve 18 and Adobe Premiere Pro 2023, we have the problem of importing DNxHD (and DNxHR) ".MOV" and ".MXF" from the video/legal and full level interpretation.

Wouldn't it be possible to implement a feature to interpret the media between legal and full? (As it may exist in DaVinci Resolve)

Best

E

excited_Genie16B8

Legend

MOV has long been problematic on this front. Use MXF files instead.