ON1 import and treatment of .original xmp files
I am evaluating the use of FastRawViewer to cull when I am ingesting (before bringing into ON1). I shoot raw so when I have completed culling I have a collection of .NEF files and a few corresponding .xmp files where, for example, I set a rating.
I tried using ON1 Import for this set of files. What I found is that ON1 wrote a complete set of .xmp files for each .NEF. In the process it apparently overwrote the original .xmp files created by FastRawViewer.
Are there settings that control this behavior? I would have thought that ON1 would honor any .xmp files it found when importing. Instead it appears to overwrite them and therefore my original culling choices (like rating) are lost. Is there any description of how to work with .xmp files when importing into ON1?
I see there is a feature on the Photo Tab, "Read Metadata from Photo". Can I get this behavior when importing?
-
I agree that import should work the way you describe. If import is over writing previous metadata you should bring this to the attention of On1. Since the whole reason On1 uses the xmp file is to be compatible with other programs, you'd think On1 itself would be compatible.
In the mean time. You don't need to use the import function to use On1. Just point the browser at your photos. The browser should see the existing metadata. Then use the metadata functions in the browser to update whatever fields you want and 'hopefully' it won't overwrite what you had.
0 -
I brought this topic with support and was told this was how the software was designed to operate.
After a few exchanges, I gave up trying to explain the value of alternative operation. Maybe more people can help change the On1 mind?
In my case, i also found that "reading" embedded data (using the metadata function) to get the lens information from the file into On1 so I could use the automatic lens correction... deletes the previous IPTC information I had in the file. Gggrrrr...
0 -
I heard from support. What I am seeing is the functionality of Import by design.
By design Import assumes there are no sidecar files and it generates its own. So it's destructive in a sense but only because it isn't designed to handle being a "next stage" in a photo workflow.
If you want to use .xmp from a previous stage in your workflow you merely copy the raw and xmp files to your destination area and then, from within ON1, you just Browse to them. In that case ON1 will read the existing xmp files.
0 -
But there are some important criteria for the formatting of .xmp files. The first few lines in the XMP file specify the formatting and level of the file. XMP has changed over the years. I had a import sw package that allowed me to add metadata and I used it when importing. However, it was a lower version than what ON1 expected and ON1 basically left the XMP file alone, and did not update it as it should. This caused me issues and once I noted that XMP files were being added to the catalog from this importing sw, I turned that function off and everything went back to normal. I do not remember what that issue was, as it was a year or two ago.
0 -
Just like what I heard... "it is by design"... The feedback and associated workaround makes sense... but may be a bit lacking as a long term solution... to me the design could be improved.
If development could consider the following: Looked at the contents of the XMP file --first-- , then appropriately processed and the information followed by a correct update... we could have a tool that can work with other tools.
From a development standpoint, to just write your own file without concern for what is there is much easier/quicker. The fact they have employed this process sounds like a development team that is overworked, maybe forced to cut a corner.
0 -
Things can get even more complex. You are using FastRawViewer as a preparatory step only. Just imagine using both LR and On1 in parallel, happily overwriting the same .xmp. Entertaining combo.
0 -
I am incredibly frustrated with the inability of ON1 to correctly recognize .xmp files from Photo Mechanic. I realize that this is not the same as FastRaw Viewer, but the problem is the same. I cannot for the life of me get ON1 to properly recognize changes or even new folder scans. The Read Metadata from Photo option simply erases the changes that were made in external programs - it seems to read ON1's information and then write that into the XMP (which Photo Mechanic picks up INSTANTLY, incidentally). I am willing to wait 20 seconds for an image to load to edit, but that is IMPOSSIBLY slow for culling and selecting. I am also disappointed to see this in the support thread from 4 years ago… evidently that means ON1 is not an option for my professional use as they have no intention of addressing this issue. Very disappointed as the editing part of the program is excellent.
0 -
Kevin, you may not be aware that these forums are meant for user to user help and tech support does not monitor them or respond here. The people you are talking to are just other users like yourself. If you want to contact tech support use the Submit a Request link at the top and bottom of these pages or from the Help menu within the program.
0 -
Already did that, Brian. Before I ever commented on the forums. Thanks.
0
Please sign in to leave a comment.
Comments
9 comments