XMP in C++

hi everybody,
iam trying to implement XMP metadata in C++, i download the SDK toolkit from adobe website, can i directly include the header files given in toolkit or i have to create static library for those files? i dont know? can anybody help me by replying this with samples?
thanks in advance.

Look at the sample directory. There is everything you need to get started.

Similar Messages

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

XMP doesn't display proper info in Photoshop CS2 for Mac.

Dear List members:
I have just recently installed Creative Suite CS2 and begun to explore the functionality of XMP. After purchasing Bruce Fraser's book on Camera Raw for CS2, I downloaded Metalab (Pound Hill Software) and created my first custom XMP panel that can be seen under the file info in Photoshop when an image (digital photo) is open.
The problem is that I noticed a few odd things and began to question myself if there is some kind of bug or a problem with my installation of CS2.
1. The window that opens under the file info command has several categories of information on the left to be chosen from, in the following order:
(1)Description, (2)Camera Data 1, (3)Camera Data 2, (4)Categories, (5)History, (6)IPTC Contact, (7)IPTC Content, (8)IPTC Image, (9)IPTC Status, (10)Adobe Stock Photos, (11)Origin, (12)Advanced
The Camera Data 1 option when selected opens a panel in the file info window that seems to contain all the information it is supposed to contain. The Camera Data 2 panel, on the other hand, doesn't display any information at all. Although the fields are there, they are empty. The fields are:
(1)Pixel Dimension X and Y, (2)Orientation, (3)Resolution X and Y, (4)Resolution Unit, (5)Compressed Bits per Pixel, (6)Color Space, (7)Light Source, (8)File Source.
All these fields are empty but when looking at the same file under Bridge the information is there, displayed under the metadata menu.
This is something I noticed "before" installing Metalab so I know it is not a compatibility issue generated by the installation of the software.
After installing CS2 I noticed that CS1 remained installed in my system. The version I purchased of CS2 is the upgrade one. Since I have no use for CS1 as I am now totally converted to CS2, I would like to uninstall CS1. The following are some of the questions I have:
1. How can I uninstall CS1 without causing any problems to my installation of CS1 ? Is there an uninstall utility with the software or will I have to uninstall the entire package manually ?
2. My G5 came with only one internal 160 GB drive where I originally installed CS1. I then purchased another internal 400 GB HD and copied the original drive onto it. This week I am going to replace the original 160 GB drive with a second 400 GB drive so that I can do regular "mirror image" back-ups between the two drives. Shold I expect any problems as I remove the drive where I originally installed CS1 ? Since I used disk utility to "copy" the 160 GB drive onto the 400 GB drive, my understanding it that any Adobe software key or authorization was also transferred to the drive. Is this right ? In case it hasn't, how can I transfer this information so that after I remove the 160 GB drive I will not experience any problems when trying to run CS2 ?
3. How can I fix the problem with the Camera Data 2 panel under the file info window and command ? I noticed that the folder that is supposed to hold the Custom File Info Panels (HD>Library>Application Support>Adobe>XMP>Custom File Info Panels) has files for CS1 and CS2. Could this be a problem ? There many more files with .dat extenson than there are with the .txt extension. Bruce Fraser specifically says that the ones with the .txt extension are the ones that hold the XMP templates for information related to the image files. The files I have in this folder with the .txt are:
(1)Camera1_CS2.txt , (2)Camera1.txt , (3)Camera2_CS2.txt , (4)Camera2.txt , (5)Categories.txt , (6)History.txt , (7)IPTC_Contact.txt , (8)IPTC_Content.txt , (9)IPTC_Image.txt , (10)IPTC_Status.txt , (11)StockPhotoInfo.txt
The only ones that have two separate files one each for CS1 ad CS2 are Camera 1 and Camera 2. Camera 2 seems to be the only that is now non-functional. What should I expect to happen if I were to manually uninstall the ones that relate to CS1 ? Could that cause any problems ?
My apologies for the long post but I didn't really know how to make it shorter.

The Photoshop and/or Bridge forums would be more likely places to get answers to your questions. This forum is inhabited more by programmer types interested in implementing the XMP specification in applications we write.
I'd expect CS2 to ignore CS1 panels so I doubt that's the issue. Panels don't interfere with each other--they just offer different views of the data. In any case, move the extra panels to your desktop and see what happens.
As far as I know, all you need to do on the Mac is drag the CS1 application folder to the trash to uninstall it.

Adobe XMP Files not deleted with Raw Files in ACR

I am using Photoshop CS3 on a Windows XP platform. My camera raw files are mostly kept on a Windows 2003 file server, which has a gigabit connection to my workstation. However, I have the same problems when using PS CS3 on my Windows XP laptop.
I take many hundreds of 'technical' photographs using an Olympus E1 and Canon G9 cameras. I usually bracket the exposures on the E1, specially when photographing white painted yachts, and then rate and select the images that I want in ACR 4.1.1. Unwanted images are deleted at this time.
The problem I am having is that the associated *.xmp files are not always deleted with the camera raw files, with the result that I now have literally thousands of these 'orphaned' files cluttering up the server. The only options I have are to delete the files manually, which is a pain, or to leave them on the server, wasting unnecessary space.
I have the same issue with Canon and Nikon raw files, so this problem is not specific to Olympus files.
This is a long standing problem, and I would be grateful if anyone has any answers?
If any Adobe programmers are watching, it would be handy if you could provide a simple utility to delete orphaned *.xmp files, or at least compress them into some kind of archive.
Thanks,
Nigel.

