Exporting HDR10 P3-D65 does not make color primaries P3 in metadata

Teagan wrote on 8/22/2021, 10:03 AM

Hi, just got Vegas Pro 18/19 and I'm having a problem trying to export V-Log V-Gamut footage as HDR10 but P3-D65 limited and the metadata is incorrect for color primaries. I've tried setting the view transform to match P3-D65 ST2084 1000 nits (ACES) and also the default Rec. 2020 ST2084 1000 nits (ACES) and both give my final video rec 2020 color mastering primaries according to media info.

However, the color spaces seem to be working as intended, as the davinci resolve CIE chromaticity scope seems to tell me the file is limited to P3-D65 as compared to the same file rendered in rec 2020. Is this just a problem of the metadata not being created properly? Where it says "mastering color primaries" in media info it should say "Display P3", right? Most of my 4k blu rays' media info say this.

My source file is V-Log V-Gamut.

Here's the output render settings according to P3-D65 ST2084 1000 nits (ACES) with the P3-D65 ST2084 1000 nits (ACES) view transform. I have also tried the default rec 2020 1000 nits view transform. Same result.

Output file media info for video:

Video
ID                          : 2
Format                      : HEVC
Format/Info                 : High Efficiency Video Coding
Format profile              : Main 10@L5@Main
HDR format                  : SMPTE ST 2086, HDR10 compatible
Codec ID                    : hvc1
Codec ID/Info               : High Efficiency Video Coding
Duration                    : 2 s 211 ms
Bit rate                    : 21.6 Mb/s
Width                       : 3 840 pixels
Height                      : 2 160 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 23.976 (24000/1001) FPS
Color space                 : YUV
Chroma subsampling          : 4:2:0
Bit depth                   : 10 bits
Bits/(Pixel*Frame)          : 0.109
Stream size                 : 5.70 MiB (99%)
Language                    : English
Encoded date                : UTC 2021-08-22 14:17:26
Tagged date                 : UTC 2021-08-22 14:17:26
Color range                 : Limited
Color primaries             : BT.2020
Transfer characteristics    : PQ
Matrix coefficients         : BT.2020 non-constant
Mastering display color pri : BT.2020  
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Codec configuration box     : hvcC

 

All below scopes are from the same frame exported differently in vegas pro 18/19

File exported in P3-D65 ST2084 1000 nits (ACES) davinci CIE scope (project set to P3-D65 1000 nits timeline)

File exported in Rec. 2020 ST2084 1000 nits (ACES) davinci CIE scope (project set to rec 2020 1000 nits timeline)

To make sure the first scope is not incorrect I have incorrectly set this project to rec 2020 1000 nits for timeline color space for the following P3D65 clip (first one):

As you can see it has stretched it out incorrectly, so I believe it is indeed P3D65 limited.

For more background info on why I think this is a problem, here's the media info from a 4k blu ray mastered in P3:

Video
ID                          : 1
ID in the original source m : 4113 (0x1011)
Format                      : HEVC
Format/Info                 : High Efficiency Video Coding
Format profile              : Main 10@L5.1@High
HDR format                  : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible
Codec ID                    : V_MPEGH/ISO/HEVC
Duration                    : 1 min 5 s
Bit rate                    : 62.4 Mb/s
Width                       : 3 840 pixels
Height                      : 2 160 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 23.976 (24000/1001) FPS
Color space                 : YUV
Chroma subsampling          : 4:2:0 (Type 2)
Bit depth                   : 10 bits
Bits/(Pixel*Frame)          : 0.314
Stream size                 : 491 MiB (93%)
Language                    : English
Default                     : No
Forced                      : No
Color range                 : Limited
Color primaries             : BT.2020
Transfer characteristics    : PQ
Matrix coefficients         : BT.2020 non-constant
Mastering display color pri : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Original source medium      : Blu-ray

 

So to sum this up, is there a way to make my color mastering primaries Display P3 in the metadata of my files that are exported correctly in P3-D65 1000 nits in HDR10?

Comments

Yelandkeil wrote on 8/23/2021, 3:48 AM

Again and again:

P3 is NOT among the color primaries (Rec.709/2020/2100 are!)

P3 is a hardware color specification, though you can say it's a "color space", thus, in your "more background info", it is called:

Mastering Display color Primaries!

So, the simplest way to check whether your output does match your display hardware - now you have VP18/19 - just render the same timeline to 1-HDR10, 2-HLG, 3-P3D65HDR and compare them on the same timeline.

For your info:

an HDR10-Project in VP18/19 has nothing to do with DavinciResolve

an VP-HDR10-Project can use every kind source material

an VP-HDR10-Project can use every kind display equipment

 

If your desired output, say P3D65-HDR10-Stream, is correctly rendered and you reconstruct it in a UHD-Bluray-Disc, the needed "Mastering Display color Primaries" must be added by the construction itself - I just imagine, could be wrong.

For my thoughts: VP could be also lack of info details in the HDR10 area. More over, importing Rec709 source material into HDR10 project is catastrophic. Though I find my way to treat this problem but the direct color space allocation (too much expose and oversaturation) indicates that VP-engineers whether didn't even try out it or they just haven't used HDR-Monitor to test it.

Last changed by Yelandkeil on 8/23/2021, 4:23 AM, changed a total of 1 times.

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

Teagan wrote on 9/24/2021, 6:07 AM

I have managed to make the Display P3 show up in the metadata by selecting the "target display" option in the render settings (customize template > system tab while in hdr10 mode), to "P3, 1000 nits, D65, ST 2084, Full", for anyone else wondering about this.

This shows "Mastering display color pri : Display P3" in media info.

This is in Vegas pro 19.