ExtendScript : store XMP / metadatas

Hi,
First of all, please excuse my poor english, hope I'll be understandable.
CS5 - AE 10.0.2.4
OSX 10.6.8
I'm trying to save user datas (ie: production context, batch render options, composition history, statistics ...) with after effects projects, using extendscript routines.
app.settings.get/saveSetting, and app.preferences.get/savePref will store datas at a session level, shared amongst any project a user will open, which is not what I want.
XMP scheme approach seem pretty appropriated, but I can't find a "scriptish" way to manage things. I can create a new scheme and save fields with a project through the metadatas window, but I cannot reproduce this with simple extendscript commands.
I only found an app.project.xmpPacket string reflecting changes made through the interface, but I can't find anything but the basic XML module to edit it, the XMPMeta module described in the documentation is not accessible and seem designed for bridge scripting only.
Any tip about this matter would be greatly appreciated, thanks in advance !
Tonio

Walt,
No, you totally misunderstood what I meant. I'm not talking about LR catalog backups, I'm talking about backing up scores of dng files completely outside of LR, from the OS or some other external tool. With my suggestion, the xmp file would be right next to its dng file, and i would be backing up the whole directory hierarchy that hold my files. One of the benefits of LR over Aperture is that I can access, manipulate, and/or backup my files outside of the app rather than having them locked up in a vault which must be backed up in one huge blob.
If I change the brightness of 500 dng files using LR, then back up all my dng files using rsync (for example), I will be copying 500 large binary files around. If my edits were saved in separate text files (xmp), then my backup program could only copy the DIFF of each of the text files (one line added to each file, so one line, or five in a normal unified diff format, is all that needs copied around). This would be exponentially faster.
Embedded xmp edits is not a good practice, from an OS-level backup point of view. Since not everyone will agree on that, I'm asking for a checkbox option - I'm fine with it being embedded by default.
With xmp data being stored inside the dng file, and LR changing the dng file every time I edit something, LR is hardly non-destructive from an OS-level point of view when dng files are used.
No where in the spec does it state that xmp changes data MUST be stored in the dng file. I'm simply asking for the option to store that data outside of the DNG file, so that the dng file only needs backed up once or rarely, rather than every time I make an edit.

Similar Messages

[CS3] the file cannot store XMP metadata

Hello,
I want to add some metadatas like keywords and description to my video files (raw avi and mpg). It works for most of them in bridge but some will not accept any changes. I get the following error message: "xxx.avi cannot store XMP metadata. No changes will occur." Even so all the video files have been recorded during the same session (no visible differences between the files), some of them work, some do not work.
Do you know a known problem with embemdding XMP into video files? Or if the problem comes from Bridge, how can I do?
Thanks to everyone who could help me.
Steeven
from France

Clear the cache in preferences.

Message: 'FILE CANNOT STORE XMP METADATA'

I have encountered a problem that I cannot resolve by myself and cannot find any relevant information. I hope you can help: In some cases (this has only been happening with my last big job of about 1000 selected images which are divided in subfolders) in most folders when I try to apply a new keyword in an entire group of photographs I get the message ".. the metadata of some of the selected items cannot be changed. Do you want to continue and apply the changes to some of the selected items only?.." whilst when i select individual files (photographs) I get the message ".. the file xxxx.CR2 cannot store XMP metadata. No changes will occur..". This has been happening both before and after the batch rename processing. Also I noticed on my desktop that the RAW files that do not accept keywords are not initially accompanied by an XMP file. I guess that there is a problem with my 'settings' but I cannot located it or resolve it... Can you help please?

..a couple of hours later..
However, if I ReNAME the file which contains the photographs that 'refuse' to have new keywords added to them, IT APPEARS that everything is fixed. After a 'blink' on the screen which resembles with a refresh, I can add the keywords that I desire. Moving the contents of my initial subfolders in one NEW folder does not change the METADATA or the KEYWORD status and so far they are retained when my files are moved to the new folder.
B U T... if I rename the file again (through the Bridge window) and give it its previous name, the problem persists....
-Am I doing something wrong?...since I am not following a different procedure.. why did problem occur out of the blue?
-Will the problem occur again?
-will the Raw files retain the details (keywords/metadata) that I have added from now on?.. or is it possible that I will loose them again at some point?
-why does this happen?

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.

Option to store xmp metadata outside of DNG file

This would serve to improve differential backups, as the xmp file format is text based and easy to tell differences.

Walt,
No, you totally misunderstood what I meant. I'm not talking about LR catalog backups, I'm talking about backing up scores of dng files completely outside of LR, from the OS or some other external tool. With my suggestion, the xmp file would be right next to its dng file, and i would be backing up the whole directory hierarchy that hold my files. One of the benefits of LR over Aperture is that I can access, manipulate, and/or backup my files outside of the app rather than having them locked up in a vault which must be backed up in one huge blob.
If I change the brightness of 500 dng files using LR, then back up all my dng files using rsync (for example), I will be copying 500 large binary files around. If my edits were saved in separate text files (xmp), then my backup program could only copy the DIFF of each of the text files (one line added to each file, so one line, or five in a normal unified diff format, is all that needs copied around). This would be exponentially faster.
Embedded xmp edits is not a good practice, from an OS-level backup point of view. Since not everyone will agree on that, I'm asking for a checkbox option - I'm fine with it being embedded by default.
With xmp data being stored inside the dng file, and LR changing the dng file every time I edit something, LR is hardly non-destructive from an OS-level point of view when dng files are used.
No where in the spec does it state that xmp changes data MUST be stored in the dng file. I'm simply asking for the option to store that data outside of the DNG file, so that the dng file only needs backed up once or rarely, rather than every time I make an edit.

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 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 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

