Re: [Avid-L2] Quicklimes with wrong levels flags.

The 'gama' atom is 'old'

But it 'can' be there. If the Transfer Function is set to 2 (unspecified), it will be used if present.

(Custom output Gamma 2.4 from Resolve will do this.)

But this will only show on a ColorSync display, it has noting to do with the file, just how to display it. 

If you read a scope, is it connected to a ColorSync controlled output?

Bouke / edit 'B

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/

On 26 Mar 2023, at 03:34, John Moore <bigfish@pacbell.net> wrote:

So for a test I took a 23.976 sequence one second of smpte bars and exported same as source which is DNX 175X one with legal checked and once with Scale to Full Range checked.  Then I did a ProResHQ export using a custom export which goes through the QT engine.  I'm on MC 2018.12.15.  Here are screen grabs.  I guess I'm not sure this app displays the metadata flag that tells how QT should interpret the video essence.  I guess Full Range or Legal doesn't change the color matrix or primaries.  I'm in an area where I know how to read a scope but don't know exactly what metadata types of information define full range vs. legal video essence is this the colr atom and or the gama atom?  Or is it another atom?  Also there is mention on Lift Gamma Gain about tagging files 1-1-1.  I'm not versed in this aspect of file metadata.  Here is what I read:

Sebastian Bodirsky said: ↑
I wonder if there is a downside to this metadata specification, or why else it is not common practice by all NLEs. But probably there is already a thread about this somewhere...
That metadata is supported for display by many post apps, but only editable in a few of them, hence the need for a metadata editing app like this.

Resolve allows setting that metadata on export, while NLEs like Premiere and FCPX default to tagging all SDR exports as 1-1-1. FCPX is at least internally color managed around 1-1-1, while Premiere Pro is just a hopeless mess since it doesn't color manage for 1-1-1 yet it tags outputs that way.
 
Jamie LeJeune, Apr 19, 2021
#9

 
Erik Lindahl

1,128

322

0
Jamie LeJeune said: ↑
That metadata is supported for display by many post apps, but only editable in a few of them, hence the need for a metadata editing app like this.

Resolve allows setting that metadata on export, while NLEs like Premiere and FCPX default to tagging all SDR exports as 1-1-1. FCPX is at least internally color managed around 1-1-1, while Premiere Pro is just a hopeless mess since it doesn't color manage for 1-1-1 yet it tags outputs that way.
Premiere Pro is even worse than this.

- Material will always export as 1-1-1 in SDR
- Material with other tags than 1-1-1 will likely be converted to 1-1-1
- You can't affect how Premiere reads footage (i.e. force all SDR to be read as Rec 709 / Gamma 2.4).

So if you render files externally tagged with Rec 709 / Gamma 2.2, Rec 709 / Gamma 2.4 and Rec 709 / Gamma 2.6 they will all render differently with-in Premiere and be converted to a Rec 709 / Rec 709 (1-1-1) file. Files tagged with Rec 709 / Rec 709 are rendered as Rec 709 / Gamma 2.4.

The above behaviour seems unique to Premiere and AME thought. After Effects in a color managed workflow seems to assume Rec 709 / Gamma 2.4 and render out 1-1-1. It makes sense the color managed app disregards these tags…

Oh, I think since some versions back AVID respects these tags also.
 
Erik Lindahl, Apr 19, 2021
#10



Here are screen shots of my bars exports:

<dummyfile.0.part>
<dummyfile.1.part>