XnView Software

Adobe Lightroom allows me to convert my old JPGs to DNG format so I can use non-destructive editing/versioning on those converted files. During editing, Lightroom saves an "XMP" (appears to be XML format) file in the same folder as the DNG image, giving it the same name-part as the DNG file. The XMP file contains the series of commands executed on the file during my editing session on the DNG in Lightroom.

Request:

Please allow me to identify a "companion" file to also automatically copy/move/rename when I use XnView to copy/move/rename the "parent" file.

Here's how I think it should work:

1. Using the Xnview options page for the filetype, User defines a "companion" extension for the file type. For instance, if image filetype is DNG, then I would specify XMP as the companion file extension.

2. User selects a file (for instance, a DNG) in the XnView file list

3. User executes copy (or move or rename)

4. XnView looks for a companion file in the same folder whose name-part matches the selected file and whose extension-part matches the "companion" extension paired with the image type (for instance, XMP).

5. If XnView finds the companion file, then it moves/copies/renames the companion file at the same time as the selected file.

Also, there should be a user interface toggle in the copy/move dialog to indicate whether XnView should also perform on the "companion" file (or not).

Hope that is clear.

JohnFredC wrote:Adobe Lightroom allows me to convert my old JPGs to DNG format so I can use non-destructive editing/versioning on those converted files. During editing, Lightroom saves an "XMP" (appears to be XML format) file in the same folder as the DNG image, giving it the same name-part as the DNG file. The XMP file contains the series of commands executed on the file during my editing session on the DNG in Lightroom.

Request:

Please allow me to identify a "companion" file to also automatically copy/move/rename when I use XnView to copy/move/rename the "parent" file.

Here's how I think it should work:

1. Using the Xnview options page for the filetype, User defines a "companion" extension for the file type. For instance, if image filetype is DNG, then I would specify XMP as the companion file extension.

2. User selects a file (for instance, a DNG) in the XnView file list

3. User executes copy (or move or rename)

4. XnView looks for a companion file in the same folder whose name-part matches the selected file and whose extension-part matches the "companion" extension paired with the image type (for instance, XMP).

5. If XnView finds the companion file, then it moves/copies/renames the companion file at the same time as the selected file.

Also, there should be a user interface toggle in the copy/move dialog to indicate whether XnView should also perform on the "companion" file (or not).

Hope that is clear.

Is it possible to send me a sample?

xnview wrote:Is it possible to send me a sample?

Here is one DNG and its matching XMP. Sorry the file is so large.

---> 6Mb Zip

Here's hoping for a generalized function that would work for any paired file extensions, not just DNG/XMP. I expect this 2-file paradigm (raw image file + edits file) will be more prevalent in the future.