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

Can we keep this discussion 'clean'?

From what we've learned, levels as hard coded into files are one thing.

Then there is metadata on how to interpret the values.

For 'us', we want to access the 'raw' data, as it is. (Sometimes, other times we do not have time to get bothered with that, we want it 'as intended'.)

What we want for sure is an answer to:

What the fuck am I looking at????

(Pardon my French…)

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 21 Mar 2023, at 19:11, Gowanus Canal <gowanuscanalstinks@gmail.com> wrote:

What has been discussed in the Resolve forum is that ProRes 422 and HQ by default are video levels. And some applications assumes it is video levels (Adobe Premiere). Setting it to data levels can cause issues. 

DQS

On Mar 21, 2023, at 1:49 PM, John Moore <bigfish@pacbell.net> wrote:

One very basic question I would like to know is what the expected level is for a ProResHQ file?  As I mentioned earlier in this thread I recall discussions on the L2 and IIRC the consensus was a ProResHQ file should be assumed to be legal level but of course you should always double check.  Earlier in this thread Marianna mentioned that form the Avid engineer Avid assumes both ProResHQ and ProRes 444 to be full range.  Is there an actual spec set by Smpte, EBU or the International Committee that F's with John Moore's head on a regular basis?