iMatch xmp and Capture One

badkar_ · October 17, 2015, 01:57:08 PM

So i'm new to iMatch and are trying to set it up. I think it has come down to this: iMatch can read the xmp files that C1 creates but C1 can't read all of the xmp iMatch wrights. This means that when I do adjustments in C1 they will come through to iMatch. But if I do changes in iMatch, C1 will try to sync and then it doesn't understand the xmp and rewrites it with the C1 one version. So it doesn't matter if I have C1 running or not, as soon as I start C1 it will rewrite all the xmp and then everything I have done in iMatch will disappear. I could tell C1 to not sync the xmp but that kind of defeat the purpose.
They can share some info like rating but not much more.

Here is an original xmp from C1 without iMatch touching it:

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP Core 4.4.0">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:xmp="http://ns.adobe.com/xap/1.0/"
xmlns:exif="http://ns.adobe.com/exif/1.0/"
xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
xmlns:xmpRights="http://ns.adobe.com/xap/1.0/rights/"
xmp:CreateDate="2014-09-18T09:54:00.68"
xmp:CreatorTool="NIKON D810 Ver.1.01 "
xmp:Label="Green"
xmp:Rating="0"
exif:ExifVersion="0221"
exif:GPSVersionID="2.3.0.0"
photoshop:Urgency="0"
photoshop:DateCreated="2014-09-18T09:54:00+02:00"
photoshop:LegacyIPTCDigest="6BD675A1D210207538D6FA543E483B8F">
<dc:creator>
<rdf:Seq>
<rdf:li>Viktor Andersson</rdf:li>
</rdf:Seq>
</dc:creator>
<dc:rights>
<rdf:Alt>
<rdf:li xml:lang="x-default">Viktor Andersson</rdf:li>
</rdf:Alt>
</dc:rights>
<Iptc4xmpCore:CreatorContactInfo
Iptc4xmpCore:CiAdrExtadr="Via alpsu 43"
Iptc4xmpCore:CiAdrCity="Disentis"
Iptc4xmpCore:CiAdrRegion="GR"
Iptc4xmpCore:CiAdrPcode="7180"
Iptc4xmpCore:CiAdrCtry="Switzerland"
Iptc4xmpCore:CiTelWork="+41 76 22 63 243"
Iptc4xmpCore:CiEmailWork="studio@single-pixel.com"
Iptc4xmpCore:CiUrlWork="single-pixel.com"/>
<xmpRights:UsageTerms>
<rdf:Alt>
<rdf:li xml:lang="x-default">All rights reserved</rdf:li>
</rdf:Alt>
</xmpRights:UsageTerms>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

and here is one from iMatch after adjustments:

<x:xmpmeta xmlns:x='adobe:ns:meta/' x:xmptk='Image::ExifTool 9.99'>
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>

