Ad
Ad
Ad
Pages: [1]   Bottom of Page
Print
Author Topic: Are there metadata problems w/ Aperture3?  (Read 1514 times)
wtlloyd
Full Member
***
Offline Offline

Posts: 126


« on: February 23, 2010, 08:40:36 PM »
ReplyReply

Not trying to troll here, just want to bring attention to comments on Aperture3's metadata conventions. David Riecks Controlled Vocabulary forum is quite good reading for all things Metadata.

Article below discusses possible issues with the way Apple handles some Metadata, and whether programs outside of Aperture may not display all data fields...


http://www.controlledvocabulary.com/imaged.../aperture3.html
Logged
JonRoemer
Full Member
***
Offline Offline

Posts: 131


WWW
« Reply #1 on: February 23, 2010, 09:40:47 PM »
ReplyReply

Quote from: wtlloyd
Not trying to troll here, just want to bring attention to comments on Aperture3's metadata conventions. David Riecks Controlled Vocabulary forum is quite good reading for all things Metadata.

Article below discusses possible issues with the way Apple handles some Metadata, and whether programs outside of Aperture may not display all data fields...


http://www.controlledvocabulary.com/imaged.../aperture3.html

Yes, there is some sort of issue.  In plain english, if you fill in the IPTC metadata in Aperture, export a version of the file (e.g. jpeg, tiff, or psd) and then open the file in Photoshop CS4, not all of the metadata be read or saved if you work on the file in PS.  You would have to reenter the metadata via PS' File Info window.

Apparently Bridge can read more of the metadata (which points to PS and Bridge not working the same way) and the Apple 10.6 OS can read all of the metadata (open a file exported from Aperture in Preview, hit command-I, to see the metadata.)

As David points out there is some question as to what the issue is here - if Apple's jumped the gun with a new standard that's not widely in use yet, if Photoshop hasn't kept pace, or if Apple needs to be more compliant with older versions (probably the latter given that PS is the industry standard).  Regardless though the problem is there.

It could be a bug or or an oversight on Apple's part.

Best way to deal with it, if you use Aperture, is to report it to Apple.  The more who do the quicker they'll deal with it.
« Last Edit: February 23, 2010, 09:43:04 PM by JonRoemer » Logged

Pages: [1]   Top of Page
Print
Jump to:  

Ad
Ad
Ad