XMP metadata to manage ad copy ?

I'm currently looking for a solution to manage ad copy and I'd like to explore the viable use of XMP metadata to do so.
I've created custom XMP pallets I can edit through Bridge but what happens when my packaging is updated and my image is deleted and replaced by another? All of my XMP metadata is lost and I have to re-enter it?
Is there any way to store all of my XMP in a separate file to allow me to replace the image without losing my XMP data?
Any insight would be appreciated!
Thanks

The short term solution is to export an XMP "Template" (right arrow in upper right corner) from each of the current images with systematic file names (.xmp). Each is a standalone copy of the XMP packet. You probably need to edit this down to the significant metadata for your application, deleting the camera-specific and date-specific metadata. When an image is replaced, the corresponding Template can be imported and appended to the new file's XMP.
If you are careful, you could edit metadata prior to template export via the Advanced panel, and then Cancel out of the File Info Window after the export, or not Save the changes to the image file.
A longer term solution would be to save the metadata in an external database, referenced by an assigned Ad Copy ID field. The user would be required to enter the Ad Copy ID field into the replacement image, and then it would be used to populate the other fields from the database. This is feasible with Pound Hill's MetaGrove Plug-ins for CS3, and with File Info CS4 fully custom panels.
Regards,
Carl Rambert

Similar Messages

Copy existing clip data to XMP Metadata

Hi, after looking on the forums and reading the Adobe Premiere Pro Metadata manual, I discovered that when entering Metadata in the clip data field you need to have the little link box checked next to the clip data field in order to have that metadata follow that clip to whatever project you import it into in the future. However, I discovered this after entering clip data for hundreds of clips and would like to know if there is a way to link the information I already entered into the clip data field to the XMP metadata so I don't have to do it all over again for every clip. The manual only says that clicking the link does NOT copy over existing clip data, but does not say whether or not there is a way to do this. Any suggestions?

Hi,
MattJayC wrote:
Its running into an error.
error "Can’t make «class cfol» \"Submissions\" of «class cfol» \"Zoom\" of «class cfol» \"Brands\" of «class cdis» \"DCKGEN\" of application \"Finder\" into type list, record or text." number -1700 from «class cfol» "Submissions" of «class cfol» "Zoom" of «class cfol» "Brands" of «class cdis» "DCKGEN" to list, record or text
Because sourceFolder and targetFolder are Finder items --> folder "Submissions" of folder "Zoom" of folder "Brands" of disk "DCKGEN".
You must first convert the path to make the coercion (the path and the name), like this : ((sourceFolder as text) & eachFile)
But this call the the Finder each time.
It's best to convert the variables only once :
set sourceFolder to sourceFolder as string
set targetFolder to targetFolder as string
-- now loop though the files
repeat with eachFile in newFiles
But it may have other consequences if these variables are used later in the script
So I recommend to use other variables, like this :
set sFolder1 to sourceFolder as string -- convert Finder item to text and put it in another variable
set tFolder2 to targetFolder as string
-- now loop though the files
repeat with eachFile in newFiles
-- convert the filenames to posix paths that the shell can handle
set srcFile to quoted form of POSIX path of (sFolder1 & eachFile)
set destFile to quoted form of POSIX path of (tFolder2 & eachFile)
-- and cat the data, removing the files as you go
do shell script "cat " & srcFile & " >> " & destFile & " && rm " & srcFile
end repeat

"Writing XMP Metadata Did Not Complete Successfully" Issue

Hi all,
I've been using Lightroom for a bit now. I'm on V2.5 now. I just did a new system build and so reinstalled Win Vista 32. My photos and XMP files are on a seperate external drive and I saved my catalog file (plus did a backup). When I reinstall Lightroom and did the updates I then copied the old catalog 2 file to the right location. All my pics were there with edits no problem. I've done this several times now when I have had to reinstall the OS for various reasons. Never had an isuse
This time I went back to change some status data on a photo that I took before the reinstall. When I went to update the metadata I get a message that says "Writing XMP Metadata Did Not Complete Successfully". I looked in Bridge and the data did not update. This happens for all my RAW photos that were taken before the reinstall. I can make changes fine but cannot get the XMP to write.
Bridge will not make changes either. I tried changing the star rating and color label and it does nothing.
For files that I have imported after the reinstall it all works fine.
It is like the old XMPs are locked or the programs can't find them. I can see them in the file manager so they are all there.
Any ideas on the problem and how to fix it?

