xmp output has less data than txt output

[Archive]

[Originally posted by wski on 2008-05-28 20:52:37-07]

I have enjoyed using exiftool and find it very useful.

I am having some trouble figuring out how to do a recent usage I came up with.
I have tried various parameters with Windows stand alone 7.27 version can't seem to get all the items reported when using -w txt to show up in xmp.  Working with Nikon raw so lots of info in there.  

Have used:

exiftool -o out.xpm in.nef

exiftool -TagsFromFile in.nef out.xmp

exiftool -TagsFromFile in.nef "-all&ltxmp:all" out.xmp

        by the way examples show single quote for line above, but I was getting errors.

Have I missed a parameter, is it a limitation of xmp???

Doing some stages of image processing and would to carry everything in sidecar files until last stage.

Thanks

Cliff

[Archive]

[Originally posted by wski on 2008-05-28 21:58:57-07]

In following example I made error in converting it to html, should have been "&gt" not "&lt":

exiftool -TagsFromFile in.nef "-all&ltxmp:all" out.xmp

[Archive]

[Originally posted by exiftool on 2008-05-28 23:43:02-07]

The XMP page in the Tag Names documentation shows what
can currently be written to XMP.  With what you have done,
only the tags with names that exist in XMP will be written.
It is possible with exiftool to add user-defined tags to
XMP, but this would be tedious to say the least if you want
to store all of the information from the maker notes.

If you want to store the meta information for later recovery,
you should use a .MIE sidecar file with "-tagsfromfile -all:all".
The MIE file type supports storage of all meta information in
its native format so no information is lost (other than the
PreviewImage, which you need to copy separately if you want
to keep it).

- Phil

[Archive]

[Originally posted by wski on 2008-05-29 02:57:03-07]

Phil,

Thanks.  I will go the .MIE sidecar route, it will get the job done.

Cliff

[Archive]

[Originally posted by wski on 2008-05-29 03:36:21-07]

I have tried the .mie and it looks good except for one of the fields I am using.
The field "Bits Per Sample" is not getting copied with the "-TagsFromFile -all:all" you mentioned.  Nor does it end up in BitDepth field, seemed like a close match in MIE tag docs.   If afterwards I copy just Bits Per Sample to the mie file it gets added as a Bits Per Sample field with correct value.

Cliff

[Archive]

[Originally posted by exiftool on 2008-05-29 10:57:33-07]

Hi Cliff,

ExifTool protects any tag that could effect the way an image is rendered.
You will see these tags marked by an exclamation point in the Writable
column of the tag name documentation.  After after you are done your
image processing, your image processing software should write the
BitsPerSample, ImageWidth, ImageHeight, YCbCrPositioning, etc that are
applicable to the new image, and these should not be overwritten when
copying the meta information back from the MIE file.  So by default, exiftool
does not copy these tags when you specify -all:all.  If you really want,
they can be specified explicitly (ie. "-all:all -exif:bitspersample"), but I
would recommend against it.

- Phil

[Archive]

[Originally posted by wski on 2008-05-29 17:47:30-07]

Hi Phil,

Thanks.  I will use the override, in my case I need the value in the sidecar. Sorry I missed that exclamation point detail, reading too fast.  I am using dcraw for my front end to output the linear raw to a tiff.  The format of the tiff is 16 bits and it is just the container while the camera data contained may be 10, 12, 14, or ? bits.  Some of the image processing I am doing is easier if number of bits contained is known.  Understand the warning, at first thought I could use your tool to overwrite just BitPerSample exif tag (12bit) in the tiff file while leaving tiff tag (16bit) untouched, but your design is smart enough not to create conflicting settings, so I think it changed the tiff tag which made the file unusable until I switched it back.  The sidecar is the best way for me, just have to pay attention to image file data structure verses actual data.

Must say exiftool has excellent design to provide flexiblity for esoteric uses like this.

Thanks again.

Cliff

[Archive]

[Originally posted by exiftool on 2008-05-29 18:06:52-07]

Hi Cliff,

You say that you were able to make a TIFF image unusable.  This
shouldn't happen unless you specifically change a tag that exiftool
would considers "unsafe".  (Please let me know otherwise!)

I'm glad you appreciate the design:  I attempt to give the expert
user the power to change anything, while preventing the novice
user from damaging images by changing something they shouldn't.

- Phil