On 17 Dec 2003, at 17:53, Shangara Singh wrote: > >How else do you interpret his post? If I append metadata to a TIFF, I see no >sidecar XMP file. If I append it to a RAW, I see it. He thinks the appended >data is put into a sidecar XMP file. Either he misread or he's referring to >a RAW. Either way, only he knows.
Rod/Shangara: Actually I was referring to standard TIF and Jpegs, but turns out (after a bit of testing) that I was confusing the operation of Photoshop CS with RAW files and more standard types of files. Short story, the sidecar issue doesn't seem to be an issue with TIFF or Jpeg files, but that's all I've looked at so far. If you are "replacing" metadata it does indeed get placed inside of the image file for both TIFF and Jpeg images. This does take some time if you are doing this to large files however. On the system I was using to test this happened almost immediately for 3 megapixel Jpeg images, but took about 10-12 seconds for an 18 mb TIF, and about 25 seconds for a 55 mb TIF. The results were readable in iView Media Pro 2, iView Media Pro 1.5 (on OS9), as well as within Photoshop 7, and even Photoshop 4! However there is a caution I would thow out for the use of the "Append Metadata" feature as that operation can remove all FILE INFO for legacy TIFF files. I had a couple of TIF files that were saved with versions of photoshop prior to version 7, that had all metadata stripped. The file gave an error message when opened and when trying to access the File Info feature. I'd suggest testing first to be sure. There was no problem using the "replace" metadata feature, however, so that's probably the best way to proceed when in doubt as to how the image was last saved. My guess is that files saved with Photoshop 7 or CS should be fine to "append" metadata to, though I've not tested this exhaustively. Earlier versions of photoshop used the FFO format for storing info within files and I'm guessing it's the lack of the XMP format in these old files that's at issue. There were some other interesting things happening that have implications for those working in larger organizations, or on larger networks. I happened to test this on a colleagues system where he is attached to a large network. When we pulled files from an area of the network where he had "Read Only" access, these files appeared with a "lock" on them when viewed in the file browser of photoshop CS. If we went in to view the files info using the "command+I" "find info" you could see that the file had inherited the permissions from the server as the "unlock" feature was grayed out. You could do a SAVE AS within photoshop, but until you did this you couldn't use the replace or append metadata feature in the file browser on this file. What was more interesting, however, was if he pulled the file from that server (where he had "read only" access) to another volume (where he did have permission to read and write) AND then subsequently dragged a copy of that over to his desktop, it DID NOT have the file marked as read only (and the lock didn't appear when viewing the file in the PS CS file browser). Very odd behavior, but it may have to do with their network configuration. The reason I mention this is because it has implications for being able to use the File browser to replace or append metadata. It stands to reason that if you are trying to add metadata to an image that is on a part of a network to which you only have "read only" access, that you would not be able to do this. But why you shouldn't be able to do this from your own desktop is a bit strange. I certainly hope that's not the case with images on a CDR! All for now. David -- David Riecks (that's "i" before "e", but the "e" is silent) http://www.riecks.com , Chicago Midwest ASMP member http://zillionbucks.com "The Webhost for your Creative Business" =============================================================== GO TO http://www.prodig.org for ~ GUIDELINES ~ un/SUBSCRIBING ~ ITEMS for SALE