<rdf:Description rdf:about=''
xmlns:Iptc4xmpCore='http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/'>
<Iptc4xmpCore:CreatorContactInfo rdf:parseType='Resource'>
<Iptc4xmpCore:CiAdrCity>Disentis</Iptc4xmpCore:CiAdrCity>
<Iptc4xmpCore:CiAdrCtry>Switzerland</Iptc4xmpCore:CiAdrCtry>
<Iptc4xmpCore:CiAdrExtadr>Via alpsu 43</Iptc4xmpCore:CiAdrExtadr>
<Iptc4xmpCore:CiAdrPcode>7180</Iptc4xmpCore:CiAdrPcode>
<Iptc4xmpCore:CiAdrRegion>GR</Iptc4xmpCore:CiAdrRegion>
<Iptc4xmpCore:CiEmailWork>studio@single-pixel.com</Iptc4xmpCore:CiEmailWork>
<Iptc4xmpCore:CiTelWork>+41 76 22 63 243</Iptc4xmpCore:CiTelWork>
<Iptc4xmpCore:CiUrlWork>single-pixel.com</Iptc4xmpCore:CiUrlWork>
</Iptc4xmpCore:CreatorContactInfo>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:MicrosoftPhoto='http://ns.microsoft.com/photo/1.0'>
<MicrosoftPhoto:Rating>50</MicrosoftPhoto:Rating>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:aux='http://ns.adobe.com/exif/1.0/aux/'>
<aux:Lens>35mm f/2.0</aux:Lens>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:dc='http://purl.org/dc/elements/1.1/'>
<dc:creator>
<rdf:Seq>
<rdf:li>Viktor Andersson</rdf:li>
</rdf:Seq>
</dc:creator>
<dc:rights>
<rdf:Alt>
<rdf:li xml:lang='x-default'>Viktor Andersson</rdf:li>
</rdf:Alt>
</dc:rights>
<dc:subject>
<rdf:Bag>
<rdf:li>Natur</rdf:li>
</rdf:Bag>
</dc:subject>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:exif='http://ns.adobe.com/exif/1.0/'>
<exif:ApertureValue>4970854/1000000</exif:ApertureValue>
<exif:Contrast>0</exif:Contrast>
<exif:CustomRendered>0</exif:CustomRendered>
<exif:DateTimeOriginal>2014-09-18T09:54:00</exif:DateTimeOriginal>
<exif:DigitalZoomRatio>1/1</exif:DigitalZoomRatio>
<exif:ExifVersion>0221</exif:ExifVersion>
<exif:ExposureBiasValue>0/1</exif:ExposureBiasValue>
<exif:ExposureMode>1</exif:ExposureMode>
<exif:ExposureProgram>1</exif:ExposureProgram>
<exif:ExposureTime>1/320</exif:ExposureTime>
<exif:FNumber>56/10</exif:FNumber>
<exif:FileSource>3</exif:FileSource>
<exif:Flash rdf:parseType='Resource'>
<exif:Fired>False</exif:Fired>
<exif:Function>False</exif:Function>
<exif:Mode>2</exif:Mode>
<exif:RedEyeMode>False</exif:RedEyeMode>
<exif:Return>0</exif:Return>
</exif:Flash>
<exif:FocalLength>35/1</exif:FocalLength>
<exif:FocalLengthIn35mmFilm>35</exif:FocalLengthIn35mmFilm>
<exif:GPSVersionID>2.3.0.0</exif:GPSVersionID>
<exif:GainControl>1</exif:GainControl>
<exif:ISOSpeedRatings>
<rdf:Seq>
<rdf:li>400</rdf:li>
</rdf:Seq>
</exif:ISOSpeedRatings>
<exif:LightSource>0</exif:LightSource>
<exif:MaxApertureValue>2/1</exif:MaxApertureValue>
<exif:MeteringMode>5</exif:MeteringMode>
<exif:Saturation>0</exif:Saturation>
<exif:SceneCaptureType>0</exif:SceneCaptureType>
<exif:SceneType>1</exif:SceneType>
<exif:SensingMethod>2</exif:SensingMethod>
<exif:Sharpness>0</exif:Sharpness>
<exif:ShutterSpeedValue>8321928/1000000</exif:ShutterSpeedValue>
<exif:SubjectDistanceRange>0</exif:SubjectDistanceRange>
<exif:UserComment>
<rdf:Alt>
<rdf:li xml:lang='x-default'/>
</rdf:Alt>
</exif:UserComment>
<exif:WhiteBalance>0</exif:WhiteBalance>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:exifEX='http://cipa.jp/exif/1.0/'>
<exifEX:SensitivityType>2</exifEX:SensitivityType>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:lr='http://ns.adobe.com/lightroom/1.0/'>
<lr:hierarchicalSubject>
<rdf:Bag>
<rdf:li>Natur</rdf:li>
</rdf:Bag>
</lr:hierarchicalSubject>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>
<photoshop:DateCreated>2014-09-18T09:54:00.68</photoshop:DateCreated>
<photoshop:LegacyIPTCDigest>1A6A1720EEF3F98EFF387222CA4A717B</photoshop:LegacyIPTCDigest>
<photoshop:SidecarForExtension>NEF</photoshop:SidecarForExtension>
<photoshop:Urgency>0</photoshop:Urgency>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:tiff='http://ns.adobe.com/tiff/1.0/'>
<tiff:BitsPerSample>
<rdf:Seq>
<rdf:li>14</rdf:li>
</rdf:Seq>
</tiff:BitsPerSample>
<tiff:Compression>34713</tiff:Compression>
<tiff:ImageLength>4928</tiff:ImageLength>
<tiff:ImageWidth>7380</tiff:ImageWidth>
<tiff:Make>NIKON CORPORATION</tiff:Make>
<tiff:Model>NIKON D810</tiff:Model>
<tiff:Orientation>1</tiff:Orientation>
<tiff:PhotometricInterpretation>32803</tiff:PhotometricInterpretation>
<tiff:PlanarConfiguration>1</tiff:PlanarConfiguration>
<tiff:ReferenceBlackWhite>
<rdf:Seq>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
</rdf:Seq>
</tiff:ReferenceBlackWhite>
<tiff:ResolutionUnit>2</tiff:ResolutionUnit>
<tiff:SamplesPerPixel>1</tiff:SamplesPerPixel>
<tiff:XResolution>300/1</tiff:XResolution>
<tiff:YCbCrPositioning>2</tiff:YCbCrPositioning>
<tiff:YResolution>300/1</tiff:YResolution>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:xmp='http://ns.adobe.com/xap/1.0/'>
<xmp:CreateDate>2014-09-18T09:54:00.68</xmp:CreateDate>
<xmp:CreatorTool>photools.com IMatch 5.4.0.17 Trial Version (Windows)</xmp:CreatorTool>
<xmp:Label>Yellow</xmp:Label>
<xmp:MetadataDate>2015-10-17T13:07:38+02:00</xmp:MetadataDate>
<xmp:ModifyDate>2015-10-17T13:07:38+02:00</xmp:ModifyDate>
<xmp:Rating>2</xmp:Rating>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:xmpMM='http://ns.adobe.com/xap/1.0/mm/'>
<xmpMM:DocumentID>xmp.did:de574979-4518-4197-9aad-bf9e82863875</xmpMM:DocumentID>
<xmpMM:InstanceID>xmp.iid:19950a35-b876-4e94-891d-44f686426ffc</xmpMM:InstanceID>
<xmpMM:OriginalDocumentID>xmp.did:de574979-4518-4197-9aad-bf9e82863875</xmpMM:OriginalDocumentID>
</rdf:Description>

<rdf:Description rdf:about=''
xmlns:xmpRights='http://ns.adobe.com/xap/1.0/rights/'>
<xmpRights:UsageTerms>
<rdf:Alt>
<rdf:li xml:lang='x-default'>All rights reserved</rdf:li>
</rdf:Alt>
</xmpRights:UsageTerms>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

and at last when C1 opens and rewrites the xmp:

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP Core 4.4.0">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:MicrosoftPhoto="http://ns.microsoft.com/photo/1.0"
xmlns:aux="http://ns.adobe.com/exif/1.0/aux/"
xmlns:exif="http://ns.adobe.com/exif/1.0/"
xmlns:exifEX="http://cipa.jp/exif/1.0/"
xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
xmlns:tiff="http://ns.adobe.com/tiff/1.0/"
xmlns:xmp="http://ns.adobe.com/xap/1.0/"
xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xmpRights="http://ns.adobe.com/xap/1.0/rights/"
xmlns:lightroom="http://ns.adobe.com/lightroom/1.0/"
MicrosoftPhoto:Rating="50"
aux:Lens="35mm f/2.0"
exif:ApertureValue="4970854/1000000"
exif:Contrast="0"
exif:CustomRendered="0"
exif:DateTimeOriginal="2014-09-18T09:54:00"
exif:DigitalZoomRatio="1/1"
exif:ExifVersion="0221"
exif:ExposureBiasValue="0/1"
exif:ExposureMode="1"
exif:ExposureProgram="1"
exif:ExposureTime="1/320"
exif:FNumber="56/10"
exif:FileSource="3"
exif:FocalLength="35/1"
exif:FocalLengthIn35mmFilm="35"
exif:GPSVersionID="2.3.0.0"
exif:GainControl="1"
exif:LightSource="0"
exif:MaxApertureValue="2/1"
exif:MeteringMode="5"
exif:Saturation="0"
exif:SceneCaptureType="0"
exif:SceneType="1"
exif:SensingMethod="2"
exif:Sharpness="0"
exif:ShutterSpeedValue="8321928/1000000"
exif:SubjectDistanceRange="0"
exif:WhiteBalance="0"
exifEX:SensitivityType="2"
photoshop:DateCreated="2014-09-18T09:54:00.68"
photoshop:LegacyIPTCDigest="3A9972222BF1AC1E200ADE272605425C"
photoshop:SidecarForExtension="NEF"
photoshop:Urgency="2"
tiff:Compression="34713"
tiff:ImageLength="4928"
tiff:ImageWidth="7380"
tiff:Make="NIKON CORPORATION"
tiff:Model="NIKON D810"
tiff:Orientation="1"
tiff:PhotometricInterpretation="32803"
tiff:PlanarConfiguration="1"
tiff:ResolutionUnit="2"
tiff:SamplesPerPixel="1"
tiff:XResolution="300/1"
tiff:YCbCrPositioning="2"
tiff:YResolution="300/1"
xmp:CreateDate="2014-09-18T09:54:00.68"
xmp:CreatorTool="photools.com IMatch 5.4.0.17 Trial Version (Windows)"
xmp:Label="Green"
xmp:MetadataDate="2015-10-17T13:07:38+02:00"
xmp:ModifyDate="2015-10-17T13:07:38+02:00"
xmp:Rating="1"
xmpMM:DocumentID="xmp.did:de574979-4518-4197-9aad-bf9e82863875"
xmpMM:InstanceID="xmp.iid:19950a35-b876-4e94-891d-44f686426ffc"
xmpMM:OriginalDocumentID="xmp.did:de574979-4518-4197-9aad-bf9e82863875">
<exif:Flash
exif:Fired="False"
exif:Function="False"
exif:Mode="2"
exif:RedEyeMode="False"
exif:Return="0"/>
<exif:ISOSpeedRatings>
<rdf:Seq>
<rdf:li>400</rdf:li>
</rdf:Seq>
</exif:ISOSpeedRatings>
<exif:UserComment>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</exif:UserComment>
<tiff:BitsPerSample>
<rdf:Seq>
<rdf:li>14</rdf:li>
</rdf:Seq>
</tiff:BitsPerSample>
<tiff:ReferenceBlackWhite>
<rdf:Seq>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
<rdf:li>0/1</rdf:li>
<rdf:li>255/1</rdf:li>
</rdf:Seq>
</tiff:ReferenceBlackWhite>
<Iptc4xmpCore:CreatorContactInfo
Iptc4xmpCore:CiAdrCity="Disentis"
Iptc4xmpCore:CiAdrCtry="Switzerland"
Iptc4xmpCore:CiAdrExtadr="Via alpsu 43"
Iptc4xmpCore:CiAdrPcode="7180"
Iptc4xmpCore:CiAdrRegion="GR"
Iptc4xmpCore:CiEmailWork="studio@single-pixel.com"
Iptc4xmpCore:CiTelWork="+41 76 22 63 243"
Iptc4xmpCore:CiUrlWork="single-pixel.com"/>
<dc:subject>
<rdf:Bag>
<rdf:li>Natur</rdf:li>
</rdf:Bag>
</dc:subject>
<dc:creator>
<rdf:Seq>
<rdf:li>Viktor Andersson</rdf:li>
</rdf:Seq>
</dc:creator>
<dc:rights>
<rdf:Alt>
<rdf:li xml:lang="x-default">Viktor Andersson</rdf:li>
</rdf:Alt>
</dc:rights>
<xmpRights:UsageTerms>
<rdf:Alt>
<rdf:li xml:lang="x-default">All rights reserved</rdf:li>
</rdf:Alt>
</xmpRights:UsageTerms>
<lightroom:hierarchicalSubject>
<rdf:Bag>
<rdf:li>Natur</rdf:li>
</rdf:Bag>
</lightroom:hierarchicalSubject>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

Note how for example how the programs fight over the label. But C1 will always end on to. So Labels and Keywords cant really be changed. Because it will always revert back to C1. Can I tell iMatch to output metadata so that C1 can read it?

Mario · October 17, 2015, 03:46:28 PM

IMatch creates XMP data using ExifTool, the reference in Metadata Processing. ExifTool produces complete, high-quality and fully XMP standard compliant metadata. There is nothing better.

I know that many C1 users use IMatch and so far I'm unaware of any problems caused by the metadata created.
For example, I don't see why IMatch should change the label. Does the label you have entered in C1 show up in IMatch? Do you change the label in IMatch?

Does your NEF file perhaps contain an XMP record in addition to the XMP in the sidecar file? C1 may ignore that, but IMatch will use it. By default XMP metadata embedded in the image gets precedence over XMP data found in an XMP sidecar.

You can check if your NEF file contains XMP metadata (perhaps with a yellow label?) in IMatch using the ExifTool Command Processor. Select a NEF in the fiel window, go to Tools > ExifTool Command Processor. Select the "List Metadata" from the drop-down at the top and run it by pressing the "Run" button. If XMP data shows up on the right, your NEF file has embedded XMP data, and this will explain your findings.

badkar_ · October 17, 2015, 04:22:01 PM

So maybe I was a bit unclear. iMatch reads the files correctly. I do an edit in iMatch, change the Label to Yellow. Now when I open C1 it doesn't seem to be able to read the Yellow Label so it just rewrites the Label back to the last one used in C1, in this case Green. And as you see the xmp's are definitely build in a different way. Not saying that iMatch does anything wrong, I just try to get my head around Metadata, xmp, raw and so on. What is the best solution? Just learn to work around it? Or can I actually do something about it.

How can I check if the raw data has metadata written to it? I don't think C1 does this since if I set C1 not to read xmp files, nothing shows. Rating, label, keyword and so on.

And an other question that I find interesting. C1 seams to write metadata in an instant, iMatch takes at least 30 sec or more updating the metadata panel, why is this?

Mario · October 17, 2015, 08:11:27 PM

IMatch by default postpones write-backs to files. If a file has pending metadata, a pen icon is displayed in the file window. Click the pen to write-back the metadata for all selected files. Or use the commands available in the Commands menu.

For details, please type write back into the index tab in the IMatch help system. Then open the help topic via the Metadata entry in the result list. The help topic explains how IMatch writes metadata, why it by default updates metadata only in the database, how you configure IMatch to write-back metadata immediately etc.

IMatch also does a bit more with metadata than C1, for example it ensures that your metadata is properly synchronized between all standards as recommended by the Metadata Working Group. And IMatch uses ExifTool to read and write metadata, for best possible quality.

The typical update time for one of my NEF files is less than 1 second. Maybe 1.5 if the metadata is written for the first time and ExifTool has to splice the file and re-combine it. I don't know why it takes 30 seconds on your system to update metadata.

Please provide mode details, e.g. a debug log file.
See How to report bugs and problems for more information.

This article in the IMatch knowledge base may also be of interest. It's about Lightroom and IMatch, but the same principles apply to C1. If you work with multiple applications on the same files and the metadata contained within, it is important to make sure that all applications write the metadata to the files immediately. IMatch can do that of course.

