[krita] [Bug 424551] New: Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Bug ID: 424551 Summary: Gamma error in picture scaling Product: krita Version: 4.3.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: lukasfran...@gmail.com Target Milestone: --- Created attachment 130324 --> https://bugs.kde.org/attachment.cgi?id=130324&action=edit Specially crafted image to demonstrate gamma error SUMMARY Resizing images produces a gamma error. This can clearly be demonstrated by resizing a specially crafted image. It affects all images and worsens the image quality by making them "darker". A more in depth explanation and how to fix this problem can be found on the website http://www.ericbrasseur.org/gamma.html?i=1 STEPS TO REPRODUCE 1. Download "gamma_dalai_lama_gray.jpg" from the attachments 2. Open gamma_dalai_lama_gray.jpg with Krita 3. Proportionally resize the image by doing: 3.1 Image -> Resize Picture 3.2 Tick "Constrain Proportions" and Select "%" 3.3 Pick 50% for width and heigth 3.4 You can pick any one of the filters except Nearest Neighbour 3.5 Press OK ALTERNATVE STEPS TO REPRODUCE 1. Step 1 and 2 as above 2. Scroll down the mouse wheel until the zoom factor is 50% OBSERVED RESULT The image comes out grey or grey with some barely visible outlines. EXPECTED RESULT Picture with natural colors. SOFTWARE/OS VERSIONS Archlinux with kernel 5.6.17 KDE Plasma: (available in About System) KDE Plasma Version: plasma-desktop 5.19.3-1 KDE Frameworks Version: plasma-framework 5.72.0-1 Qt Version: qt5-base 5.15.0-4 ADDITIONAL INFORMATION krita 4.3.0-1 amdgpu-core-meta 19.30_934563-1 xf86-video-amdgpu 19.1.0-2 mesa 20.1.3-1 lib32-mesa 20.1.3-1 libva 2.8.0-1 libva-mesa-driver 20.1.3-1 lib32-libva-mesa-driver 20.1.3-1 mesa-vdpau 20.1.3-1 lib32-mesa-vdpau 20.1.3-1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Lukas Frank changed: What|Removed |Added CC||lukasfran...@gmail.com Flags||Backport+, Brainstorm-, ||corner_case-, ||Translation_missing-, ||Usability+ Component|Filter Layers |Filters -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Lukas Frank changed: What|Removed |Added Component|Filters |General -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 --- Comment #3 from Lukas Frank --- Thank you for clearing my misunderstanding. I see that I can fix the "problem" with scrolling by selecting scRGB(linear) in display settings. The gamma is also correct in resizing if I select scRGB(linear) as Color Profile for the picture. A quick way to change the colorspace of multiple images seems to be to go to Extras->Scripts->ColorSpace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491719] Brightness is reduced unintentionally when monitor does Pixel Refresh or is reconnected
https://bugs.kde.org/show_bug.cgi?id=491719 --- Comment #4 from Lukas Frank --- Created attachment 173348 --> https://bugs.kde.org/attachment.cgi?id=173348&action=edit kwinoutput and UI in original 100% brightness and after reconnecting the display cable kwinoutput and UI in original 100% brightness and after reconnecting the display cable -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491719] Brightness is reduced unintentionally when monitor does Pixel Refresh or is reconnected
https://bugs.kde.org/show_bug.cgi?id=491719 --- Comment #5 from Lukas Frank --- The kwinoutputconfig.json file shows no difference after reconnecting. The actual screen brightness stays the same, but the UI brightness got set from 100% to 1% by reconnecting (see attachment AFTER.png in Archiv.tar.gz). After reboot the brightness was back to 100% again, but in other cases it was permanently decreased. I do not know why it did not happen this time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491719] Brightness is reduced unintentionally when monitor does Pixel Refresh or is reconnected
https://bugs.kde.org/show_bug.cgi?id=491719 --- Comment #6 from Lukas Frank --- Created attachment 173349 --> https://bugs.kde.org/attachment.cgi?id=173349&action=edit Manual Pixel Refresh If instead I do a manual pixel refresh with the monitor, I do get the same brightness, but the refresh rate changed from 165 to 100 Hz in kwinoutputconfig.json and the UI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491719] New: Brightness is reduced unintentionally when monitor does Pixel Refresh or is reconnected
https://bugs.kde.org/show_bug.cgi?id=491719 Bug ID: 491719 Summary: Brightness is reduced unintentionally when monitor does Pixel Refresh or is reconnected Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brightness and Color Assignee: plasma-b...@kde.org Reporter: lukasfran...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY The software brightness is reduced when my OLED Monitor comes out of a Pixel-Refresh or is reconnected. This is an issue for OLED Monitors that automatically do Pixel Refresh and other Monitors that get regularly reconnected. STEPS TO REPRODUCE 0. Set brightness to 100% 1. Unplug display cable 2. Reconnect display cable 3. Observe changed brightness OBSERVED RESULT Brightness changes unexpectedly EXPECTED RESULT Preferably brightness stays the same or alternatively brightness is set to full 100%. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
