the official package is signed - so osx intentionally prevents from running that if someone has patched that 
btw: my build doesn’t use different libraries - it’s build following the same description as the official builds.
@MStraeten I tried your build - but it did not solve my colour problems. However, from your comment above, it sounds like it doesn’t include the patched libraries after all?
no it’s current master code base (sometimes with upcoming but not yet merged pull requests but no third party stuff)
I’m coming back to this once again, in 2024.
This time I have downloaded Darktable 4.6.1, and everything in my OP still seems to apply.
So, is there anything I should know about that has changed, that might allow me to fix the problems, or is it time for me to wave goodbye to Darktable?
recent darktable is 4.8.1 there were plenty of changes since 2022 - you might have a look at the release notes of all of those releases inbetween.
at least i don’t have issues with color management using recent darktable and macos …
I’m still on macos 12.5 so can’t update beyond 4.6.1 but thanks, I will have a look at release notes, and i guess try 4.8.1 once I get around to updating my macos.
have a look at darktable 4.8.1 for older macOS versions (10.14 & 11.0)
Thanks @MStraeten . I’ve successfully installed 4.8.1.
Still, Darktable doesn’t show images in the same way as other applications (as per “problem 2” in my OP).
Both Affinity photo & Mac preview appear to use the whole gamut of my display. But Darktable doesn’t. This screenshot shows the same image opened in Affinity, Preview, and Darktable (on the right).
Did you open a raw file in DT while the others are jpegs? At least for preview and DT, that seems to be so, based on your screenshot. And that’d explain what you’re seeing.
No, it’s the exact same image opened in each of the three applications - a JPG image with an Adobe RGB colour profile; an image that I know contains colours outside of the sRGB gamut.
Its interesting that your module order is “3.0 raw”. What are your color management settings in DT?
I’m not sure why that was - on reopening DT it was “3.0 JPEG” instead.
Which colour management settings specifically?
Monitor profile, working profile, etc etc
How about sharing the jpg?
Thought I had it figured out but I don’t, hence deleted posts above. I need to come back to this…
Here are three screenshots.
This is using a test image which has two reds, one of which is outside the sRGB gamut so can’t be seen on a non wide-gamut monitor. If I look at this image on my secondary monitor (which is not wide gamut) I just see a red square, but if I look at it on my main (wide gamut) monitor I can see the logo that’s revealed.
These screenshots are taken from my main monitor, and you should be able to see the various profile settings I am using in DT.
Screenshot A: If I set “display profile” to my calibrated monitor profile (the profile name starts with UP2716D) then the logo in the image is visible but you can see that it’s not displayed the same in DT as it is in Affinity or Preview.
Screenshot B: If I set “display profile” to “Adobe RGB” then the logo in the image is visible but you can see that again it’s not displayed the same in DT as it is in Affinity or Preview.
Screenshot C: If I set “display profile” to “system display profile” then the logo in the image disappears when viewed in DT.
My “system display profile” (the profile that’s chosen in macos display settings) is that calibrated one (the UP2716D one) so it seems to me that in both A and C I ought to be seeing the logo revealed and i ought to be seeing the image just the same as it appears in Affinity or Preview. But that’s not what’s happening.
So viewing this post in Chrome, in A and B I see the logo in all the elements of your screenshot and in C only the DT screen doesn’t show it…but if I click on the picture to pull them up full screen what I see changes I don’t see the logo’s anymore… so for me with my ~sRGB monitor its funny I see it in your post but not when I click on each… and the test image my monitor doesn’t show it…
Actually the same happens for me, viewing on my wide gamut monitor. Obviously something happens due to the way the website decides to serve the images.
If I download the test image (from my post above) to my computer, and then open it in eg. preview, it behaves as expected though.
1 Like
For anyone interested in investigating the problem I describe above - I think you need to download the images that I have posted to your computer, in order to see what I am seeing, because there’s something about the way this website serves them that means they appear differently.