[quote] As far as Photoshop and ACR go, ALL raw files are treated as read-only.
Your original raw files remain untouched, no matter what you do to them.
Any adjustments you make to a raw file are kept only as metadata (flags, if you will) in that XMP side-car file. Every time you want to re-open that raw image file, ACR will reach for the XMP file and apply the adjustments automatically, transparently. [/quote]
That is not quite correct. Camera RAW files can be permanently deleted from within Adobe Camera Raw. The problem with ACR 4.1 to 4.4 4 was that the XMP files were left behind. This now seems to have been rectified in the latest version (ACR 4.5).
Thank you Adobe!

Can you remove XMP data from .eps files in Illustrator-CS5.5?

Background:
I'm using font software called Typetool 3 and Illustrator CS5.5.
I am using these on Windows 7, 64 bit.
This is entry level font software released by Fontlab.
This software accepts artwork through the .eps file format in both theory and practice.
However: it refuses illustrator CS5.5 .eps files.
When I looked at this I came up with two highly interesting things: First- CS5.5 illustrator files are roughly 13 times the size of CS5 files, of this type (a simple font glyph-comparing a 29-30 kbfile to a 420-450 kb file in cs5 and cs5.5 respectively).
Thing two came from looking at what that data was (by opening it in a text editor). It appears that some of the data XMP data, illustrators data for tracking things like who created the file, copyright, and other. In document info many of these fields were blank. I'm sure this isn't the only issue because my exported xmp data is 64 kb large, but it does account for a chunk of the file.
The main question being: Can this xmp data; which for my purposes is redundant, because I have to put copyright and other data in the font, be removed or not included at the point of document creation?
The technical question being:Can the file be saved in a manner which will allow it to be exported from adobe CS5.5 and imported into Typetool 3?
Things I've tried:
In saving .eps file: removing document headers, previews, color data, saving as different versions of the language. Basically saving it without all settings.
In saving .ai file: saving without any settings checked (without compression, pdf editting, ect.) and saving it to a different level of illustrator.
I do not know enough about postscript programming to navigate the file or remove the offending data. Nor do I have time to do this over multiple glyphs.
As a matter of opinion I do not like that my software is including potentially identifying information (which is one of the intents of XMP data, to provide identification) without notifying the creator, let alone allowing me to keep it from doing that. I would not mind or bother-except for the fact its messed up an established workflow. If someone editted this data without my knowledge, say with a virus or heaven forbid manually, it would be also be bothersome. Having a check that identifies that I am sending this data out would give me something to know if this situation was in fact happening. Additionally for a situation like mine-communication between programs in a closed environment where no other users are involved, its unnecessary and wasteful... like putting gold rims on what is intended to be an oxcart.
I'm planning on going to Fontlab for later this week, as it is as much thier issue as it is Adobe's. From what I know XMP is both a useful and popular technology- having a workaround for this situation seems like it would be a good idea. If necessary I can attach some working files for comparision.

I would save it as EPS (version Illustrator 3). This should be compatible to almost any software that takes EPS.

Short list of some vendors supporting XMP

I am working on getting a list of vendors that support XMP together - below is a short list of vendors with mostly "off the shelf" products.
There are of course larger asset management vendors such as IBM, Media Bank, etc. that support XMP - working on getting that together.
I thought this might be helpful regarding some questions I was hearing regarding search etc.
Please post info on other vendors as you find them.
Thanks,
Gunar
Extensis
Portfolio also supports the ability to read information stored using industry standard metadata storage conventions such as IPTC, EXIF, and Adobes RDF-based XMP metadata standard. In addition to reading metadata from image files, Portfolio can also embed IPTC and XMP metadata directly back into JPEG, TIFF, and Adobe Photoshop PSD files, ensuring that critical information remains permanently attached to these assets, even when exported to other applications.
http://www.extensis.com/en/products/product_features.jsp?id=prod60005
iView
IView Media Pro 2.5 supports XMP read & write for compatible IPTC fields. MediaPro? 2.5 is designed for creative professionals in film, video, photography, broadcast, education and scientific fields. MediaPro? helps streamline workflows and allows professionals to quickly and easily import, sort, organize and manage very large volumes and types of digital fileshelping cut costs and speed project delivery.
http://www.iview-multimedia.com/products/
Netxposure
NetXposures Image Portal software is the next-generation in Digital Asset Management giving you a central library for collecting, storing, managing, and distributing image assets. Get controlled, immediate, Web-based access to media assets and ensure the proper use of those assets in all your sales, marketing, and Web initiatives.
EXIF, XMP, and IPTC meta-data formats are supported within the image assets. Additionally, Image Portal can store custom meta-information about an image that is searchable and browsable.
http://www.netx.net
IXIASOFT TEXTML Server
IXIASOFT is a Montreal-based company founded in 1998. Its flagship product, TEXTML Server, is an XML Content Server developed to store, index, and retrieve XML documents. TEXTML Server is aimed at OEMs, System Integrators, and Value-Added Resellers (VARs) who are developing web content management solutions. In fact, IXIASOFT provides its customers and partners with a set of APIs that enable developers of web applications to effectively publish large volumes of semi-structured XML content and make critical information easily accessible.
XMP & TEXTML whitepaper at: http://www.ixiasoft.com/whitepapers.asp
Context Media
Context Media's products and solutions make it possible for you to exploit the full value of your content without disrupting existing workflows or replacing existing content management investments. Whether you need to virtually integrate disparate content systems for an efficient real-time enterprise; organize and manage distributed content for improved employee access and productivity; securely distribute content throughout your extended network of partners and customers; or all of these, Context Media's integrated family of products and solutions are designed to help companies implement a more efficient, productive, and scalable enterprise content management strategy.
Context Media also announced its support for the open standards-based Adobe XMP (Extensible Metadata Platform). Based on W3C standards, Adobes XML-based XMP framework provides an open standard for the creation, processing and exchange of metadata across publishing workflows.
http://www.contextmedia.com/news/full_story.jsp?itemId=185
Poundhill Software
Pound Hill Software Inc., developer of XTensions and plug-ins for the digital asset management industry, today announced the Catalyst Solution for XMP, the world's first integrated set of tools for Adobe's eXtensible Metadata Platform (XMP). Metadata is data about data. With Catalys

