XMP file problem

As a photo archivist at a museum I need to be able to fill in the description fields of the xmp file before the image is created. My work flow is exceptionally inefficient due to wait time as the scanner creates the image file. Short of using two scanners and two computers is there a function or step within photoshop that will allow me to create an xmp file out ahead of the image file?

I'm wondering if Photoshop version is going to make a difference from the point of view of image size.  Have we always been able to paste a layer bigger than the canvas for instance?  I am pretty sure the answer is yes.
But Noel's idea would work perfectly, and I suspect the OP's version of Photoshop is too new to support TWAIN.
So there you are.  Create a new document and start filling in the EXIF data in Bridge.  Then duplicate the scanned artwork into that document and flatten.

Similar Messages

  • Acrobat X save metadata to XMP file problem

    I am having no luck saving metadata from a PDF to an XMP file using Acrobat X. This has worked properly for me in previous versions of Acrobat, but since upgrading to Acrobat X 10.1.7 the XMP file is given no name automatically, and when saved is zero K and contains no data. I am running on a Mac Pro 3,1 using OS X 10.7.4. I have found only one other mention of this problem in the forum, but it was not answered clearly. Is anyone else having this problem?
    Many thanks for any assistance with this!
    2014 Update: Still no solution to this. Am I alone with this problem?

    Hi Steve,
    Thanks for your time on this. Our workflow includes having to repurpose xmp metadata from existing PDFs and apply it to new PDFs. This involves going to the "Document Properties" dialogue, selecting "Description", then "Additional Metadata". From the sidebar of the Additional Metadata dialogue, we would choose the "Advanced" option, which would then allow us to either "Save" the xmp data to a file, or "Replace" the PDF's current metadata with data from an existing xmp file.
    This worked perfectly up until we moved to Acrobat X, at which point we were no longer able to save the xmp data to a file. We are able to use the Replace function, but it's critical that we also are able to Save the data.
    As David noted, we are also able to successfully Save an xmp file using Acrobat XI Pro running on Windows 7. However, all our production work is done on our Macs, so we hope to regain this capability on the Mac version of Acrobat X Pro or XI Pro.
    Cheers and thanks.

  • ACR 4.3 .xmp file problem

    Would appreciate help on this if anyone has seen the problem.
    I use ACR 4.3 on windows XP Pro with CS3, 4 gig ram.
    My normal practice is to copy my CF cards to folders on the desktop, then
    drag each folder to Bridge to rough select the keepers.
    I then open the remaining images in ACR and make further deletions if
    necessary.
    When I delete images from the ACR screen, the X appears as normal but the
    sidecar.xmp file is not been deleted, only the NEF deletes.
    I can't recall having this problem before I upgraded to ACR 4,3 from 4,2.
    Perhaps it's a bug or I may have disturbed a setting in the preferences etc
    when I upgraded.
    Any ideas?
    Regards
    Michael

    Ramón G Castañeda wrote:
    > Camera Raw 4.4.1 contains new profiles for all cameras and fixes.
    That's right. And it also can read the updated DNG 1.2 file format. Camera Raw 4.3 cannot; it will read DNG 1.0 and 1.1 only ... or to be more precise, it
    i can
    read DNG 1.2 files but only the 1.0 and 1.1 parts of them.
    And DNG Converter 4.4 and 4.4.1 will write DNG 1.2 files.
    -- Olaf

  • 4.1.1 SDK Problems with missing xpacket tags in sidecar XMP files

    The current 4.1.1 SDK has problems with sidecar XMP files that don't have the xpacket headers and trailers, i.e:
    <?xpacket begin='' id='W5M0MpCehiHzreSzNTczkc9d'?>
    <?xpacket end='w'?>
    is missing. Now, unfortunately Adobe Bridge CS2/CS3 does not export these xpackets in sidecar XMP files.
    The standard, http://www.aiim.org/documents/standards/xmpspecification.pdf, is also very vague about it all:
    ● Write external metadata as though it were embedded and then had the XMP Packets
    extracted and catenated by a postprocessor.
    The grammar is strange(past tense had) and the spec implies that the xpacket should be extracted and again catenated... Someone should review this document and clearly state if xpacket statements should be in sidecar files or not. I suspect myself that they should be there, but the standard is very vague.
    Anyway, there are two places in the SDK code where changes might be needed:
    XMPFiles::Initialize has XMP_Asserts in case the xpacket header/trailer is missing, but the underlying assert is only active in debug builds.
    XMPScanner::PacketMachine::FindNextPacket () also has in its truth table the assumption that the xpackets exist.
    There could be even other places in the code that assumes that the xpacket tags are present in all files, which includes text XMP sidecar files.
    Anyway.
    a) Shouldn't bridge export the xpacket tags? Same with any other application?
    b) If the spec is vague, then the SDK should not assume that the xpacket tags are present.
    Any comments? Has someone already fixed this issue as I suspect a lot of apps using the the XMP SDK would break concerning reading XMP sidecar files? Thx, Kent

    I was able to work around the problem by creating a mapped view of the .xmp file (this creates an array in memory backed by the file on disk, so there's no need to read the file into a separate internal buffer), and constructing the SXMPMeta object directly from the buffer. (The ctor for that class calls ParseFromBuffer, so this is the same thing as was suggested by other messages in this thread.)
    It seems that Adobe needs to do one of these things:
    (1) say that Bridge CS3 has a bug, and agree that Bridge CS3 should include a proper xpacket header when writing xmp sidecar files
    (2) say that the XMP Toolkit has a bug, and that the SDK should be able to parse sidecar files without an xpacket header, and agree to fix the toolkit
    (3) say that Bridge CS3 and the XMP Toolkit behave as expected, but then provide a sequence of steps by which users of the XMP Toolkit are expected to read xmp sidecar files written by Bridge CS3
    Does Bridge CS4 write an xpacket header to the xmp sidecar files?
    Maybe what I could do is create a custom file handler for .xmp sidecar files, so I could use the SXMPFiles for everything, instead of having to special-case .xmp files.
    My needs are pretty modest though, and it might be just as simple to use the MS DOM-based XML parser for load the xmp sidecar file. I bet I could get the data I need (only the "Rating" for now) using a simple XPath expression.
    -Matt

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

  • 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

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

  • How can I make metadata saved to xmp file stay saved?

    When a raw file badge shows that the file has been changed, I use Metadata Save to File & for the large majority of my images, the badge goes away and Metadata Status Changed does not show the file.  For some of my files, however, the Save to File command doesn't work properly.  If I am only displaying files with changes, the file briefly disappears, then returns.  Even if I go to Windows Explorer and delete the xmp file, then again Save metadata to file, it pops up again with the badge saying it needs to be saved.  Can anyone tell me what I might be doing wrong, or is there a bug?  I'm using Lightroom 4.3 64 bit on Windows 7.

    I have determined one definite cause for this problem, documented (see 2nd post) here:
    http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_4rc_metadata_needs_to_be _saved_status_not_cleared_by_saving_metadata
    As has been mentioned, following metadata save with metadata read is a work-around.
    Note: you can see exactly, everything, the difference between metadata in catalog and metadata in xmp on disk, using ChangeManager's "Compare Catalog to Disk" feature; hint: choose 'No Exclusions' to see the "inconsequential" differences too. Reminder: this does a bunch of stuff involving xmp file copying and saving xmp / reading metadata / restoring afterward... - which presents lots of hoops to jump through, at first, in Windows, and forever, on Mac, but if you tough it out, you will get the pot of result gold at the end of the hoop rainbow...
    Cheers,
    Rob

  • Bridge stops recognizing it's own .xmp files from Canon 5DMKIII

    I use Bridge to add keywords to my RAW files. I use both a Canon 1D MKII and a Canon 5D MKIII camera. I use Canon's "Digital Photo Professional" (DPP) to process my RAW files because I prefer the colors (I am a picky perfectionist, so don't try and convince me to use ACR to process my RAW files!) When I make changes to my RAW files shot with the 5DMKIII in DPP and "save" the changes to the RAW files, Bridge suddenly doesn't recognize the file's associated .xmp file, and my keyword association is lost. If I simply open the file in TextEditor and re-save it, suddenly Bridge recognizes the file again. RAW images shot and processed with this same procedure from my Canon 1D MKII don't exhibit this problem.
    This thread from a couple years ago is the same problem I am experiencing:
    http://forums.adobe.com/message/2933287#2933287
    Is there any other solutions to this? I shoot several thousand images per weekend, and opening each file in TextEdit and saving is NOT an option!
    Please help!
    P.S., I'm using Bridge CS5.1 v 4.1.0.54

    Wes Duenkel wrote:
    I am a picky perfectionist, so don't try and convince me to use ACR to process my RAW files!
    Birds of a feather you and I, except that (with the help of a very nice forum member here) I have actually managed to get the same color out of Camera Raw that I get from Canon, so that is now my default in Camera Raw.  Unfortunately, we created a profile for a different camera than you have (I use a 40D), so it is not applicable for you.  But I just wanted to comment to say that I know EXACTLY how you feel. 
    Sorry, I don't have much to offer re: help for your .xmp issue.
    -Noel

  • Camera Raw 6.7 does not save XMP files

    I am running Camera Raw 6.7 on a Windows XP machine.
    In the Preferences under "General" I have the "Save image settings in" set to "Sidecar ".xmp" files.
    And in the DNG File Handling, I do NOT have the "Ignore sidecar ".xmp." file check-box checked in.
    But still when I alter a raw file and press Done the DNG file changes date/size and no XMP-file is
    created in the directory. Also when Ioad the picture and "reset" it to "Camera Raw Default" and
    press Done, the next time I open it is in the "Image settings" state anyway
    Anyone have any idea what the problem could be ?
    Regards,
    Klas

    Noel Carboni wrote:
    Adobe has taken the decision to ALWAYS write metadata into file types they know the structure of.
    Personally I find this approach apalling...
    And you were accused of being an Adobe "fan-boy" only hours ago...
    +1 vote for sidecar option - all file types...

  • .xmp files showing up in my SD card when accessing RAW files in Finder... Very weird!

    Hi,
    I'm having a very weird problem...  I'm using a 4GB Scandisk SD card and am shooting my RAW photos on a Canon Rebel 2ti.  I'm using a Macbook Pro, 2011 2.3Ghz i5, 4gb of Ram, with Lion v. 10.7.2 and am accessing the SD card RAW files through Finder.  I'm secondary clicking on the image file or double clicking them as PS is my default opening program for RAW files.  When I hit the "Done" key on any of the Photoshop files, a new .xmp file shows up in Finder.  When I open it, it's a Microsoft Messenger for Mac 8 License Agreement...
    I do have Microsoft Office 11 installed and have never used Messenger.  It's not a huge deal, but it's driving me crazy and it's totally weird!
    Thanks,
    -Dave

    It's a lot of separate, unrelated things happening to you in one long chain, but each step is normal and explainable.
    You are opening raw files straight from a card into Photoshop. Photoshop will open them in Camera Raw. Camera Raw's preferences are set to save changes in XMP sidecar files. You are clicking Done, which applies the default Camera Raw processing, and that change generates an XMP file to store these new settings. That's why an XMP file is showing up in the same folder. On a computer, that's fine. But writing back out to a camera card with a device other than the camera is not recommended. What is recommended is to use another, faster way to preview raw files on a card without changing them (Adobe Bridge, Lightroom, Apple Aperture, Photo Mechanic, etc.), so that the card's left untouched as it should be.
    If you don't want the XMP file to be generated, you have to do just one of the following:
    In Camera Raw preferences, change the "Save image settings in" option to "Camera Raw database", not "Sidecar XMP files".
    Instead of clicking Done every time, which applies any changes, click Cancel instead, if you were just looking and not editing.
    Use something other than Photoshop to preview raw files. Most of the other ways are faster than opening them in Photoshop. The recommended workflow is to use a camera downloading utility to look through all the images on the card at once (instead of one by one as you are doing), and then select only the ones you want to bring into your computer. Bridge (via File > Get Photos from Camera, not by browsing), Lightroom, Aperture, and iPhoto all have that capability.
    As to why double-clicking an XMP file opens a Messenger license agreement: As you probably know, the system has to figure out what program should open a file with a given filename extension. It sounds like maybe both Adobe and Microsoft have used the XMP extension, and the Office installer probably associated it with some type of MS Messenger file. So when you double-click an XMP file, Mac OS X opens Messenger. Since you have not used Messenger before, it's showing you the "first run" screen for Messenger, and Microsoft has set it up so that you have to click Agree on the license agreement before using it. If you never click Agree, it will still be the "first run" next time you open Messenger, whether you meant to or not. You can use Get Info in the Mac Finder to reassign XMP to open in another program.
    You probably didn't expect so many things to happen from just opening a raw file off a card, but that's the way it worked out.

  • ACR not using .xmp files after 03/09/2011

    I'm using ACR 6.4.1.145 and Bridge CS5 on a Windows 7 x64 Pro machine. Canon S95 and G12 CR2 files created before 04/09/2011 behave exactly as they should: changes aved in .xmp files are recognized and applied in Bridge thumbnails and when the image is re-opened in ACR.
    Images created on 04/09/2011 and any later date (tested by altering the file dates) have their changes saved in an .xmp file, but this file is not applied to the thumbnail in Bridge, the Bridge thumbnail does not indicate the .xmp file exists, and the .xmp changes are not applied when the image is reopened unless the .xmp file is loaded manually.
    I have purged the cache, restarted Bridge, and restarted Windows. I've moved the images to a different directory, then a different drive. I've loaded the images from the SD card several times now. The problem persists.
    All assistance appreciated.

    Thanks Thomas.
    I am pretty sure the CR2 files don't contain any .xmp data. For one thing, the problem only occurs on my installation. If I use another computer, everything works as it should.
    The problem has returned, however. I just tried to make changes in ACR to images created today, and although ACR saves the .xmp, it does not recognize it when I open the image again. I have to load the .xmp manually.
    I will bet that tomorrow, the problem has gone away. That would make it somehow time/date dependent. More important to you and anyone else trying to help, it seems to happen only on my installation of CS5. Something has gotten corrupted, I think. If the problem persists, I will probably try a re-install, but I hate the patching proces that follows.

  • Camera Raw does not read previously saved XMP files (Canon 60D)

    Hi,
    I want to ask if it is a real problem or just me doing something wrong.
    I open RAW files made with Canon 60D (Photoshop CS5, Camera Raw 6.6), then I do what a do (cropping, exposure changes, sharpen ... etc.), then I click the Done button. Camera Raw saves XMP files along with the RAW files. After this I want to do some more editing, I open the RAW files, but Camera RAW does not "remember" what it did just minutes before. I suppose that it is not reading the XMP files that it created.
    So is it me or it is some kind of bug?
    I don't have this problem when editing RAW files made with Canon 400D.
    Thanks for your time!

    Bo LeBeau wrote:
    If I understand correctly the issue is not viewing in Bridge, but rather that ACR doesn't remember the changes.
    There is a discussion in the Camera Raw forum about this issue of not always reading the changes after clicking Done in ACR.
    But no solution.
    http://forums.adobe.com/message/4096784#4096784
    Yes, ACR doesn't remember/show the changes I made.
    It seems that I have the same problem as the other forum member from the link. I tried to recreate the issue, but this time all went well and ACR displayed the changes I made ...
    It is strange because I had the issue numerous times on two different windows PC's ...
    Message was edited by: Orhan Chakarov

  • Can I save PS edits in an xmp file to be read by LR?

    The reason I ask this is I have hundreds of photos that were taken on a 5D with a scratched filter, so I am treating the marks as dust bunnies and getting rid of them in the same way, using spot healing and for the scratches, whtever the feature is called where you use the spot healing brush but you 'draw lines'.
    However I am one of the many who suffer appalling performance in Lightroom edits so after maybe 20 spot heals the computer slows down so much so as to be unusable. So I then send the file into PS/CS6 as the same doesn't happen there.
    I quickly fix all my spots and scratches and then I appear to only have the option of saving the file as a TIF back to LR.
    What I'd love to do is save the xmp file, and then have LR update the image given those xmp changes.
    Is this possible or do I have to continue to have the extra TIF file?

    Hmmm I can't replicate what I did now. The problem with using ACR is that the spot removal tool is just that, a spot. It doesn't allow the removal of scratches, which is the whole point of what I'm doing. If I hit 'Done' after healing a spot it does indeed write to the xmp file, but then I hvae to delete the preview and refresh in order to see the change. I could cope with that if the ACR spot removal was the same tool as in LR, where you can do scratches as well.
    Oh well, I'm halfway there so should be grateful for that. Cheers.

  • Save Metadata to File Problem

    This is really puzzling me .... In Catalogue Settings, I have 'Automatically write changes into XMP' NOT ticked. When I want to save, I Select All and then 'Save Metadata to File' . However, most of the time this only saves the 'Most Selected' image, it does not create/write to XMP for all the selected files? However, I know this is meant to save to all the selected files and I also know that sometimes it does/has saved all the XMP files for me. I cannot figure out why sometimes it saves all the files and sometime only the 'most selected' ? I have tried in both Library and Develop Modules. Is there a reason for this or is it some kind of bug?
    I'm using Lightroom Ver. 3 on a Mac. But I also used to have the same problem on Version 2 as well.
    Many Thanks

    Switch to Grid view - anything you do in Grid view will always apply to all selected images.

Maybe you are looking for

  • Program crashes when I try to load EPUB/ASCM ebook file or transfer the file to Nook ereader.

    I recently checked out an ebook from my library's OverDrive and downloaded the EPub file to my Mac OS 10.10.1 computer. File downloaded to computer without incident, showing up as a acsm file in my Downloads folder. But when I attempt to open the fil

  • Help me in my chat program please

    hi, Im doing chat program same as yahoo messenger using Java.Please help me in creating rooms....so that it will be a great help for me to finish my project.. Thanks in advance PadmaPriya.

  • Hibernate jsf

    hi, I have two application and persist my objects with hibernate. In my first app I persist member objects(forename,surname, age) and in my second app i persist publication objects(name of publisher, title, year of publication). My question is: how c

  • How to export and import reports and presentations?

    Hi Guys, how to export and import reports and presentations from Analyzer 7.2 to Web Analysis 11.1.1. Can you plz tell me the procedure. Thanks

  • Printing from CS3 under Vista to Windows 2003 server print que very slow

    I just upgraded one of my machines to vista with CS3. I normally print to a windows 2003 server print spool que. When I go to print it takes forever to pull up my different printers and then go to properties. On my XP machines there is no problem, I