IMatch XMP Metadata Support
Adobe™ XMP® is a new, versatile meta data standard. Based on a sub-set of XML, all the metadata is kept in text form inside your images or in external so-called sidecar files (with the .XMP extension).
One of the drawbacks of XML, XMP and other text-based formats is that they require a high computation overhead, which makes them "slow" to work with. An image file may contain an XMP record with 100 KB or more data. In order to use or display the information, IMatch has to locate and extract the information from the image file and to process the text to extract the meta data. This process is rather slow.
IMatch 3.5 introduces a proprietary caching technology for XMP metadata. This technology enables IMatch to display and search XMP data with amazing speed.
IMatch extracts the XMP data once from the image or sidecar file and then stores a copy of the data in compressed form inside the database. In addition, IMatch builds an index of the actual XMP contents to make XMP data available for sorting, searching and variables.
IMatch automatically updates the cache when you index new or updated images. If you update XMP in other applications, IMatch will pick up the changes automatically when the folder is rescanned.
Manual Cache Refresh
If required, you can refresh the XMP cache manually via the Tools > XMP > Refresh XMP Cache command. This may be required if another software does not update the timestamp of your files after modifying XMP data, or when you change the XMP options in your database.
This command imports XMP data for the current selection. If you run this command while a folder is selected, it will refresh the cache for all files in the folder. Same for categories. If a thumbnail window is active, the command will refresh the XMP cache for all selected images.
Initially Building the XMP Cache
When you use IMatch 3.5 for the first time, you should create/update the XMP cache for the entire database. The easiest way to do so is to switch to the category view and to select the @All category. Then, run the Refresh XMP Cache command from the Tools > XMP menu.
Before you run this task, make sure tha the XMP options under Options > Preferences > XMP are configured to your requirements. The defaults usually work well.

You can change the XMP settings and any time and refresh the XMP cache using the new settings.
Depending on number of images in your database and the file formats you use, this step can take a while. After the process has finished, your IMatch database contains cached XMP data read from your images and sidecar files. If you have enabled the automatic import of IPTC and EXIF, IMatch has also imported the IPTC and EXIF data in your images into the XMP records in the cache.
You now can fully utilize all the new XMP features in IMatch.
Using XMP data
IMatch allows you to use XMP data everywhere you can use variables. This includes the Contact Sheet Builder, Batch Processor, Smart Renamer, the Property window, thumbnail panels and of course the Slide Show.
In addition, IMatch allows you to search for XMP Data (Search menu > Search for XMP) and to sort images based on XMP metadata (Tools > Sort Presets).
The XMP Editor
To see the XMP data for an image, click on the XMP button in the toolbar above the thumbnail window or press <Shift>+<Alt>+<F12> to open the editor.

The toolbar at the top of the editor allows you to save the XMP to the image/sidecar file (depending on your XMP options) and to load / store the XMP data into XMP files.
On the left you have the field name, on the right the field value. Repeatable fields like keywords or categories show up in indexed form, like Keyword[1], Keyword[2] etc. This is the native XMP syntax and IMatch uses it.
For new images or images which have not yet an XMP record, you can use the IPTC button to insert a standard IPTC XMP template as a start.
If you work with Photoshop® or Brigde® and you have created XMP templates in these applications, you can load them here also.
For information about the meaning of all the XMP fields, please read the documentation from Adobe, available at the Adobe Website.
Since an image can contain hundreds of XMP fields, IMatch uses a hierarchical display. XMP fields are grouped into so-called namespaces. IMatch allows you to fold and unfold these namespaces and saves the state of the namespace automatically. This allows you to hide the information you don't need all the time.
In addition, with the Show fields containing and Show values containing edit fields you can filter the XMP data for specific information.
Updating XMP
XMP is still "new". I admit than I don't understand all aspects of XMP yet, especially when you work with multiple applications. Different applications seem to treat XMP differently. Some applications store application-defined data inside XMP, and only they know what all the fields mean or if you are supposed to change them.
IMatch currently imposes no general restrictions on which fields can be changed or removed. It depends on your specific circumstance and workflow setup if and which fields you edit in XMP. Only some fields are marked as read-only and you cannot edit them.
Note: If you remove the last field in a name space, IMatch will remove the name space too. This is due to a limitation in the Adobe™ XMP toolkit.
Using the right mouse button on a field to open the context menu with additional commands. For several fields that have a relation with an IPTC field, IMatch displays the thesaurus you know from the IPTC Editor in IMatch. You can use elements from the thesaurus and even edit the thesaurus. The changes you make here will automatically show up in the IPTC editor too. On this level, you have a similar workflow in both the IPTC editor in IMatch and also the XMP editor.
Currently, the IPTC editor works only with standard IIM IPTC data. It does not directly update the new IPTC core data available in XMP directly. But when you update the IPTC in your images, IMatch will pick up the changes and import them into XMP automatically.
Loading existing XMP data into the IMatch cache or displaying XMP data in IMatch is save. Updating XMP data may require some extra testing with your other applications to ensure optimal interoperability. I also suggest that you use external sidecar files (.XMP files) instead of changing the XMP record inside you images. You can replace the XMP file at any time without touching the image.
IMatch currently supports embedded (in-image) XMP data for PSD, TIF, JPG, JPEG2000 and DNG files. Sidecar files work for all file formats.
Initial experiments indicate that Adobe™ Bridge seems to ignore sidecar files for image file formats for which it supports embedded XMP data. If you have a JPEG file A.JPG with a sidecar A.XMP file, Bridge will use the embedded XMP file in the JPEG file and also update XMP in the image file, ignoring the external XMP file. I have at least not found a setting that seems to influence this behavior. If you know how this is supposed to work, please let me know.
In order to work together with Bride, allow IMatch to store and load XMP data to/from the image file itself under Options > Preferences > XMP. If you then change a label or rating in Bridge, the change will show up in IMatch automatically. If you change the rating or label or other XMP data in IMatch, Bridge usually only show the change when you purge the cache for the folder holding the image. Sometimes it works without this step, but not always.
Applying XMP Templates
To apply an XMP template to one or more images, use the Apply Template command from the XMP submenu in the Tools or Image menu. This command allows you to import an existing XMP file into the selected image. If you work with Adobe applications or agency systems with XMP support, you usually can reuse existing templates with IMatch.
Pending Updates
For performance reasons, IMatch by default updates only the XMP cache when you change ratings, labels or data in the XMP editor. This means that updates are immediate and fast, even when you update a large number of files at the same time. You can change that under Options > Preferences > XMP.
If you work with other XMP-compliant applications, they won't see the changes until you flush the changes from IMatch into XMP or image files. To do so, use the Process Pending Updates command from the Tools > XMP or Image > XMP menu.
The dialog is pretty self-explanatory. Just press Start to flush the XMP cache into your XMP sidecar or image files (depending on the options you have set under Options > Preferences > XMP).

IMatch can of course only update images currently on-line. If an image cannot be updated, it will be marked in a different color. The Result column contains more information about the reason of the problem
|