XMP metadata for Photo Libraries

I demo lightroom at shows for Adobe and one of the constant gripes I get, and spend a long time trying to convince punters I have no answer for, is that Lightroom doesn't interact at all well with some of the software that photo libraries use. I have never had any exposure to such applications, but I recall one being called Photo Suite.
Apparently the problem is metadata captions do not travel well from Lightroom back to these Photo Library apps. So I have just had a load of photographers over the last few days come to me complaining that they have captioned images in Lightroom, but the captions have not been captured in such a way that they can be read by these library apps.
Can anybody make this happen for these people supplying photos to the libraries, because I feel that suppliers are a little hesitant to use Lightroom fully unless it improves. I can't shed much more light on it than this as I have no experience of any Photo Library software.

I'm not so sure that a lot of image libraries are prepared to ditch their library software. My understanding of it is that the photographers who have the library software - and there seems to be a number of them - are being forced to use the image library software by the image library they are submitting their shots to. If captions aren't being retained, then the shots they are submitting are being rejected by the libraries which is obviously causing a loss of income. Something that causes me a loss of income doesn't get used.
So, by the lack of communication and updating of captions between the apps, photographers are being held back, and I get the feeling the photographers would very much like to use LR and know it is without fail compatible with the image library software.
These captions and changes are apparently being recognised by PSCS3, but not lightroom, so where does the fault lie?

Similar Messages

Is it possible to use markers in a Premiere Pro sequence such as Chapter / Comment / Segmentation and export the XMP metadata for a database so that when the video is used as a Video On-Demand resource, a viewer can do a keyword search and jump to a relat

Is it possible to use markers in a Premiere Pro sequence such as Chapter / Comment / Segmentation and export the XMP metadata for a database so that when the video is used as a Video On-Demand resource, a viewer can do a keyword search and jump to a related point in the video?

take have to take turns
and you have to disable one and enable the other manually

Examples of web photo galleries that display xmp metadata

Hello, I am wondering if anyone knows of an online image gallery that displays xmp metadata for the images displayed?
Thanks,
Bob