Part 2 since it got cut off...
Poundhill Software
Pound Hill Software Inc., developer of XTensions and plug-ins for the digital asset management industry, today announced the Catalyst Solution for XMP, the world's first integrated set of tools for Adobe's eXtensible Metadata Platform (XMP). Metadata is data about data. With Catalyst, creators and managers of graphic arts intellectual property can specify both the metadata embedded in graphic arts documents and the look-and-feel of the dialogs that collect the data. In addition to designing and defining these controls, enterprises can generate their own plug-ins for applications such as Photoshop®, InDesign®, Illustrator®, Acrobat® and QuarkXPress to collect the data.
Products: MetaLab - free XMP panel creator, Catalyst Solution - XMP schema and plugin generator
Product Plugins: AppleScript, FileMaker Pro, PHP
http://www.poundhill.com/
Knowbody
InDesign XMP plugins for workflow, automation and search
http://www.knowbody.dk/productbasement/index.asp?language=2
PixVue
PixVue is an image management application. PixVue integrates with the Microsoft Windows Explorer to provide unsurpassed ease of use and ready access to a wide variety of image-related functions and data.
http://www.pixvue.com/editorHelp.html
Qarbon
ViewletBuilder4 by Qarbon - ViewletBuilder makes it possible for anyone to create compelling, animated online presentations with ease. Whether you need to design product demonstrations, software tutorials, online documentation or e-learning material, Viewlets are the answer.
http://www.qarbon.com/products/viewletbuilder/comparison.html
PreClick
PreClick - Preclick offers both a free and paid version of the Preclick Lifetime Photo Organizer. It's the world's easiest and fastest way to find and organize your growing digital photo collection. In addition to fast find, sort, slide show, editing tools, email, renaming and rating, Preclick offers the internet's best professional quality prints at great prices (29 cents per 4x6) from top-rated photo-finishers.
http://www.preclick.com/support/faq.php - look under PhotoBack
Soft Experience
Catalogue by Soft Experience - Soft Experience software editor provides Windows products such as Idem, Catalogue Files Metadata Miner, Delenda, MacNames, utilities helping PC users and Windows administrators to automate technical tasks. Our tools focus on file and content management with functions like file synchronization, Macintosh file management on Windows platforms, automation of old files suppression, metadata extraction.
http://peccatte.karefil.com/software/Catalogue/CatalogueENG.htm
IFilterShop
XMP IFilter by IFilterShop - We develop high quality custom solutions based on Microsoft Index Server technology. Index Server is at the foundation of Microsoft content management offering. Various Microsoft products including Sharepoint Portal Server, Exchange Full Text Search and Site Server rely on Index Server technology to make content accessible.
http://www.ifiltershop.com/xmpfilter.html

CR6.4 RC1 - XMP export bug, anybody else has it?

I think I found a bug, and although I also found a workaround, here it is.
My environment: Windows 7, Photoshop CS5, Camera Raw 6.4 RC1, all of them 64-bits.
Steps to reproduce the bug:
1. Open several raw files at once in Camera Raw (in my case, Olympus E-PL2 ORF files, but it probably doesn`t matter). For this bug, take images that are likely to have different white balance settings. Also make sure that those are original files, never modified by Camera Raw (or anything else) and that they have no XMP sidecars yet.
2. Wait until thumbnails are generated (may not be relevant...). Don't click on any of them, just let them be created.
3. Click on "Select All". Again, don't change the displayed image, just select them all.
4. In Basic/White Balance, select Auto. All thumbnails are properly updated
5. Export settings to XMP (from the menu on the right-most toolbar, i.e. still "Basic" if you haven`t changed it)
6. Keep Camera Raw open, and have a look at the XMP files.
The BUG : they all contain the same white balance settings (crs:WhiteBalance, crs:Temperature and crs:Tint) which happen to be the computed settings for the first image (the only one displayed so far). All other settings seems to be fine though (i.e. they are from their respective image).
However, if you go back in Camera Raw and then click on some other images, not all of them. You can see that their WB settings are different and properly computed (as far as "Auto" can properly compute them). Export to XMP again. WB settings are then right, but only for the images that you clicked on. Those that were never displayed full size still have the wrong WB settings (from the first image).
Obviously, the workaround is to click on each of them. Still that's a bit awkward, especially in my "quite-automated" workflow, where I'm not yet to the point to look at each image individually. Can't tell if this bug exist too on any other version of CR, and my E-PL2 raw files can only be opened in CR 6.4 anyway (unless I change some tags to fool CR).
Can anybody can reproduce that bug on similar or different environment? And could Adobe fix it, if it is a bug?

btw, don't know why I wrote RC1... I just meant Release Candidate!

InDesign XMP Not Working with Live Caption

I have images in InDesign CS5 (Mac OS X 10.6..), and although they have XMP data (Set from Bridge), when I set with Live Caption, my caption always says "<No data from link>". I've set up captions in Objects > Captions... > Caption Setup - metadata to "Description" and the XMP data doesn't get put into the caption. I can see the XMP information in Links > Image > XMP File Info... "Description". That's Fine. I've tried other user-defined fields, "Title, Keywords" and none work in Live Caption. I've also been updating the images after setting the XMP data in Bridge. I've also just deleted the images and re-placed them. Still can't get live caption to work.
I also saw a related thread where a user set file XMP via photoshop (CS5), which I also tried. When I do that, InDesign CS5 doesn't see the XMP data (via Links > XMP File Info). I can see it if set via Bridge, but can't make Live Caption work. If I set XMP via Photoshop, I can't see XMP data, and naturally can't set Live Caption.
I could have done my project 5 times manually by now - but the fact this isn't working has been driving me crazy. Wondered if anyone has seen this or, hopefully, got it to work. And am I doing something wrong?
Thanks,
Matt

I think this is a bug - probably in Photoshop (though the various engineering teams may disagree on this ).
Here's what I did:
Opened a TIFF image in Photoshop CS5, and confirmed that it had "Description" metadata.
Placed it in InDesign CS5 and created a live caption which DID work.
Saved the image as a PNG using "Save for Web and Devices" in Photoshop CS5 with metadata set to "All".
Placed that PNG in InDesign CS5, and found that a live caption did NOT work
Examined the PNG image in Bridge CS5, and found that the description WAS shown
Opened the PNG image in Photoshop CS5, and found that the description field was empty (in fact all fields were).
Looked at the "Raw Data" section in the File Info dialog box in Photoshop, and found that it was essentially empty.
Opened the PNG in a hex editor, and found that the missing metadata WERE there, but somehow must be formatted/structured in a slightly incorrect way which somehow prevents Photoshop and InDesign from properly parsing the XML, but not so far afield as to prevent Bridge from doing so.
I would suggest filing a bug report against Photoshop CS5 since it cannot read the metadata that one of its own components wrote into the file.

~~ New XMP CS6 SDK Releases ~~

Hi,
You can now find new versions of our XMP SDKs on Adobe Devnet:
http://www.adobe.com/devnet/xmp/
So please check out the CS6 versions of the SDKs and post your feedback in this forum!
The prior versions are still listed.
Updates:
Updated XMP Specifications [version: April 2012]
New version of the XMP Toolkit SDK (c++) [version: CS6]
Compiler Upgrade: Xcode 4.x, Visual Studio 2010 (VC10)
A plug-in SDK for XMPFiles that allows you to add custom file handlers, or replace existing file handlers with custom ones in XMPFiles
A new version of the file handler for RIFF-based formats that also support AIFF. The AVI handler still uses the old code, but WAVE and AIFF are based in the new file handler
New functions in XMPFiles that allows you to use your own I/O code in XMPFiles
Support of EXIF 2.3 properties
A new XMPFiles function, GetFileModDate(), that retrieves the most recent OS file modification date for the associated metadata of a file
Many bug fixes and minor improvements in XMPFiles
The XMP FileInfo SDK is now available in version CS6
Custom Panel Plugin for Flash builder 4.x
EVE Panel converter (to convert CS 2/3 panels)
Create generic panel without Action Script (XML only)
XMPCore Java is now is now available in version CS6 and seperated from the C++ toolkit (see new Java section)Many bug fixes and minor improvements
The Adobe XMP Team

Hi,
i used the previous version of the java XMPCore. I tried to upgrade however i got the following exception (using java 1.5 and 1.6):
java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
    at com.adobe.xmp.impl.XMPMetaParser.createDocumentBuilderFactory(Unknown Source)
    at com.adobe.xmp.impl.XMPMetaParser.<clinit>(Unknown Source)
    at com.adobe.xmp.XMPMetaFactory.parseFromBuffer(Unknown Source)
    at com.adobe.xmp.XMPMetaFactory.parseFromBuffer(Unknown Source)
