Jeff Sousa

My feedback

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Premiere Pro » Formats  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeff Sousa commented  · 

    We just need Premiere to be able to import DNxHR 444. When exporting from Premiere, we can use ProRes. The main reason to need to import DNxHR 444 is that is the best way to export in DaVinci Resolve as a "ProRes4444" equivalent when using Windows. So if you are color grading professionally on a PC and your client is using Premiere on a Mac (most common scenario), you want to be able to render them DNxHR 444 (to avoid chroma subsampling, for instance) and you want them to be able to see your color accurately in Premiere. It's what they paid for.

    An error occurred while saving the comment
    Jeff Sousa commented  · 

    Premiere is misinterpreting DNxHR 444 as "Full/Data" levels, which is wrong. Avid specifies all DNx codecs should be / are video levels. So DaVinci Resolve writes video levels into DNx clips, then Premiere misinterprets.

    DNxHR 444 files written by Resolve look correct in Resolve, Assimilate Scratch, Avid Media Composer, and Mistika Boutique. Only Premiere is wrong.

    This is a major bug, not something we should have to feature request. And the fact that the request is from 2018 and it's now 2020...it doesn't take 2 years to change how a clip is flagged.

    We also urgently need the ability to choose between video/data level interpretation manually on any clip.

    So if a new codec is developed in the future and Adobe also bungles the interpretation, we don't have to wait 2+ years for the fix.

    Jeff Sousa supported this idea  · 
  2. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeff Sousa commented  · 

    Dude...we need this. Not just for Lumetri, but Colorista and FilmConvert. We can figure out the mapping, just need After Effects talking to Tangent Mapper.

    Jeff Sousa supported this idea  · 
  3. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Jeff Sousa supported this idea  · 
  4. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Jeff Sousa supported this idea  · 
  5. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeff Sousa commented  · 

    We need this, stat. At least the interpretation part. Has this idea seriously been around for 2 years and has not been implemented? Being able to set video / levels is basic. As things stand in 2020:

    (A) Premiere misinterprets all incoming DNxHR 444 clips as being "Full," when in fact Avid specifies all DNx, including 444, should be video levels. This results in washed out files in Premiere and angry clients.

    (B) Premiere ignores metadata that DaVinci Resolve writes into the clip header explicitly saying that this clip contains Video Levels

    (C) Premiere provides no easy toggle in interpret settings to override its wrong behavior

    Jeff Sousa supported this idea  · 

Feedback and Knowledge Base