LR 1.1 updates XMP/metadata apparently for no reason

I have checked both "Write develop settings to XMP..." and "Autmatically write changes to XMP" and I find that just by browsing through images DNG files and XMP files are updated even though I haven't done any changes. If I have a library full of RAW/DNG files, I will suddenly have a lot of modified files, even if I haven't done any changes.
Possibly similar is that when "Automaticall..." swich is not checked, I might get the little indicator saying tha the metadata must be saved to file. Even though I haven't made any changes.
Thanks
HEK

No, I did not apply any settings or do anything. Just viewed them.
Even though I hate an application that do something behind my back, it's still better than 1.0 that actually went ahead and changed all my files in my collection (wrote XMP to JPG files). That was pretty bad...
Henrik

Similar Messages

I just did a software update that was apparently for iPhoto. When I try to open iPhoto it stops at "step 5" and will not go further. what do I do?

I just did a software update that was apparently for iPhoto. When I try to open iPhoto it stops at "step 5" and will not go further. what do I do?

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

How to update managed metadata column for all file in document library using powershell

Hi,
How to update managed metadata column for all file in document library using powershell?
Any help on it.
Thanks & REgards
Poomani Sankaran

Hi TanPart,
I have changed the code which you have give in order to get the files from SharePoint 2010 Foundation Document Library.But i am getting below error in powershell.
Property 'ListItemCollectionPosition' cannot be found on this object; make sure it exists and is settable.
Could you tell me which is the issues in it?
See the code below.
$web = Get-SPWeb http://ntmoss2010:9090/Site
$list = $web.Lists["DocLib"]
$query = New-Object Microsoft.SharePoint.SPQuery
$query.ViewAttributes = "Scope='Recursive'";
$query.RowLimit = 2000
$caml = '<Where><Contains><FieldRef Name="Title" /><Value Type="Text">Process Documents/Delivery</Value></Contains></Where>' +
        '<OrderBy Override="TRUE"><FieldRef Name="ID"/></OrderBy>'
$query.Query = $caml
do
    $listItems = $list.GetItems($query)
    $spQuery.ListItemCollectionPosition = $listItems.ListItemCollectionPosition
    foreach($item in $listItems)
        #Cast to SPListItem to avoid ambiguous overload error
        $spItem = [Microsoft.SharePoint.SPListItem]$item;
        Write-Host $spItem.Title
while ($spQuery.ListItemCollectionPosition -ne $null)
Thanks & Regards
Poomani Sankaran

My iPhone 4s has the latest OS update and this morning for no reason all my contacts have disappeared. Is there a fix or reason for this?

My iPhone 4s has the latest OS update and this morning for no reason all my contacts have disappeared. Is there a fix or reason for this?

After some troubleshooting, I decided to order a new battery. I replaced the battery and was then able to get it to restore, however--after I restore it and it comes time to restart the phone, it gets stuck and doesn't turn on.
Sorry, your repair ruined the iPhone.
She does not have apple care and even though she loved this device, she isn't going to buy another iPhone because of all the problems shes had with this one (it's just over a year old).
After you ruined the iPhone with DIY, Apple won't touch it anymore. You should have asked before all these had happened.
I'm an android user myself and I love rooting/flashing new ROMS, so if jailbreaking her phone or doing some kind of super-restore with 3rd party programs might help, I'm all for it-
Yeah, all Android user can think of is Jailbreaking, read this: http://support.apple.com/kb/HT3743

Apple iOS is ****.... I just update my apps then for some reason is stop and can't use it.. If you delete and reinstall your apps profile will be lost..

Apple iOS is ****.... I just update my apps then for some reason is stop and can't use it.. If you delete and reinstall your apps profile will be lost....
There's no rollback in the application if you encountered failed during the installation.. The application profile will be lost... ****....

Try update the app using iTune (computer) and sync to iPad.
http://i1224.photobucket.com/albums/ee374/Diavonex/Album%201/47e895d853a70f226f0 e254ed8bca59f.jpg

Re: updating XMP sidecar-file for NEF files