On further investigation the problem is, that you are trying to call a method
factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
on an abstract class however you are not catching that error, as you propably intended to.
The code has been introduced into the new version:
class XMPMetaParser.java:
try
            // honor System parsing limits, e.g.
            // System.setProperty("entityExpansionLimit", "10");
            factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
        catch (Exception e)
            // Ignore IllegalArgumentException and ParserConfigurationException
            // in case the configured XML-Parser does not implement the feature.
The exception is of the type "Error" and thus won't be catched by the "catch (Exception)" block at this point. If you change the following to:
try
            // honor System parsing limits, e.g.
            // System.setProperty("entityExpansionLimit", "10");
            factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
        catch (Throwable t)
            // Ignore AbstractMethodError, IllegalArgumentException and ParserConfigurationException
            // in case the configured XML-Parser does not implement the feature.
or to
try
            // honor System parsing limits, e.g.
            // System.setProperty("entityExpansionLimit", "10");
            factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
        catch(Error e){
            // Ignore AbstractMethodError in case there is no implementation at all
        catch (Exception e)
            // Ignore IllegalArgumentException and ParserConfigurationException
            // in case the configured XML-Parser does not implement the feature.
Everything is working as aspected again...

Bugs: open new doc, custom XMP panel crash

When opening a new document after starting Photoshop, it appears with half a checkboard pattern:
Drawing on it looks like below:
I also had an issue where I closed the doc (without saving) after drawing, then opened a new doc. The previous drawing then appeared partially twice (large, and a small version in top left corner) in the new doc, this only happened once though.
I added a custom XMP panel that works fine with CS5 to $user-dir\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels
On selecting the custom panel, in the File Info window, the panel window / CS6 crashes. (The grey window in the sshot below is an imprint of the irfanview settings I used to take these screenshots, this imprinting behaviour (not sure if it has a proper name) is reasonably common with crashed programs).
I am using the 64 bit version on Windows 7 business 64. 8GB RAM, Sys info from PS CS6 below:
Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:15, Stepping:6 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 2
Processor speed: 2666 MHz
Built-in memory: 8191 MB
Free memory: 4745 MB
Memory available to Photoshop: 7256 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GT 240/PCIe/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 960, right: 1280
Video Card Number: 1
Video Card: NVIDIA GeForce GT 240
OpenCL Unavailable
Driver Version: 8.17.12.9610
Driver Date: 20120229000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1280 x 960 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GT 240
Video Card Memory: 512 MB
Video Rect Texture Size: 8192
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Rusty\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
Startup, 136.7G, 48.9G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   5,0,10,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

According to Nvidia's website, I already have the latest drivers installed (I updated them just a few days ago). I turned off hardware acceleration as you suggested, and that fixed the problem.
You can download the XMP panel that causes the crash from: http://www.iliveinabin.com/image-xmpPanel%20v2.zip That contains the source for the panel and also the compiled panel I'm using, which is in the target folder.

Bridge doesn't recognize its own .xmp files

Using Bridge CS3 on Mac OS 10.5.8. I edit RAW (.nef) files in ACR. When I click done, save, or open image, an .xmp sidecar file is generated and saved in the same folder as the .nef. However, changes made in ACR do not show in the preview thumbnail in Bridge, and when I re-open the file in ACR, my changes are lost. The .xmp file is still there, it's just not applied. It's like Bridge doesn't know the .xmp file is there. The icons in Bridge indicating altered develop settings or crops do not appear after adjudstments are made. Star ratings made in Bridge remain. When this issue began, it would ignore sidecar files for some images, but not others. It is increasing in frequency, or may now be consistent. (If I open the file into Photoshop or save an image file out of ACR, the changes are applied to the developed image file, they are simply ignored by Bridge in regards to the Raw file.)
Files that were adjusted before the problem began still synchronize with their sidecar files. Looking at the sidecar files in a text editor shows that they contain the adjustments made.
There were no changes in any installations/updates to software or OS at the time of the problem's onset.
I've tried using a Camera Raw database instead of sidecar files, and the changes are still lost. I've tried purging caches for Bridge and for ACR. I've tried resetting and dumping preference (.plist) files.
Anyone have ideas on what I can do to salvage this program as my RAW library manager?

Matthew,
Same problem here. But I'm using CS5 in Win7.
Bridge cannot find its XMP files. Bridge does not see its XMP files. XMP files do not work. Camera Raw settings do not show in thumbnails. ACR settings lost.
I just now figured out the problem/solution.
In my case, the association between CR2 files and Bridge was usurped by Canon DPP (the Canon raw converter) which I just installed this afternoon. When I installed it, there was no immediate problem. But when I started a new work session tonight, Bridge acted as if the XMP files weren't even there.
Solution: In Windows, to set a file association, you just right-click on a file (in this case the CR2 file) and select "Open With", and then navigate to Bridge (in my case Bridge CS5). That re-establishes the link between Bridge and its own XMP files. Then simply purge your cache and let Bridge rebuild it using its XMPs (which it can now find again) to rebuild the cache with the adjustments that are stored in the XMPs.
I don't know how to do this on a Mac, but the principle is the same.
I hope this solves your problem.
Dave

Can't Enable XMP after BIOS flash to V1.4 on P55-GD85

I didn't put this in the BIOS section because while the BIOS is involved, I don't think it's necessarily a BIOS issue. However, if it should go there please move it.
While not new to computers by any stretch I committed the cardinal sin of updating my BIOS when I didn't absolutely have to. While their were some issues I'd hoped would be fixed with a new BIOS revision, they weren't critical.
I have a i7 860 Lynnfield system running Win 7 Home Premium 64 with a MSI P55-GD85 mobo which has been running fine since being built in March of this year. This was the first BIOS flash since I've built the system. The system came with either V1.0 or V1.1 (I think it was V1.1). I checked using Live Update (yes, I now know this is bad) and found there had been several udpates since my current version. I went ahead and used Live Update to flash the BIOS (yes, I know...not a good idea). Contrary to the horror stories the flash itself went fine. I watched it flash the BIOS and everything verified fine. Of course after the update I had to reset my BIOS settings to get the system to run which went fine. The problem is that the one thing I can't do is enable the XMP option for the memory without the system crashing. If I enable this option the system will POST and then do a memory dump before ever getting to the desktop. Without turning this option on I can't take full advantage of my RAM. I am running G.SKILL Trident 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 2000 (PC3 16000) which are XMP compliant and ran without issue up until the BIOS update. It is possible that there is some other setting that I didn't reset after the BIOS change to allow this to work that I am missing. I know I did a bunch of tweaking and changing of settings trying to get things to run correctly when I first built the system. I've gone over and over the BIOS and can't find anything else to try to get me to allow to enable the XMP option without crashing. By simply enabling that option my system would normally run stable at about 3.6-3.7GHz.
Does anyone have any ideas as to why this might be happening or what I can do about it? About the only other thing I can think of is to reflash the BIOS back to a previous version to see if that helps. I am sure there is something I am missing as there is no reason the BIOS shouldn't allow the XMP feature to be enabled without crashing. Any help would be most appreciated. Thanks.

Have you try to increase your RAM voltage to 1.55v ~1.6v?

How can I create a XMP List with multiple selection

Hello,
I try to build my own XMP custom panel. Herefore I need a couple of lists with the possibility for multiple selections (e.g. the choice for one language or multiple languages).
But how is it possible to integrate a list into a panel? There is no XMPList inside the custom folder. I have experimented with the standard mx:list and an array collection for data binding into the list. But how can I write the user selection into an XMP field? Example: In the List the user choose three languages (DE, EN, FR). Is it possible to collect the choice into a string and to write the result into an XMP standard field (e.g. dc:description)?
A further question is, if it's possible to use the "HTTPService" to bind an external xml-file with the languages and other informations into the panel or is it only possible to work with an array collection inside the code?
Here is my code:
<?xml version="1.0" encoding="utf-8"?>
<fi:XMPForm
          xmlns:mx="http://www.adobe.com/2006/mxml"
          xmlns:fi="com.adobe.xmp.components.*" width="100%" height="100%"
          xmlns:Iptc4xmpCore ="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
          label="XMP-Custom Panel"
          initialize="ds.send()"
          >
     
     <fi:XMPNamespaces>
          <fi:XMPNamespace prefix="dc" value="http://purl.org/dc/elements/1.1/"/>
     </fi:XMPNamespaces>
     <fi:XMPForm>
          <mx:HBox width="100%" height="26" verticalAlign="middle">
               <mx:HRule width="50%"/>
               <mx:Label text="Allgemeine Metadaten" fontSize="12" fontWeight="bold"/>
               <fi:XMPSeparator width="50%"/>
          </mx:HBox>
          <fi:XMPFormItem
                    label="Titel"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPTextInput xmpPath="dc:title" xmpType="Localized" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Titel"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPTextInput xmpPath="dc:title" xmpType="Localized" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Druckkennzeichen"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPTextInput xmpPath="dc:title" xmpType="Localized" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Verfasser"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Erzeuger des Dokumentes" fontSize="11" width="100%">
               <fi:XMPComboBox xmpPath="dc:creator" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Versionsnummer"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPComboBox xmpPath="dc:creator" width="100%"/>
          </fi:XMPFormItem>
          <mx:HBox width="100%" height="26" verticalAlign="middle">
               <mx:HRule width="50%"/>
               <mx:Label text="Enthaltene Sprachen" fontSize="12" fontWeight="bold"/>
               <fi:XMPSeparator width="50%"/>
          </mx:HBox>
          
             <mx:Script>
        <![CDATA[
            import flash.events.MouseEvent;
            import mx.controls.Alert;
            import mx.collections.ArrayCollection;
            private const NL:String = "\r";
            // A data provider created by using ActionScript
            [Bindable]
            private var subscriptions:ArrayCollection =
                new ArrayCollection
                        {data:0, label:"Deutsch"},
                        {data:1, label:"Englisch"},
                        {data:2, label:"Französisch"},
                        {data:3, label:"Italienisch"}
            [Bindable]
            private var market:ArrayCollection =
                new ArrayCollection
                        {data:0, label:"(Bitte Marktversion auswählen)"},
                        {data:1, label:"Marktversion Deutsch (M_DE)"},
                        {data:2, label:"Marktversion Englisch (M_EN)"},
                        {data:3, label:"Marktversion Frankreich (M_FR)"},
                        {data:4, label:"Marktversion Italien (M_IT)"}
            [Bindable]
            private var documenttyp:ArrayCollection =
                new ArrayCollection
                        {data:0, label:"(Bitte Dokumenttyp auswählen)"},
                              {data:1, label:"Gebrauchsanweisung"},
                        {data:2, label:"Ersatzteilkatalog"},
                        {data:3, label:"Service-Anleitung"},
                        {data:4, label:"Etikett"}
        ]]>
    </mx:Script>
                <fi:XMPFormItem label="Sprachauswahl" width="100%">
                <mx:List
                    id="userSubscriptions" rowCount="4"
                    allowMultipleSelection="true" width="100%"
                    dataProvider="{subscriptions}"
                />
            </fi:XMPFormItem>
                <mx:Text text="* Mehrfachauswahl möglich." fontWeight="normal" fontSize="10"/>
            
          <fi:XMPFormItem
                    label="Marktvariante"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPComboBox xmpPath="dc:creator" width="100%" dataProvider="{market}"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Dokumenttyp"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%">
               <fi:XMPComboBox xmpPath="dc:creator" width="100%" dataProvider="{documenttyp}"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Stichworte"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Erzeuger des Dokumentes" fontSize="11" width="100%">
               <fi:XMPTextArea/>
          </fi:XMPFormItem>
          <mx:HBox width="100%" height="26" verticalAlign="middle">
               <mx:HRule width="50%"/>
               <mx:Label text="Metadaten Photoshop" fontSize="12" fontWeight="bold"/>
               <fi:XMPSeparator width="50%"/>
          </mx:HBox>
          <fi:XMPFormItem
                    label="Originalname FA"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%" id="PS1">
               <fi:XMPTextInput xmpPath="dc:title" xmpType="Localized" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Fotoauftragsnummer"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Dateiname" fontSize="11" width="100%" id="PS2">
               <fi:XMPTextInput xmpPath="dc:title" xmpType="Localized" width="100%"/>
          </fi:XMPFormItem>
          <fi:XMPFormItem
                    label="Interne Anmerkungen"
                    labelTooltip="$$$/xmp/sdk/custompanels/Test/TitleToolTip=Erzeuger des Dokumentes" fontSize="11" width="100%" id="PS3">
               <fi:XMPTextArea/>
          </fi:XMPFormItem>
          <mx:Text text="* hier steht eine kleine Erläuterung" fontWeight="normal" fontSize="10"/>
     </fi:XMPForm>
</fi:XMPForm>
Any suggestions?
Thank you in advance.
Markus

Hi Markus,
the FileInfo SDK does not offer a ready-made list component allowing for multi-selection.
So you would need to implement one using the FileInfo SDK API. Your component "XMPList" would inherit from mx:list and would need to implement the XMPRead and XMPWrite events and talk to the XMP using the IXMPAccess interface within those event handlers.
Please have a look at the Programmer's Guide, section "XMP Flex components" and at the API description available in "docs" for further guidanc.
Hope this helps
Kind Regards
Jörg
Adobe XMP

How can I use an old XMP file on a new set of images??

I have an older XMP file that contains settings used to retouch some previous images in a particular way. I'd like to apply those same settings to a new set of images. How can I use that older XMP file on a new set of images in Lightroom?
The contents of the XMP file are as follows:
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40
">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
   <crs:Version>6.0</crs:Version>
   <crs:ProcessVersion>5.7</crs:ProcessVersion>
   <crs:WhiteBalance>Custom</crs:WhiteBalance>
   <crs:Temperature>4700</crs:Temperature>
   <crs:Tint>+4</crs:Tint>
   <crs:Exposure>-0.35</crs:Exposure>
   <crs:Shadows>5</crs:Shadows>
   <crs:Brightness>+50</crs:Brightness>
   <crs:Contrast>+25</crs:Contrast>
   <crs:Saturation>-8</crs:Saturation>
   <crs:Sharpness>25</crs:Sharpness>
   <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
   <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
   <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
   <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
   <crs:VignetteAmount>0</crs:VignetteAmount>
   <crs:ShadowTint>-1</crs:ShadowTint>
   <crs:RedHue>0</crs:RedHue>
   <crs:RedSaturation>0</crs:RedSaturation>
   <crs:GreenHue>0</crs:GreenHue>
   <crs:GreenSaturation>0</crs:GreenSaturation>
   <crs:BlueHue>0</crs:BlueHue>
   <crs:BlueSaturation>0</crs:BlueSaturation>
   <crs:FillLight>0</crs:FillLight>
   <crs:Vibrance>+5</crs:Vibrance>
   <crs:HighlightRecovery>24</crs:HighlightRecovery>
   <crs:Clarity>+8</crs:Clarity>
   <crs:Defringe>0</crs:Defringe>
   <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
   <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
   <crs:HueAdjustmentYellow>0</crs:HueAdjustmentYellow>
   <crs:HueAdjustmentGreen>0</crs:HueAdjustmentGreen>
   <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
   <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
   <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
   <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
   <crs:SaturationAdjustmentRed>0</crs:SaturationAdjustmentRed>
   <crs:SaturationAdjustmentOrange>0</crs:SaturationAdjustmentOrange>
   <crs:SaturationAdjustmentYellow>0</crs:SaturationAdjustmentYellow>
   <crs:SaturationAdjustmentGreen>0</crs:SaturationAdjustmentGreen>
   <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
   <crs:SaturationAdjustmentBlue>0</crs:SaturationAdjustmentBlue>
   <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
   <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
   <crs:LuminanceAdjustmentRed>0</crs:LuminanceAdjustmentRed>
   <crs:LuminanceAdjustmentOrange>0</crs:LuminanceAdjustmentOrange>
   <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
   <crs:LuminanceAdjustmentGreen>0</crs:LuminanceAdjustmentGreen>
   <crs:LuminanceAdjustmentAqua>0</crs:LuminanceAdjustmentAqua>
   <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
   <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
   <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
   <crs:SplitToningShadowHue>138</crs:SplitToningShadowHue>
   <crs:SplitToningShadowSaturation>13</crs:SplitToningShadowSaturation>
   <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
   <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
   <crs:SplitToningBalance>0</crs:SplitToningBalance>
   <crs:ParametricShadows>0</crs:ParametricShadows>
   <crs:ParametricDarks>0</crs:ParametricDarks>
   <crs:ParametricLights>0</crs:ParametricLights>
   <crs:ParametricHighlights>0</crs:ParametricHighlights>
   <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
   <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
   <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
   <crs:SharpenRadius>+1.0</crs:SharpenRadius>
   <crs:SharpenDetail>25</crs:SharpenDetail>
   <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
   <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
   <crs:GrainAmount>0</crs:GrainAmount>
   <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
   <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
   <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
   <crs:ToneCurve>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>32, 22</rdf:li>
<rdf:li>64, 56</rdf:li>
<rdf:li>128, 128</rdf:li>
<rdf:li>192, 196</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
   </crs:ToneCurve>
   <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
   <crs:CameraProfileDigest>3DA8CE4A626CE36A1D0C55BF157793C9</crs:CameraProfileDigest>
   <crs:HasSettings>True</crs:HasSettings>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

I’m pretty sure Adobe NEVER intended for someone to copy an XMP file from one photo to another outside of LR as a way to replicate settings.   You can make a preset from a photo, as discussed, or if you don’t want to do that, copy-paste the settings from a representative photo that you initially select to one or more new photos. You could have a special LR folder that holds standard photos to copy/paste from. Of course creating a Develop preset from the representative photo is the “normal” way to handle such situations, but maybe you have hundreds of different situations to copy settings from and don’t want to create presets for each one, but I’d argue that you could create a complex folder hierarchy for your presets and still have them findable without that much problem.
As far as the mystery about why some photos show Reset and some show From Metadata, is the Process Version (down in Camera Calibration) of the photo before reading the settings the same between the two situations? And in general, are these virgin photos newly imported into LR or have some been modified in LR, already? Does an XMP file already exist for any of these, where that XMP is being overwritten by your external-to-LR copying? Or do you have auto-write-XMP enabled and your hand-copied XMP is getting overwritten by LR, automatically, before you have a chance to read in anything?

Whats the difference between the two XMP packet tags

Hi,
I opened a file Bluesquare.indd(from XMP SDK sampke) and I found two XMP packets inside the file.
One packet with tag
and another one with tag
When I tried to extract the xmp using getXMP() method from XMPFiles then, I got the packet with tag
So can you tell me, what is the difference between two packets, why they are different
what is its use.
Thanks & Regards,
Venkatesh.E

My feeling here is that simply changing join syntax and case vs decode issues is not going to give any significant improvement in performance, and as Tubby points out, there is not a lot to go on. I think you are going to have to investigate things along the line of parallel query and index vs full table scans as well any number of performance tuning methods before you will see any significant gains. I would start with the Performance Manual as a start and then follow that up with the hard yards of query plans and stats.
Alternatively, you could just set the gofast parameter to TRUE and everything will be all right.
Andre

How do I reconnect my xmp files in PE9?

After moving and copying photos between two internal and one external hard drive I find I have a lot of xmp files in the Recycle bin. Can I "reconnect" these files to the images and video clips they belong to? The dates are messed up and tags are missing from a lot of my stuff after all the moving.
Tim K

dsf,
Not sure exactly how you moved your library but this link may help
http://www.ilounge.com/index.php/articles/comments/moving-your-itunes-library-to -a-new-hard-drive/

XMP in C++

Similar Messages

Maybe you are looking for