This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 51%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJD%3C/text%3E%3C/svg%3E)
DXGI 1.5 adds the IDXGISwapChain4 interface which includes a function to set HDR metadata and supports HDR10 static metadata with a structure. The enumerated type specifying the type of HDR metadata includes an enumeration for HDR10 Plus, DXGI_HDR_METADATA_TYPE_HDR10PLUS, but is not documented. Is this currently supported or planned to be supported and does or will it take the current HDR10 Plus VSVDB syntax as specified in official HDR10 Plus documentation?
HRESULT SetHDRMetaData(
DXGI_HDR_METADATA_TYPE Type,
UINT Size,
void *pMetaData
);
enumeration: DXGI_HDR_METADATA_TYPE_HDR10PLUS
Thank you,
Jim DiNunzio
Samsung Research America
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
Perhaps this is currently supported. I have seen the DXGI_HDR_METADATA_TYPE_HDR10PLUS listed in the document except there is no explanation.
If it is supported it is unclear. Should the void pointer point directly to the VSVDB structure? Yes, I saw the enum appear in the docs, but as you said there is no explanation. I consider that "not documented" as I stated above.
Jim
I have seen the DXGI_HDR_METADATA_HDR10PLUS structure in the code dxgi1_5.h and Perhaps the void pointer point directly to the DXGI_HDR_METADATA_HDR10PLUSstructure.
Hi Xiaopo,
None of the sources defining DXGI_HDR_METADATA_HDR10PLUS structure found on google are from Microsoft. These random sources define the structure with a byte array of 72 bytes. Why should I believe them?I would like an official Microsoft answer. Furthermore the Vendor Specific Info Frame structure (VSIF) I have for HDR10Plus, which I have been using successfully with a 3rd party graphics card API, is 27 bytes. If Microsoft's version is indeed 72 bytes, then I need to know the layout of the 72 bytes.
Jim
Perhaps you should try 27 bytes version in Windows DXGI_HDR_METADATA_HDR10PLUS structure. It is’t uncommon to reserve some bytes.
Windows currently do not support HDR10+ after consulting.