badkar_ · October 18, 2015, 03:24:36 AM

Hi, maybe 20 sec was a bit much but it atleast 10-15sec. This affects all files as far as I tried it. Updating metadata makes iMatch very sluggish, I almost stops. And updating more files takes for ever. But it never crashes. This is the Output when changing Text in matadata:

-overwrite_original_in_place
-charset
FILENAME=UTF8
-m
-use
MWG
-charset
ExifTool={PTETCHARSET}
-ex
-tagsfromfile
D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.NEF
-@
C:\Program Files (x86)\photools.com\IMatch5\arg_files\exif2xmp.args
--Exif:rating
-@
C:\Program Files (x86)\photools.com\IMatch5\arg_files\iptc2xmp.args
-@
C:\Program Files (x86)\photools.com\IMatch5\arg_files\gps2xmp.args
-sep

-XMP-lr:HierarchicalSubject=
-XMP-dc:Subject=
-XMP-lr:HierarchicalSubject=dgf
-XMP-dc:Description-x-default=sdfgsdfg
-XMP-tiff:ImageDescription-x-default=sdfgsdfg
-XMP-exif:UserComment-x-default=sdfgsdfg
-XMP-dc:Subject=dgf
-XMP-photoshop:CaptionWriter=sdfg
-XMP-photoshop:Credit=gg
-XMP-photoshop:Headline=sdfg
-XMP-photoshop:Instructions=sdfgsdfgsdfgsdfg
-XMP-photoshop:TransmissionReference=sdfgsdfg
-XMP:CreatorTool=photools.com IMatch 5.4.0.17 Trial Version (Windows)

-xmp:InstanceID=xmp.iid:ee23b2ec-2f4d-4e6c-b2bf-8a4ea7506e45

-XMP:MetadataDate=now
-XMP:ModifyDate=now
D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.xmp
-execute
-overwrite_original_in_place
-charset
FILENAME=UTF8
-m
-EXIF:ImageDescription=
-EXIF:Software=
-EXIF:Copyright=
-EXIF:Artist=
-EXIF:UserComment=
-IFD0:ModifyDate=
-IFD0:Rating=
-IFD0:ImageDescription=
-IFD0:Software=
-IFD0:Copyright=
-IFD0:Artist=
-IFD0:XPTitle=
-IFD0:XPComment=
-IFD0:XPAuthor=
-IFD0:XPKeywords=
-IFD0:XPSubject=
-GPS:all=
-tagsfromfile
D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.xmp
-@
C:\Program Files (x86)\photools.com\IMatch5\arg_files\xmp2exif.args
-@
C:\Program Files (x86)\photools.com\IMatch5\arg_files\xmp2gps.args

D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.NEF
-execute9999

1 image files updated

1 image files updated

and this is when I change rating:

----- Runtime: 0,3 s.
Warning: Error converting value for ExifIFD:SubSecTime (ValueConvInv) - D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.xmp
-overwrite_original_in_place
-charset
FILENAME=UTF8
-m
-use
MWG
-charset
ExifTool={PTETCHARSET}
-ex
-sep

-XMP-xmp:Rating=3
-XMP:CreatorTool=photools.com IMatch 5.4.0.17 Trial Version (Windows)

-xmp:InstanceID=xmp.iid:9cbe4547-d253-46db-bb2a-cb2a02aed9d0

-XMP:MetadataDate=now
-XMP:ModifyDate=now
D:\Downloads\2014-09 Stockholm\Capture\_DSC0519.xmp
-execute
-execute9999

1 image files updated

----- Runtime: 0,1 s.

what happens is that the metadata menu gets grayed out for 10-15 sec and it says Updating... with big letters.

Mario · October 18, 2015, 07:29:49 AM

The ExifTool output you have posted says

----- Runtime: 0,1 s.

