Thanks for making this important development, it will help not dealing with two separate branches.
So far the only difficulty I have is backward compatibility for those images I processed in the stable branch where I went straight to lab colour space in the initial raw development. These now produce a an incorrectly coloured image. This was the same for the previous linear gamma branch but I did not get round to raising the issue (sorry). I can get round it by introducing an RGB colour space before changing to lab.
You are absolutely right! That’s a bug I will probably fix within a couple of days. Apart from that, backwards compatibility should be fully guarantee.
Using the stable branch (just built) I opened an image in the LAB color space (from Lindbloom’s Profile Evaluation set - Welcome to Bruce Lindbloom's Web Site). The image just looks solid black, was opened “as if” it were sRGB with no profile. Assigning a LAB profile from disk didn’t make any difference. Krita opens the same image as a LAB image and it looks correct, so I’m guessing there is no problem with the image file itself.
The packages from today should completely solve the issue with opening old .pfi files with straight conversions to Lab colorspace… please let me know if this is still not fixed for you, or if you still experience other backward compatibility issues…
Just checked again and whilst there are appimage and windows versions dated 29th there is no OS X version. The one dated 28th does not include the fix I presume as it does not open the direct to Lab files correctly.
I don’t know if you prefer issues reported via github or here, but… I just tried the latest appimage of PhotoFlow (./PhotoFlow-20171129_0741-git-stable-070c6d3e7be6e654b13c83e980bb5c2213742b7f.glibc2.17-dbg.glibc2.17-x86_64.AppImage) and I get a segfault if I try to set a custom DCP profile in the RAW developer module. The crash happens as soon as I select “DCP from disk”…