Did 9.4.2 break XMP metadata, or just the logo?

I updated to Acrobat Pro 9.4.2 several days ago, and so far have not had problems printing (from up-to-date Vista Home Premium to networked Xerox 6180 via Postscript driver). But this morning I noticed something odd in the Properties for any PDF. When I click Additional Metadata under Properties, down in the lower left corner where I used to see "Powered by XMP" I now get a red button with a white X:
Oddly, if I go to Document/Examine Document and look at the metadata there, I get the same view of the metadata, except now it has the "Powered by XMP" logo:
I'm hoping that there is nothing more serious than 9.4.2's simply losing the XMP logo in this one location, but who knows? I have been encouraging customers to use metadata, but glitches like this don't make it any easier.
David W. Goodrich

Try resetting the SMC.
Barry

Similar Messages

Is there a way to tell if the date on a picture in iPhoto is from actual metadata vs just the date it was imported to the program?

I have many photos in iPhoto whose dates I know to be wrong and many appear to be the date I moved them all to a new Mac. I photos in question, I think, were originally on a PC and in Picassa. If it was taken before metadata was embedded, I suppose I can just guess and change the dates on the photos however, if iPhoto just applied the date of the transfer to the Mac, perhaps there is accurate metadata somewhere that I could retreive. How can I tell where iPhoto is getting its dates for pictures?
Thanks,

If the Exif metadata is intact, then iPhoto gets the date from there. If it's not, then iPhoto gets the file date.
So, if iPhoto is showing you the date of import there is no Exif intact.

Problem with Bridge CS4 reading/editing XMP metadata added in Bridge CS6

Please excuse me if this is a dumb/obvious question. I did try searching the forums for similar problems and didn't find anything that seemed to speak to my issue.
I'm having a problem where Bridge CS4 won't read/edit xmp metadata (specifically, keywords and descriptions in the IPTC panel) that I have entered using CS6. it will read some files, not others. The files are all .mp4s. Of these files, I can read/edit IPTC panel metadata for some of them in Bridge CS4; I can add metadata for all of them in CS6. I see no particular pattern in these files to explain what is and isn't read/editable in CS4.
My question is whether this is a compatibility issue between different versions of CS (in this instance, CS4 and CS6). i know it's a tired refrain to blame software when it could easily be user error, in which case I'd be frankly delighted to know what i'm doing wrong. Please bear with me as I give a few more details.
I'm using macs. I've tried this on multiple systems - for instance, on a mac pro 3 which for some reason has both CS4 and CS6 installed, i can add and edit keywords using CS6, but not when using CS4. Again, in CS4, some .mp4 files read/edit, others do not.
Bridge CS4 blames the files and tells me that the selected file cannot store xmp metadata, and that the properties cannot be modified. To be specific, in the metadata panel it says "this property cannot be modified"; in the keyword panel, it says, "This file (zzz.mp4) cannot store xmp metadata. No changes will occur." This seems odd, because I'm able to add xmp metadata for the same files in CS6 on the same computer, and other computers. I know this problem would disappear if all our computers were using CS6 (or CC), but unfortunately that's not a possibility at the moment. Some of them only have CS4.
Computer details (not an exhaustive list, but two instances): mac pro 3.1 running snow leopard, 16GB memory; macbook pro 4.1 running snow leopard, 4GB memory; adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Things I have tried:
Permissions - the files are set to read/write for everyone. Given that I can add/edit metadata in CS6, it doesn't seem to be a permission issue.
Purging the cache - other users seem to have had problems adding metadata in Bridge CS4 where purging the cache for affected files solved the problem. Didn't work in this instance.
Upgrading all affected computers to CS6/CC is beyond my control. I need to figure out why CS4 won't let me read/add/edit xmp metadata, if only for the sake of understanding the broader implications for interoperability.
Any helpful suggestions would be much appreciated.
Thanks,
Kevin

adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Without having experience with mp4 files and metadata my observation is that you certainly have not updated Bridge CS6 ( should be 5.0.2.4) and I believe also not the latest version of CS4, can't imaging this also stayed at .0.0 so first try to update both.
And if CS4 can read the data of some files it should be capable of reading them all. Be sure to have the files completely cached first, can take a while.
Other things to try in CS4 is refresh preferences (hold down option key while restarting Bridge and choose reset prefs).
And also check for hidden cache files using menu view/show hidden files. Sometimes those cache files can be troublesome between versions.
If purge cache did not work and reset prefs also failed consider to also delete Bridge plist file and Bridge cache file manual (from user library)