[Reply to a message mistakenly posted in the SDK forum:
http://forums.adobe.com/thread/1158444?tstart=0]
Adobe has stated that LR 3.4 and later follow the standard "Guidelines For Handling Image Metadata" from the Metadata Working Group, which incorporates the EXIF and IPTC standards. Adobe continues to make incremental improvements to LR's metadata handling, so I'll just focus on the behavior of the current release, 4.3. Following the detailed steps you posted:
LR 4.3 does not add Photoshop:Urgency to the .xmp sidecar.   As you've observed, Photoshop:Urgency is a deprecated field not part of the IPTC Core, so that makes sense.
LR 4.3 does copy the XMP field MicrosoftPhoto:RatingPercent from the .nef to the .xmp, but it doesn't update that field when you change the Rating in LR.   Both of these behaviors make sense. RatingPercent is not part of the standards supported by LR, so of course it won't update that field. But it is part of the XMP metadata in the .nef, and tools should in general preserve all of the XMP metadata, even if they don't use it or know how to interpret it (XMP = "Extensible Metadata Platform").

[Reply to a message mistakenly posted in the SDK forum:
http://forums.adobe.com/thread/1158444?tstart=0]
Adobe has stated that LR 3.4 and later follow the standard "Guidelines For Handling Image Metadata" from the Metadata Working Group, which incorporates the EXIF and IPTC standards. Adobe continues to make incremental improvements to LR's metadata handling, so I'll just focus on the behavior of the current release, 4.3. Following the detailed steps you posted:
LR 4.3 does not add Photoshop:Urgency to the .xmp sidecar.   As you've observed, Photoshop:Urgency is a deprecated field not part of the IPTC Core, so that makes sense.
LR 4.3 does copy the XMP field MicrosoftPhoto:RatingPercent from the .nef to the .xmp, but it doesn't update that field when you change the Rating in LR.   Both of these behaviors make sense. RatingPercent is not part of the standards supported by LR, so of course it won't update that field. But it is part of the XMP metadata in the .nef, and tools should in general preserve all of the XMP metadata, even if they don't use it or know how to interpret it (XMP = "Extensible Metadata Platform").

Firefox stopped updating a while ago for unknown reason;now stuck at v 2.0.0.20-- trying to manually update from your site doesn't work.

Firefox stopped updating a while (couple of years) ago for some unknown reason. The button is checked for automatic updates. It was a while before I noticed, so now I've been stuck at v 2.0.0.20 for some time, and trying to manually update from your site doesn't work.
No update available will work, since I missed some. I can't even see what most of the buttons are on these pages of your site. Do I need to reinstall Firefox, as some people have suggested to me, and if so, how do I go about doing that? I'm not particularly computer program savvy.
Thanks,
Taav

Which version of Mac OS are you running?<br />
Is that a OS X 10.2 or 10.3 version?<br />
The last Firefox version that works on OS X 10.2 and 10.3 is 2.0.0.20.
*https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/
The last Firefox version that runs on Mac OS X 10.4 is Firefox 3.6.28.
*https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest-3.6/
*http://www.mozilla.org/en-US/firefox/3.6.28/system-requirements/
Current Firefox versions require a Mac with an Intel processor and OS X 10.6 (Firefox 16 runs on Intel Mac OS X 10.5).
*http://www.mozilla.org/firefox/23.0/system-requirements/
For an unofficial Firefox 17.0.8 ESR compatible version that runs on a PowerPC Mac with OS X 10.4.11 or OS X 10.5.8 you can look at TenFourFox.

When the 5.0 version came out a notice was sent to my laptop stating it was not compatable with Garman GPS updates at this time. I would like to know if that has been fixed allowing Garman GPS updates now? I did not update to 5.0 for that reason.

I did not update to 5.0 Firefox because it said it was not compatable with the Garman GPS updates at this time

I did not update to 5.0 Firefox because it said it was not compatable with the Garman GPS updates at this time

I have lost all my bookmarks, apparently for no reason. I tried all suggestions offered by Firefox without success

As I have already explained, all my bookmarks have mysteriously disappeared. I tried the suggestions in Firefox's support page on lost bookmarks. No success.

In your C:\User folder, do you have a folder for your old account? Your Firefox data would have been in that folder:
C:\Users\''oldusername''\AppData\Roaming\Mozilla\Firefox

[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

XMP metadata is lost while updating XMP using Exempi on linux

Hello, I'm using the library XMPFiles for Linux (Exempi) to update XMP metadata of a tiff file. As a result RichTiffIPTC Tag is being removed and Photoshop tag was changed (2 photoshop image resources are also being removed : IPTC metadata (ID=1028) and MD5 digest of the IPTC (ID=1061)).
I've checked the library sources and found the following code :
#if XMP_UNIXBuild
// ! Hack until the legacy-as-local issues are resolved for generic UNIX.
        iptc = 0;    // Strip IIM from the file.
        if ( tiff != 0 ) tiff->DeleteTag ( kTIFF_PrimaryIFD, kTIFF_IPTC );
        if ( psir != 0 ) {
            psir->DeleteImgRsrc ( kPSIR_IPTC );
            psir->DeleteImgRsrc ( kPSIR_IPTCDigest );
#endif
Can anyone please explain the reason of such behavior?
TIA,
Slava

John Nack on Adobe : Per-layer metadata comes to Photoshop
This was the article that made me think this might be possible.
There is also the preference to Create Markers From Metadata
["Metadata"]
          "CreateLayerMarkersFromFootageXMP" = 01
Which made me wonder if there is a way to create the metadata in the first place that made it something AE would read and automatically change to layer markers.
Any ideas?

Modifying XMP metadata does not modify the document

Another from couple questions which accumulated over time.
If I modify layer in document by adding or updating XMP metadata, the document itself is not modified (does not enable save), so far if document is closed without doing some other action which marks document as modified, data are lost.
Question: how to either force document to see changes in XMP meta or how to mark document as modified?
Code snippet:
activeDocument.activeLayer.xmpMetadata.rawData = meta.serialize();
Thanks,
--Petr

When you ask app-specific questions, you should really specify the app you are referring to.
I'm guessing you are talking about Photoshop. This seems to be a scripting related question, and you'll probably get better answers on the Photoshop forum: http://forums.adobe.com/community/photoshop/photoshop_scripting
Harbs

DB13 SXPG_COMMAND_EXECUTE failed for backup reason

Dear Gurus,
I am facing error during DB13 since passed few days during backup and update statistics .SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
cancelled after system exception ERROR_MESSAGE..
Please do need full.
Thanks,
Regards,
Snehal Patel

Hi,
Do you have Standalone gateway on your server ?
You can try Go to the db13 -> goto -> backend configuration
And change background or application server to the database server (where DB physically resides)
If you Database is on another host then SAPXPG_DBDEST_<dbhost> or <virtual_dbhost> (a TCP/IP connection) will play an important role for executing SAPXPG command.
1) Install a Gateway instance on the DB server
2) Mention the Gateway hostname and service ( sapgwxx) in the RFC destination SAPXPG_DBDEST_<DBHOST> using SM59.
Also check the permission of the SAPXPG file.
SAP Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13 - Point 8

Clarification for nef vs xmp metadata

I am learning Lightroon, and am attempting to understand how to maintain consistency between applications.
If I understand correctly:
On import, or on “Read metadata from file”:
If an .xmp sidecar exists, I assume Lightroom will read the .xmp, and ignore the metadata in the .nef file.
If there is no .xmp file, Lightroom will read the metadata from the .nef file.
The data read is stored in the catalog, along with any changes, and is not written back unless the Catalog preferences is set to “Automatically write changes to XMP.” or a manual write is initiated for selected files.
Lightroom will not ever write metadata to the .nef files.
If metadata was read directly from the .nef file, the sidecar is only created when a change to metadata is made in Lightroom, and Catalog preferences is set to “Automatically write changes to XMP.” or a manual write is initiated for selected files.
Can anyone confirm that my understanding is correct, or clarify the process for me?
Thanks

Turns out I was completely wrong about Lightroom ignoring the .nef file if a sidecar file exists. So, my revised attempt to understand this is a follows:
On import, or on “Read metadata from file”:
If there is no .xmp file, Lightroom will read the EXIF and tagging metadata from the .nef file.
If an .xmp sidecar exists, it appears that Lightroom will read the EXIF data in the .nef file. It also appears to read both the .nef and .xmp sidecar files, and selects the latest tagging/rating information based, probably, on the Metadata date field. (See lower section for further info)
The data read is stored in the catalog, along with any changes, and is not written back unless the Catalog preferences is set to “Automatically write changes to XMP.” or a manual write is initiated for selected files. ( For some reason, Lightroom appears to create .xmp files on import for a few files before any changes occur. I have not figured out a pattern to this yet). When Lightroom does create or update a pre-existing .xmp file, it writes a significant portion of the EXIF data.
As Geoff the Kiwi pointed out, Lightroom will write to the .nef files if you are changing the creation date, and have the “Write date or time changes into proprietary raw files” box checked. (It appears you also need to check the “Automatically write changes into XMP” box before Lightroom (5) will actually write the changes to the .nef files.
I have been using Daminion for my tagging and rating tasks. I allows writing to the .nef file or to an .xmp sidecar file. Changes written to file in either program, are picked up when “Read tags from file” is executed in the other program. This is true whether Daminion writes to the .nef or .xmp files. Both Lightroom and Daminion have to read both .xmp and .nef files, and have the ability to select the latest information for this process to work, and it does work flawlessly in my somewhat limited testing to date.
There is a YouTube video that demonstarates this very nicely.

Editing XMP metadata in Bridge for checked-out files?

Our custom connector does not implement the WRITE_XMP_METADATA Capability because we do not want to change the XMP of a file in our DAM system without checking in a new file version.
However, when a file is checked out through Adobe Drive, we would expect to be able to edit its XMP metadata in Bridge just like we can for local files.
It looks like this is still not possible with Adobe Drive 3, i.e. if your connector does not implement the WRITE_XMP_METADATA Capability you cannot edit XMP for checked out files either.
It seems weird that you can edit XMP metadata for checked out files with regular CS applications but not with Bridge. Is this something that is expected to be fixed in a future version?
Thanks

In our design, editing XMP data in Bridge and in regular CS applications is different, the former one will be routed to SetXMPHandler in you connector, in the latter case, CS applications take the normal file writting ways to embed XMP data in the file content.
The purpose of this design is to offer similar user experience for normal users when they edit XMP data for AD assets and local file assets, they don't need to check-out files first.
To address your issue, I think you can add some codes in SetXMPHandler to auto check-out files before real XMP operation, and check-in them before exiting the handler
We will consider to make some enhancements for this part, that's, to allow editng XMP data for the checked-out files in Br, in the next release, thanks for this advice.

LR 1.1 updates XMP/metadata apparently for no reason

Similar Messages

Maybe you are looking for