XMP and C#

Hi!
I am writing an application in C# for reading/writing xmp metadata to adobe pdf files. I've downloaded the xmp sdk but it is written in C++ and it's difficult for me (almost impossible) to see what's happening there.
Do you know such a free library for C#?
I need some help for my BSC Degree ... and I can't find any library free on the web.

I recently ran across: "Drive: An RDF parser for .NET"
http://www.driverdf.org
The site offers both source code and a binary dll with instructions for calling it from C#.
If you just need to read XMP, it should do most what you need. More importantly, the docs and articles might help in your efforts.
(When searching the Web for XMP tools, add RDF to your search string. That gives you more and better hits.)

Similar Messages

LR 1.3.1 waiting for non-existing xmp and thm files

I am experiencing a problem where Lightroom 1.3.1 stalls while I am scrolling through larger folders/collections. This happens on some (specific) folders only, but can get to a point where LR becomes unusable.
Trying to nail that down, I used a file monitor (filemon from sysinternals) and spotted that LR is looking for xmp and thm files that do not exist. The reason this is slow for me probably relates to the fact, that this search happens over my local network (because my original photos are on a different computer). Estimating numbers, LR waits approx 500 ms per photo (looking for .xmp, .XMP, .thm and .THM in that time), but only for some photos in that folder.
I upgraded from 1.2 to 1.3.1 and am quite certain, that this was smooth with 1.2.
My catalog definitely doesn't write to xmp automatically. I do in fact not have a single xmp file in any of my directories. In catalog settings I also have the 'Include develop settings in metadata in jpg...' deactivated (what does that btw?).
Anyone experiencing similar issues? Any ideas what I am doing wrong here? Why is LR looking for those files in the first place?
Stefan

I am actually a bit surprised I am the only one hitting that problem.
Does anyone else have a setup where the original photos are on a networked machine, and the working catalog is on the local machine where Lightroom is running? I assume this is why I am experiencing long delays whereas 'normal' users just don't notice that problem...

DNG, XMP, and Exporting

The following pertains to Lightroom 1.1 (and possibly only to the Mac version on an Intel Mac with OS 10.4.10).
I have searched Lightroom 1.1 Help, the knowledge-base, this forum, and elsewhere for simple instruction on how to do either of the following:
Task #1: Create a separate XMP sidecar file from a DNG file for which the metadata relating to picture adjustments made in the Develop module has been embedded in the DNG file or stored in the Lightroom database.
Task#2: Export a DNG file (for which the development metadata has been embedded in the DNG file or stored in the Lightroom database) while at the same time creating a separate XMP file that contains the development metadata.
I did some experimenting relating to Task #2:
In Lightroom, I set the exposure of a DNG file to +4.00 in the Develop module, then switched to the Library module and clicked on the menu item "Metadata > Update DNG Preview & Metadata", and then exported with "Original" selected as the file format. Immediately after this, I set the exposure to -4.00, without updating, and then exported with "Original" selected as the file format. Immediately after this, I exported with "DNG" selected as the file format.
Here's what I found:
1. Looking at the thumbnail preview for each in Mac OS 10.4.10's Finder window: Exports 1 & 2 look like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). Opening any of these files within Mac OS X's Preview application shows the original state of the file without ANY of the development adjustments made before exporting.
2. Looking at the pictures in Adobe Camera Raw 3.7 (because I have only Photoshop CS2): Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Exports 2 & 3 look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). No subsequent changes occur by going on to open the files within Photoshop CS2 after they are displayed in ACR 3.7.
3. Looking at the pictures after re-importing into Lightroom: Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). For a few seconds, export 2 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Then it switches to look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). It seems this has something to do with thumbnail previews being already embedded in the files and with Lightroom displaying them temporarily before updating them.
4. All three exports, when re-imported into Lightroom, begin with two snapshots already in the Snapshots panel of the Develop module: "Import" & "Import 2". "Import" is the original file condition when the file was first imported into Lightroom (before any of my export experiments). "Import 2" is the state of the file at the time I exported it, not the state when I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. "Import 2" is with -4.00 exposure) EVEN IF THE CATALOG IS DELETED AND A NEW ONE CREATED BEFORE IMPORTING THESE, THE SAME THING OCCURS.
In none of these scenarios was an XMP file created. This had me wondering whether XMP files were possible at all in conjunction with DNG files. On to...
Task #1:
Now, as I was beginning to think that the only solution for creating XMP files from DNG files was to have Lightroom set up to maintain metadata in XMP files instead of in its own database (i.e. full-time XMP files as opposed to XMP files created only when exporting), I tried to alter settings in Lightroom's preferences, clicking menu

(to Lee Jay: Yes, as I found out.) Here's the rest of my post:
...items and buttons in this sequence: Preferences > General > Go to Catalog Settings > Metadata. Nothing I tried with the settings there would induce Lightroom to create XMP files alongside DNGs.
AFTER MORE WORK WITH JPGs AND CANON RAW FILES (.CR2), I FOUND THAT I COULD CREATE XMP FILES FOR THE CANON RAW FILES ONLY.
My conclusions are:
1. Lightroom writes separate XMP sidecar files for 3rd-party proprietary RAW formats only. This view is supported by the verbiage under these headings in Lightroom Help: "About metadata and XMP" and "Synchronize metadata with Adobe Camera Raw and Bridge".
2. This means that, for other formats, enabling the following catalog settings under Preferences does not result in separate XMP files: "Write develop settings to XMP for JPG, TIFF, and PSD", "Automatically write changes into XMP".
3. Also, for the other formats, enabling these catalog settings either does not alter the files at all or else alters them in a way that shows up only within Lightroom, Photoshop CS3, and any other applications that use Adobe Camera 4.0 or later. My additional export/re-import experimentation with JPGs in Lightroom suggests the latter is the case.
4. In Lightroom settings and documentation, "to XMP", "into XMP", etc. mean "to the XMP data embedded within the file", "into the XMP data embedded within the file", etc., except for those cases in which the associated file format is 3rd-party proprietary RAW, where these phrases mean "to a/the separate XMP sidecar file", "into a/the separate XMP sidecar file", etc.
5. The problem that seems to remain is that, apparently, not all non-Adobe software that can read DNG files is able to view changes made to these files by Lightroom (e.g. Mac OS X Preview).

P67a-gd55 and memory problems (xmp) and other things

my memory is gskill sniper 2*4gig sticks 1600mhz xmp- now if turn on xmp in the bios i get bsod`s and if i do a mem test in bios it says mem failed so i turn off xmp reboot and mem test passed i bumpt the bios upto v 1g(1.16) but still the same but as its already running at 1600mhz (without xmp) i can live with it unless somebody has an answer>
..second problem is that afer installing latest bios i have lost all settings under the hardware monitor,it used to tell the cpu temp and fan speeds but now its blank ...any ideas

flashed bios back to 1.15 and hardware info has returned ...did a memtest86+ v4.20 and passed,, so did a full cmos reset (no power) and went into bios and did f6 optimezed settings and went into utillities and did a mem test and FAILED so after updating my settings i rebooted and did a further memtest (in utilllitites) and passed....iam having trouble attaching a screenshot because when i click instert image nothing happens so i must be doing something wrong any help is accepted (using ie8)
on my asus mobo this memory is seen as spd 1333 with out xmp and 1600mhz with xmp.but this mobo puts as spd 1600mhz..once i find out how to attach a screen shot i will post a foto of cpuz mem and spd ok
http://s1098.photobucket.com/albums/g370/jackal121/?action=view&current=cpuz.jpg

Loss of relationship between xmp and associated raw file.

This is wierd. Please HELP!
I have a folder in my LR Library where the relationship between the xmp files have lost the relationship to ALL the raw files that it "represents" in that single folder. All I see in my grid view are the thumbnails with the exclamation symbol. When i select a thumbnail, LR indicates that the filename of the selected thumbnail is dsc0xxx.XMP instead of dsc0xxx.NEF. The warning box that comes up reads "Lightroom has encountered problems reading this photo". I checked the directory where xmp lives by right-clicking "Show in Explorer". I see the xmp file highlighted and i also see the RAW file just above it as well as all the other raw files.
How do i get my raw files to be once again read by lightroom? Why is lightoom only reading the xmp file? This folder has 288 images that are sorted into collections as well. Re-importing is out of the question. I don't want to go through and sort through everything again.
I tried sychronizing the folder, but that didn't do anything.
I'm using LR version 1.3.1. I then upgraded to 1.4.1 and the problem still persists. Platform is Windows XP SP2
Please Help!

John,
I tried searching for the NEF file and LR doesn't return anything. When i switch the query to .xmp it sees the 'image'. It's not really the image, just the thumbnail of the image that points to an xmp file.
I also moved out all the xmp files out of that folder, did a restart and it still couldn't point back to the raw file. The thumbnail still points to the xmp file. I do however get the question mark icon. clicking on it brings up a browse for a file location dialog box. But the 287 other thumbs in grid view still point to the xmp files. ...Drat.
"Original Nef" files? You mean the ones that were on my CF card? Uh, no. These photos were taken 2 months ago. i've gone through several read write cycles on my CF cards. I still have my NEF files. It's just that LR has decided to only point to my xmp files. This is really messed up.
Don,
Where did you read about this "bug" for LR 1.3? This is the first i've heard of a bug, besides in 1.4.
I read the "missing file" threads. i've done everything suggested there..and no succcess. I've done a variety of querys and nothing is close that what i'm seeing on my machine. My files aren't missing. They are on my disk. i'm looking right at them and i can manually redirect the thumb to point to the nef file...but i need to do that for each and every thumb....I'm not doing that.
[Begin rant]: You'd think that if you paid for software you'd get tech support included as well... apparently NOT. It's $40 per 'incident': http://www.adobe.com/support/programs/photoshoplightroom/index.html?tab:contact=1
Ouch. Why am I paying money for this? for the priveledge? Adobe, please consider including phone-in tech support for matter's like this. Knowledge bases and forums can only get you so far before you need to get it from the 'horses mouth'. [end of rant]

XMP and Premiere

Is it possible to custom script with the xmp sdk module an interface to work with adobe premiere to do the following.
Im trying to attach and embed certain keywords and descriptions and iptc data info into a digitized video file during the digitizing process.
I then want to test to see if that injected metadata digitized file will then carry that information for when i goto encode that same file into a wmv file.
with the wmv file that has been created i would like to view and inspect the properties in adobe bridge to find out if the original metadata was able to be transfered during the encoding process.
any one with insight that has done this before and or can help (willing to pay the programmer) will greatly be appreciated

My point is that the documentation says that the application will read the metadata and can show it in the Metadata panel. After Effects doesn't use the XMP metadata to apply image adjustments.
You can submit feature requests here:
http://www.adobe.com/go/wish

Virtual copies are not synchronized in a second Lightroom catalogue although metadata are written in XMP and synchronization with metadata was selected

Dear community,
I operate one Mac with Lightroom 5.7 that is configured to store all metadata in xmp files. The Lightroom catalogue is stored locally on the Mac and only contains references to the images and their xmp files that are stored on a network device. There is another Mac with the same configuration having a separate local Lightroom catalogue and access to the same images on the network device.
At a starting point, both Lightroom catalogues are identical - they refer to the same images on the network device and contain the same metadata.
When I update image properties on the first Mac, these changes are reflected in the xmp file. After using the option "synchronize" with activated "metadata synchronization" on the second Mac, the modified image properties are visible on the second Mac. This is fine.
However, when I create a virtual copy on the first Mac, I realize that the corresponding xmp file gets updated. However, even after synchronization, the virtual copy is not visible on the second Mac. I may modify image properties of the original image and get these modifications replicated to the second Mac, but the virtual copies remain on the first Mac.
What needs to be done that also virtual copies get synchronized?
Thank you very mich for your support.
Best regards,
Peter

I do not doubt that File Export / File Import will work to transfer the virtual copies.
My question was related to the fact whether the imported folder should not previously exist on the second Mac.
Consider the following situation:
time = 0:
first Mac: folder A is in a first status
second Mac: folder A is in a first status
time = 1:
first Mac: folder A is in a second status, export folder A in second status
second Mac: folder A is in a first status, import folder A in second status
My question is: What happens with these two folder A on the second Mac? Does folder A in the Lightroom catalogue of the second Mac gets overwritten? Do I receive an error message because folder A is already present in the Lightroom catalogue?
I understand your answer that everything will be fine on the second Mac if there is no folder A at all at the second Mac while I import the new folder A. Under this assumption, I can import folder A and it will show the second status. Clearly.
My question is only related to the fact that there is already a folder A on the second Mac, with the same images, but with different metadata and/or virtual copies.

XMP and Python (also DLL compilation help needed)

Has anyone tried using the XMP SDK through Python? I know python fairly well, but not C++. I would like to code in python if possible.
From what I have gathered I have a few options:
1. Use Python's built-in 'ctypes' methods (not sure if this will only work with C as opposed to C++)
2. Use Boost
3. Use Sip
Does anyone have any experience with any of these (or any other solutions)?
The current route that I am experimenting with is using ctypes. For this to work I will need to compile the XMPCore and the XMPFiles projects into .dll's (as opposed to the default .libs). I have seen quite a few posts on this forum asking how to go about doing this, but have found no answers. I have been able to succesfully compile a .dll for XMPCore but not for XMPFiles. I am using Visual Studio 2008 and cannot figure out how to compile XMPFiles without producing errors such as:
2>WXMPFiles.obj : error LNK2019: unresolved external symbol "void __cdecl XMP_EnterCriticalRegion(struct _RTL_CRITICAL_SECTION &)" (?XMP_EnterCriticalRegion@@YAXAAU_RTL_CRITICAL_SECTION@@@Z) referenced in function "public: __thiscall XMPFiles_AutoMutex::XMPFiles_AutoMutex(void)" (??0XMPFiles_AutoMutex@@QAE@XZ)
2>TIFF_Handler.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall TXMPMeta<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >::~TXMPMeta<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > >(void)" (??1?$TXMPMeta@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@@UAE@XZ)
These are the steps that I have taked:
1. Download and add the Quicktime SDK, Expat XML Parser, and Zlib libraries to the proper folder paths
2. Open the provided XMPToolkit.sln in VS8
2. Build > Build Solution. Produces two static libraries, XMPCoreStaticDebug.lib and XMPFilesStaticDebug.lib. (This works! ... but I want dll's)
3. Change the properties of the XMPCore and XMPFiles projects:
Configuration Properties -> General-> Configuration Type: Dynamic Library (dll)
4. Clean Solution; Build Solution
This results in many errors. Most of which are like the two listed above.
Anybody have any advice /input in regards to using python with the XMP SDK and/or compiling these two libraries into .dll's ?
Thanks for any help!!!

I you have installed the java runtime engine then put the j3D libraries in that drectory tree in the jre\lib\ext directory, and .dll`s in the bin directory. I you have not installed the jre then do so. That will create the java.library.path you need. to run java programs. Each compiler has its own procedures for running an app from the IDE, check your docs if that`s what you are doing.
regards

XMP and DNG support?

I'm using Aperture 2 on Mac 10.4.11...
After importing DNG files I have some problems and what to ask if other users experience the same or perhaps I'm doing something wrong?
I have a Lightroom Workflow where I convert all my 40d Raw files to DNG. I apply a lot of Metadata and some basic adjustments in the Lightroom Develop module. I update my DNG files with metadata and preview images to include everything in the files. After importing these files into Aperture 2 I have following problems.
Metadata is not imported properly.
Example 1:
Creator in Lightroom: Susi & Paul
Artist in Aperture after import: Paul
"Susi &" is missing. Artist is not the only field with this problem. I have the same in behaviour in "Writer/Editor", "Credit", "Source", "Byline"....., simply i n all fields...
Example 2:
Caption in Lightroom: Köln, Cologne
Caption in Aperture after import: öln, Cologne
The "K" form "Köln" is missing.
Example 3:
All adjustments I have done in the Lightroom Develop Module are saved in the XMP Metadata and all previews are updated in the DNG files after adjustment to reflect the changes. I expected that Aperture is reading this metadata and use it for rendering. This is not the case.
I was trying with Aperture 2 in German and English Language without any difference.
Now again my question... Do you experience the same behaviour with Aperture 2 or is it my mistake?
Thanks for any answer and... sorry for my bad english.

Thank you very much Adsy for reply!
After a few experiments I believe the wrong metadata import is a bug too. But this bug effects only my dng files, if I import jpeg's with the same metadata everything is fine. I'm not sure is it the DNG format or the included XMP (my jpegs also have XMP metadata).
In my jpegs I have EXIF, IPTC and XMP (IPTC for XMP). Do you know in which order Aperture is reading this information and which information has precedence and is used?
"IPTC" before "IPTC for XMP"?
And who is the winner if metadata in "IPTC" and "IPTC for XMP" has the same values?

XMP and IPTC mapping

Is there a document that identifies which fields in Photoshop and Illustrator "file info" map to the corresponding IPTC field and XMP field repectivly. Also, if I enter a value in a field that is represented in both standards will both fields be populated in the image file?
Regards
Chris

The 'File Info' in Photoshop since version 3.0 is stored in numerous places in a given file for various formats.
On the Macintosh, some information is stored in the resource fork for any file format:
The keywords are stored in a 'KeyW' resource and the caption is stored in a 'TEXT' resource. These resources are referenced by the 'pnot' resource. This information is readable by Aldus Fetch (now Extensis Portfolio). For more information on the format of these resources see:
Inside Machintosh: QuickTime Components
Aldus Fetch Awareness Developer's Toolkit
All of the data from File Info is stored in an 'ANPA 1000' resource. The data in this resource is stored as an IPTC-IIM version 2, record 2. For more information on the format of this resource see:
"Information Interchange Model (IIM) version 4"
Available online at:
Telephone: +44 1753 705051
Facsimile: +44 1753 831541
E-mail: David Allen, Managing Director
Post: IPTC
Royal Albert House
Sheet Street
Windsor
Berkshire
SL4 1BE
UK
On all platforms, the IIM is also stored in the data fork of the file. For file formats that can support Photoshop's image resources the data is stored as an image resource '1028' (kCaptionID) in IPTC-IIM record 2 format.
For TIFF files the caption data is stored in an image description tag '270' and all the information is stored as an IPTC-NAA record 2 in tag '33723' the tag number was chosen by inspecting files written by Iron Mike software, and is supposed to be defined in a Rich TIFF specification that I haven't been able to track down. The tag is also specified in:
NSK TIFF
The Japan Newspaper Publishers & Editors Association
Nippon Press Center Building
2-2-1 Uchlsaiwai-cho
Chiyoda-ku, Tokyo 100
For more information about the TIFF format see:
"TIFF Revision 6.0"
Available online at:
In reading the files, the following order is used with information read
lower on the list replacing information read higher:
* kCaptionID image resource
* For old Photoshop files, the caption data is read from the image resource '1008' (kOldCaptionID) or '1020' (kPrintCaptionID) (it cannot appear in both). Old PrintCaption data could coinside with caption data in some beta releases in this case the print caption data is ignored.
[NOTE version 3.0 and 3.0.1: Print caption was appended to the caption
information but this caused duplicate captions in TIFF files. This bug was fixed for version 3.0.2]
* Image Description Tag (TIFF only)
* IPTC-NAA Tag (TIFF only)
[NOTE version 3.0 and 3.0.1: TIFF data did not override the previous image resources. This bug was fixed for version 3.0.2.]
* 'pnot' resource related data (keywords and caption) (Mac only)
* 'ANPA' resource (Mac only)
[Additions for Photoshop 7.0]
* XMP Data - The kCaptionID image resource is written out with a digest
signature. The digest is re-generated from the above information when
a file is opened. If the digest doesn't match then the XMP information
for properties that that are contained by the kCaptionID resource
(IIM records, photoshop:WebStatement, and photoshop:Marked) are
dropped from the XMP Data. Otherwise, the XMP Data takes precedence over all previous data.
NOTE: The TIFF information comes prior to the image resource information on this list. This means that an edit to the TIFF info will not be recognized unless the image resource information is removed.
Photoshop Schema
The namespace prefix is ÒphotoshopÓ. The namespace is http://ns.adobe.com/photoshop/1.0/.
Property Type IIM Record Alias Category
photoshop:Caption Text 2:120 Caption/Abstract dc:description/*[@xml:lang='x-default'] External
photoshop:Author ProperName 2:80 By-line dc:creator/*[1] External
photoshop:Title Text 2:05 Object Name dc:title/*[@xml:lang='x-default'] External
photoshop:Keywords bag Text 2:25 Keywords dc:subject External
photoshop:WebStatement URL xapRights:WebStatement External
photoshop:Copyright Text 2:116 Copyright Notice dc:rights/*[@xml:lang='x-default'] External
photoshop:CaptionWriter ProperName 2:122 Writer/Editor External
photoshop:Headline Text 2:105 Headline External
photoshop:Instructions Text 2:40 Special Instructions External
photoshop:AuthorsPosition Text 2:85 By-line Title External
photoshop:Credit Text 2:110 Credit External
photoshop:Source Text 2:115 Source External
photoshop:DateCreated Date 2:55 Date Created (1) External
photoshop:City Text 2:90 City External
photoshop:State Text 2:95 Province/State External
photoshop:Country Text 2:101 Country/Primary Location Name External
photoshop:TransmissionReference Text 2:103 Original Transmission Reference External
photoshop:Category Text 2:15 Category (2) External
photoshop:Marked Boolean xapRights:Marked External
photoshop:SupplementalCategories bag Text 2:20 Supplemental Category External
photoshop:Urgency Integer 2:10 Urgency (3) External
photoshop:JobName (4) Text xapBJ:JobRef/*[1] External
xapMM:ManageTo (5) URL Relational
xapMM:Manager (5, 6) AgentName Relational
xapMM:DocumentID (7) URI Internal
(1) Explicitly not aliased to the internal creation date which denotes the document creation. This field is intended to follow the IIM conventions:
Designates the date the intellectual content of the document was created rather than the date of the creation of the physical representation. Thus a photo taken during the American Civil War would carry a creation date during that epoch (1861-1865) rather than the date the photo was digitized for archiving.
(2) This field is limited to three 7 bit ASCII characters only.
(3) Valid range is 1-8.
(4) Not aliased in Photoshop 7.0 due to bug in XMP.
(5) If xapMM:Manager is not "AdobeARM" and the ARM is not managing this
document then these properties are preserved.
(6) Set to "AdobeARM" for managed files.
(7) DocumentID will be set if it was previously blank and once set it is especially "sticky" and won't be lost even if other metadata takes
precedent and can not be set by loading XMP data from File Info although plug-ins are able to set, but not clear, this property.

Xmp and dng

So I have a question.
There is this outsourced company, that I use for editing, and I export from my raw files to dng so I can send it to them, They edit in lightroom, and they return xmp sidecar files with the edits that I simply apply back to my raw files.
Now I want to train another person on remote location to do the editing instead of using the company i used to use, and I'm trying to replicate this process.
The problem is, from all I read, you can't create xmp from dng files, so how did they do it? Is there another program that can save the xmp data out of dng? or did they conver the dng that I gave them to another format so that they can write xmp files out?
Can anyone give me a way of doing this?
thanks

If DNG is read-only, Bridge will create sidecars for xmp. However there is no way to do the same in Lightroom, without some stunts...
Lightroom will read DNG sidecars (if they're recent enough), but won't ever write them.
papjohns wrote:
Is there another program that can save the xmp data out of dng?
Can anyone give me a way of doing this?
Easiest way is via xEmP plugin, but you can also use exiftool directly if you prefer.
Rob

XMP and PHP

Hi, is there anyone out there who is working on a PHP implementation of the XMP-packet reader?
Thanks,
R.

There's a free one if all you need to do is read from JPEGs. That's all I need. It's a combination of C and PHP.
The C code needs compiled and I've never compiled anything under OS X before. Surprising, that only took typing two commands and a few minutes. (A configure and a make.)
This solution dumps the entire XMP packet, so you'll have to parse it yourself.
The C:
http://www.w3.org/People/Bos/JPEG-XMP/
The PHP:
http://chimpen.com/xmp/ (a working example)
http://chimpen.com/things/archives/001128.php (the code)
It's fast, getting the XMP from a 3MB JPEG is almost instantaneous when the JPEG is on your local machine.

XMP and Windows Explorer

How can I set XMP data in a PDF file and display the data in columns in Windows XP Explorer?
I have tried pixvue from www.pixvue.com bit it only works for images - not PDF files.
Any ideas?

Greetings,
We have done such a tool,, it contains a windows explorer like clone, as well as a column handler for Windows explorer but it is in an alpha stage, so it may cause problems in certain cases. You can download the tool here:
http://www.optimasc.com/products/dex/
We are currently working on a BETA version of the tool, that will hopefully be available soon.
Carl Eric Codere

XMP and Quicktime .mov

Is there a formal specification for embedding XMP within Quicktime .mov containers, and any associated new XMP schema? Perhaps I'm missing the specs, but I thought this was part of the Production Studio release (which I don't have a copy of), but I've not seen any actual specs on how to inject XMP into .mov files.
Am I hallucinating?

You're not hallucinating.
The public documentation for XMP embedding is currently behind the shipping products. We're working on getting updated documentation out, can't say anything about exactly when.
Developers in a time crunch should contact Gunar Penikis ([email protected]) if you want to try to get early info under NDA.

Applescript, XMP, and custom namespaces

Having had to switch gears from JS to AS to solve a database integration problem, I could use some help getting specific XMP out of my AI files via AppleScript. Extracted this from the InDesign forums... doesn't work for illustrator (gives error "expected expression but found property")
tell links
set InhouseClient to get property link xmp namespace "http://ns.Inhouse.com/Inhouse" path "Client"
end tell
I know I can dump the whole XMP string with:
set XMPStringData to (get XMP string of current document)
but I'd rather do something like the first example. If I were in JS, I'd use
var property = myXmp.getProperty(propertyuri, propertyname, XMPConst.STRING);
The syntax looks pretty close to the first AppleScript, but why is it choking on the "property" when inside a "tell Illustrator" when is works inside a "tell InDesign"?

Thanks for the suggestions Mark.
Here's the situation. We have approx 1TB of various files on multiple partitions of a server. I'm creating a library (FileMakerPro) to use as a search engine for specific AI files and associated metadata scattered throughout the server. We have a pattern of folders where the AI files I need live (jobFolder/Graphics/filename.AI), but these are nested in a variety of places.
I'm using set folderList to (folders of entire contents of (startFolder) whose name is "Graphics") as alias list to get a list of eligible folders to search, then checking to see if AI files are present, then adding the AI files to a list of file paths. This list is the source for other scripts to be called by Filemaker to extract the custom XMP, find and link to the preview (already generated in a separate folder).
Current times to ingest small sets of graphic paths using this method:
Set 1, found 160 eligible folders with 1600 files in 44 minutes, or 17 seconds per folder/1.6 seconds per graphic.
Set 2, found 310 eligible folders with 3800 files in 82 minutes, or 16 seconds per folder/1.3 seconds per graphic.
Set 3, needs to crawl through about 8 times the number of folders, and can't finish before the server times me out (I pushed the AppleScript timeout to 20 hours, so that's not the problem).
In additon to metadata that has already been defined, I want to capture the full-text of the graphics in the DB for search purposes... so will have to open each file anyway to do that (unless there's another way).
Thanks,
Alex

XMP and C#

Similar Messages

Maybe you are looking for