Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows/DirectX: fix overexposed HDR stream with pixel shader #689

Closed
awawa-dev opened this issue Dec 14, 2023 · 0 comments · Fixed by #691
Closed

Windows/DirectX: fix overexposed HDR stream with pixel shader #689

awawa-dev opened this issue Dec 14, 2023 · 0 comments · Fixed by #691
Assignees

Comments

@awawa-dev
Copy link
Owner

awawa-dev commented Dec 14, 2023

Some time ago, one of the Windows updates introduced a change in the image capture result when the OS HDR feature is activated. The result is an overexposed captured image with too much brightness. It is not related to internal HyperHDR tone mapping, the screen comes in as it is. But we can do it better: Use pixel shaders to correct this problem directly on the GPU using its acceleration.

Screenshots illustrating the described problem reported by the users (#515).
Windows desktop with system HDR OFF
chrome_VSAb4z5J0T (Custom)

Windows desktop with system HDR ON
chrome_cNfxEsGKGX (Custom)

The inspiration for the package of new changes for HyperHDR (#688 #690) is the new Intel N100 SBC platform and the extensive capabilities of Windows 10/11, which enable hardware-accelerated capture of even the HDR signal. You should still remember about the capturing limitations related to HDCP, e.g. when Netflix app is used, but since the video player requires its use and the user has consciously agreed to its terms then it is not our concern. For HDCP workaround you still need a proper HDMI splitter and USB grabber.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant