Works perfectly as described (on Linux), thanks Carmelo.
I understand they are personal so far but here are my comments:
- What is the benefit to include jpg or tif in the extension of the created pfi (like .tif.pfi) ? If I export the same source to tif or jpg, the pfi file content is exactly the same (as pfi doesn’t describe the export process). If Path/Name of the image file is the same, there is no reason to have different development. That’s true for jpg & tif, but also for any other format you could add in the future.
- Once we have set the configuration option “save sidecar files” it is to use it. Asking the question everytime we open the file is a useless click. If some users find the question important, it could be another configuration option: “always use sidecar files”.
- Now I can see all my output files in the DAM and re-open the development at any time opening the output file itself. That’s GREAT ! But I’m still missing to re-open the development of the source image (nef). The pfi file attached to the nef file is for me the basic development, where I start from to create one or several output images. I could display the pfi files in the DAM but I would lose the full benefit of your change.
My intial suggestion was the following (without showing pfi file in DAM). Sorry if I have not been clear enough.
If for each image we consider the path, the name and the extension (ext) like path/name.ext. The ext = nef, cr2, … are source images, but jpg and tif can be source as well.
Case 1 (basic)
The pfi file can have been created by “Save current Image” or by “Export current …”. Whatever the image I open PF opens the nef with pfi development.
Case 2 (extended)
path/name_xx.jpg (could be path_xx/name.jpg)
path/name_xx.tif (could be path_xx/name.tif)
path/name_xx.pfi (could be path_xx/name.pfi)
If I open name.nef file PF opens the nef file with name.pfi development. If I open the name_xx.jpg (or tif) file PF opens the nef file with name_xx.pfi development.
The case 2 covers the case where the source is a jpg (or tif) file as well. As the pfi knows the source file there is no confusion between the source jpg and the output jpg.
If I understand properly the impact for a non DAM user would be the following, with:
If I open from PF the name.nef file PF would use the name.pfi development instead of no development (or using default.pfp when applicable).
We could use “always use sidecar files” to avoid this when not desirable. If set, PF always uses the sidecar file, even for source image. If not set (as default) the current PF behaviour is totally kept.
I apologize for the length of this post. And again a huge Thanks for your work !