Skip to content

Conversation

@matte-schwartz
Copy link

The HDR10 infoframe creation was nested inside the EDID parsing block, so it only ran when HDR info came from the EDID. If a PQ EOTF was set via lua config, bHasKnownHDRInfo would be true, the EDID block would be skipped, and pDefaultMetadataBlob would never be created.

Move the infoframe creation outside the EDID parsing block and gate it on HDR10 so the metadata is created whenever PQ output is configured, regardless of whether the HDR info came from lua config or EDID.

We still use the EDID metadata when undefined in the lua config, or when there is no config for a PQ-compatible display.

The HDR10 infoframe creation was nested inside the EDID parsing block,
so it only ran when HDR info came from the EDID. If a PQ EOTF was set
via lua config, bHasKnownHDRInfo would be true, the EDID block would
be skipped, and pDefaultMetadataBlob would never be created.

Move the infoframe creation outside the EDID parsing block and gate it
on HDR10 so the metadata is created whenever PQ output is configured,
regardless of whether the HDR info came from lua config or EDID.

We still use the EDID metadata when undefined in the lua config, or when
there is no config for a PQ-compatible display.
@misyltoad misyltoad merged commit 9416ca9 into ValveSoftware:master Dec 6, 2025
1 check failed
@matte-schwartz matte-schwartz deleted the pq-hdr-lua branch December 6, 2025 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants