Writing metadata to Nikon raw

Given the
recent statement by Nikon and Adobe and the provision of a mini SDK, does this allow the possibility to write metadata from Bridge to Nikon raw files? If so, I'd be enthusiastic to see it implemented.

Then why does anyone buy Nikon Capture or use programs like iView to write metadata to raw files? Granted, anyone with any sense also ensures they have a pristine backup.
Clearly it would be a risk for Adobe to do it blind (iView use the full SDK) but if the mini SDK doesn't allow the possibility of writing metadata, its desirability seems pretty moot.

Similar Messages

  • Bridge 4.1.0.54: Error writing Metadata to some [....].jpg

    I am sorting my files (.JPG) with bridge. Some files just can't get rated (bridge fails without giving me an error), and if I try to set other metadata (like keywords), bridge tells me "There was an error writing metadata to ".....JPG".
    I have full access to the folder, it is an internal disk, the files are not locked. It affects about 5% of all files - this is the second shooting (&folder) where I have this problem. I don't see any differences between the files I can change and the ones where I can't.
    I can rename the file with bridge, but that does change nothing. I tried purging the cache, it changed nothing.
    I just found out: I can change the tags with Windows Explorer, Bridge does show them, and afterwards I can change them with bridge too. Someone got an Idea how I can avoid this step?
    [Win7Pro x64, i7]

    Jingshu Li wrote:
     I tested your issue but haven't reproduced yet. Could you please provide more info? 
    1. You mentioned usually you will select tens of images (in the smart collection or search result) and apply metadata, and then you get the error. I'm wondering can you apply metadata successfully if you only select one image and then apply metadata?
    2. Before you apply metadata, do you wait for the images thumbnails genaration complete?
    3. Can you apply metadata successfully if you selete the images at their real location (not in the smart collection or search result?)
    4. Your OS info, mac or win, and version?
    I just set up a quick test, and it failed immediately. I haven't even been using Bridge today...
    The computer runs CS5 on Windows 7 Professional 64-bit. I used to run CS3/CS4 on a different computer loaded with Windows XP Professional. I'm always up-to-date with OS/driver/application updates. Both systems exhibited the same problem.
    The raw image 3-tier folder hierarcy is on a separate internal drive: P:\Camera\2011\08-15 Location\, P:\Camera\2011\08-16 Location\, etc.
    The Bridge cache is on a separate internal drive: T:\BridgeCS5\, Camera Raw's cache is in T:\CameraRaw\.
    The images are mostly Nikon NEF (D300), and ACR saves settings to 'sidecar' files. Most of the images have settings, and many have crops.
    I created a new Collection, and dragged the contents of 7 image folders into it - a total of 407 images. None of these files have had keywords applied, but most had been worked in Camera Raw already. After waiting for thumbnail/preview generation to finish, I selected the collection, created a new sub-keyword, selected all images in the collection, and ticked the new keyword (automatically ticking the parent keyword). Within a few seconds, I started getting the "Error writing metadata..." warnings, and had to OK 15 images.
    The failed images were spread across 3 of the 7 selected directories. Trying the same thing 30 minutes later resulted in the same errors. Trying each failed image individually gave the same error (either as part of the collection, or from it's own folder).
    I opened one of the problem images in Camera Raw, and adjusted Blacks, clicking Done to save the settings. I then tried to apply the keywords again. This time it worked.
    To answer your questions directly:
    1. I have never experienced this problem keywording files individually (apart from after the errors, as mentioned above), but then I wouldn't usually be selecting lots of images to keyword individual images.
    2. Yes, I always wait for the spinning circles to disappear, sometimes even longer!
    3. I just tried applying keywords to a single folder of 102 images, and 2 failed to update. So the answer is No, it fails at real locations too.
    4. Windows 7 Professional 64-bit, running on Intel Core2 Duo and 4GB RAM. Same thing happened before on a Windows XP Professional PC, running on an Intel Pentium 4 and 2GB RAM and a single hard drive.
    I hope that helps.

  • Error writing metadata to photo files

    I am using CS6 and have moved to a new computer with a clean install of CS6 under Windows 8.1.  In the past I had no problem using Bridge to append my personal metadata file to photos (RAW files, NEF).  With the new installation I am getting the repeated message " Error writing data to...."  even after trying all the " fixes"  suggested by the help files.
    Can anyone help me to resolve this issue?
    Thanks.

    I found an answer, somewhat different.  I did more search and found that you need to be administrator and for Adobe to see you as administrator, for many functions to work, such as writing metadata to files or putting stars on photos to rank them.  I could do neither.
    THEN, I tried opening Bridge by right clicking on the icon, and opening the file as administrator (a choice).  Everything worked.  So, why was Adobe not seeing me as administrator.  My user account was the only account on the computer and has administrator privileges.
    I started doing searches on that, and stumbled, yes stumbled, on what I think is a solution to that situation.
    I set up my account so that I needed a password to log in.  Once I did that, Bridge worked fine.  But, I still did not want that additional startup step.  You can then back to change password and leave the password entries blank.  Then, the computer starts up with blank passwords, zips past the welcome screen directly to the desktop, and Windows now sees me as the administrator, and so does Adobe.
    Keep you fingers crossed folks, this seems to be working.

  • CS6 "There was an error writing metadata" message PC and Mac

    I have seen this in the forums but looks like no one has an answer yet. Adobe chat support was totally not helpful.
    I am getting an error message when trying to apply keywords to some images in Bridge. The error is very non-specific, all it says is "There was an error writing metadata to "filename.ext"".  This happens when trying to apply keywords to a batch or single images.  If not all images in the batch are error-prone, keywords are applied to those images and I get the error message for each image that had a problem.
    My version is CS6 5.0.2.4 x32, but my co-worker downloaded a free trial today for her PC and is having the same problem.  Another co-worker downloaded to his Mac and has the same issue. I am on a windows machine. 
    Sometimes one co-worker get the error message on an image, and I am able to tag thje image without error.  Other times, none of us are able to tag the image.  The images were not made by the same camera and come from different sources.
    We are all administrators on our computer and have tried opening Bridge with "run as administrator".  We still get the error. 
    The images are on our local machine, not a shared network drive.  Some of the images did live on a shared network drive at one point, but not all.  We can't seem to find a pattern between the files this is happening with.

    That sounds like a problem with your machine, perhaps not enough Ram, a hard drive going south, a permissions issue, etc.
    BOILERPLATE TEXT:
    Note that because this is boilerplate text, not all points may apply to any given, specific poster.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Problems writing metadata in Bridge CS4

    Anyone seeing this? When I add metadata to my RAW images in Bridge, I frequently get an "Error writing metadata" message. If I have selected a folder full of images, say 700 images, I get 700 error messages. The only option is to force quit.
    The problem seems to happen reliably if thumbnails or preview images are still being created, though I've had it happen with a stable folder.
    Another consequence of the force quit under these circumstances is that I lose all my image adjustments on my raw files. It seems the sidecar .xml files get corrupted.
    I'm on Mac 10.4.11, and the problem happens on both the desktop and the laptop.

    That explains why the problem is worse on the laptop. Here's what I have in the deesktop Mac Pro, which is only 15 months old:
    ATI Radeon X1900 XT:
    Chipset Model: ATY,RadeonX1900
    Type: Display
    Bus: PCIe
    Slot: Slot-1
    PCIe Lane Width: x16
    VRAM (Total): 512 MB
    Vendor: ATI (0x1002)
    Device ID: 0x7249
    Revision ID: 0x0000
    ROM Revision: 113-A52027-140
    EFI Driver Version: 01.00.140

  • Unknown Error Writing Metadata

    Scenario: After editing photos in Lightroom I select a bunch to be edited in Photoshop CS3 beta, editing a copy with Lightroom adjustments. In Photoshop the only thing I do is run a batch that runs Noiseware then saves and closes each file. After doing this, about 70-80% of the completed files have an exclamation in the upper right hand corner of the photo in the Lightroom thumbnail. Clicking on the exclamation point displays this error message - "There was an unknown error while writing metadata to this photo - retry?" Comparing metadata between the raw photo and the tiff reveals no difference in metadata. The only difference is that the affected tiffs are not rotated for display properly. If I click on the "Retry Metadata Export" button the exclamation point goes away, but the thumbnail still needs to me rotated manually. Anybody seen this one?

    Yep, LR see a discrepancy and wants to know how to fix it instead of asuming an overwrite. Otherwise edits elsewhere may be inadvertantly overode before you ask Lr to read them.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
    http://donricklin.blogspot.com/

  • Bridge error "there was an error writing metadata"

    If I want to add keywords to my RAW files in PS adobe Bridge I get regularly (usually) a message as follows "there was an error writing metadata nr img 1326 CR2". How can this be resolved ? iMac
    grts
    ingridMG

    How can this be resolved ?
    It might have several reasons but my best first guess is that you want to much at the same time?
    When adding keywords Bridge is not capable on multitasking. When the activity bar starts to spin (bottom left in bridge window) you best wait until the first bunch has finished.
    My second guess is about XMP files, Bridge does not write metadata in the Raw file itself but to a separate XMP file with the same file name but different extension (.xmp). By default the XMP files are hidden in Bridge (you can see them in the Finder folder structure, the moment you make changes in ACR, add rating and or labeling as well as metadata and keywords the XMP files get's created) and using the menu view/ show hidden files/ they will show in the content window.
    It might be you have a locked file or not the correct permission. So also use your Apple Disk Utility to check and repair permissions.

  • Error writing metadata when Importing Lr 2.7 catalog in Lr 3 final

    Hi,
    I imported (and sucessfully converted) my Lr 2.7 Catalog in Lr3 final but now, all my photos have  this little icon that says " Error writing metadata "
    Why?
    Thx!

    According to Martin Evening in his Lightroom 2 book p. 178, "If you see the icon shown in Figure 4.74 [the !], click to open the dialog box where you can either choose Import Setting from Disk if you think the external settings are right, or choose Overwrite Settings if you think the Lightroom catalog settings are the most up to date."
    If you did not edit these images in another program like Camera Raw some unknown event caused Lightroom to indicate that the files were edited in another program.  In this case you probably do not want to include this edit.  It will probably work out if you choose Overwrite Settings which will keep the settings that you have in the LR database, disregard the changes from outside LR, and remove the !.
    If you edited these images in another program and you want to keep those changes, choose Import Settings from Disk to bring the external settings into the LR database.
    If you want to write the LR settings to the DNG files go to Metadata > Save Metadata to File or (Ctrl-S).  I strongly recommend saving LR settings to the file.  Others disagree.  In the Catalog Settings under Metadata, check Automatically Write Changes to XMP, if you prefer this to be done automatically.
    Whatever you do, be sure to backup your LR database, at least two or three times, and be sure that all of you images are backed up.
    Follow the above procedures by doing a few files at a time, and check that you are getting what you want before doing them all.

  • Cs4 error writing metadata?

    When I tried to add a keyword to a bunch of photos under a smart collection,
    I encountered this problem "There was an error writing metadata to XXX.cr2."
    Thank you for your help.

    Nobody can tell you anything without proper system info or other technical details, including specific details about your Raw files, where they are stored, what data fields you use and so on. Either way, ask in the respective product forum.
    Mylenium

  • LIghtRoom color problem vs PhotoShop CS2 on Nikon RAW

    I recently bought Adobe Lightroom and I was surprised to notice some huge color differences compared to PhotoShop CS2.
    Im using Nikon D80 and shooting RAW. I have calibrated semi-pro monitor.
    The same RAW file opens in LightRoom pretty well until you get the rendering preview. Once the preview is done, the picture becomes desaturated in red and blue and has a green cast especially in the shadows with much lower contrast. If I use Edit in PhotoShop option, the picture becomes even worse (even more desaturated and greenish) when opens in PhotoShop. If I open the same RAW in PhotoShop directly (using the NEF plug-in, not CameraRaw!) everything is just fine. The picture looks as opened in Nikon Picture Project or as I saw it when I took the picture.
    After doing some research, I think that my problem relates to the way that Adobe Camera RAW, Bridge and LightRoom open a Nikon sRGB 4.0.0.3001 (D80) raw file. However, all the things being equal, PhotoShop CS2 (using the NEF plug-in) renders the same colors as Picture Project does (and what I saw on my camera and in reality). I also noticed that choosing sRGB in Camera Raw bring the things closer to the Picture Project colors but far from identical. Anyways, there is no way to change anything in LightRoom, outer than manually twicking all colors until I think it looks good. Which, I think Is very subjective and is different for every picture.
    Right now, my Creative Suite Color Settings is North America General Purpose 2 (synchronized for all CS applications) and no application asks me anything about changing the color profile when opening the file. I shoot (with D80) in raw, Normal camera mode (no saturation / contrast, color profile change). I opened the same file in all mentionned applications (LightRoom, CameraRaw from Bridge, PhotoShop and Picture Project) and save them as .jpeg (same size, dpi, etc.) without changing anything (no camera calibration in ACR or LR; no printer profile in PhotoShop). I sent the .jpegs to my local Costco and printed them on glossy paper. All of them printed the same way that they look on the screen. LR, ACR - desaturated on red&blue, color cast on green and low contrast, while great vivid colors and contrast from PhotoShop and Picture Project. For me it looks pretty much as Adobe applications convert Nikon sRGB into a very unappealing Adobe sRGB (and way different from what I saw in reality). I know this is very subjective; some people may argue that Nikon profile is too reddish and oversaturated. But I find the whole story rather unusual. They all work in the sRGB space and there shouldn't be any differences. I've done lot of testing with color profiles and replacing the Camera Raw plugin file format (common files) with Nicon plugins and vice-versa. But still the same result.
    I create a User Profile in LightRoom and I get pretty decent colors now, but when I want to edit the file in PhotoShop (from LightRoom) I get the same green and desaturated version.
    What do you think?

    >Regarding LR, what I'm looking here is a "factory made" solution; something that can give consistent results in the initial conversion (like Nikon plugin for PhotoShop, for e.g.)
    The problem with that conversion is that you cannot change it. In lightroom you change the actual conversion parameters, which gives you far more leeway and allows for far better conversions in the end. Currently (this will change with Lightroom 2.0 apparently) the only recourse you have if you prefer Nikon's colors is to shoot jpeg, or run your NEFs through capture and create 16-bit tiffs. This is just the way it is. A hammer gives a different result than a screwdriver.
    >It's hard for me to believe that Adobe has invested so much energy and resources in color profiling but it's unable to get nearly close to the Nikon raw colors.
    Nikon's colors are far from colorimetrically correct which you can see in many tests. Here is an example for the D300: http://www.imaging-resource.com/PRODS/D300/D300IMATEST.HTM It is off in the deep reds, the saturated blues, and the Olive-like colors. Profiling the camera does not help you get close to Nikon's colors, but it will get you closer to the ideal colors. I doubt it has been Adobe's goal to get close to the in-camera rendering with Lightroom upto 1.4. They profile all the cameras and make some value judgments on what is more important. Skin tones vs saturated colors etc just like Nikon does.
    Regarding getting close to camera colors, there is a trick that you can do to get close to the camera jpeg that involves the ACR calibration scripts. You do need PS CS3 though.
    >I find rather strange that apparently there is no way to get professional conversion. This is defying the main purpose of Color Profiling, I think.
    Why is Nikon's conversion professional and Adobe's not? They are both just interpretations of the sensor data. Adobe's is actually colorimetrically more correct in many cases. Colorimetrically correct often means boring unfortunately. This has to do with the fact that our eyes are not color measurement devices but that we have brains interpreting the data. To get pleasing results, Color Profiling does not help as much as you'd like. My issue with the in-camera or Nikon software approach is that it locks you down creatively to the
    creative choices the Nikon folks made. Now, be aware that in the Lightroom 2.0 forum the Adobe folks have hinted at major changes to the rendering engine that will bring colors closer to the vendor rendering. How they will do this is unknown right now.

  • Adobe camera raw 4.6 and nikon raw files from the d700

    when opening a nikon raw file from the new d700, the picture appeares almost 1 step brighter than if you open the same picture in nikons capture nx2 software. the same happens when you do so with the new camera raw support in apples aperture - also almost 1 step to bright.
    mac 2x2,8 ghz quad core intel xenon
    8gb 800mhz ddr2
    photoshop cs3
    camera raw 4.6
    josef

    >I expected that a raw file shows up the same in every raw-converter.
    Your expectation is wrong. Every RAW converter will give you a different interpretation of the data. There is no single accepted way of interpreting RAW.
    >shouldn't that be so?
    Not really. I think what makes RAW so interesting is that you are not tied to the camera maker's interpretation of the data. This gives one far more versatility to get to your desired result. Of course, if you prefer the camera maker's interpretation, youu can use their software to develop the RAW or you can use the beta profiles in ACR/Lightroom and get
    close to identical rendering. I don't know if Adobe released any beta camera profiles for the D700 yet though.

  • New install of CS3 won't open NEF (Nikon RAW) images

    New install of CS3 on my new PC laptop won't open NEF (Nikon RAW) images. Same PC product opens them on my older desktop, and CS5 for MAC opens them on my iMAC.
    What am I missing? CS3 has been registered and activated. Thank you

    Hi, Again, John,
    I followed the instructions to the letter, and nothing worked. I still got the wrong kind of file message. After I tried to use the plug-in, I could no longre open pages in IE or Firefox. I have to wipe my new computer and reinstall everything. This time, I made CS3 the first thing I installed, and followed the instruction again as follows:
    "Windows
    ®
    1. Exit Photoshop CS3 and Adobe Bridge.
    2. Open My Computer.
    3. Double-click Local Disk (C:).
    4. Navigate to Program Files\Common Files\Adobe\Plug-Ins\CS3\File Formats.
    5. Move the existing Camera Raw.8bi plug-in to anot
    her location (for example, a new folder on your
    desktop). Ensure you keep this version in case you need to revert back.
    6. Copy the Camera Raw plug-in, Camera Raw.8bi, fr
    om the download into the same folder as Step 4.
    7. Launch Photoshop CS3 or Adobe Bridge."
    Still unable to open RAW images in PS. I did notice that the two files I copied to the desktop folder were the same, although one was slightly larger than the other. I chose to keep both.
    Why is CS3 working on my desktop from the same disk with no plu-in, but not on my new laptop? Is it Windows 8.1 instead of XP? That doesn't make much sense. PLEASE help. This is insane.

  • My version of LR-5.7 (OS X 10.8.5) apparently does not save the .NEF (Nikon RAW) edits done in the basic module.

    My version of LR-5.7 (OS X 10.8.5) apparently does not save the .NEF (Nikon RAW) edits done in the basic module. That means that I can correct exposure, highlights, shadows etc. but once I go to another picture and returned to the edited one the histogram (on the edited photo) and specifically the clipping triangles are white or some other color. This is normally suppose to indicate that some channel or all channels are clipped in the highlight/shadow areas. If I adjust any slider in the Basic panel even as little as one +/- value or press the J-key, the histogram will now show the original edit. Moving on to another photo and then returning to to previously edited one and again the edits are "not saved" and I have to hit the J-key or adjust a slider to see the previously edited information reflected in the histogram.
    This is especially frustrating for fours reasons. If I have edited a shoot and return to it I cannot see from the clipping information whether the original edit was correct and of course I might re-edit it (to some now incorrect value). This brings up the second issue synchronization. I can't rely on it because if I go back to fine tune a specific image in the batch the triangles are white or some other color for that and every image. I have to hit the J-key to show/hide clipping or the back slash key to see before/after previews. This is the third issue which is very time consuming and inefficient regarding my workflow. The forth issue is that I have noticed that normally when an image is saved in PS, LR adds a copy of the saved version to its catalogue. I have noticed that the PS to LR saves are all wrong in terms of exposure (they are much lighter in tone) than the original LR edit and the PS edit on my screen. If I check the PS to LR photo in LR I notice that the Basic panel values have been changed and that I have to sync the image with the originally edited RAW/NEF LR file to get it to look the same.
    Note 1). I am using an Apple cinema display and a calibrated Eizo ColorEdge monitor to view my NEF files. I have reverted back to using LR 4 however I am not sure if I should expect compatibility problems with Camera Raw 7.4 in LR 4 vs. Camera Raw 8.6 in LR 5.
    Note 2.) I am going to do an import converting everything to .dng  to see if this is a work around.
    Note 3). I would be interested in knowing if this issue is related to the PS RAW engine ver. 8.6, the Adobe created NEF calibrations or LR 5.
    Note 4). I have duplicated this issue in OS X 10.8.5, OS X 9.xx and OS X 10.10.1
    Hopefully someone else has noticed this problem. Any shared information would be valuable. Thanks for the reply.

    Happy New Year!
    The Develop panel Tone settings in your Dec 31 screenshot show both the Highlights and Shadows controls set to negative values (-48 and -19). For most images (such as this model shot) they should be set to opposite values (-Highlights and +Shadows). To try and duplicate your issue I used negative values for both of these controls with a similar high contrast image. I noticed that the Shadows control becomes non-linear when both the Highlights and Shadows controls are set to negative values. As I moved the Shadows control from a positive value the Shadows clipping indicator comes ON as expected. Moving the Shadows control to a value caused the clipping indicator to turn OFF and moving it further negative caused it to turn back ON again.
    The following screenshots demonstrate the issue with only Highlights & Shadows controls applied as shown.
    The Highlights & Shadows controls set just to the threshold of extinguishing the clipping indicators.
    Moving the Shadows control toward negative causes the Shadow clipping indicator to come ON (as expected), but at-13 it goes OFF again!
    Moving the Shadows control further negative causes the Shadows clipping indicator to come back ON at -33.
    This is probably normal behavior for the PV2012 Image Adaptive Tone controls as they were not designed to be used way (- - or ++ Highlights & Shadows). The PV2012 Tone controls all interact with each other, which is why it is suggested to adjust them from the Top down starting with Exposure. For most images using -Highlights and +Shadows of near equal value produces good results.
    I still can't duplicate the change in clipping indicators after selecting another image, so it may be unique to certain camera models and/or lighting conditions.
    SUGGESTION
    Try one of the image files that exhibits this issue using the following PV2102 Tone control adjustment procedure:
    Start with all of the Tone controls at their default 0 settings and adjust them from the top-down in the order shown below.
    Set Exposure to correct midtone brightness ignoring the highlight and shadow areas for now. Setting Exposure slightly higher (+.25 to +.50 EV) than what looks correct for the midtones seems to work best with most images.
    Leave Contrast at 0 for now. It’s usually better to adjust this after the first pass.
    Adjust Highlights so that blown out areas are recovered and “fine tonal detail” is revealed.
    Adjust Shadows to reveal fine detail in dark areas. For most normal images simply setting +Shadows = -Highlights (Example +50 and -50) works very well.
    The Whites control sets the white clipping point, which you can see by holding down the ALT key as you move the slider. Adjust it to the point where you see clipping appear with the ALT key.
    The Blacks control sets the black clipping point, which you can see by holding down the ALT key as you move the slider. Adjust it to the point where you see clipping appear with the ALT key.
    Now go back and adjust the Contrast control to establish the best midtone contrast
    If necessary “touch-up” the controls using the same top-down workflow.
    If the issue persists I suggest Exporting an image to DNG file format with the settings that exhibit the issue and post it to Dropbox or other file download site.

  • Is it possible to show Nikons raw files (.nef) in the organizer as thumbnails?

    Hello
    Is it possible to show Nikons raw files (.nef) in the organizer as thumbnails?
    Best regards Dieter

    Yes it is possible, depending on your camera and version of PSE

  • Error writing metadata to file

    I am getting constant error messages from Bridge CS4 when trying to add keywords to my images "Error Writing Metadata to file "XXXX". It's very annoying and destroying my workflow. I have tried resetting original preferences, and using purge cashe. Finally I reorganized my entire folder structure which seemed to make the problem less frequent.
    The circumstance that makes this error pop up most frequently is when I add keywords to a handful of files that already have another keyword assigned. Quitting the folder and then re-entering it solves the problem for the photos with the current error, but then 20 or so photos later I get the error message again.
    Any Fixes?

    A new suspicion was that the read/write data might be different for the images files themselves than it was for the folder holding them. So I applied the read/write permission to the image files themselves. No luck though. Still getting "Error writing metadata to file xxxx" Errors. Would love to be spending all this time editing photos instead of chasing down bugs. Brand new MacBook Pro and I'm spending more time trying to fix errors than using the software. ::sigh::

Maybe you are looking for