| Summary: | Color management inconsistency | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | David <gardiandavid> |
| Component: | ColorManagement-Views | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/7861910af570f88b53ffbd7a26c402234448ef22 | Version Fixed/Implemented In: | 8.7.0 |
| Sentry Crash Report: | |||
| Attachments: |
screenshots of my color management settings
The ICC profile I use for my monitor that is both enabled in Windows and selected in digiKam profile settings |
||
|
Description
David
2025-04-18 11:24:03 UTC
ok, so the CM settings is not retained between the digiKam sessions. Right ? Can you sahre yoi ICC profile file ? Best Gilles Caulier At least here on Linux, I can't reproduce the problem using the test images. I'll test it later on Windows. A note regarding the incorrectly displayed red thumbnail in your YouTube video. The thumbnails are saved with color management or not, depending on whether color management is enabled or disabled. This is done for performance reasons. Therefore, you'll need to regenerate the thumbnails after making changes, e.g., by pressing F5 in the current album or using the maintenance tool. Maik Created attachment 180380 [details]
The ICC profile I use for my monitor that is both enabled in Windows and selected in digiKam profile settings
(In reply to caulier.gilles from comment #1) > ok, so the CM settings is not retained between the digiKam sessions. Right ? Yes, restarting digiKam makes CM stop working, although it is still enabled in the settings. As I said, it often happens after only changing open directory. > Can you sahre yoi ICC profile file ? Ok, I added the ICC file. I can reproduce the problem with the first image after launching digiKam. It's related to the Histogram tab in the right sidebar, if it's active at startup. The problem doesn't occur with other active tabs. It's likely related to retrieving the image from the image cache; I'll fix it. Maik (In reply to Maik Qualmann from comment #5) > I can reproduce the problem with the first image after launching digiKam. > It's related to the Histogram tab in the right sidebar, if it's active at > startup. The problem doesn't occur with other active tabs. It's likely > related to retrieving the image from the image cache; I'll fix it. > > Maik Nice, thank you! Git commit 7861910af570f88b53ffbd7a26c402234448ef22 by Maik Qualmann. Committed on 18/04/2025 at 18:14. Pushed by mqualmann into branch 'master'. check cached image for color management applied FIXED-IN: 8.7.0 M +1 -1 NEWS M +20 -0 core/libs/threadimageio/fileio/loadsavetask.cpp M +8 -7 core/libs/threadimageio/fileio/loadsavetask.h M +5 -0 core/libs/threadimageio/preview/previewtask.cpp https://invent.kde.org/graphics/digikam/-/commit/7861910af570f88b53ffbd7a26c402234448ef22 |