I don't think they are locked. I think Vista is just blocking Lightroom. I went back this morning and deleted a few of the xmp's as you suggested and Lightroom worked fine and wrote the files. Then I thought about the potential lock issue and tried opening Lightroom "As an administrator". When I did that everything worked fine. For some reason Vista won't let lightroom open the older files unless it sees it as the admin. All works fine now. Thanks!!
Glenn

Viewing XMP Metadata in Adobe Bridge via Adobe Drive Connector

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

How can I get Adobe Bridge to show XMP metadata using Adobe Drive 4 CMIS Connector?

I have successfully connected to an Alfresco Enterprise Edition 4.1.0 repository, using the Adobe Drive 4, created a test folder and uploaded a jpeg file containing XMP metadata into it.
When I view the image's metadata (using Adobe Bridge), I observe that only part the standard file properties are displayed.
When I view a local copy of the image using the same, I see all fields of the standard file properties plus available metadata.
My question: what should I do in Adobe Bridge to be able to see all available XMP metadata?
Kind Regards and Appreciation
Don Greenwood
Pixelboxx GmbH
Dortmund

How did you get through to customer service? They've changed the website and I can't even find phone numbers or a chat button any more.
Here's my story that I posted on discussion yesterday, but no one has replied:
I am screaming and pulling my hair out right now! The last six months with Adobe has been a nightmare.
Once again I am completely locked out of Creative Cloud and cannot use the apps even though my automatic monthly deduction for payment was just made a couple of days ago. Creative Cloud continues to reset itself to the trial version which runs out in 30 days and after that I am locked out once again.
Now it looks like it is harder to access support than before. Where are chat and the phone numbers now? This was a nightmare with countless hours spent on chat and the phone over the last six months, and now I don't even know how to access support in order to spend even more time that does not solve the problem. What am I to do?
I cannot use the product I have paid for!
Please help!

How do you import (or convert) XMP metadata into iPhoto '08?

Having recently made OS X my primary operating system, I switched from using Picasa/Windows Photo Gallery on Vista to catalogue my photos to iPhoto '08. However, the 7,000+ pictures I have all have XMP metadata tags. None of them show up in iPhoto '08 after import. Needless to say, I am not looking forward to having to retag 7,000+ pictures in iPhoto.
I know people in various forums, here and elsewhere, have said that iPhoto '08 does not do XMP at all. Is this true? Is there a workaround or plugin? I find it weird that XMP has been an open standard since May, and 6 months later, there isn't a plugin or solution, especially from Apple. Unless I am just daft and missing something obvious, which is entirely possible.
At any rate, I would really appreciate any help in me not having to retag over 7,000 pictures...thanks in advance!

mrbofus:
Do you still have the PC and the photos on it? If so you might look into the demo version of iView MediaPro and see it if can read those Picasa files and embed the metadata into the files like it can when reading an iPhoto library on the Mac platform. If it can, you'll be able to write the metadata to the files and bring them over again to the Mac and import into a new library. This is only speculation as I'm not conversant in Windows at all.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Access XMP Metadata outside of Acrobat

Is it possible to access the PDF metadata without using the full version of Acrobat?

