I'm not sure what could be done about that - throw an error if the user tries to act on a RAW file when an onphoto of the same name is deteced? Seems complicated at best.
So, it would appear that the risk is if a RAW and its sidecars are moved or deleted while ON1 RAW is not running, a related onphoto could lose its edits. If, on the other hand, I rename the onphoto in the first step above, or go back to it after removing the parent's on1 file and make an edit to it, a new on1 file is created for the onphoto and it appears to become independently portable. (And the RAW retains its edits).įrom this, I conclude that the onphoto's edits are carried in the parent RAW's on1 file.
If I reunite all the files in the new folder, the onphoto regains its edits. If I then move the onphoto to a new folder - it does not retain its edits. When I then go back to the onphoto, it retains its edits (from the database, I assume.) If I quit ON1 RAW and remove those files, no on1 file is generated for the onphoto. If I leave ON1 RAW running and remove the RAW, on1 and xmp files, a new on1 is generated for the onphoto and all is well. If I start with a RAW file and edit it, then add a layer to make an onphoto, I end up with four files: a RAW, an on1, an xmp, and an onphoto. I went back and tried to make my experiment more rigorous, to try to isolate sidecar behavior from the behavior of ON1 RAW's live database. Or maybe acting on RAWs and onphotos as pairs - see below. But, when I copy one to a new folder, or rename it, it has both a. xmp if they exist in the same folder as their ancestor files. You can only make one by adding layers to an existing image. If I can help figure this out (after a good night's sleep), please reach out. It's been a long week and this is making my brain hurt. onphoto, it would seem you would be breaking the relationship between the parent files and its sidecars. But, if you moved the sidecars along with the. If an onphoto is living with its parents (a millennial file? :-), its sidecars would be the parent's. xmps with the same name would be sidecars to it. In other words, until they are renamed or moved, they seem to use their parent's.
0 kommentar(er)