Something you may want to consider is DBGallery (http://grrsystems.com/DBGallery). This product stores iptc/xmp data in a MySql database as well as in the image file (using Adobe's XMP Toolkit). Websites can access this data using any number of ways: PHP (google 'accessing mysql with php'), MS Access, and many others. Unfortunately right now there isn't an extremely easy means to access it directly from html like in the sample above: "< div class="content">DESCRIPTION: %FILEINFO% "; although finding someone to put together a little PHP to get close to this easy wouldn't be difficult (elance.com, etc).
DBGallery itself allows that data to be extracted and placed in emails and pdf's (see a sample at http://grrsystems.com/DBGallery/DBGallery_Sample.pdf). It also generates websites with Title and Description, but the websites are fairly basic I'm afraid (see
http://www.grrphotography.com/Collections/WorldPlaces/index.htm)
Dropping any images with iptc/xmp data into DBGallery gets their data into the database because the metadata is automatically read and added to the database.
If there are questions about this option reply here or email me at [email protected]
Best Regards,
Glenn Rogers
Designer of DBGallery: Photo DATAbase System
http://grrsystems.com/DBGallery

How can I read out metadata for captions from a Canon photo

I have to tried to find an answer via Adobe and Google. Still not able to figure out on how to read out XMP metadata for captions out of my photos. Checking the XMP data in InDesign shows info on Camera Make, Exposure etc. But if I use metadata fields from "Caption Setup" like "Camera" the caption shows <No data from link>. Fields where the XMP field name matches (e.g. "Lens") are ok. I need following fields for the caption: Camera Make, Exposure (aperture and speed) and ISO.

Lets keep it simple then.
If I take my utf file generated and open and view it in notepad I can see the accented characters. But if I open it in Wordpad , the accented characetrs are corrupted.
If I then save the file specifiying type Ascii, then the characters are written out correctly.
What I want to do is to be able to write out the file in ascii format without having to open it in utf-mode and then having to save it in ascii.
Ie I want the file to be opened in ascii format
All the characters to be written in Ascii format
But the source is still a unicode database.
I have gone through using convert and characters get lost. In fact, at this stage, I'm not sure its possible to do What I need to do.
Remember I am using an 8 bit character set which is why I have values above 127.
So basically if you take the word 'Annulé'
if I view it in wordpad it displays as
AnnulÃ©
But if I view it in notepad it displays as
'Annulé' which is because notepad detects that the file has a utf-8 character in it.
When I save it as type ascii I can then open it correctly in wordpad.
So I basically want to open this file in Wordpad and have it display Annulé rather than the garbled characters,
without having to go through the process of opening and saving the file as type ansi.

Editing XMP metadata in Bridge for checked-out files?

Our custom connector does not implement the WRITE_XMP_METADATA Capability because we do not want to change the XMP of a file in our DAM system without checking in a new file version.
However, when a file is checked out through Adobe Drive, we would expect to be able to edit its XMP metadata in Bridge just like we can for local files.
It looks like this is still not possible with Adobe Drive 3, i.e. if your connector does not implement the WRITE_XMP_METADATA Capability you cannot edit XMP for checked out files either.
It seems weird that you can edit XMP metadata for checked out files with regular CS applications but not with Bridge. Is this something that is expected to be fixed in a future version?
Thanks

In our design, editing XMP data in Bridge and in regular CS applications is different, the former one will be routed to SetXMPHandler in you connector, in the latter case, CS applications take the normal file writting ways to embed XMP data in the file content.
The purpose of this design is to offer similar user experience for normal users when they edit XMP data for AD assets and local file assets, they don't need to check-out files first.
To address your issue, I think you can add some codes in SetXMPHandler to auto check-out files before real XMP operation, and check-in them before exiting the handler
We will consider to make some enhancements for this part, that's, to allow editng XMP data for the checked-out files in Br, in the next release, thanks for this advice.

[CS3 JS] How to force XMP metadata update for a thumbnail?

Hi Folks,
In a JavaScript in Bridge CS3, I'm updating a value in the XMP metadata for a Thumbnail. Later in the script I want to read the updated XMP metadata information from the Thumbnail, but often Bridge hasn't updated the metadata by the time I read it. In other words, my script reads the value prior to the update. I'm guessing there's a caching issue going on.
I'm new to Bridge scripting, and I am hoping someone here can offer suggestions on how I can (or, even *if* I can) force Bridge to update the XMP metadata cache for a file so that when I read it later in the script it will reflect the recent changes. I've tried using Thumbnail.refresh(), but that doesn't seem to do the trick. I don't mind a slower script, I just want to be able to read the correct value.
Thanks in advance for any help!
-- Jim

Hi David,
I'm running this script on a MacBook Pro, 2.5GHz, 4GB RAM.
Here is a sample JSX that shows the issue I'm having:
#target "bridge-2.0"
main();
function main() {
    if( xmpLib == undefined ) {
        var pathToLib = Folder.startup.fsName + "/AdobeXMPScript.framework";
        var libfile = new File( pathToLib );
        var xmpLib = new ExternalObject("lib:" + pathToLib );
    var myValue = "Headline Test";
    var myFilePath = "~/Desktop/TestFile.tif";
    var curHeadlineStr = XMPGetHeadline(myFilePath);
    $.writeln("Headline value: \"" + curHeadlineStr + "\"");
    XMPWriteHeadline(myFilePath, myValue);
    // *** I would like to refresh the cache here ***
    curHeadlineStr = XMPGetHeadline(myFilePath);
    $.writeln("Headline value: \"" + curHeadlineStr + "\"");
function XMPGetHeadline(theFilePath) {
    var thumb = new Thumbnail(File (theFilePath) );
    md = thumb.synchronousMetadata;
    xmp = new XMPMeta(md.serialize());
    var myHeadlineXMPProp = xmp.getProperty
        (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
    return myHeadlineXMPProp;
function XMPWriteHeadline(theFilePath, theTextStr){
    var thumb = new Thumbnail(File (theFilePath) );
    md = thumb.synchronousMetadata;
    xmp = new XMPMeta(md.serialize());
    var myOrigHeadlineXMPProp = xmp.getProperty
        (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
    xmp.deleteProperty(XMPConst.NS_PHOTOSHOP, "Headline");
    xmp.setProperty(XMPConst.NS_PHOTOSHOP, "Headline", theTextStr, 0, XMPConst.STRING);
    var updatedPacket = xmp.serialize
        (XMPConst.SERIALIZE_OMIT_PACKET_WRAPPER | XMPConst.SERIALIZE_USE_COMPACT_FORMAT);
    thumb.metadata = new Metadata(updatedPacket);
To run this script, in main(), set the myFilePath variable to the path of a file that has an "IPTC Code" "Headline" property.
This script, when run, sets the "Headline" property value to the value of myValue. After runing the script for the first time, take a look at the console log. You should see that Headline value displayed does not change between the two console entries. My log looks like this after the first run:
Headline value: "undefined"
Headline value: "undefined"
The thing is, the second entry in the console listing, above, was created after the Headline value was set by XMPWriteHeadline(). The two values should be different between the two console entries.
If you run the script a second time against the same file, you will see that the Headline value does contain the value that was written in the first run of the script--it just took some time to update the cache, I'm guessing. Here's the second run's log:
Headline value: "Headline Test"
   Headline value: "Headline Test"
So, what I'm looking for is a way to insert code (where the comment line "//*** I would like to refresh the cache here ***" appears), to force Bridge CS3 to refresh its cache so that when I call XMPGetHeadline() after calling XMPWriteHeadline(), the Headline value will return the value that was just written.
I hope this is clear enough...
Thanks!!!!
-- Jim

Can I automate the writing of XMP metadata into JPEG and TIFF files?

I have written an ASP.NET 3.5 website application on behalf of an annual international photographic competition. Entrants will be uploading digital photos in either JPEG or TIFF format. Ideally, I would write entrant identity and image title information into the XMP metadata for each image immediately after upload - but so far, I have failed to find any way to do this in ASP.NET.
Thousands of images are involved, so I need to find a way to automate the metadata insertion, perhaps with some sort of script that uses a text file (extracted from the SQL Server database on my website) as the source of the metadata for a batch of images. Is this the sort of task that can be done by writing a script for Bridge CS3? Are there any scripts already in existence that I could use? I am a total beginner in this area.
I use a Win XP PC, though I have a colleague who, I think, has CS3 on his Mac (running under the Leopard OS), so scripts for either platform might be usable.
David

You are the man X!
Ok here is another version with a check for the dll.
#target bridge
   if( BridgeTalk.appName == "bridge" ) {
addInfo = new MenuElement("command", "Update Entry Details", "at the end of Thumbnail");
addInfo .onSelect = function () {
     main();
function main(){
var csv = File.openDialog("Please select CSV file.","CSV File:*.csv");
if(csv != null){
loadXMPScript();
csv.open("r");
while(!csv.eof){
   strInputLine = csv.readln();
   if (strInputLine.length > 3) {
      strInputLine = strInputLine.replace(/\\/g,'/');
   inputArray = strInputLine.split(",");
   var csvFile = new File(inputArray[0]);
   var title = inputArray[1];
   var author = inputArray[2];
if(!csvFile.exists) {
alert(csvFile + " Does not exist"); //////////Check if file exists
return;
if(csvFile.exists){
var file = new Thumbnail(csvFile);
try{
var xmpFile = new XMPFile(file.path, XMPConst.UNKNOWN,XMPConst.OPEN_FOR_UPDATE);
}catch(e){
      alert("Problem opening xmp for update:-\r" + file.path +"\r" +e.message);
      return;
try{
var xmp = xmpFile.getXMP();
}catch(e){
      alert("Problem opening xmp data:-\r" + e.message);
      return;
xmp.deleteProperty(XMPConst.NS_DC, "creator");
xmp.deleteProperty(XMPConst.NS_DC, "title");
try{
xmp.appendArrayItem(XMPConst.NS_DC, "creator", author, 0,XMPConst.ARRAY_IS_ORDERED);
xmp.appendArrayItem(XMPConst.NS_DC, "title", title, 0,XMPConst.ARRAY_IS_ORDERED);
}catch(e){
      alert("Problem writing xmp data:-\r" + e.message);
      return;
if (xmpFile.canPutXMP(xmp)) {
xmpFile.putXMP(xmp);
}else{
alert("Can not write new metadata to " + csvFile.spec);
xmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY);
unloadXMPScript();
function loadXMPScript()
   var results = new XMPLibMsg("XMPScript Library already loaded", 0, false);
   if (!ExternalObject.AdobeXMPScript)
      try
         ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
         results.message = "XMPScript Library loaded";
      catch (e)
         alert("Could not load AdobeXMPScript \r" + e.message);
         results.message = "ERROR Loading AdobeXMPScript: " + e;
         results.line = e.line;
         results.error = true;
   return results;
function unloadXMPScript()
   var results = new XMPLibMsg("XMPScript Library not loaded", 0, false);
   if( ExternalObject.AdobeXMPScript )
      try
         ExternalObject.AdobeXMPScript.unload();
         ExternalObject.AdobeXMPScript = undefined;
         results.message = "XMPScript Library successfully unloaded";
      catch (e)
         results.message = "ERROR unloading AdobeXMPScript: " + e;
         results.line = e.line;
         results.error = true;
   return results;
function XMPLibMsg (inMessage, inLine, inError)
   this.message = inMessage;
   this.line = inLine;
   this.error = inError;

Problem with Bridge CS4 reading/editing XMP metadata added in Bridge CS6

Please excuse me if this is a dumb/obvious question. I did try searching the forums for similar problems and didn't find anything that seemed to speak to my issue.
I'm having a problem where Bridge CS4 won't read/edit xmp metadata (specifically, keywords and descriptions in the IPTC panel) that I have entered using CS6. it will read some files, not others. The files are all .mp4s. Of these files, I can read/edit IPTC panel metadata for some of them in Bridge CS4; I can add metadata for all of them in CS6. I see no particular pattern in these files to explain what is and isn't read/editable in CS4.
My question is whether this is a compatibility issue between different versions of CS (in this instance, CS4 and CS6). i know it's a tired refrain to blame software when it could easily be user error, in which case I'd be frankly delighted to know what i'm doing wrong. Please bear with me as I give a few more details.
I'm using macs. I've tried this on multiple systems - for instance, on a mac pro 3 which for some reason has both CS4 and CS6 installed, i can add and edit keywords using CS6, but not when using CS4. Again, in CS4, some .mp4 files read/edit, others do not.
Bridge CS4 blames the files and tells me that the selected file cannot store xmp metadata, and that the properties cannot be modified. To be specific, in the metadata panel it says "this property cannot be modified"; in the keyword panel, it says, "This file (zzz.mp4) cannot store xmp metadata. No changes will occur." This seems odd, because I'm able to add xmp metadata for the same files in CS6 on the same computer, and other computers. I know this problem would disappear if all our computers were using CS6 (or CC), but unfortunately that's not a possibility at the moment. Some of them only have CS4.
Computer details (not an exhaustive list, but two instances): mac pro 3.1 running snow leopard, 16GB memory; macbook pro 4.1 running snow leopard, 4GB memory; adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Things I have tried:
Permissions - the files are set to read/write for everyone. Given that I can add/edit metadata in CS6, it doesn't seem to be a permission issue.
Purging the cache - other users seem to have had problems adding metadata in Bridge CS4 where purging the cache for affected files solved the problem. Didn't work in this instance.
Upgrading all affected computers to CS6/CC is beyond my control. I need to figure out why CS4 won't let me read/add/edit xmp metadata, if only for the sake of understanding the broader implications for interoperability.
Any helpful suggestions would be much appreciated.
Thanks,
Kevin

adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Without having experience with mp4 files and metadata my observation is that you certainly have not updated Bridge CS6 ( should be 5.0.2.4) and I believe also not the latest version of CS4, can't imaging this also stayed at .0.0 so first try to update both.
And if CS4 can read the data of some files it should be capable of reading them all. Be sure to have the files completely cached first, can take a while.
Other things to try in CS4 is refresh preferences (hold down option key while restarting Bridge and choose reset prefs).
And also check for hidden cache files using menu view/show hidden files. Sometimes those cache files can be troublesome between versions.
If purge cache did not work and reset prefs also failed consider to also delete Bridge plist file and Bridge cache file manual (from user library)

XMP Schema for WAV files

Hi,
I am planning to use XMP metadata for WAV files and I would like to create a Schema for the same. I know that that XMP has schemas for other Formats like TIFF and EXIF. If there is a XMP schema for WAV already(probably the Adobe Audition uses it), I would like to use it; else, I have to create a custom XMP WAV schema.

Greetings,
Since a WAVE file is actually a simple RIFF file format, I think it should fit into my proposal for embedding XMP data in RIFF files (I already posted it somewhere else in this forum). (For WAVE schemas, thats another story)...
p.s: I have not had any comment from Adobe on this proposal, either they don't read this forum or they don't care...
Comments?
I have the same proposal for IFF files (AIFF/ILBM etc) if you wish to have it?
Here follows the specification:
Embedding XMP data into IBM-Microsoft RIFF file formats
=====================================================================
This proposal permits adding XMP compatible metadata to standard
RIFF files. A RIFF file is composed of chunks of data; each of
the chunks precedeed by a header giving the type of data that
follows, as well as the length of the data in the chunk. For
more information on the RIFF file format, consult the specification
"Multimedia Programming Interface and Data Specifications 1.0"
Including XMP data in an RIFF compatible file is a matter
of adding a subchunk to the INFO LIST chunk. The subchunk
ID for this type of date shall be "IXMP".
Guidelines for RIFF writers
If the XMP packet is to be used, the software can optionally
write out all other INFO LIST registered (from the standard),
assuming the following mapping:
IRSC dc:creator
ICRD dc:date
ICMT dc:description
ICOP dc:rights
IKEY dc:subject
INAM dc:title
IGNR dc:type
IARL dex:source
In the case where they are written, for better validation by reader
software, the XMP packet should also contain the xmp:MetadataDate
property.
For better portability, and to easily modify the embedded
XMP data, the following guidelines should be followed by
the RIFF writer:
- The XMP packet should contain the full packet signature;
this permits easier searching for tools that do not
understand the RIFF file format.
- The XMP packet should be encoded in UTF-8.
- As specified in the XMP specification, an XMP packet
should be filled with blank spaces for easier updating of
the XMP packet without rewriting the entire file.
A suggested size of an XMP chunk is 4096 or 8192 bytes.
- Only one "IXMP" chunk should be present in the INFO LIST
chunk. Preferrably, there should only be one INFO LIST
chunk per file.
Guidelines for RIFF readers
If an XMP packet is present in an RIFF file, then one of
the following options can be used to retrieve the
metadata from the file:
If the existing metadata chunks are also present,
then, one of the following solutions can be used:
a) Compare the xmp:MetadataDate property with the
file modification date to determine which chunk to use
: either the IXMP subchink or the other info subchunks.
(If the file modification date is greater than
xmp:MetadataDate, it is probably safe to assume that
the standard metadata chunks might have been updated
by software that does not
understand XMP packets).
b) Simply ignore these chunks and use the XMP
packet for the metadata.
c) Simply ignore the XMP chunk , and use the
other chunks for getting the metadata of the file.

How to save metadata in .xmp also for .jpgs?

In LR 2.5, I have selected "save the metadata in .xmp files" in the Catalog Settings, and I have NOT selected "include develop settings inside jpeg, tiff, ... I notice however that the metadata is saved in .xmp files only for photos in RAW format (which for me is .ORF, the Olympus RAW format).
In jpegs, the metadata seems to be saved in the jpeg. This is not ideal in my situation, because when I back up photos using rsync (or the time machine), all jpegs where I have modified metadata will be backed up again, causing a lot of data to be backed up, when a tiny .xmp would in fact be enough. Is there a way to ensure that the jpegs per se are not touched, and all information is stored in sidecar .xmp files?
Second question: if I select "store all metadata in xmp", when is this stored? Whenever I make a change? Or do I have to explicitly select the command "save metadata" for a folder?
Many thanks! Luca.

A reason RAWs are the only ones with XMP sidecars and JPGs don't, besides the fact it is easy to save metadata in JPGs compared to RAWs, is that when a camera shoots RAW + JPG both files have the same name except for the extension and so when an XMP with the same name except for the extension exists, it wouldn't be clear whether its metadata was for the RAW or for the JPG.
I am on a PC, so am not sure how TimeMachine works, but a well-done backup stores file differences, not the entire file, for each cycle, and also uses block-checksums to see what parts of the files have changed, so it doesn't need to read the entire backup file, nor store entire files as part of the backup process.
There is a Save Metadata to Files command and there is a Automatically Save Metadata... preference. Either one writes things out to the XMP for RAWs or the image files themselves for formats that support this. I usually have Automatically Save Metadata... enabled but I also explicitly write it out to the files before doing things like purging files off my main work drive and moving them off to a backup device because LR seems to do the Automatic Save Metadata... operation in the background and it's never clear when it is finished.

No metadata in Photo Stream shared libraries

After uploading images to a Photo Stream shared library, I noticed they do not inclue the IPTC caption, keywords and other metadata, making the process virtually useless. All images are referenced files in Aperture 3.4.5, under Mac OS 10.8.4, with "write metadata to masters" applied. How can you include metadata in Photo Stream shared libraries?
Thanks!

Eric,
Now I see - you are asking about "Shared Photo Stream" - I was confused by shared "libraries".
With the "Shared PhotoStream" the only data I am receiving from friends are the EXIF tags - GPS, lens, aperture, etc, none of the IPTC.
When I want to send annotations, I add a comment by pressing the call out badge.
My standard IPTC metedata is also absent after choosing the "Export > Version…" command, and opening the file in the Preview app.
Do you mean, when you are exporting an image from the Photo Straem, or any image? With File > Export > Versions and exporting an image from the library with IPTC as a jpeg, these tags will all show in Previews Inspector.
Grüße
Léonie

When using tethered capture I often get this notification "The metadata for this photo has been changed by both Lightroom and another application". This slows or stalls the loading of incoming photos. How do I find out which other application is changing

When using tethered capture I often get this notification "The metadata for this photo has been changed by both Lightroom and another application". This slows or stalls the loading of incoming photos. How do I find out which other application is changing the metadata and stop it?

Thanks Sean,
I've had a look at the TC settings dialog and tried to keep it as simple as possible. I also had a copy of LR 4 on the hard drive so have trashed that also incase of any conflicts. LR seems to be running ok now but as said it's an intermittent problem.
I also have a copy of Capture One on the hard drive so am going to uninstall that also in case it is trying to launch.

How to setup Sync and Stream for Different Photo Libraries?

I've read through most posts, but still can't get ATV to both sync and stream photos.
On my MBP I have my iTune library with music, movies, etc. I also have several iPhoto libraries for each year ('05, '06 '07, etc). I initially set up ATV to sync to my MBP iTune Library and my iPhoto '07 iPhoto library and everything went fine. Even if ATV->source->my music->photos, I get the photos streamed fine.
The question is how do I stream the other iPhoto libraries? If I go into MBP-> iTunes->Devices->ATV->Photos and deselect sync, I can't select any other Photo Albums and lose the ones I just sync'ed. If I try ATV->source->my itune lib->connect to new iTunes->sync #, but then when I go to MBP-> iTunes->devices->ATV there is no window to insert the # to stream.
What am I missing? Usually Apple is very logical, but this has me stumped. Basically I would like to sync and store my music on ATV, but be able to stream different photo libraries, the photos don't have to be stored on ATV. If I could sync some and stream others that would be better.
Can anyone give me a step-by-step on how to do this? I must be missing a step somewhere. Thx

Welcome to the  Discussion Forums.
It's debatable whether you could ever sync and stream photos from the same library. tv v 1.1 gave that impression because it showed photos in a synced source and a streamed source when the source was the same library. However as they were effectively the same photos it was never really clear what was happening.
Now that synced and streamed content is in the same menu under v 2.0 it really doesn't matter. If your itunes library is synced to your tv then you must sync your photos, if your itunes library is stream only then you must stream your photos.
Moving on, because this doesn't actually address your problem, which is that you want to sync or stream multiple iphoto libraries from the same itunes library. Well you can't, although you have a couple of workarounds.
If you must have multiple libraries, then you could open additional user accounts, stream the itunes libraries in those user accounts and allocate a single library to iphoto under each user account. This is quite messy if you have more than a couple of libraries and will not work with more than 5 libraries, which you may well have if you are working by years.
Your second option and I don't think you'll like it too much is to put all your photos in one library. To be honest I'm not really sure why you split your photos up as you do, I would have thought that iphoto was more than capable of coping with photos from all years.

Custom command for custom XMP metadata

Hi
I'm trying to create a custom command for setting and getting custom XMP metadata using InDesign CS3 SDK with Xcode.
I think I got the step 1) to 3) ok. But not so sure about step 4).
Please take a look and tell me if I have got anything wrong.
1) Create 2 classes and 1 interface
MyCustomMetadata
MyCustomMetadataSetCmd
IMyCustomMetadata
2) Define class definitions in the resource file
/** Boss class for kMyCustomMetadataBoss */
Class
kMyCustomMetadataBoss,
kInvalidClass,
IID_IMYCUSTOMMETADATA, kMyCustomMetadataImpl,
/** Boss class for kMyCustomMetadataSetCmdBoss */
Class
kMyCustomMetadataSetCmdBoss,
kInvalidClass,
IID_ICOMMAND, kIQAdTicketMetaDataSetCmdImpl,
IID_IMYCUSTOMMETADATA, kMyCustomMetadataImpl,
3) Define functions for setting and getting values in MyCustomMetadata
GetMyTitle()
SetMyTitle()
Within these functions, use IMetadataAccess interface to set/get values.
4) Create Do() function in MyCustomMetadataSetCmd
??? I'm not sure what I'm supposed to do here ???
Any help would be really appreciated.
Thanks,
JP

m41miller42 wrote:
I am attempting to create a custom RSS file (.mrss) that references XMP metadata from Premiere.
I was basing the move on this statement. This was posted in the Adobe Connect forums.

Message regarding Metadata for this photo has been changed

We recently transferred from PC to Mac. We now get, over each image, an icon that when you hover over it the message says, "The metadata for this photo has been changed by both Lightroom and another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?" What should our action be please?

Normally, that message indicates that another program has changed the photo's metadata on disk after it was imported into the LR catalog. But sometimes LR generates that message spuriously, i.e. it's a false alarm. In this case, I think it is likely a false alarm, and you should choose Overwrite Settings. However, before you do so, make sure you have a good backup of your catalog, just in case. See Lightroom Help | Back up a catalog for how to make a manual backup of your catalog when LR exits.

XMP metadata for Photo Libraries

Similar Messages

Maybe you are looking for