An XML packet created with XMP tool kit, which conforms to XMP, can be added to the document level by attaching to the Catalog dictionary. It is also possible to add object level metadata to PDF component represented as a dictionary or stream. In either case, a reserved key Metadata associated with the dictionaries indirectly references the XMP metadata streams. However, in reality, writing XML packet into PDF without using Acrobat APIs, is complicated and requires a good understanding of PDF. The client must handle it cautiously: · construct an XMP conformant XML packet as the document metadata, which is in a writable XML Packet with enough padding provided for the in-place edits and expansion; · synchronize the information in the metadata stream with that in the document information dictionary; · write the XML packet to the right place in PDF; · interpret the multiple versions of XML packet correctly. As recommended in the XMP framework specification, applications should allocate 50% of the XML data size as padding, with a minimum of 4 KB. The purpose is to enable in-place edits and expansion of the embedded XML if the value of the end attribute is set as w in the packet trailer, <?xpacket end='w'?>. In addition, applications that create PDF 1.4 documents (such as Acrobat 5.0) should include the metadata for a document in the document information dictionary as well as in the documents metadata stream. Applications that support PDF 1.4 should check for the existence of a metadata stream and synchronize the information in it with that in the document information dictionary (see Implementation Note 104 on p. 804 of PDF Reference: Third Edition, version 1.4). Moreover, in Acrobat 5.0 (PDF1.4), the document level metadata is constructed automatically from the document information dictionary. However, due to the incremental update mechanism of PDF, it is possible to end up with more than one copy of XML packet in PDF. Whenever the PDF is saved, a new copy of XMP metadata stream will be appended to the cross-reference section, although there may be only one or two properties are changed (i.e., ModDate and MetadataDate). The following PDF sample illustrates the complications. When the PDF was first created, the metadata stream is defined in the object 19 associating with the /Metadata key in the /Catalog dictionary. The value of <xap:MetadataDate> property is 2002-02-11T13:43:24-08:00. When the PDF was saved later, a new XMP metadata packet was appended to the cross-reference section, which associated with the updated entry (/Metadata 21 0 R) in the catalog dictionary. The value of <xap:MetadataDate> property is 2002-02-11T13:46:52-08:00. %PDF-1.4 7 0 obj << /Type /Catalog /Pages 3 0 R /Metadata 19 0 R /PageLabels 2 0 R >> endobj 19 0 obj << /Type /Metadata /Subtype /XML /Length 1338 >> stream <xap:MetadataDate>2002-02-11T13:43:24-08:00</xap:MetadataDate> endstream endobj startxref 7 0 obj << /Type /Catalog /Pages 3 0 R /Metadata 21 0 R /PageLabels 2 0 R >> endobj 21 0 obj << /Type /Metadata /Subtype /XML /Length 1338 >> stream <xap:MetadataDate>2002-02-11T13:46:52-08:00</xap:MetadataDate> endstream endobj xref %%EOF Because of the above complications, Adobe can only support use of the PDF Library and Acrobat SDK plug-in for adding new XMP packets into PDF.

Automating XMP Metadata in Illustrator CS4

How do I use actions or scripting within Illustrator CS4 on the Mac to automatically copy all of the text within an Illustrator pasteboard and paste it into the Keyword XMP Metadata field under File Info.
I've tried Select/Text objects, then Copy (Cmd-C), File Info (Shift-Cmd-Opt-I), Paste (Cmd-V after clicking in the Keyword field), OK.
It works fine manually, but the File Info sequences are not saved in the action.
Thanks for any help I can get.

I guess this is not feasible via Actions, but possible through JavaScripting. You may try that. Hope information helps.

XMP metadata lost in PNG files

Hello,
My XMP metadata is lost from a PNG file if the file is modified and saved. Here is what I am doing
1. Put some metadata in a PNG file using m_xmpFile.OpenFile( FileName, kXMP_PNGFile , kXMPFiles_OpenForUpdate)
2. Edit this file in Photoshop (changed the brightness and contrast of the file)
3. Saved the the modified files.
All my XMP metadata is now lost fromt the file.
is my implementation wrong? Is there some other way to stamp metadata in PNG files?
Thanks,
Hitesh

Info: Mac, Yosemite, Bridge CC
I have an extensive collection of PNG files that HAD been keyworded in Bridge (XMP). I noticed several days ago that the XMP of all those files is now missing.
When attempting to assign keywords back in, I also get the message: "The file ####.png canot store XMP metadata. No changes will occur." Weird. Like you said, it's looking like a bug.
And here's the kicker... if I duplicate the PNG file (Edit > Duplicate), the "copy" DOES contain the original XMP that went missing.
I really don't want to have to manually duplicate all my PNG files just to regain the metadata. Any brainy solution? I'm attaching an example of the original PNG (missing XMP) and the duplicated PNG (magically restored XMP).

XMP metadata generation

is XMP metadata generation only for images, do it support video?
What are the techniques and standards follows for metadata genaration. Is xmp metadata generation is also for videos also. What all are XMP read and write tools.

Hi Sethunath,
>is XMP metadata generation only for images, do it support video?
XMP Metadata is a standard way to describe metadata about any resource in general. “XMP metadata generation” I assume here that by generation you mean = creating or processing or handling of Metadata. Yes, XMP Toolkit SDK , which is a tool to manipulate Metadata, does support different image and video formats. For more information on which file formats it supports please refer to XMP Spec part 3<http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/xmp/pdfs/cc-201306/XM PSpecificationPart3.pdf> .
>What are the techniques and standards follows for metadata genaration. Is xmp metadata generation is also for videos also. What all are XMP read and write tools.
You may want to have a look at XMP developer home to get all the information you need.
http://www.adobe.com/devnet/xmp.html
The page lists different tools to view , handle or manage XMP metadata , and the specifications on which they are based.
Please do let us know in case of questions regarding the technology or the SDKs.
Thanks
Inder

Bridge - "The file cannot store XMP metadata. No changes will occur"

