Strange cast on CR2 files since moving to 5.0.0

Just wondering if anyone has any idea why some of my pictures have suddenly stopped displaying properly since moving to 5.0.0. It just seems to be on a few images so far, and I’m trying to find a pattern. The only commonality I’ve found so far is that they have been CR2 files. But I thought I’d quickly post here to see if anyone immediately knows what’s going on.
Disabling modules one by one doesn’t seem to fix the problem or pinpoint where the issue is, which makes me wonder if it’s something to do with the input colour profile, something like that.
This is an image I processed about a year ago and have not many any changes since.

Here’s the thumbnail in the Lighttable, which is what it should look like:

image

But when I open it in the Darkroom, it looks like this:

Can you share one that misbehaves with the xmp so others can try to replicate it…

It could be an issue with the pixelpipe. We’ve been working on it and I’ve seen several images that look like this in my testing. There is a PR being tested that fixes the problem. If everything is OK, the fix will be in 5.0.1

Thanks @priort and @wpferguson . I’ll just monitor it for now then and see if 5.0.1 fixes it. If not, I’ll be back!

It is still best to share the cr2 and xmp in a GitHub issue. Otherwise you might need to wait until 5.2 for a fix.

1 Like

Good point. I’ll submit one now.

Dinner would kill for such a built-in retro filter, and you complain? Users these days… :wink: