Repository navigation
Screencopy frames carry no image description — clients cannot tell PQ/HDR frame content from SDR #16954
Replies: 2 comments
|
Fair point — #16882 is after the same missing piece. One data point that differs: on my setup (7900 XT, cm = hdredid, stock 0.57.2) fullscreen captures aren't clipped, they carry real PQ values (brightest patch reads 0.9414), just with no description attached — while region captures of the same content come back as SDR values (≈0.52). I'll put the measurements in #16882 and close this one. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Running Hyprland 0.57.2 (tag v0.57.2, commit 11cbc6c, built from the v0.57.2 branch).
On an HDR output, the frames delivered through screencopy are PQ-encoded — I measured this, more below — but neither zwlr_screencopy_manager_v1 nor ext-image-copy-capture-v1 tells the client the frame's image description. So a client like grim has no way to know what the buffer values mean, and just writes an untagged 8-bit PNG. Viewers then read it as sRGB and HDR screenshots come out wrong: in Loupe, an untagged capture tops out at the SDR-white code value 0.622, while the same content on screen reaches 0.9414.
Setup: DP-1 at 3840×2160, bitdepth = 10, cm = "hdredid", panel peak 1400 nits, SDR reference 300 nits. RX 7900 XT (amdgpu), kernel 7.3.3-1-cachyos.
To reproduce:
What I get:
What I'd expect: capture clients can get the image description of the frames they receive (through the protocol, or via a documented, reliable association with wp_color_management_output_v1) so they can tag their output files properly, and region/fullscreen captures of the same content agree in values.
Workaround I'm using locally: the client cross-checks wp_color_manager_v1 — query each output's image description, and if the capture targets are HDR, keep 10-bit precision and write a cICP chunk. It works, but it's guesswork: nothing guarantees the delivered frame actually used the description the client fetched.
All measurements are from stock 0.57.2, before any local patching. I've since patched both Hyprland and grim locally to work around this; I can share the measurement scripts (raw-sample PNG reader and comparisons) if useful. I searched issues and discussions for "screencopy", "cICP" and "image description" before posting and didn't find the same report.
All reactions