I am trying to use keywords to organize all my projects. But on every file I try to apply a keyword too I get the message "The file cannot store XMP metadata. No changes will occur". I'm on windows 7 64bit with Creative Cloud and all the latest updates.

Not sure what kind of files you are trying to add keywords, but I am having the same problem with .MTS and m2ts files. I am running Bridge 4.0.0.529 and Win 8.1. I found a work around, which was to change the extension to .mpg in File Manager, then you can add keywords. However, not sure of the implications of doing this when I import them into Premiere. I noticed in File Manager that under file properties that the "Type of File" changes to reflect the file extension. Running some tests to try and find out. I suppose one could change the extensions back to the original. But if you have a lot of clips, that is a big hassle. Unfortunately, Bridge "Batch Rename" doesn't allow one to change the extension. Any help would be appreciated. However, I am not very optimistic in that it appears the "Cloud" version of Bridge has the same issues.

Photoshop xmp metadata editing

Adobe xmp metadata in photoshop, is there a way to edit script info so files will show the transactions done on a photograph?
(eg. such as number of times saved, copied, printed, log in time)

Hi,
I do not fully understand which kind of script files you want to show or edit.
You can see all XMP metadata in the "raw packet" view.
To show or edit XMP metadata properties that does not show up on the panels that are delivered with Photoshop,
you have to create a "custom panel" to leverage these properties.
-- Stefan

XMP metadata from Flashbuilder why not visible in Adobe Bridge?

Hi there,
I'm currently wondering around XMP metadata and swf files.
A: Flash CS5: works
When I use the XMP panel in Flash CS5 and export a swf, open Adobe Bridge CS5 and select the file, the XMP data are correctly displayed.
B: Flash Builder(Flex 4.1): don't work
When I use Flashbuilder and add my metadata to the compilation, then compile, open Adobe Bridge CS5 and select the file, nothing is included in metadata.
Procedure based on the following (same problem if metadata are directly set through compiler arguments):
http://livedocs.adobe.com/flex/3/html/help.html?content=compilers_14.html
../src/config/ProductMetaData.xml
<flex-config>
<metadata>
 <title>My title</title>
 <description>My description</description>
 <publisher>The publisher</publisher>
 <creator>The creator</creator>
 <language>EN</language>
</metadata>
</flex-config>
compiler argument
-load-config+=config/ProductMetaData.xml
As far as understood, on the background the following is added to the swf at compile time:
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
 <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
 <dc:format>application/x-shockwave-flash</dc:format>
 <dc:title>My title</dc:title>
 <dc:description>
 <rdf:Alt>
 <rdf:li xml:lang='x-default'>My description</rdf:li>
 </rdf:Alt>
 </dc:description>
 <dc:publisher>The publisher</dc:publisher>
 <dc:creator>The creator</dc:creator>
 <dc:language>EN</dc:language>
 </rdf:Description>
</rdf:RDF>
I've checked that the medata is correctly added to the swf file using this small software polarswf:
http://download.cnet.com/Polar-SWF-MetaData/3000-6676_4-10738623.html
I do not know if it is safe to use it in a produciton context at least in trial mode it allows to check the metadata included in your swf.
I wonder if this metadata coonot be read by Adobe Bridge because they are at a "lower level" than those put by flash CS5 XMP panel?
Thank you in advance for your help.
This is not a blocking situation, but I'm curious to understand what happend.
Cedric Madelaine (aka maddec)

I was following this post for a LONG time, since I noticed the same problem.
This week I was getting in it into myself again and I noticed you use load-config. I used these compiler options :
contributor name
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
creator name
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
date text
Sets metadata in the resulting SWF file. For more information, see Adding metadata to SWF files.
But that resulted in this XML string where the dc namespace was missing a / on the end of the URI
That caused the metadata which was added in flashbuilder was only visible in bridge in the rawXML panel, and not the specific fields
changing the URI in http://purl.org/dc/elements/1.1/ did the trick ( did this in bridge by exporting the rawXML, changed the / , and imported it )
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
 <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1'>
 <dc:format>application/x-shockwave-flash</dc:format>
 </rdf:Description>
</rdf:RDF>
Sadly there was no way I could add this / myself everytime.
BUT then I discoverd this option :
raw-metadata XML_string
Defines the metadata for the resulting SWF file. The value of this option overrides any metadata.* compiler options (such as contributor,creator, date, and description).
This is an advanced option.
And you could give the exact RAW XML as you described
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
 <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
 <dc:format>application/x-shockwave-flash</dc:format>
 <dc:title>My title</dc:title>
 <dc:description>
 <rdf:Alt>
 <rdf:li xml:lang='x-default'>My description</rdf:li>
 </rdf:Alt>
 </dc:description>
 <dc:publisher>The publisher</dc:publisher>
 <dc:creator>The creator</dc:creator>
 <dc:language>EN</dc:language>
 </rdf:Description>
