I'm having some weirdness with RGB triplets. Unfortunately I haven't been able to figure out exact repro steps, but the rough outline is that I opened a folder with several sets of RGB images in it. NegPy correctly figured out which ones went together (I didn't need to make any changes there), but the initial conversions looked all wrong. One looked almost black and white, one was super orange, etc. Example in screenshot. I "fixed" it by toggling Linear Raw off and on, which seemed to trigger re-doing the conversion. I didn't make any other changes, so I don't think it was a wrong setting or something. It just needed to be forced to try the conversion again for some reason.
This example is in 0.39.0 because I was in the middle of trying to figure it out when I saw that 0.40.0 was released. Since the set I have is already fixed, I can't confirm if the behavior is the same in 0.40.0 or not, but I didn't see anything in the changelog that sounded like it would have touched this part of the code.
I'm having some weirdness with RGB triplets. Unfortunately I haven't been able to figure out exact repro steps, but the rough outline is that I opened a folder with several sets of RGB images in it. NegPy correctly figured out which ones went together (I didn't need to make any changes there), but the initial conversions looked all wrong. One looked almost black and white, one was super orange, etc. Example in screenshot. I "fixed" it by toggling Linear Raw off and on, which seemed to trigger re-doing the conversion. I didn't make any other changes, so I don't think it was a wrong setting or something. It just needed to be forced to try the conversion again for some reason.
This example is in 0.39.0 because I was in the middle of trying to figure it out when I saw that 0.40.0 was released. Since the set I have is already fixed, I can't confirm if the behavior is the same in 0.40.0 or not, but I didn't see anything in the changelog that sounded like it would have touched this part of the code.