Honestly, it’s really hard to figure out what your problem actually is. I recommend you read this before you report more issues: How to Report Bugs Effectively
Are you aware of all the color profiles in DT and how they all interact to give you a result and also values… For example the histogram profile will determine the values provided by the color picker… if you change if from the default or rec2020 to srgb you will get different values reported and your histogram will change but the image will not change on the display… DT has an input output display and histogram profile … the settings for each can determine your result…
PNG will likely not use the same module order as raw… another nuance of DT ie understanding the pixel pipeline…
But as others have said just share a file and or sidecar and we can dissect what you are experiencing and make some better targeted comments… I feel like it will take 5 min once you share that…
And for sure you would need to confirm that you not only have the profile settings correct but that they are the same for GIMP and darktable as @kofa mentioned…
Please be more careful with the formatting, it’s very hard to track what’s something you quote, and what is your answer.
Sorry for the bad quote formatting. I have ended up being a little time pressed at the moment.
input color profile has nothing to do with printing: it describes the input image.
I had so little time that I misread it for a ICC profile.
Anyway thanks for you posts kofa, I will answer it later this weekend, as I have a lot of other things that I need to do right now.
1 Like
Are you aware of all the color profiles in DT and how they all interact to give you a result and also values… For example the histogram profile will determine the values provided by the color picker… if you change if from the default or rec2020 to srgb you will get different values reported and your histogram will change but the image will not change on the display… DT has an input output display and histogram profile … the settings for each can determine your result…
Thanks for the suggestion. I do know these things are there, and have tried to make some changes. Although I don’t know these models in any fine detail. But as I have said the issue seems to stem from the way the Darktable outputs data to the graphics card, as non raw files also came out way too dark.
But as others have said just share a file and or sidecar
I will write again later this weekend, as I have a lot of things that I need to do right now. Sorry for the wait.
That’s some serious memory-digging and data interception system you are running there. Care to tell me how to do that?
Well in Most Linux most input and output checks are easy to do. Linux was made by programmers to programmers after all. So I can hardly take any real credit for the effort here. All you have to do most distros is to make a PNG screenshoot, and analyze it with a color picker tool.
NP but please consider sharing a real file so others can try to reproduce your observations or more easily point out why you are seeing what you are seeing…
I will, but I have been hit with some unforeseeable problems that I have to fix first. Sorry it is midnight now and I will have to try to make it tomorrow if I can.
1 Like
Hi, I apologies for the long wait, sadly I have been quite sick with a virus on top of all(sadly where I live, we are in the flu season).
Now these things are hard to determine by eye alone. So I sampled some colors from my worst outputs, and tested if the transformation could fit with a gamma correction model(Vout = constant*Vin^gamma). Short story, some of the colors where far away from fitting. So I thought maybe the icm profile is bad. So I tried to reinstall it again. When doing so I saw a obscurely placed option called; “Set for all users”. Now I only have my own user account, so this should not have an effect. However I tried to figure out what the option could mean anyway. It turns out that if this options not ON, then some programs/processes sometimes get wrong profiles (other profiles from a profile list in the OS). And the tricky thing is that the effected programs/processes apparently can get more than 1 profile, such that the effected program changes appearance while working in it. And as this issue is seen when using a specific program, it gives the impression that the issues occur inside the program/process, and not configuration of the OS. And this explains my misidentification of the problem.
I don’t really understand this design in the OS, as 1 monitor should only have 1 icm profile(especially if the user have imported one). But given that the option uses the term “users” which is normally given to the concept of accounts, I suspect that the color profile implementation of the OS was rushed/unpolished.
In summation the there is no native output issue in Darktable. And everything works as it should now.
I also answered you other questions from kofa. The only thing is that I can’t find cmstest in my flathub version of Darktable.
I installed the latest version found on Flathub. It is numbered 4.6.0. And I use Linux Mint.
I am mostly using Linux Mint 20.3, as LM 21.X have gave me some GRUB issue. But I have also tried to install LM 21.3 and can see that it do not have any of the issues and it does add some limited Wayland support. I am not using any OpenCL support, as I assume that this should only effect speed a little and the 10 core CPU seems to be utilized well.
All of them are from the darkroom
Yes, I have. And that in itself was not enough. As it had to be set ON by an option to work for all programs.
Yes, they do use the same icm profile that I set for the monitor. But apparently there is a “program state” in the way that the OS handle icm profiles which cause the behavior.
I can’t find darktable-cmstest in the folders of
~/.var/app/org.darktable.Darktable/
Can you give the specific folder path in the flathub version?
Yes it is JPG and it is in sRGB. The requested files are here:
Pjuske i Farver.jpg.xmp (3.6 KB)
Given the the cause of the issue I don’t think they will provide any answer.
I think that this info is in the XMP file.
system display profile.
Well I was responding to:
The word misconfiguration can mean many things, many of which can have wide consequences when talking about Linux. And the issue was not a misconfiguration, rather a “program state” issue in the OS configuration for the icm profiles. So the icm I installed was only used for some programs but not Darktable.
My point was that it is not trivial to change things in Linux, as many things are coupled in ways that only the programmers can understand . As an example I mentioned that I have tried to fix things in linux back in SCSI days(late 90s/ early 00). And the tricks worked early on, but later as modules became more complicated, even “Linux experts” gave advice that could take down an operating system.
It was very easy to edit models in many distros back in the day. Yet this was removed in most distros as it was deem to complicated. And to day it is mostly distro makers that deal with these concerns.
I hope this clarify the matter and thanks for the suggestions.
I assume that means “case closed”?
Yes, so I should add [Solved]. But I can only see the options:
Watching, Tracking, Normal, Muted
I guess that asking how I closing this topic down, is my bonus question.
Go to the OP and click the pencil icon underneath to edit the caption.
Were you logged in?
Yes you can see my image of the OP. There is a B in the blue circle for my log-in.
I see no such blue circle at top right …
Since this user is new, they haven’t earn the ability to edit titles past a certain point. While adding solved is fine, it isn’t requisite.
Thanks for the clarification. As an administrator, can you do this or close it instead?
We don’t close threads unless there is some social issue.
Someone else will have your issue later on ,better they find your thread and post to it than start a new one.