which means that it took 1/10 of a second to write the data. Not 10. So the time is spent elsewhere.

I asked for an IMatch log file (see my info above) so we can see what else IMatch is doing.

When you write back metadata, IMatch updates not only the XMP file, but also synchronizes changes back into the NEF file itself (Metadata Working Group compliance, synching XMP, IPTC, EXIF, GPS etc.) And then it re-imports the file into your database. Depending on how you have configured things like data-driven categories, collections, if you run metadata templates or complex file relation and version rules, this step may take longer than writing to the file. And of course it also depends on your computer, the disks involved.

Without an IMatch log file (in Debug mode please, Help menu > Support > Debug Logging) and a bit more info from you we can only guess what you do, what takes so long etc. The ExifTool output dump is rather useless in this case.

After enabling the logging, change data for maybe 10 of your files, then write back. Then copy the log file and switch back to normal logging. This will show us how long ET needs for each file, what else is going on, which other steps are performed and take how long, if your database has 20,000 or 300,000 files, etc. Please also include information about how many data-driven categories you have, if you run metadata templates on file import, if you have created file relations or version rules, if you have set IMatch to produce cache files on-demand or always etc. All this affects how long IMatch takes to write and read files.

Please do not just copy and paste the IMatch log file in your post like you did above with the large amount of XMP data. This not only makes your posts very hard to read but also fills the community search engine with lots of useless data. Save the log file to disk (there is a command for that in the Help help menu and attach it to your reply. Thanks. The Attachment function is directly below the post editor.

badkar_ · October 18, 2015, 11:24:07 AM

Hi, Here is the Debug log file. I got an SSD drive. When I made changes to more photos it was faster this time, just as fast as one photo. It wasn't like that yesterday.
Thanks for all the help

[attachment deleted by admin]

Ferdinand · October 18, 2015, 01:15:59 PM

Quote from: badkar_ on October 17, 2015, 01:57:08 PM
So i'm new to iMatch and are trying to set it up. I think it has come down to this: iMatch can read the xmp files that C1 creates but C1 can't read all of the xmp iMatch wrights. This means that when I do adjustments in C1 they will come through to iMatch. But if I do changes in iMatch, C1 will try to sync and then it doesn't understand the xmp and rewrites it with the C1 one version. So it doesn't matter if I have C1 running or not, as soon as I start C1 it will rewrite all the xmp and then everything I have done in iMatch will disappear. I could tell C1 to not sync the xmp but that kind of defeat the purpose.
They can share some info like rating but not much more.

I can confirm this. If you have C1 configured to full XMP sync, then whatever metadata you input using IMatch before ingesting into C1 will be read by C1. However any metadata you input using using IMatch after ingesting into C1 will not be read by C1. If you have C1 set to full sync then C1 will wipe out the metadata entered using IMatch. My understand is that C1 creates its own store in its own sidecar, and wil always seek to restore it to the xmp sidecar.

The only exception to this is ratings. If you change a rating in IMatch then C1 will immediately read it under full sync.

I think this is a bug in C1, rather than a "feature". The metadata panel has a reload option, but it doesn't reload the xmp. It reloads its own .cos sidecar and then rewrites the xmp sidecar.

However there is a partial solution. If you configure C1 to Load the XMP sidecar but not sync, then C1 will read any metadata changes made by IMatch, once you choose the reload option. There are two exceptions. Rating is still immediately synced. And label is never reimported, no matter what you do.

So Load is mostly a solution. This is workable because it's generally good practice to make all metadata changes in IMatch, although the label bug is really annoying because that's what you'd most like to send back to C1. The only way that I can find to do that is delete the .cos C1 sidecar, but then you lose any edit settings.

This is all a C1 bug in my view, because LR has no problem exchanging metadata with IMatch, provided that you reload XMP in one program after changing it in the other. The C1 problem is not an IMatch problem in the slightest.

If you haven't seen this, here are my recommendations for C1 buddy file definitions:
https://www.photools.com/community/index.php?topic=2407.0

markkums · October 18, 2015, 01:22:42 PM

Hi there,

I think I partly recognize problems with C1. I have used C1 since its C1 Pro 6 version. At that time I also had their Media Pro DAM software, but it was really miserable experience due its instability and, finally, I swapped to iMacth (3 at that time). Now I see some inconsistencies (ranking info not transferred in all images) in transferring ranking from iMatch to C1 and nothing else (user modified metadata) can be transferred at all (

?)

I continued to use C1 in following workflow in order to avoid miscommunication between softwares:
-I manage my images in iMatch and by ranks I show and select those for post processing. I have C1 icon in Favorities panel.
-I filter set of images (by a rank) for post processing and drag them all into C1 icon in Favorities (C1 must be running)
-C1 will display selected images (nothing else in a same folder)
-I do post processing in C1 and use its commands to save resulting jpgs into a subfolder of that particular forder having originals.

I do not see overwriting by C1 in xmp maybe as I have removed automatic sync in C1 preferences.

So, this is very limited but currently only way I can use these softwares parallel.

B.r: Markku

badkar_ · October 18, 2015, 01:52:36 PM

OK, I guess I also realized it is all C1. To bad C1 is such a good raw converter which makes me really want to use it. Everything else with it is a mess, full of bugs, I never used a software that I have been in contact with support so much as C1. I really think they should remove proffessional from their advertisements since they are not professional at all when it comes to realising stable and functional software.
Thank for the help.

Ferdinand · October 18, 2015, 02:05:11 PM

It's a good converter, in terms of its results and editing abilities. Like LR/ACR, they assume that you use nothing else. They really want you to use C1 catalogs, which are not compatible with IMatch at all. At least sessions are partly compatible.

You can use it with IMatch if use sessions and if you know how it behaves and how to adapt to its behaviour. The thing I really hate is all those subfolders its sessions create. I always delete the cache subfolder when I've finished. I think the idea of a distributed cache rather than centralised cache is crazy!

The general rule of a DAM is to make all metadata changes in a DAM. The only exception I make to this sometimes is ratings. If you do that they there aren't a lot of issues. Markkums suggestion to only send selected images to C1 via an IMatch favourite is a good one in my view.

badkar_ · October 18, 2015, 04:00:13 PM

Do you just keep the raw file imported in Daminion or do you export a tiff copy to see the changes you made?

Menace · October 18, 2015, 06:00:03 PM

Quote from: Ferdinand on October 18, 2015, 01:15:59 PM
However there is a partial solution. If you configure C1 to Load the XMP sidecar but not sync, then C1 will read any metadata changes made by IMatch, once you choose the reload option.

Thank you, Ferdinand. This sounds not bad.

If we want to change something in C1, we should also write them by creating a support ticked. If enough people are complaining, maybe the change something and/or complaining in their forum. I have no problem with C1, because I don't use the DAM-Part in C1.

RalfC · October 18, 2015, 06:25:18 PM

Quote from: Ferdinand on October 18, 2015, 02:05:11 PM
The thing I really hate is all those subfolders its sessions create. I always delete the cache subfolder when I've finished. I think the idea of a distributed cache rather than centralised cache is crazy!

To my understanding:
C1 uses only a cached image for most of its activities while you work on an image. (100% view, processing and exporting do read/need the original raw-file).
Additionally, all metadata is kept in the catalog until processing / exporting.

I think that their point of having the cache distributed, is the fact that it makes it easy to give the complete session (including the development data, previews etc.) as one package by just copying/zipping the session's folders...

Anyhow, I agree that it can be a pain to have a raw converter who also wants to manage the images (or vice versa). The needed compromises might just be too big.

Imatch is spezialized on managing [and soon viewing/printing?] and gives a lot of possibilities to adjust it to the preferred way of working. (And I am quite sure that Mario is happy that he does not have to maintain raw converters

)

Regards,
Ralf