Started by jarraun, July 27, 2014, 01:44:58 PM
QuoteDelete NEF file -> NOT OK, xmp file not deleted.
Quote from: jarraun on July 27, 2014, 05:01:30 PMMore findings. It is something about TIF files in the same folder as RAW files (NEF files in this case).
Quote from: Mario on July 04, 2014, 08:33:55 AMBy definition, an XMP file belongs to all files with the same name in the same folder. So if you have bla.nefbla.xmpbla.jpgIMatch does not delete the XMP because it is still linked to the jpg file.
Quote from: Erik on July 09, 2014, 05:28:35 AMThis issue seems to becoming common (or at least it's been posted about a couple of times).Richard covered why the problem occurs, but as a note this conflict with XMP files that happens when two files have the same name but different extensions can be dangerous to a user in cases such as this.As mentioned in the original post, you end up with an XMP file that is only tied to a JPG, but JPGs rarely have XMP files, unless a user specifically sets it that way. There are many other conditions where XMP files could conflict if you were purposely only working with sidecars (such as orientation, develop settings, etc).This is one of the reasons that I chose to make version files have unique names from the master files. Instead of having:File1.rawFile1.jpgFile1.xmpI use:File1.rawFile1-v1.jpgFile1.xmpThe result is that when I delete or move the Raw file, the XMP is now only tied to the master file. If the version were to have its own sidecar fileFile1-v1.xmpThen that file is unique to the version. The added advantage is that I can easily track and manage multiple versions, but the primary reason I had started adding a suffix to the original file name for versions was to avoid conflicting xmp records, which was an issue for me back in IM3.6. --Anyway, I can see possible value to the request, but I can also see it getting quite complicated in cases where both similar named files legitimately need the XMP and having to keep track of the Metadata Settings closely to know when to delete an XMP file or not. Ultimately, the issue can be remedied by a user with a bit of planning on their file naming convention.
Quote from: jarraun on July 28, 2014, 09:56:22 PM... remember that if someone renames his derived files (until Mario decides to implement the new behaviour) some XMP files will be produced and must be deleted.