</rdf:RDF>
to the compiler. This could also be done in Flash with JSFL.
In the end I wrote an ANT script which injects the exact XMLstring of metadata to Flash and Flex projects by using the raw-metadata parameter in FLEX and JSFL for flash.
Hope this helps

How to get XMP MetaData as an XML String in a process?

Hi there,
I have a process where I would like to export a documents XMP MetaData, manipulate the XMP MetaData and then import the MetaData again to the document.
I thougt first I will use the service Name "XMPUtilityService" with the Service Operation "Export XMP" to export the XMP MetaData as a document.
Hoewer I am not sure how to manipulate the output document from the Export XMP service.
When I print out the document.toString() in a execute Script Service I get the following:
<document state="active" senderVersion="0" persistent="false" senderPersistent="false" passivated="false" senderPassivated="false" deserialized="false" senderHostId="null" callbackId="0" senderCallbackId="0" callbackRef="null" isLocalizable="true" isTransactionBound="false" defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="3440" contentType="null" length="-1"><cacheId/><localBackendId/><globalBackendId/><senderLocalBackendId/><senderGl obalBackendId/><inline><?xpacket begin="ï»¿" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="A...</inline><senderPullServantJndiName/><attributes/></document>
Actually I expected something like this:
<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.0-jc006 DEBUG-1.0, 2009 Jun 23 11:07:21-PDT">
 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
 <rdf:Description rdf:about=""
 xmlns:pdf="http://ns.adobe.com/pdf/1.3/">
 <pdf:Producer>Adobe LiveCycle PDF Generator ES2</pdf:Producer>
 </rdf:Description>
 <rdf:Description rdf:about=""
 xmlns:xmp="http://ns.adobe.com/xap/1.0/">
 <xmp:ModifyDate>2010-04-20T20:43:59+02:00</xmp:ModifyDate>
 <xmp:MetadataDate>2010-04-20T20:43:59+02:00</xmp:MetadataDate>
 </rdf:Description>
 <rdf:Description rdf:about=""
 xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/">
 <xmpMM:DocumentID>uuid:0cf2c6c6-2fba-2b39-5fb6-33ad8ccf58aa</xmpMM:DocumentID>
 <xmpMM:InstanceID>uuid:187bc5a2-acb0-2fa9-711d-33ad8ccf58aa</xmpMM:InstanceID>
 </rdf:Description>
 </rdf:RDF>
</x:xmpmeta>
<?xpacket end="w"?>
What do I need to do to get the XMPMeta data as an XML String from a document within a process?
Thanks in advance!
Paul

Hi,
thanks for the answer.
I know that I can retrieve the XMPUtilityMetadata object, but this object provides only access to a few information suche as creator, subject, producer, etc.
However I would like to retrieve the whole XML String of the XMP Metadata.
How is this possible?
Thanks.
Paul

XMP metadata from Premiere Pro

I have installed on Mac OS X:
Extension Builder 3 in Eclipse
Adobe Premiere Pro CC
Adobe ExtendScript Toolkit CC
Working on basic example extension project I want to exchange XMP metadata to/from Adobe Premiere using ExtendScript.
I added line to load XMP library in .jsx file, but it doesn't work:
ExternalObject.AdobeXMPScript = new ExternalObject("lib:AdobeXMPScript");
I also tried to extract AdobeXMPScript.framework file from Adobe Bridge installation package contents, and load it by ExternalObject, but again with no result. It seems environment doesn't know what ExternalObject is.
Is it possible to work with XMP data in extension? If yes, what I need to add/install to make it work?

The XMP data returned by projectItem.getXMPMetadata() contains all marker info for that project item. To confirm this, add some markers containing unique text strings to a clip in Prelude, import it into PPro, then getXMPMetadata() on it; you'll find your text strings in the returned XMP data.
You will need to parse the XMP on your own (or using an XML parser of your choosing), to extract that project item's marker data.
We have a feature request for "XMPScript support in PPro's ExtendScript engine"; I'll add your name to the list.
Feel free to contact me directly regarding any PPro integration development;
bbb at adobe dot com

XMP metadata to manage ad copy ?

Similar Messages

Maybe you are looking for