I'm just glad the two-tiered method for saving non-destructive edits exists! It saved me from having to dig into my backups to restore files. It could be a bad block on a disk, cosmic rays. I believe this to be a case of the sidecar file being corrupted in some way. It has happened to one and only one of my photos among thousands and thousands in my library. And we're running experiments to see if the problem is reproducible. I've already been in touch with ON1 about this phenomenon. And yes, I did stop and restart Photo RAW after the sidecar file was regenerated. That's enough to refresh the sidecar file. In Photo RAW, using sidecar files allow us to edit the RAW files in a non-destructive manner unlike editing JPGs or TIF files directly. You don't see them within Browse, but you will see them in the Finder or Explorer. For example, raise the Exposure slider and then Undo the operation. ON1 sidecar files are small files that hold a copy of the metadata changes and non-destructive edits you make in Photo RAW. I quickly open the Develop module and make a token change. The sidecar files are generated when a processing change is made. By renaming the sidecar, Photo RAW used its internal database to appy the changes instead. Apparently, Photo RAW reads the sidecar if its present. Photo RAW keeps its own copy of the changes in its internal database. how did those edits come back? Remember I said the ON1 sidecar file is a backup of the non-destructive edits. And even better news! All of my non-destructive edits are intact. Of course, sidecars come with there own risks, but I would rather loose my edits than my image.I restart Photo RAW. Of course, if the developers are careful to follow the XMP spec precisely, you are probably OK, but for me (with lots of experience with programmers), I would much rather not take the chance. There are always risks when a file is modified, including the possibility that some future app of yours does not understand the changes made by the old app. In the case of image files, there is a benefit to leaving the original RAW file pristine. So you might decide to use PDF's internal update stuff, but then the client apps probably have to offer its users a way to rewrite the file when bloat starts becoming a problem. From a programming point of view, you can delete the old annotation only by completely rewriting the document, and this can be an expensive operation. For example, if you delete an existing annotation and replace it with a new one, it is likely that the old one will not actually be deleted. Although PDF is very well specified, the mechanism for modifying existing PDFs can lead to the document constantly growing in size. ![]() I favoured sidecars for various reasons, and I still do. embedding for dealing with user annotations. ![]() We had a big internal debate about using sidecars vs. ![]() Camera raw files do not support embedded XMP. It's also perfectly happy with you leaving your photos organized in folders and just browsing to the folders - no import needed.īefore I retired, I worked for Apple, mostly on stuff related to PDF. Jpeg files do not have an XMP sidecar because the jpeg file format supports embedded XMP metadata. You can also do some tricks like add a B&W effect, tweak it and then make it semi transparent, for finely customized low saturation. One thing I especially like is that each effect has an opacity slider, so you can tone down an effect with one adjustment. On1 is great if you like the tools in the Effects panel. It does actually use sidecar files, which are best used when working in Sessions - they're saved in the Session folder hierarchy and can be found and copied with the file, and since they're in the same folder set as the images and the rest of the support files it makes taking sessions from one computer to another easy. If you don't use Fuji it's not necessary. But the main reason I like it is that it does the best job on Fuji raws. It does actually use sidecar files, which are best used when working in Sessions - they're saved in the Session folder hierarchy and can be found and copied with the file, and since they're in the same folder set as the images and the rest of the support files it makes taking sessions from one computer to another easy. you can make tool panels for different workflows, so I have one for working with camera-scanned negatives that has all the tools I use for that, in order. ![]() I'm using Capture One, and the interface is different but once you get used to it it's great.
0 Comments
Leave a Reply. |