Got it, thanks!
Storing the pp3 files in the same folder as the image files means you can just copy a folder with images and pp3 files to a different machine. If the pp3 files are stored only in cache it will be a bit more complicated.
2 Likes
Yup, something else I hadn’t thought about.
For what it’s worth, I prefer to have the edits saved in the metadata of the jpeg/tiff/png that the edits produced. Putting them in the raw means to me that only one edit chain is valid or current for that image, and in my workflow that’s not the case - small jpeg for proof, full-sized tiff for further editing, etc.
It’s what I do in my hack software now. My file menu has an “Open Source…” selection, where such an encoded image can be specified; what the software does is to read the edit chain from the output image, identify the starting image, open it instead of the and re-apply the edits. My workflow is fundamentally dependent on this capability.
Right now, I save the edit chain in the EXIF ImageDescription. Now that I know of the Adobe tags, I may consider modifying my software to use them instead, if they’ll support my editing semantics (that is, the chain of operations).
I still think that sidecars are the best solution. Personally, I dislike them not because of their utility but simply because they are there, like a fly on the wall you want to swat compulsively. Once I overcome that irrational part of my mind, I am okay with them. 
The “fly on the wall” is what prompted my initial post. I use Adobe bridge which allows for file groupings. Out of sight out of mind.
You know, you could always filter out the file type or even ask Bridge to ignore it all together. BTW, I thought that Bridge was no longer a thing… Oh I see, it is more of an optional thing now.
Available for free on Adobe cloud. I think it’s called bridge CC.
I mean, I thought it was discontinued. A quick web search shows that it is in maintenance mode for those who want to use it. For most users, LR is the go-to, at least that is what I think. Mind you, I haven’t used Adobe apps in ages…
I suppose that Lightroom is the go to for most people. I’m just not into the catalog system that they use.
Glenn, I know nothing about programing like yourself though I would prefer that the edits were stored in the raw data like in ACR. I rarely save to tiff for Photoshop edits. I usually just output to jpg for web viewing on a few sites. That said, rt is now my go to app for raw edits.
Congrats on your transition. 
Remember what we have been talking about. It isn’t be stored in the raw file but in a database. Having visible *.pp3s is awesome because you don’t have to worry about the database failing and losing everything, as many a LR customer would tell you that it is their deepest darkest fear.
Yes, I understand.
I would like the .pp3 to be seen as ‘the image’. This allows having multiple versions referring to the same raw. But then, the reference to the raw must be stored inside the pp3 (not just a partial filename match) so it is a big can of worms.
@Sympa I know what you mean. PhotoFlow does that if you are willing to give it a try. Opening the PFI opens the raw with the edits, while open the raw directly opens it without the edits.
Yes, I hesitated to post, as my perspective is really of little use with sidecar-based softwares. But this was the main reason I set out on my own, because I just don’t like having to drag multiple files around for a single rendition of a raw.
Right now, I batch process my raw ‘dailies’ with a script that gets embedded in the 800x600 proof JPEGs. When I review them in geeqie, if I want to edit differently I just drag the image over to a desktop icon (shortcut?) for my GUI program, and it automatically extracts that script, finds the original image of that edit chain, opens it and re-applies the edits and I go from there. Sometimes it’s minor edits that get saved over the original proof; other times I save a different rendition for GIMP editing or printing or maybe just a different crop. Each rendition gets the edit chain that made it embedded in the EXIF. Yep, I don’t have retinex or filmic or such, but I love this workflow and I can get decent ‘starting-point’ tiffs for later work with GIMP if I need.
Where I store in the EXIF, the ImageDescription, is a rather hacky solution. I’d much rather use tags specifically meant for such, and I may move to such when I do the big re-factor for version 1.0.
afre wrote: You know, you could always filter out the file type or even ask Bridge to ignore it all together.
How is this done?
Thanks!
No problem. Remember that RT and Adobe apps both have great documentation that you could check out anytime. 
1 Like