Pending Metadata Write-back (2,432) << no images showing, won't go to zero

[photomy]

I do not know when this happened, because I do not write-back metadata every day.  But, I took on the project of getting this number to zero and it was reduced about in half only.  No photos are in the display window, and I do not see any photos with pencil indicator showing.  NO filters on.  Is there a way to clear this out and reset to zero?

Thanks

[JohnZeman]

Menu > Database > Database Tools > Clear Processing Queues

[photomy]

Thanks.  A lot of stuff to know.

[Mario]

Clearing the queue is just a last resort.
When IMatch shows files in the Pending Files collection, they have unwritten metadata.
Clearing the queue will make the files as "written" and IMatch will no longer know which files have unwritten metadata that only exists in the database.

But, I took on the project of getting this number to zero and it was reduced about in half only.

What did you do, exactly? Did you use the one of the Write-back commands from the Commands menu?
Or did you select all the files showing in the "Pending Write-back" collection and clicked then pen?
Or did you just select files in the active file window and clicked the pen?

If IMatch performs write-backs it can hit all kinds of obstacles...

- Files which are currently open and locked in another application.
- Files which are damaged and cannot be written
- A virus checker preventing IMatch from writing to a file
- ...

If something is not working with the write-back, IMatch usually displays displays error messages and adds the yellow warning symbol next to the thumbnail. In all cases, the log file written by IMatch (Help > Support > View Application Log file) is required to figure out what the problem is.

[photomy]

Most of the time I use Collections  - pending writebacks and select images.

Sometimes, when a particular file is open showing images, I will use the pre-made filter, which seems to show the same files - then select images shown.

Normally I use ctl, alt S, or Command in menu.

Not sure what caused the problem.  Most are xmp sidecar files tied to raw images ( raw images are never touched).  I also have some older jpg from a few different cameras - I assume these jpg files would be the problem if there are problem files.  Not too worried about these older files.

Is there a way to override default and use xmp sidecars for problem jpg files?  I assume answer is no.

[Mario]

( raw images are never touched). 

This is not correct. Legacy IPTC data, EXIF and GPS data can only be stored in the RAW file itself. Only XMP data goes into the sidecar file.

Is there a way to override default and use xmp sidecars for problem jpg files?  I assume answer is no.

Yes.
But you don't want this because it would make your JPEG/XMP incompatible with every other application.
If ExifTool really has a problem updating metadata in a JPEG file, the file is most likely corrupted (or at least the metadata in the file).
Re-saving the file in your image editor or first stripping the metadata from the file in the ExifTool Command Processor usually solves this.

[photomy]

( raw images are never touched). 

This is not correct. Legacy IPTC data, EXIF and GPS data can only be stored in the RAW file itself. Only XMP data goes into the sidecar file.

Is there a way to override default and use xmp sidecars for problem jpg files?  I assume answer is no.

Yes.
But you don't want this because it would make your JPEG/XMP incompatible with every other application.
If ExifTool really has a problem updating metadata in a JPEG file, the file is most likely corrupted (or at least the metadata in the file).
Re-saving the file in your image editor or first stripping the metadata from the file in the ExifTool Command Processor usually solves this.

This brings up an important point that is not clear.  Does IMatch put new legacy IPTC data into the raw file automatically when I add basic information ?  I was under the impression once the camera created the raw file, including adding basic EXIF and camera data, perhaps GPS (but not for me), nothing else is written into it unless I instruct for this to occur?  I believe that Nikon no longer writes into NEF files with their software - instead proprietary sidecar files.

IMatch Setting>>

"Configure File Formats"  NEF file

Write IPTC      Yes  << does not say where the write is - raw file or sidecar
Write EXIF      Yes  << does not say where the write is - raw file or sidecar
Allow create IPTC/EXIF/GPS   No
XMP sidecar file       Force XMP sidecar file
Use XMP Crop      No
Use date in THM files      No      

[Mario]

This brings up an important point that is not clear.  Does IMatch put new legacy IPTC data into the raw file automatically when I add basic information ?

As detailed in the help, IMatch updates existing legacy IPTC but does not create legacy IPTC.

[photomy]

I understand.  However, in my case my camera writes just three fields to EXIF that could be changed in camera before the file is created:  1) Artist, 2) whether copyrighted, and a short 3) user comment.  No location information, or other potential classic IPTC fields.

Under normal circumstances, it sounds like I should turn off write to EXIF and turn off write to IPTC.   My goal is to only read from my raw files. I see no reason I would ever need to change metadata in the raw file (again under normal / default circumstances).  Maybe I am confused.

[Mario]

Don't.
If you update EXIF/GPS data in XMP, this data must be synchronized back into the EXIF / GPS record in the RAW. Else you have different values in XMP and EXIF/GPS. And when IMatch has to rescan the file, your XMP changes will be overwritten by the old EXIF/GPS data. But I've explained that all in the help already, so please look there for what MWG is, why IMatch works the way it works and why this is good.

[photomy]

( I posted earlier >> raw images are never touched).

This is not correct. Legacy IPTC data, EXIF and GPS data can only be stored in the RAW file itself. Only XMP data goes into the sidecar file.

Clearly my goal, as for many, is to keep my raw files unchanged if at all possible - this is the only reason I was trying to get clarification. Many people have had problems in the past, including me, of raw files becoming corrupt in some manner - sometimes after metadata has been added.  I believe this is why Nikon made the change they did so that their editing/processing software can only read the raw file - including any metadata.  Of course we keep backup files, but why not operate in a way that eliminates problems.

I believe you said the default is that IMatch only writes into a raw field if there is already data in that particular field.  I do not see any Legacy IPTC data that my camera ever creates except for Artist which IPTC calls Author.  I cannot find any good source online of Legacy IPTC data that might be generated by a camera in a raw file.

The only other fields that I see in raw NEF that might be changed in the future are: User comment, and copyright - but 99% of the time this would not need to occur. Also, if I chose to add GPS data and decided I needed to have it reside in the raw file.  So almost all of the time operating in read-only mode gives peace of mind and is no issue.

The problem behavior you described with the raw file data later writing over the edited xmp, only seems to occur with the following settings:  Config File Format settings for NEF as follows:   Write IPTC > NO  Write EXIF > NO ;  XMP sidecar file > Default .

A Config File Format with no problems/conflicts except if one of the data fields mentioned above is corrected:  XMP sidecar file > Force XMP sidecar file, OR, Favor XMP sidecar file. Then the new xmp file data appears to stay intact in the database and xmp sidcar file. If I need to fix a problem file so "both sides match", I can temporarily go back to default mode - else stay in read-only mode.

SORRY for the lengthy post, and I appreciate the great advice and help there is on this community site - especially Mario.


OKAY- Mario is right (of course)  I will just stay with default.  The good part is I have a better understanding of how these fields piece together.