Problem as to how MP writes xmp data to sidecars.
I noticed that Media Pro has a problem with writing xmp data. I have a collection of photos with keywords already entered very carefully as standard hierarchical keywords with the vertical pipe separator. All other software that I tested reads them perfectly including the new Media Pro. However, if you attempt to make any changes such as a basic label color change, and then write back to the xmp side car file, instead of merging and only writing the changes, MP creates a whole new xmp side car file with all of the original data gone, except for a few fields that MP creates. AND, it does not write back the hierarchical keywords, even if the correct menu selection is made. FYI, I use nef files and selected only write to XMP side car files and tried clicking on all of the write options, and also clicking all of them off. Same out come either way.
This basically makes MP almost worthless except to just look at the files, organize them, etc. But, any organizational information cannot be easily transferred back out so other software can see it without ruining your previous xmp data.
Speaking of label color changes, I did notice that MP only writes the label color reference to the urgency field. Very few programs read the urgency field as the color label anymore. Most use the xmp color label name field. It does this despite giving the option in annotations to call the field color label rather than urgency. If you make the annotation choice of IPTC core, it label in MP shows the word Label rather them Urgency, but MP still writes number to the urgency field. BUT, this is small potatoes compared to the general XMP write problem mentioned above.
I use Windows 7 pro 64 bit vs. with Intel 930 chip, if that make a difference.
This basically makes MP almost worthless except to just look at the files, organize them, etc. But, any organizational information cannot be easily transferred back out so other software can see it without ruining your previous xmp data.
Speaking of label color changes, I did notice that MP only writes the label color reference to the urgency field. Very few programs read the urgency field as the color label anymore. Most use the xmp color label name field. It does this despite giving the option in annotations to call the field color label rather than urgency. If you make the annotation choice of IPTC core, it label in MP shows the word Label rather them Urgency, but MP still writes number to the urgency field. BUT, this is small potatoes compared to the general XMP write problem mentioned above.
I use Windows 7 pro 64 bit vs. with Intel 930 chip, if that make a difference.
0
-
I, too, noticed this on a Mac (MP 1.0.1). No heir. keywords seem to be written to the XMP sidecar file (ever). Whenever 'synching' back to a sidecar or creating a new one, XMP file ends up screwed, not 'synched.' (Yes, I chose to output heir. keywords in the sync dialog.)
Larry0 -
YOUCH! Not good at all.... 0 -
Here is what I get when exporting to XMP and embedding into a JPEG (no pre-existing meta data in JPEG; bottom of text file ended up with last tags </x:xmpmeta> and <?xpacket end="w"?> clipped):
http://dl.dropbox.com/u/6317362/mp/XMP_HKeywords-notExporting_8bA.png
And here is the embedded meta data in the JPEG read by Photoshop (after removing generated XMP from being read):
http://dl.dropbox.com/u/6317362/mp/Photoshop_FileInfo-AnnotateEmbed_8bA.png
So, no hier. keywords exported to XMP, but they are outputted to the embedded lightroom.hierarchicalSubject container. Keywords, catalog sets (nested), etc. seem to be generated correctly within the XMP.
Have not fully tested with pre-existing meta data, since our workflow is usually writing out fresh meta data.
Larry0
投稿コメントは受け付けていません。
コメント
3件のコメント