Bug 504515 - Software screen tints affect screen recordings
Summary: Software screen tints affect screen recordings
Status: RESOLVED DUPLICATE of bug 504512
Alias: None
Product: kwin
Classification: Plasma
Component: screencasting (other bugs)
Version First Reported In: 6.3.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-19 10:35 UTC by Tech-Tac
Modified: 2025-05-19 17:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Fullscreen recording brightness and night light effects (1.74 MB, video/mp4)
2025-05-19 10:35 UTC, Tech-Tac
Details
How brightness affects region recordings (458.60 KB, video/mp4)
2025-05-19 10:36 UTC, Tech-Tac
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tech-Tac 2025-05-19 10:35:20 UTC
Created attachment 181503 [details]
Fullscreen recording brightness and night light effects

SUMMARY
Night light and software brightness control subtly/indirectly affect screen recordings as follows:

Screen brightness completely darkens the video when recording fullscreen only (https://bugs.kde.org/show_bug.cgi?id=504512), but when recording a region it appears at normal brightness but with the colors seemingly compressed.

Night light doesn't directly appear in any kind of recording, but has the same color compression effect as above.

STEPS TO REPRODUCE
1. Start recording
2. Turn down the screen brightness (software mode)
3. Change night light values

OBSERVED RESULT
Color changes in recording, with brightness affecting it when full-screen

EXPECTED RESULT
Recording is pure as if effects were off

SOFTWARE/OS VERSIONS
Linux: Arch
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
Comment 1 Tech-Tac 2025-05-19 10:36:45 UTC
Created attachment 181504 [details]
How brightness affects region recordings
Comment 2 Nate Graham 2025-05-19 17:55:37 UTC

*** This bug has been marked as a duplicate of bug 504512 ***