Xmp metadata searchable on mac os x server 10.5.6?

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

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

Modify LabelGraphics.js to extract other XMP metadata from images

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

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

[CS3 JS] How to force XMP metadata update for a thumbnail?

Hi Folks,
In a JavaScript in Bridge CS3, I'm updating a value in the XMP metadata for a Thumbnail. Later in the script I want to read the updated XMP metadata information from the Thumbnail, but often Bridge hasn't updated the metadata by the time I read it. In other words, my script reads the value prior to the update. I'm guessing there's a caching issue going on.
I'm new to Bridge scripting, and I am hoping someone here can offer suggestions on how I can (or, even *if* I can) force Bridge to update the XMP metadata cache for a file so that when I read it later in the script it will reflect the recent changes. I've tried using Thumbnail.refresh(), but that doesn't seem to do the trick. I don't mind a slower script, I just want to be able to read the correct value.
Thanks in advance for any help!
-- Jim

Hi David,
I'm running this script on a MacBook Pro, 2.5GHz, 4GB RAM.
Here is a sample JSX that shows the issue I'm having:
#target "bridge-2.0"
main();
function main() {
    if( xmpLib == undefined ) {
        var pathToLib = Folder.startup.fsName + "/AdobeXMPScript.framework";
        var libfile = new File( pathToLib );
        var xmpLib = new ExternalObject("lib:" + pathToLib );
    var myValue = "Headline Test";
    var myFilePath = "~/Desktop/TestFile.tif";
    var curHeadlineStr = XMPGetHeadline(myFilePath);
    $.writeln("Headline value: \"" + curHeadlineStr + "\"");
    XMPWriteHeadline(myFilePath, myValue);
    // *** I would like to refresh the cache here ***
    curHeadlineStr = XMPGetHeadline(myFilePath);
    $.writeln("Headline value: \"" + curHeadlineStr + "\"");
function XMPGetHeadline(theFilePath) {
    var thumb = new Thumbnail(File (theFilePath) );
    md = thumb.synchronousMetadata;
    xmp = new XMPMeta(md.serialize());
    var myHeadlineXMPProp = xmp.getProperty
        (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
    return myHeadlineXMPProp;
function XMPWriteHeadline(theFilePath, theTextStr){
    var thumb = new Thumbnail(File (theFilePath) );
    md = thumb.synchronousMetadata;
    xmp = new XMPMeta(md.serialize());
    var myOrigHeadlineXMPProp = xmp.getProperty
        (XMPConst.NS_PHOTOSHOP, "Headline", XMPConst.STRING);
    xmp.deleteProperty(XMPConst.NS_PHOTOSHOP, "Headline");
    xmp.setProperty(XMPConst.NS_PHOTOSHOP, "Headline", theTextStr, 0, XMPConst.STRING);
    var updatedPacket = xmp.serialize
        (XMPConst.SERIALIZE_OMIT_PACKET_WRAPPER | XMPConst.SERIALIZE_USE_COMPACT_FORMAT);
    thumb.metadata = new Metadata(updatedPacket);
To run this script, in main(), set the myFilePath variable to the path of a file that has an "IPTC Code" "Headline" property.
This script, when run, sets the "Headline" property value to the value of myValue. After runing the script for the first time, take a look at the console log. You should see that Headline value displayed does not change between the two console entries. My log looks like this after the first run:
Headline value: "undefined"
Headline value: "undefined"
The thing is, the second entry in the console listing, above, was created after the Headline value was set by XMPWriteHeadline(). The two values should be different between the two console entries.
If you run the script a second time against the same file, you will see that the Headline value does contain the value that was written in the first run of the script--it just took some time to update the cache, I'm guessing. Here's the second run's log:
Headline value: "Headline Test"
   Headline value: "Headline Test"
So, what I'm looking for is a way to insert code (where the comment line "//*** I would like to refresh the cache here ***" appears), to force Bridge CS3 to refresh its cache so that when I call XMPGetHeadline() after calling XMPWriteHeadline(), the Headline value will return the value that was just written.
I hope this is clear enough...
Thanks!!!!
-- Jim

How to remove xmp metadata?

I need to remove the "XMP metadata" information in the tiff(photoshop) files via scripting. Is it possible? Kindly advice me. Please provide examples.
Thanks for looking into this..
Regards,
Maria Prabudass

This will remove as much metadata that is possible by using scripting, anything else you need ExifTool.
#target photoshop
var f = File(Folder.desktop + "/example.tif");
removeMetadata(f);
function removeMetadata( file){
if ( !ExternalObject.AdobeXMPScript ) ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
        var xmpf = new XMPFile( File(file).fsName, XMPConst.UNKNOWN, XMPConst.OPEN_FOR_UPDATE );
        var xmp = xmpf.getXMP();
        XMPUtils.removeProperties(xmp, "", "", XMPConst.REMOVE_ALL_PROPERTIES);
      if (xmpf.canPutXMP( xmp )) {
         xmpf.putXMP( xmp );
      xmpf.closeFile( XMPConst.CLOSE_UPDATE_SAFELY );
The only other way is to save for web, open the file again and save as a tif.

"Writing XMP Metadata Did Not Complete Successfully" Issue

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

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

Resolving " Writing XMP Metadata did not complete successfully " Errors

On certain files, when I try to save the metadata, I get this error - Writing XMP Metadata did not complete successfully
Does anybody know why and how to resolve the issue?
Thank you.

Check if your files are write protected! For RAW files, the xmp sidecar file must not be write protected. For JPG and other non-RAW files, the image file itself must not be write protected.

What's the reason for " 'Writing XMP Metadata' did not complete successfully

I rightclicked an image and selected "save metadata to file" and got this not-so-very-informative error message. What could be the cause? The file is there and it is not write protected.
Adobe - what about giving some more information when LR encounters errors?
Win XP, LR 1.3.1

While read only is the most likely cause, I have been trying to track down a similar problem which so far I can only equate to the creation time of the file ending in 00.
For example, I have a file taken at 6/13/2006 1:00:00 PM
If I do Metadata -> Edit Capture Time...
and set the time to be 6/13/2006 1:00:01 PM
Then click twice on the Resolve Conflicts button for Metadata, the second one works. Both times I tell it to overwrite the metadata on disk. My assumption is that the data processing logic has issues reading in entries like:
2006-06-13T13:00:00-08:00
I would even go so far as speculating it treats them as just the day and drops the hour / minute portion. The reason for this conjecture is that I stumbled on this issue when exporting images would occasionally have 2006/06/13 12:00AM as the timestamp and when I checked which ones had problems, they all were taken at 00 seconds into the minute.
Henrik, if you are still having this problem, does the file happen to have a 00 second creation timestamp? If so, try changing it by a second and I would be curious if you it starts working for you too.
Cheers,
John

XMP metadata from Flashbuilder why not visible in Adobe Bridge?

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

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

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

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

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

Best practice in writing xmp metadata?

I know to switch off the 'automatically write to xmp metadata' feature. But, after doing this, what is the best way to ensure the xmp metadata does actually stay up to date?
My understanding is that by switching the automatic writing back on, LR goes through the whole catalogue, comparing the data in its database with the data in the xmp files, and every time it finds something different, it copies from the database to the xmp. However, there would seem to be two problems with this. i) it's extremely slow, because it's such a big job, and (b) presumably any changes made elsewhere, eg in ACR, will be overwritten.
The alternative seems to be to right click on the folder while in library mode and select "save metadata". However, for some unknown reason, this is unbelievably slow. What prompted me to write this message is that nearly an hour ago, I did this with a folder of 78 files, and it's still churning away. In that time, I've had time to log on to this forum, read a few messages, do a search to see if there is anything helpful, and then write and edit this. I don't dare try this with the folders I have with three hundred photos in!
The LR catalogue is in a partition with hardly anything else in it, on a different physical drive from LR itself. It gets defragged more frequently than the defrag utility thinks it needs to be. During metadata writing and many other operations, the CPU maxes out at 100% yet only about 75% of my 1GB memory is used.
Is there anything I can do?
I'm on an old-ish PC and am not in a position to upgrade (please - any messages just saying I need a newer computer are not going to be any help :-) ). Any other help would be appreciated.

Thanks, Mel. You just posted as I was writing the previous message!
I think you nailed it. The 78 pictures, I did by right-clicking on the folder name in the right-hand fly-out panel in library and selecting 'save metadata' (hope the choice of words here is clear!). I've just tried the ctrl-a, ctrl-s technique you describe, and it whizzed through a folder of 127 photos in no time.
So, you're right - there appears to be a bug.
One more problem - there was an error in saving to the tifs in the folder. A separate problem which I'll look at tomorrow.
Back to the other part of my original question. What is the most efficient way to keep the xmp data up-to-date? Considering that there's massive scope for human error in having to remember to save manually all the time, this can't, surely, be the best way to do it. What do people generally do, and has anyone evolved a 'best practice'?

Weird metadata problem in the "copyright" XMP field

Hey,
This is a really weird problem and I can't figure it out why it happens...
Along the years I create some metadata presets where the copyright field changes as the year changes. For instance:
© 2008 Ricardo Amaral, All Rights Reserved
© 2009 Ricardo Amaral, All Rights Reserved
However, some photos from 2008 had the copyright after the comma in lower case, like this: "© 2008 Ricardo Amaral, all rights reserved". Now, every time I try to change only 'a' to 'A' in "all", or only the 'r' to "R" in "rights" or the other 'r' in reserved or even all of them, it doesn't work. Lightroom, automatically, renames it back for me in lowercase. I have no idea why...
What's even more strange is that if I change the year to 2009 or 2007 (probably others too) and now try to rename the 'a', 'r' and 'r' to uppercase again, it works, just because I changed the year from "2008" to something else. There's also another strange issue like this, you probably noticed above that I used the copyright symbol and not "(c)" and the symbol is what I'm using in the metadata copyright field. But if I replace "©" by "(c)", leave the year at "2008" and then try once again to rename the 'a', 'r' and 'r' to uppercase, it now works too.
This is weird right?
Basically, I want to have this "© 2008 Ricardo Amaral, All Rights Reserved" but Lightroom automatically renames to "© 2008 Ricardo Amaral, all rights reserved" when I try to fix it.
Any suggestions?

Ok, I'll explaing what I did...
And of course I did backup the lrcat file before doing any changes. Now that's out of the way...
What tool did you use?
Since I didn't want to install anything and since I use Firefox, there's an extension called "SQLite Manager", I used that.
Was the tool read-only by default, or could you just start changing data values?
Not that I noticed no. But I did noticed that when I changed something, it always asked me if I really wanted to do those changes and it even shows the query it's about to perform to the database.
How did you determine which table held the relevant data? How did you determine which *rows* held the problem pictures? How did you actually change the value - just type over and tab out? Did you need to do a COMMIT or was it automatic?
I'm not very database savvy and I find easier to just search in a text editor so I just exported all tables (there's an option for that) as .sql file format and opened it up in a text editor and then searched (case sensitive) for the string "2008 Ricardo Amaral, all rights reserved". Now, you kinda need to understand a bit of the SQL syntax (the .sql exported file are just SQL instructions to insert the data you just exported into another database) and look for the relevant tables and fields.
I found 6 references to that string where 5 of those where in the table Adobe_AdditionalMetadata in the xmp field. Those were relevant to "Copyright" metadata field in the pictures added to the catalog. I didn't change those manually.
The other reference was in the table AgLibraryTag and I have no idea what this table is for. But there were some rows relevant to the metadata presets you have for that respective catalog. I only had 3, for 2004, 2008 and 2009 (dry season between 2004 and 2008 lol). There's two relevant fields on that table, lc_name and name. For the lc_name, all words were lower case and that's what I believe the lc in lc_name stands for, so, nothing to do here. As for the name field, both the 2004 and 2009 were all as they should be, with the first letter upper case, the others lower. But for the 2008, it was "all rights reserved" instead of "All Rights Reserved". So I just fixed that.
No need to save the database, when you do changes to any rows to any tables, they are directly modified in the database.
After that, I opened up Lightroom, selected the problematic pictures and aparently they were fixed; the copyright field showed correctly. However, the specific fields in Adobe_AdditionalMetadata for those pictures were not yet fixed. To fix this, I just saved the metadata to the files and then read it back; this rewrote the database fixing everything.
Did you have any problems?
Nope, everything's working fine so far...

Message: 'FILE CANNOT STORE XMP METADATA'

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

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

Did 9.4.2 break XMP metadata, or just the logo?

Similar Messages

Maybe you are looking for