??Setting XMP metadata in an image.....Possible with CF??

Hello All:
     Does anyone know if it is possible to write xmp or iptc data to an image using ColdFusion 8?
     I know you can get Exif and iptc data FROM an image but I want to save metadata back TO an image.
     Any Ideas, tutorials, examples?
Thanks in advance!
-Joe

Cool! Thanks Paul, I am checking it out now and it looks to be what I need.
I also found http://jempbox.org/ but it appears no one is working on the project and it did not seem complete.
There appears to also be a comercial Java Library from chilkatsoft.com however I would prefer to not have to pay of course.
-Joe

Similar Messages

Crystal Generated PDFs with XMP Metadata attached to Image

Using Crystal Reports 11 with the .NET runtime. I'm adding images into my document. Those images have XMP metadata attached. However, when the final PDF is generated, I do not see that metadata in the resulting PDF. It seems Crystal Reports is stripping it. How can I get crystal reports to retain the metadata of that image in the resulting PDF document.
(When you open a PDF document in a text viewer, you can see the metadata of the image as well as the metadata for the PDF itself)
(Also I'm adding the image by using the insert image feature. Then I use format graphic to specify the path to that image.)

CR does not export the XMP Metadata into PDF at this time. Perhaps a great suggestion to post in the SAP Idea Place.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Synchronizing IPTC/IIM and XMP metadata in JPEG images

Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
- To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
Moreover, it seems that it does not work regarding to the following simple experiment:
- 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
- 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
- 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
Am I missing or misunderstanding something ?
I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
http://davidcrowell.com/jStrip.aspx
Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
Patrick Peccatte
www.softexperience.com

Excerpt of "IPTC Core Implementation Guidelines", section 2.2.1 available on http://www.iptc.org/IPTC4XMP/:
The basic functionality of this synchronising mechanism [between IPTC/IIM metadata in IRB and XMP metadata] is:
- To move metadata from the IRB to a new XMP packet in case an image file is opened with such an IRB but without an XMP packet. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To move metadata from the XMP packet to a new IRB in case an image file is opened with an XMP packet but without an IRB. If the file is saved both the IRB and the XMP packet will be stored to the header section of this file.
- To update the metadata values of the IRB respectively the XMP packet from the newer source to the older destination. Which set is newer or older is detected by a hash value over each block of metadata. (More detailed information is available from Adobes XMP web pages at www.adobe.com/xmp and in the software development kits.)
I have checked for Adobe XMP web site and searched in "XMP Specification, January 2004" and I have not found explanations about this "hash value over each block of metadata" mechanism.
Moreover, it seems that it does not work regarding to the following simple experiment:
- 1. add metadata to a JPEG image using Photoshop CS (which adds both IPTC/IIM data in IRB and data in XMP)
- 2. edit these metadata using an "IPTC/IIM-only and non-XMP-aware" editor like IrfanView, XNView or any other one
- 3. go back to Photoshop CS which displays the "old" XMP metadata ignoring changes done previously using the IPTC-only editor.
Of course this experiment works using an "XMP-aware" editor like iView Media Pro or PixVue in step 2.
So it seems very easy to get images with IPTC/IIM and XMP metadata not synchronized when the image workflow uses different programs to edit metadata.
Am I missing or misunderstanding something ?
I have found a radical method stripping XMP metadata (in a step 2 bis...) using David Crowell's JStrip, see
http://davidcrowell.com/jStrip.aspx
Do you know any other best method to keep IPTC/IIM and XPM data synchronized when an image workflow uses different metadata editors and some of them are not XMP-aware ?
Patrick Peccatte
www.softexperience.com

Import XMP Metadata Kills My Image Edits

I imported a batch of JPGs from a recent trip and happily used LR to rank them, add labels and adjust them in the Develop module. Later, when LR was not running, I used another program to modify some of the embedded meta data in these JPGs (in particular the dates).
On my next visit to LR I used the Import XMP Metadata From File command, hoping to get LR to recognize the modified dates. This turned out to be a big mistake. All my previous ranking, labeling and developing was lost. Oh dear.
I guess I was under the impression that the Import XMP Metadata From File command would synchronize the metadata in the files with the metadata in the database. It appears to have simply replaced the database values with what was in the file. So is this a bug or did I just misunderstand the feature?

Last history state? See
Loading metadata resets Develop settings.
>I can go back to Develop and "back up" because the history is all there, but this would have to be done file by file,
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.8 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

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.

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;

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

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.

[CS3 JS] Possible to Inspect Custom XMP Metadata With JavaScript?

I am using custom XMP metadata in InCopy and InDesign docs in CS3 to hold custom metadata that can vary wildly. I know the full set of possible items but not what values will be in a particular document.
Short of writing the XMP to a file and then processing that from my script, is there a way to inspect the custom properties from JavaScript. I didn't see a way to do it from the data model.
Thanks,
Eliot

Here is another script to catch MetaData, some more than the basic:
// metaDataOfLinks.jsx
//DESCRIPTION: Catches MetaData of linked images and creates a report at the DeskTop.
// Martin Fischer 10/2008
var myLinkXmpArray = ["author", "copyrightInfoURL", "copyrightNotice", "copyrightStatus   ", "creationDate", "creator", "description", "documentTitle", "format", "jobName", "keywords", "modificationDate", "serverURL"];
var myIPTCArray = ["CiAdrCity", "CiAdrCtry", "CiAdrExtadr", "CiAdrPcode", "CiAdrRegion", "CiEmailWork", "CiTelWork", "City", "CiUrlWork", "CopyrightNotice", "Country", "CountryCode", "Creator", "CreatorContactInfo", "CreatorJobtitle", "DateCreated", "Description", "DescriptionWriter", "Headline", "Instructions", "IntellectualGenre", "JobID", "Keywords", "Location", "Provider", "Province-State", "RightsUsageTerms", "Scene", "Source", "SubjectCode", "Title"];
var myPSArray = ["photoshop:AuthorsPosition", "photoshop:CaptionWriter", "photoshop:Category", "photoshop:City", "photoshop:Country", "photoshop:Credit", "photoshop:DateCreated", "photoshop:Headline", "photoshop:Instructions", "photoshop:Source", "photoshop:State", "photoshop:SupplementalCategories", "photoshop:TransmissionReference", "photoshop:Urgency"];//var myPSArray = ["photoshop:AuthorsPosition", "CaptionWriter", "Category", "City", "Country", "Credit", "DateCreated", "Headline", "Instructions", "Source", "State", "SupplementalCategories", "TransmissionReference", "Urgency"];
var myTiffArray = ["tiff:ImageWidth", "tiff:ImageLength", "tiff:BitsPerSample", "tiff:Compression", "tiff:PhotometricInterpretation", "tiff:Orientation", "tiff:SamplesPerPixel", "tiff:PlanarConfiguration", "tiff:YCbCrSubSampling", "tiff:YCbCrPositioning", "tiff:XResolution", "tiff:YResolution", "tiff:ResolutionUnit", "tiff:TransferFunction", "tiff:WhitePoint", "tiff:PrimaryChromaticities", "tiff:YCbCrCoefficients", "tiff:ReferenceBlackWhite", "tiff:DateTime", "tiff:ImageDescription", "tiff:MakeProperName", "tiff:Model", "tiff:Software", "tiff:Artist", "tiff:Copyright"];
var myExifArray = ["exif:ExifVersion", "exif:FlashpixVersion", "exif:ColorSpace", "exif:ComponentsConfiguration", "exif:CompressedBitsPerPixel", "exif:PixelXDimension", "exif:PixelYDimension", "exif:UserComment", "exif:RelatedSoundFile", "exif:DateTimeOriginal", "exif:DateTimeDigitized", "exif:ExposureTime", "exif:FNumber", "exif:ExposureProgram", "exif:SpectralSensitivity", "exif:ISOSpeedRatings", "exif:OECF", "exif:ShutterSpeedValue", "exif:ApertureValue", "exif:BrightnessValue", "exif:ExposureBiasValue", "exif:MaxApertureValue", "exif:SubjectDistance", "exif:MeteringMode", "exif:LightSource", "exif:Flash", "exif:FocalLength", "exif:SubjectArea", "exif:FlashEnergy", "exif:SpatialFrequencyResponse", "exif:FocalPlaneXResolution", "exif:FocalPlaneYResolution", "exif:FocalPlaneResolutionUnit", "exif:SubjectLocation", "exif:ExposureIndex", "exif:SensingMethod", "exif:FileSource", "exif:SceneType", "exif:CFAPattern", "exif:CustomRendered", "exif:ExposureMode", "exif:WhiteBalance", "exif:DigitalZoomRatio", "exif:FocalLengthIn35mmFilm", "exif:SceneCaptureType", "exif:GainControl", "exif:Contrast", "exif:Saturation", "exif:Sharpness", "exif:DeviceSettingDescription", "exif:SubjectDistanceRange", "exif:ImageUniqueID", "exif:GPSVersionID", "exif:GPSLatitude", "exif:GPSLongitude", "exif:GPSAltitudeRef", "exif:GPSAltitude", "exif:GPSTimeStamp", "exif:DateTimeOriginal,", "exif:DateTimeDigitized.", "exif:GPSTimeStamp", "exif:GPSSatellites", "exif:GPSStatus", "exif:GPSMeasureMode", "exif:GPSDOP", "exif:GPSSpeedRef", "exif:GPSSpeed", "exif:GPSTrackRef", "exif:GPSTrack", "exif:GPSImgDirectionRef", "exif:GPSImgDirection", "exif:GPSMapDatum", "exif:GPSDestLatitude", "exif:GPSDestLongitude", "exif:GPSDestBearingRef", "exif:GPSDestBearing", "exif:GPSDestDistanceRef", "exif:GPSDestDistance", "exif:GPSProcessingMethod", "exif:GPSAreaInformation"];
var myCameraRawArray = ["crs:AutoBrightness", "crs:AutoContrast", "crs:AutoExposure", "crs:AutoShadows", "crs:BlueHue", "crs:BlueSaturation", "crs:Brightness", "crs:CameraProfile", "crs:ChromaticAberrationB", "crs:ChromaticAberrationR", "crs:ColorNoiseReduction", "crs:Contrast", "crs:CropTop", "crs:CropLeft", "crs:CropBottom", "crs:CropRight", "crs:CropAngle", "crs:CropWidth", "crs:CropHeight", "crs:CropUnits", "crs:Exposure", "crs:GreenHue", "crs:GreenSaturation", "crs:HasCrop", "crs:HasSettings", "crs:LuminanceSmoothing", "crs:RawFileName", "crs:RedHue", "crs:RedSaturation", "crs:Saturation", "crs:Shadows", "crs:ShadowTint", "crs:Sharpness", "crs:Temperature", "crs:Tint", "crs:ToneCurve", "crs:ToneCurveName", "crs:Version", "crs:VignetteAmount", "crs:VignetteMidpoint", "crs:WhiteBalance"];
var myInfo = new Array;
var myDoc = app.activeDocument;
var myLinks = app.documents[0].links;
for ( i = 0; i < myLinks.length; i++)
   getMetaData ( myLinks[i] );
writeData ( 'Metadaten zu ' + myDoc.name + '\r-----------\r\r' + myInfo.join ( '\r\r'), File ('~/Desktop/Metadaten_' + myDoc.name.replace(/.indd$/, '') + '.txt'));
// ===============================================================
//                                  Funktionen
// ===============================================================
function getMetaData ( aLink )
   var myLinkXmp = aLink.linkXmp.properties.toSource().replace( /^$\{/,'' ).replace (/$\}$/,'').replace( /parent.+$/,'').replace(/:/g, ':\t').split( ', ');
   var myString = aLink.name;
   myString += loopLinkXmp ( aLink, myLinkXmpArray );
   myString += loopArray ( aLink, "http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/", "Iptc4xmpCore:CreatorContactInfo/Iptc4xmpCore:", myIPTCArray);
   myString += loopArray ( aLink, "http://ns.adobe.com/photoshop/1.0/", "", myPSArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/tiff/1.0/", "", myTiffArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/exif/1.0/", "", myExifArray );
   myString += loopArray ( aLink, "http://ns.adobe.com/camera-raw-settings/1.0/", "", myCameraRawArray );
   myInfo.push( myString.replace( /, $/,'') );
function loopArray( aLink, s1, s2, anArray )
   var temp = '\r\t--- ' + s1 + ' ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.getProperty(\"' + s1 + '\", \"' + s2 + anArray[a] + '\")';
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function loopLinkXmp( aLink, anArray )
   var temp = '\r\t--- LinkMetadata ---\r\t';
   for ( var a = 0; a < anArray.length; a++)
      try {
         var theEvalString = 'aLink.linkXmp.' + anArray[a] ;
         var myCode = eval( theEvalString );
         if ( myCode != '' )
            temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
      } catch (e){ //temp +=e + '\r'
   return temp;
function writeData ( aData, theFile )
   theFile.open ( 'w', 'Text', 'R*ch' );
   theFile.encoding = 'UTF-8';
   theFile.write ( aData );
   theFile.close ();
Ressources:
Adobe XMP Developer Center: http://www.adobe.com/devnet/xmp/
XMP Specification: http://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
Martin Fischer

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)

Modify LabelGraphics.js to extract other XMP metadata from images

This script works flawlessly. However, I would like to be able to extract other XMP metadata than just
//XMP description
        case 2:
            try{
                myLabel = myLink.linkXmp.description;
            catch(myError){
                myLabel = "No description available.";
            break;
        //XMP author
        case 3:
            try{
                myLabel = myLink.linkXmp.author
            catch(myError){
                myLabel = "No author available.";
I have developed a custom info panel (based on the generic one) with following "properties.xml":
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
    <xmp_schema prefix="custom0" namespace="http://my.custom0.namespace/" label="$$$/Custom0/Schema/Label=Ref_SAP" description="$$$/Custom0/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        
        <xmp_property name="Ref_SAP" category="external" label="$$$/Custom0/Property/TextInputLabel=Referentie nummer SAP:" type="integer"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom1" namespace="http://my.custom1.namespace/" label="$$$/Custom1/Schema/Label=FRANS" description="$$$/Custom1/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        
        <xmp_property name="Titel_FR" category="external" label="$$$/Custom1/Property/TextInputLabel=Titel FR:" type="text"/>
        <xmp_property name="Tekst_FR" category="external" label="$$$/Custom1/Property/TextInputML_Label=Tekst FR:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom2" namespace="http://my.custom2.namespace/" label="$$$/Custom2/Schema/Label=VLAAMS" description="$$$/Custom2/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        <xmp_property name="Titel_VL" category="external" label="$$$/Custom2/Property/TextInputLabel=Titel VL:" type="text"/>
        <xmp_property name="Tekst_VL" category="external" label="$$$/Custom2/Property/TextInputML_Label=Tekst VL:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
    <xmp_schema prefix="custom3" namespace="http://my.custom3.namespace/" label="$$$/Custom3/Schema/Label=NEDERLANDS" description="$$$/Custom3/Schema/Description=This example panel contains most of the options available for the 'Generic Panel'.">
        <xmp_property name="Titel_NL" category="external" label="$$$/Custom3/Property/TextInputLabel=Titel NL:" type="text"/>
        <xmp_property name="Tekst_NL" category="external" label="$$$/Custom3/Property/TextInputML_Label=Tekst NL:" type="text" ui:multiLine="true" ui:height="100"/>
        <ui:separator/>
    </xmp_schema>
</xmp_definitions>
Now I would like to adapt the LabelGraphics.js to retrieve the information stored in the fields "Titel_FR", "Tekst_FR", "Titel_VL", "Tekst_VL", "Titel_NL", Text_NL". These fields contain fixed text that goes with the image and should be retrieved in several "goes".
Question 1: is this possible at all ?
Question 2: how to proceed ?

Have you already found Marijan Tompa's "Extract Metadata with Adobe XMP"?
David

Exporting/Sharing Custom XMP metadata schema not possible?

I've written a Python script which automatically encodes Quicktime files which I've mastered out of Premiere Pro CC with embedded custom XMP metadata (created using "New Schema" in the Metadata Display panel). I'm using the embedded custom metadata to drive the Python script (e.g. "Spot Title", "Client Name", fields etc etc), which encodes the source QT file to several different formats, based on the delivery specifications of various local TV broadcasters which the encoded files will go to.
Everything about the XMP metadata entry/writing/parsing is fantastic. My only hitch is in the exporting/sharing of the custom metadata schema which I created for this purpose. I would like to roll the schema out to the other editors in our facility, so that they can also enter the XMP metadata on their own systems when they export out master timelines from Premiere.
But unless I'm missing something, I can't figure out a way to "share" or export my custom schema for use on another system. Is this not possible in Premiere Pro CC?

There's no feature for exporting and importing custom schemas, but it's entirely doable. Here are the path to the custom schemas
MAC: Macintosh HD ▸ Users ▸ <username> ▸ Library ▸ Application Support ▸ Adobe ▸ XMP ▸ Custom File Info Panels ▸ 4.0 ▸ custom
WIN: C:\Users\AppData\Roaming\Adobe\XMP\custom file info panels\4.0\panels [I can't vouch for this path as I'm on Mac at the moment and it's been ages since I poked around for custom schemas, but this should at least be the right neighborhood.]
You might also be interested in sharing your custom metadata display profiles. They in Documents ▸ Adobe ▸ Premiere Pro ▸ 8.0 ▸ Profile-mapes ▸ Metadata Preferences.

PDF's with images open with dark (mask) overlay..not true in Explorer...how to change setting?

When browsing in Firefox, some links to PDF's that I open, those with images, open with a dark mask overlay. I have have searched around in the VIEW menu with no luck. This does not happen when I open the same PDF links in Windows Explorer so it must be Firefox setting that I need to change. By the way, I have Adobe Creative Suite 4 installed on my computer.

When browsing in Firefox, some links to PDF's that I open, those with images, open with a dark mask overlay. I have have searched around in the VIEW menu with no luck. This does not happen when I open the same PDF links in Windows Explorer so it must be Firefox setting that I need to change. By the way, I have Adobe Creative Suite 4 installed on my computer.

My client with autism needs to be able to speak/sing into a microphone and simultaneously hear his voice through a headset, preferably with reverb set on high. Is it possible to do this with the iPad and OS7? If so, what setup do I need?

My client with autism needs to be able to speak/sing into a microphone and simultaneously hear his voice through a headset, preferably with reverb set on high. Is it possible to do this with the iPad and OS7? If so, what setup do I need? I have a SM58 type mic and-over-the ear headphones.

This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

Have been trying to export versions to a friend in the UK as JPEG. He receives them as bmp and no Metadata. Tried all the JPEG settings in Image Export with no success.

Have been trying to export "versions to a friend in the UK as JPEG. He reseives them as bmp with no Metedata. Have tried all the JPEG settings in Image export with no success.
Nelson

Ernie-
Thanks for responding...but still have a oroblem. Here's what I'm doing:
In Aperture I choose a "version" that has been Adjusted (croped, etc.).
- Go to "File"...'Export"..."Version"
- In next window for "Export preset" I choose "JPEG-Fit within 1024x1024"
- Click on "Export version"
The exported version then showes up in "Finder" under "Pictures"
- Next I open "Mail" (version 5.2)
- Adderss email to friends in England.
- Click on attachment (paper clip)
- Choose my "version" from "pictures"
- Back in Mail, click on "Format"..."Make Plain Text"
- Send
My friends receive it as "bmp", not JPEG, with no Metadata.
If I do the same procedure but under "File" choose "Export Master", they receive it as JPEG and also the Metadata.....BUT, of course, no Adjustments, such as croping, that were made to the "Version".
What am I doing wrong? Is there any way to save the "Version" as a "Master" and then send it as a "Master"?
Thanks,
Nelson

??Setting XMP metadata in an image.....Possible with CF??

Similar Messages

Maybe you are looking for