This histogram of camera or premier? I've don't the same check (but in Cine-D) but FCPX seems to map the levels correctly by default (as each different mapping shows colourbars mapped differently)

(So by default FCPX crops the range to the correct values) in Premier there is a setting for range iirc.

The colour bars should always be same values regardless of luminance mode selected.

Different luminance modes should change the colour bars for every picture style. If rec 709 is crushed, can you correct it in premier? Or is there information lost? (ie: are blacks / shadows really noisy - more than usual?)

Premiere isn't wrong. It's decoding the levels according to the full range flag set in the H.264 stream, which depends on the luminance level setting in the camera. The inconsistency is due to the fact that the test pattern is only defined for video levels, because that's how the test pattern is specified in the SMPTE standard. Effectively, the test pattern is wrong when the camera is set to 0-255 because the camera writes a video stream with a flag that doesn't match the encoding.

Just forget the test pattern. It doesn't matter unless you understand exactly what the camera is doing to generate it, how your video application decodes video, and how the test pattern should be interpreted.

If you record an actual video image in the camera, you'll see that everything works right in Premiere: you get the same image with the same levels after decoding, regardless of whether you select 16-235 or 0-255 in the camera. Well, almost everything works right. Don't choose 0-255 when you record to MP4, because Premiere uses the incorrect BT.601 YCbCr to RGB decoding matrix instead of the BT.709 matrix. Stick to 16-235 or 16-255 and everything will be fine.

thanks balazer for the info...like you said i did a test with real life footage and in 10 bit 0-1023 luminance and photo 6k blacks get crashed and!! So this is my conclusion: 8 bit 0-255 8 bit 16-235 10bit 64-960 they all look the same in timeline

10bit 0-1023 and photo 6k they look more contrasty with crashed blacks Maybe they shouldn't be flagged as hd rec 709??

Oh yeah, Premiere reads the full range flag in 8-bit files, but not in 10-bit files.

Call it a bug or a limitation. The truth is that the flag is not a required part of any standard. Most video apps don't read the flag at all. Stick to the standard video levels (16-235 in 8 bits and 64-940 in 10 bits) and everything works fine. When you use non-standard levels you will find inconsistent support in video apps.

Balazer...many cameras nowdays shoot full range and they are interpretated well in premiere...this is an issue from panasinic that flagged this files hd rec709...the 8bit 0-255 has no flag and it works fine in premiere...

If you look at the clip in AE you'll see that 8bit 0/255 hasn't any embedded profile while the 10bit 0/1023 and photo 6k (both full range like 0/255) have an embedded profile(flag) hd rec 709 like the 16/235 or 0/960...

@balazer remember that 6k HVEC is also 10 bit, just not 422, (420).

I think that NLE's are going to have to get with program soon, as 8k is just around the corner, and CPU's are not getting that much faster.

Don't worry, it will be "new revolutionary" feature!

True, but 8k will not work without GPU acceleration, even with best CPUs. (As CPUs are now all multicore- they are not getting faster) so I am guessing there will be "super new amazing feature" very soon.

True, but 8k will not work without GPU acceleration, even with best CPUs. (As CPUs are now all multicore- they are not getting faster) so I am guessing there will be "super new amazing feature" very soon.

Only hardware GPU decoders will work, all this general GPU acceleration does not work good.

In reality we have strange situation.

During editing you have decoding and simple effects / transitions / titles, if done right they do not require any hefty hardware. Even with raw realtime debayer, color correction, adjustments and playback can be done on 1060.

Yet we have BM proposing 1080Ti (1070 at least) and guys doing measurements using 20 heavy blur nodes and such.

4k is only barely starting to be used for delivery and we are still a long way from full 4k acceptance in acquisition, simply because nobody really cares. Any more than 4k is a wank-fest. 8k will be a giant bottleneck in post production, and not because of technical decoding issues.

4K just show regressive nature of capitalist productions. As profit and sales are the only goals.

Any more than 4k is a wank-fest. 8k will be a giant bottleneck in post production, and not because of technical decoding issues.

I do not see any issue with 8K production. Capture 8K 420 video, frame it as you wish and export 4K. With small proper editors adjustment it can be fully realtime for H.264 and HEVC already.

@balazer,i'm abroad right now...i"ll test it as soon as is possible...