Adobe xmp metadata searchable on osx 10.5 server?

i'm not sure if this is the right category for this. we have 5 mac pro's that are connected to a NAS via Xserver running Mac OS X 10.5.x server. we've started using the xmp funtionality in adobe photoshop. on the 5 local clients, searching via spotlight, we can find files using the info typed in the xmp metadata portion of photoshop. however, when we store that same file on our NAS, searching the nas via the finder search box doesn't recognize the xmp metadata (i'm told we can't use spotlight because it only works on the local machine...even if that's not true, i tried it and it doesn't find the files). all of the local macs are on the same os version (the latest one) and spotlight indexing is enabled on the Xserve. is there a way for the xmp metadata to be searchable when searching the NAS from the local clients?
thanks

Just to let you all know... I came across this now, and will try it out tonight and confirm if it works or not
<key>interface</key>
<string>en0</string>
Using the "interface" keyword instead of "aliasIP"
Hope this works out =D

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

Xmp metadata searchable on mac os x server 10.5.6?

we have 5 mac pro's that are connected to a NAS via Xserve running Mac OS X 10.5.6 server. we've started using the xmp funtionality in adobe photoshop. on the 5 local clients, searching via spotlight, we can find files using the info typed in the xmp metadata portion of photoshop. however, when we store that same file on our NAS, searching the nas from one of the mac pro clients doesn't recognize the xmp metadata. all of the local macs are on the same os version (the latest one) and spotlight indexing is enabled on the Xserve. is there a way for the xmp metadata to be searchable when searching the NAS from the local clients?
thanks

Same issue here. I even tried to import the cert directly into keychain. I did get the certificate to show up in server admin with the correct signed info, but when I assigned a service to the cert. It actually was handing out the old unsigned cert, so I removed it to try again. Now I cannot get the cert back in server admin at all, just in Keychain under SYSTEM. The self-signed certs only show up under My Keychains... It appears also that Server Admin will only see the certs that are located in MyKeychains. Anyone have any luck?

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

Where does Bridge CS5 store the metadata files?

Where does Bridge CS5 store the metadata files that are created under the Tools menu? I moved CS5 from one drive to another on my Mac Pro and lost all of them. I'd like to recover them is possible.

Yikes!
genenphoto wrote:
…I moved CS5 from one drive to another on my Mac Pro…
First of all, all Adobe applications really need to be installed and reside permanently on your boot volume, i.e. the same volume where your OS resides. There will be endless grief if you install the applications elsewhere.
Secondly, I hope by "moved" you mean that you deactivated CS5 and then used the Adobe Uninstaller to uninstall CS5, then re-installed CS5 from the original media, from scratch, and not just drag-copied the Application folder. And hopefully there's an OS installation on that other drive that will allow you to boot off that drive.
Third, you need to refer to your preferences in Bridge as you set them to find out whether you were keeping the cache in distributed folders or were using the central database, whether you were using separate xmp sidecar files, whether you had Export Cache to Distributed Folders set in Bridge preferences, etc..
Wo Tai Lao Le
我太老了

Error writing XMP metadata

I'm running version 1.4.1 under Vista Home Premium. I have imported several hundred jpegs from my HDD and some of these have a downward arrow at the top right of the thumbnail in Library view. On clicking this, a dialog tells me the metadata has changed in Lightroom and I need to save the changes to disk. On clicking "save"I get an error dialog stating "'Writing XMP metadata' did not complete successfully". I've also tried selecting a whole folder of jpegs, or a batch selected by Keyword, and updating them all at once using the "Metadata - Save metadata to files" menu option, but more often than not there are some photos in the batch that will not write the metadata successfully. I have been unable to detect any pattern to the images "chosen" for rejection. I think they are all pictures that were originally scanned from prints, but so were many others that update successfully. The metadata I am trying to update on them consists of Keywords and Capture dates.
Can anyone suggest how I might get these files to update?

I posted a similar query a little while ago, and judging from the response this was not widespread so I reasoned it was something peculiar to my catalogue.
After extensive testing of my set-up I could find nothing - indeed the XMP data APPEARED to be written fine to the XMP segment of the jpegs, etc. and to the XMP sidecar files for the RAW images - just Lightroom was sure it wasn't OK.
To cut a long story short, I found that I had a spurious and invisible control character in one of my metadata fields. I guess I inserted this character when I was fumbling round the keyboard trying to find the correct key combination for the '©' (copyright) character. Unfortunately I did this when setting my standard metadata template I use on all imports!
When Lightroom writes the XMP data it doesn't write this control character, however the character exists (invisibly to the Lightroom user) in the catalogue database. As a result the file-based and database versions will never match - with manual or automatic syncing - so you (nearly) always get the 'File Metadata needs updating' arrow icon.
To check this out you need to choose an image and remove metadata one field at a time - trying the save between each change. When it saves OK then you have found your culprit and can sort out the rest of the images.
Strictly speaking this is a bug. The interface should show all characters in the database and shouldn't store in the database anything that is invisible in the GUI...

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

ExtendScript : store XMP / metadatas

Similar Messages

Maybe you are looking for