NEF file corruption in A3???

I have a NEF file taken on a D3 (fw: 2.02) that opens and displays fine in the latest View NX software (v 1.5.2) on Macintosh OS/X 10.6.2 ( Intel Duo Core 2) . After importing into A3, it "initially" displays fine. But after viewing the file and going back to the "Browser", the NEF file is corrupted and displays as a black square with (sometimes)random colored streaks. Most NEFS go in w/out a problem. But I have seen a few of these. Anyone seeing the same???

Using Aperture 3. Tried rebuild of thumbnails. No good. The file master can be exported (as a NEF) and viewed correctly in View NX, but it shows up "strange" in Aperture. After the rebuild, it came up looking like "snow" on a TV that was tuned to a non-active channel.

Similar Messages

  • Nef file corrupted but preview looks fine

    Hi everyone,
    That's the first time I get an error when opening an image in Photoshop and I dont really know what to do to get it to work. Its actually almost half my sd card that got corrupted, the preview image looks normal but as soon as I try to open it to start working on it, I get this error:
    "Could not complete your request because an unexpected end-of-file was encountered."
    Same thing happen in Lightroom, I even tried Picasa and always the same problem, preview looks normal but the NEF file does not open (Photoshop) Cant make changes (Lightroom) Open with plenty of lines, colors, etc (Picasa)
    Is there a way to get past this error in Photoshop or at least be able to work on the preview files ???
    Thank you for your help!

    The preview you refer to is probably the jpg image the camera makes of image, as a camera can not display a raw image.  This is called the embedded thumbnail.
    So the NEF is probably hosed.  This usually happens when a card is inserted that has been formatted with another camera.  It is wise to format your card, in the camera, before each use.
    The other posibility is that the transfer of imagaes from the card became corrupted.  The safest way is to transfer with a USB card reader.

  • NIKON NEF files corruption

    I have problem of NIKON NEF(NIKON D7000 CAMERA) files corruption after updating my MacAir to IOS Yosemite. I updated recently with latest Digital Raw Converter 9.06 but problem is still same. JPEG files are no problem. Any suggestion ho to solve? thanks

    The answer is in this link.
    FAQ: Will Photoshop Elements work with my camera, or Why won't my raw files open?
    Each Nikon camera has its own particular NEF format. First select your camera model and look in the link about supported cameras for the necessary version of the ACR plugin.
    The present version of Elements is 8.6. The dngconverter has a 'release candidate' version 8.7.

  • NEF Files Corrupting in Bridge

    Am new to Mac OS, and on clicking an image to open in CS6, the file gets corrupted? Any one can help resolve this issue.
    (Currently using IMac 21.5 inch with latest Yosemite OS [includes all the updates])

    Actually, its Nikon's NX-D which was corrupting the files, they have sent me a patch to update, and it remains to be seen if any more files get corrupted.
    I had transferred all my files from SD card to external HD, which I was using to work on.
    It seems Nikon are lately good at having problems rather than not having.

  • NEF file corrupt in lightroom, okay in Nikon ViewNX 2

    A file which displays fine in the Nikon ViewNX 2 software is displayed in Lightroom (thumbnail and image can be viewed fine, including zoom etc.), but Lightroom reports "An unexpected end-of-file occurred" and I am unable to make an adjustment (unable to make WB or lens corrections -- it does let me crop),   I deleted the file in Lightroom and imported it again with the same problem. It is a 4912x7360 file taken with a Nikon D800.  Suggestions to get Lightroom to work with it?

    There have been several reports of this problem recently. One of the most common causes seems to have been that the users have used an outdated version of Nikon Transfer to import their images. I don't  know if that could be the case in your situation, but it's worth asking.

  • Adobe DNG converter is corrupting NEF files. The color is way off and it's not the camera white balance.

    I was using the converter for a few months and it was working fine. Now it will convert the files, but the color is really messed. I know it is not the white balance, because the same files convert fine to TIF files through Nikon's software. I am using this converter for Nikon d610 NEF files. Here's a sample DNG and the same image in TIF. Can anyone help? Thanks!

    When you use the DNG Converter to make a DNG from an NEF, the DNG Converter applies the default Camera Raw settings.  When I open your DNG it looks fine, but when you open it, it looks off.  That is because you've some how set your Camera Raw defaults to have a bunch of customized settings specific to a particular picture, instead of having them all be normal settings.  Below you'll see what Photoshop is saying the settings of the DNG-Converted-JPG are, with the non-defaults marked in bold.  The main problems are the WB being custom and a bunch of HSL setting changes.
    Here is what Photoshop reports that the JPG was created using:
          <rdf:Description rdf:about=""
                xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
             <crs:RawFileName>hug_8290_0215_1.dng</crs:RawFileName>
             <crs:Version>6.0</crs:Version>
             <crs:ProcessVersion>5.7</crs:ProcessVersion>
             <crs:WhiteBalance>Custom</crs:WhiteBalance>
             <crs:Temperature>5732</crs:Temperature>
             <crs:Tint>+26</crs:Tint>
             <crs:Exposure>0.00</crs:Exposure>
             <crs:Shadows>5</crs:Shadows>
             <crs:Brightness>+50</crs:Brightness>
             <crs:Contrast>+25</crs:Contrast>
             <crs:Saturation>-4</crs:Saturation>
             <crs:Sharpness>90</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>0</crs:ShadowTint>
             <crs:RedHue>0</crs:RedHue>
             <crs:RedSaturation>+11</crs:RedSaturation>
             <crs:GreenHue>0</crs:GreenHue>
             <crs:GreenSaturation>0</crs:GreenSaturation>
             <crs:BlueHue>+12</crs:BlueHue>
             <crs:BlueSaturation>+2</crs:BlueSaturation>
             <crs:FillLight>0</crs:FillLight>
             <crs:Vibrance>-6</crs:Vibrance>
             <crs:HighlightRecovery>0</crs:HighlightRecovery>
             <crs:Clarity>0</crs:Clarity>
             <crs:Defringe>0</crs:Defringe>
             <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
             <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
             <crs:HueAdjustmentYellow>+1</crs:HueAdjustmentYellow>
             <crs:HueAdjustmentGreen>+5</crs:HueAdjustmentGreen>
             <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
             <crs:HueAdjustmentBlue>-9</crs:HueAdjustmentBlue>
             <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
             <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
             <crs:SaturationAdjustmentRed>-2</crs:SaturationAdjustmentRed>
             <crs:SaturationAdjustmentOrange>+14</crs:SaturationAdjustmentOrange>
             <crs:SaturationAdjustmentYellow>+25</crs:SaturationAdjustmentYellow>
             <crs:SaturationAdjustmentGreen>+26</crs:SaturationAdjustmentGreen>
             <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
             <crs:SaturationAdjustmentBlue>+32</crs:SaturationAdjustmentBlue>
             <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
             <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
             <crs:LuminanceAdjustmentRed>+40</crs:LuminanceAdjustmentRed>
             <crs:LuminanceAdjustmentOrange>+13</crs:LuminanceAdjustmentOrange>
             <crs:LuminanceAdjustmentYellow>+3</crs:LuminanceAdjustmentYellow>
             <crs:LuminanceAdjustmentGreen>+15</crs:LuminanceAdjustmentGreen>
             <crs:LuminanceAdjustmentAqua>+3</crs:LuminanceAdjustmentAqua>
             <crs:LuminanceAdjustmentBlue>+4</crs:LuminanceAdjustmentBlue>
             <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
             <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
             <crs:SplitToningShadowHue>231</crs:SplitToningShadowHue>
             <crs:SplitToningShadowSaturation>32</crs:SplitToningShadowSaturation>
             <crs:SplitToningHighlightHue>45</crs:SplitToningHighlightHue>
             <crs:SplitToningHighlightSaturation>33</crs:SplitToningHighlightSaturation>
             <crs:SplitToningBalance>+74</crs:SplitToningBalance>
             <crs:ParametricShadows>-39</crs:ParametricShadows>
             <crs:ParametricDarks>-7</crs:ParametricDarks>
             <crs:ParametricLights>-15</crs:ParametricLights>
             <crs:ParametricHighlights>+14</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>-24</crs:PostCropVignetteAmount>
             <crs:PostCropVignetteMidpoint>50</crs:PostCropVignetteMidpoint>
             <crs:PostCropVignetteFeather>97</crs:PostCropVignetteFeather>
             <crs:PostCropVignetteRoundness>0</crs:PostCropVignetteRoundness>
             <crs:PostCropVignetteStyle>1</crs:PostCropVignetteStyle>
             <crs:PostCropVignetteHighlightContrast>0</crs:PostCropVignetteHighlightContrast>
             <crs:GrainAmount>0</crs:GrainAmount>
             <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
             <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
             <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
             <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
             <crs:CameraProfileDigest>51B4314CF8312BA027EF3FC60481FB35</crs:CameraProfileDigest>
             <crs:HasSettings>True</crs:HasSettings>
    To fix the problem you're gonna need to reset your camera raw defaults:
    And then be careful when saving new camera raw defaults with the menu item just above, that your image has the camera raw defaults applied to it, except whatever small change you want to be the new default.

  • Cannot open my NEF files in Photoshop CS6 from my new Nikon D800 camera.

    That's it, I Cannot open my NEF files in Photoshop CS6 Camera Raw from my new Nikon D800 camera. What am I doing wrong or what is wrong? I have the plug-in Camera Raw 7. and can open TIFF files but not the NEF files.
    Peace,
    Charles Fennen

    Hi ssprengel,
    to explain the scenario, i am basically a D7000 user and I do post production with Windows computer. But for an assignment I have hired D800, they have provided me their SD memory card. I have used the same memory card while shooting.
    I have transferred the NEF files from the camera using Nikon software. The transfer was successful but i am not able to open the Raw NEF file with ACR. Even my plugins are updated till date.
    The NEF thumbnails are having small lock logo in the bottom left corner. I do not know what does that mean. Like this.
    Kindly let me know what would be the prob? if my RAW files are corrupted kindly let me know how will I recover them?
    Thank you.

  • End of File error on .nef files

    I am beginning to see a growing number of my .nef files becoming visually corrupt in the viewer and showing the "end of file" error when opening in PS or any other application.
    The corruption does NOT seem to affect the associated .jpg file (if there is one) but I am also NOT able to generate another "clean" .jpg file with the .nef files that have become corrupt.
    I hope that I haven't confused everyone - but this issue is rather baffeling in that I can't seem to pinpoint a cause.
    My master files are stored as reference files on a server share - all shot with a Nikon D2X.
    Does anyone have an idea of what may be causing this - and better yet - is there a way to reverse the corruption?

    I do have a number of other systems that I can use to test from. THe file server is a general purpose server in my home running 10.4.x with all of the latest patches, etc.
    I am using a SanDisk card reader to ingest directly into Aperture. The corruptness appears to be random.
    I am using a Nikon D2X with a number of CF cards, usually 1 or 2GB in size. I capture recording .nef (RAW) images to the CF card.
    My workstation is a PowerMac, Dual G5, with 2.5GB processors and 2.5GB of memory. I am using MacOS 10.4.2 with all of the appropriate patches and updates.
    The Server is a PowerMac, Dual G5, with 2.5GB processors and 2.5GB of memory. The server is running MacOS 10.4.x Server, again with all of the appropriate patches and software.
    The network is Gigabit speed with one switch between my workstation and the server. The Switch is a GSM7224 L2, 24-port 10/100/1000MBps managed switch.
    The users in my home (in this case; me) log into any of a number of workstations in my home and authenticate against the server using LDAP. Once authenticated, home directories are available and stored on the server.
    This appears to be network related as I can ingest and save locally to the server and open the files without any corruption.

  • Some Nikon D300 NEF files don't appear in Bridge CS3 (Mac)

    Hi all,
    I'm using a Nikon D300 and just upgraded to CS3 on my MAC in no small part because the D300 was not supported by CS2. I am running into a problem though.
    I always shoot in both JPEG and RAW modes. When I open Bridge I always see each JPEG version of a shot.
    However, only about 50% of the time can I see the NEF (RAW) version of the thumbnail. The rest of the time I only see a generic "RAW" thumbnail with no image. This sporadic NEF viewability carries over to the preview pane when I select such a NEF file.
    Furthermore, Camera Raw cannot open the NEF files that are not visible in Bridge. When I try opening them I get a message saying "Could not complete your request because Photoshop does not recognize this file type."
    I have tried purging the Cache (through Tools) as some indicated in other forums threads but this has not helped. I have also downloaded the ACR 4.4 plugin and installed it in the correct library location.
    Has anyone else experienced this (whether on a Nikon or other camera)? Any advice?
    Thanks

    I've finally solved the problem with having only some of my NikonD300 NEF files viewable in Bridge/readable by Photoshop! Jon Michael Riley had said he was having similar problems so I wanted to make sure he and anyone else has the info on what worked for me.
    The issue does not have anything to do with purging the thumbnail cache or installing the latest version of Camera RAW 4.4.1. While they were good suggestions (offered by Adobe's Technical support people also), they do not resolve this particular issue.
    I read that an earlier version of what Jon described as "Nikon's clunky software" had corruption issues when images were first transfered from the camera via Nikon PictureProject Transfer. It looks like the latest incarnation has the same issues. Nikon products can see the transfered images without a problem. HOWEVER, Adobe Bridge/Photoshop cannot rectify the corruption issue caused by transferring photos using Nikon's utility.
    So here's the solution: DO NOT use Nikon PictureProject Transfer! It is a piece of garbage! Instead, make ADOBE PHOTO DOWNLOADER the default tool to transfer images from the camera. To make it default do the following:
    Open Bridge, pull down the Bridge CS3 Preferences. Select the "General" preferences set. On this screen you will see "Behavior". The first clickable box reads "When a camera is connected launch Adobe Photo Downloader". Select this box to render this the default transfer tool.
    If you still have the pictures on your memory cards you can re-transfer them using Adobe Photo Downloader. All your NEF files should now be readable by Bridge/Photoshop. I've told Adobe Tech Support about this problem with Nikon's software. Hopefully they'll be able to check this as an option if others call in with similar problems.
    Unfortunately I have not figured out how to repair the corruption in the files I transfered earlier using Nikon's piece of garbage software. Since I don't have the images on memory cards anymore I can't just re-transfer them. Does anyone have any thoughts on how to do this? Will I ever be able to access my earlier NEF shots?
    Cheers,
    Greg
    Thanks to everyone for trying to help resolve these issues.

  • How to open .nef files

    i'm not being able to view or edit .nef (nikon raw photos) in iphoto or in any other app in my mac book air. does anyone knows what i hav to do to be able to use these files in the mac book?

    D70 has been supported forever.
    http://www.apple.com/aperture/specs/raw.html
    Since ps elements and iPhoto and Capture NX all use *different* raw conversion engines, it really sounds like a file corruption issue.
    What program on the PC opens them? Did you add the new Windows RAW support? Until very recently, a PC *couldn't* open RAW files.

  • How to open Nikon D7000 NEF Files in Photoshop CS3

    i have installed the 4.6 camera raw update but it does not recognise the D7000 NEF Files... same for Bridge.  what can i do to view files directly in CS3?

    Every camera model must be profiled and specifically supported, and Adobe only updates the current version of Photoshop when they add support for each new camera.  You should upgrade your tools just like you upgraded your camera.
    None of your new camera's NEF files should be viewable by CS3-vintage components, but all of your DNGs should be viewable by such, and if some aren't, then it sounds like your files may be getting corrupted on their way from the camera to the computer.  Are you using a cable to the camera or are you using a card-reader to access the images?  Using a card reader is preferable.  Some cameras have different modes their USB-connection can be in and something other than mass-storage mode can lead to problems.  I don't have a Nikon so am not sure of things more specifically, but if you can use a card-reader and just use Windows Explorer to copy the images that would probably be the best thing.  If you have a new memory card that could also be something to look at.

  • Camera raw 7.4 will not open the D800 NEF Raw files. D300 NEF files open OK

    Camera raw 7.4  will not open the compatible D800 NEF Raw files (Win7). D300 NEF files open OK.
    I seem to remember seeing an article that stated i would have to uninstall and re-install CS6 Photoshop completely and re-install again. However I cannot find this article now.
    If the above is true, having PS version CS4 with update CS5 & 6 installed, would i have to remove all PS versions.
    Photoshop error message just states download latetest software version, which i have done with ACR 7.4 nd ACR 8 which did not open file either.
    Adobe DNG runs OK but i would rather deal with the original file in ACR rather than adding an additional step with more files to keep track of.
    Is there a way of uninstalling all versions of ACR, cleaning system and re-installing ACR, assuming the fault lies with ACR?
    Anyone have any answers?
    Malc
    ANWER:-
    (Appologies for spelling errors but my keyboar hs just packed up). Now on  screen keyboard.
    Half an hour after posting this query (In the wrong forum -  Downloading, Installing, Setting Up) I resolved the issue. The fault lies with Nikon Transfer.
    Nikon Transfer corrupts the D800 NEF files. Apparently Nikon Transfer is well known for causing errors.
    Drag & dropping the files direct from the cameras memory card onto your hard drive and everything works fine.
    Nikon Transfer has now been assigned to the dust bin!

    Half an hour after posting this query (in the wrong forum) I resolved the issue. The fault lies with Nikon Transfer.
    Nikon Transfer corrupts the D800 NEF files. Apparently Nikon Transfer is well known for causing errors.
    Drag & dropping the files direct from the memory card onto your hard drive and everything works fine.

  • Bridge CS4 Search Not Displaying NEF Files + Keyword Problems

    Hello, I am hoping someone can be of service to peculiar problem that apparently nobody else has had.
    I am running Adobe Bridge CS4 (came bundled with Photoshop Elements 8) on a 2009 24 inch iMac with 4GB RAM and a 2.6mHz processor running Snow Leopard v10.6.2.
    I use Adobe Bridge CS4 to add Keywords to all my photos and edit 14 bit Nikon NEF RAW files. I write the keywords to an .XMP sidecar
    file.
    Two days I ago I changed something in Preferences->Metadata and the next time I started Bridge CS4 and used the loupe tool on a NEF
    file, it took longer than usual for the preview to come up and when it did, it was at 200% magnification instead of 100%. Once the loupe preview showed up, the NEF file had some sort of processing applied to it (it became more contrasted.) This was all within Bridge ant NOT Adobe Camera Raw. I quit the program and the next time I started Bridge, it crashed upon using the loupe tool. I looked up help on Adobe's website and it appeared I had corrupted preferences. Per Adobe's instructions I option clicked at Bridge startup to delete the preferences and purge the cache.
    Everything appeared to be normal until today when I searched for a keyword and got 36 random results when I know I have hundreds of
    photos tagged with that particular keyword. I started typing in other keywords and getting the same sort of results- very limited numbers of photos I have hundreds of. I always include all subfolders in all searches and used every search method available through Bridge to no avail. The searches always came up with a fraction of the photos I actually have tagged.
    I then verified and repaired all disk permissions from the operating system installation CD and Bridge started returning results as
    usual. However, when I clicked on an individual file in the Content pane, some of my Keywords started to appear in italics below the rest of my Keyword tree. There doesn't appear to be any rhyme or reason as to why some images will return the Keywords normally and others in italics. Also, sometime the italicized keyword tree will include keywords I edited due to typos and thus no longer existing my normal Keyword tree. I gave the "Make Persistent" command a try. It converts the italics to regular case, but it also doubles the tag so I now have two of that tag (one in the normal keyword tree, and the now converted italics keyword tree.)
    Now I'm noticing that all my search results are not including NEF files; just JPEG and the occasional DNG file that I made through Adobe Camera RAW. I'm not sure if this has been the case throughout my problem or if I just noticed it late.
    Regarding not displaying NEF files in searches, it appears that it will default to displaying JPEG if it has the option because as of lately I have only been shooting RAW and some of those files are showing up in the still-wonky searches (still displaying random or no photos of keywords.) However, if I manually navigate to a file, I can open and edit NEF files with no problem, they just don't display in any search modes.
    Here's two short videos of what happens when I navigate a folder with NEF files by manually searching:
    http://www.youtube.com/watch?v=WDjUDZzULKQ
    http://www.youtube.com/watch?v=-Y9HkDK7DCs
    When I click on a NEF file, the one ahead of it in Content view processes into a more contrasty image and the loupe tool previews jump between 100% and 400% and then change to 100% when dragged or they just process themselves right then and there.

    I am running Adobe Bridge CS4 (came bundled with Photoshop Elements 8) on a 2009 24 inch iMac with 4GB RAM and a 2.6mHz processor running Snow Leopard v10.6.2.
    Snow Leopard and Bridge CS4 do have some issues. Some have no problems and others have much problems I'm afraid.
    I use Adobe Bridge CS4 to add Keywords to all my photos and edit 14 bit Nikon NEF RAW files. I write the keywords to an .XMP sidecar file.
    To my knowledge the keywords are written into the XMP Metadata that is saved in the IPTC section of file itself, the XMP data in the sidecar file contain the changes you made in ACR. In other words, the keywords you have added should still be there.
    Also see this Knowledge Base article about Keywords:
    http://kb2.adobe.com/cps/402/kb402660.html
    Two days I ago I changed something in Preferences->Metadata and the next time I started Bridge CS4 and used the loupe tool on a NEF file, it took longer than usual for the preview to come up and when it did, it was at 200% magnification instead of 100%.
    Changes metadata in prefs only affects the visability of the fields in the metadata panel. put or deselect a checkmark in front of an option will let you see or not see the field in this panel, the actual data and fields ar still in the file.
    it was at 200% magnification instead of 100%. Once the loupe preview showed up, the NEF file had some sort of processing applied to it (it became more contrasted.) This was all within Bridge ant NOT Adobe Camera Raw.
    You can change the magnification for the loupe to 100 / 200 / 400 and 800 % using the scrollwheel or with loupe active the + and - keys. Bridge shows the settings that you made in ACR. If you have changed the default Camera Raw setting it will also change the thumbs for this file. A thumbs needs some time to be cached. First it shows with a black border around, when first cached it shows the embedded preview and in the second round it renders the ACR settings and High Quality preview (if you have not disabled this setting). Caching needs some time.
    Everything appeared to be normal until today when I searched for a keyword and got 36 random results when I know I have hundreds of photos tagged with that particular keyword. I started typing in other keywords and getting the same sort of results- very limited numbers of photos I have hundreds of. I always include all subfolders in all searches and used every search method available through Bridge to no avail. The searches always came up with a fraction of the photos I actually have tagged.
    Maybe you need to let the indexing in find do its work again but it might also be a snow leopard issue. Try an other app (Digital Asset Management like Expresion Media or  Portfolio) to check about the keywording and find. You can use a trial version for several days. You have several options to use find keywords. In the panel itself, in the filterpanel uner the keyword tab, when clicking on a visible keyword it only shows the files with that keyword or in the menu Edit / find (shortcut cmd + F) explore the options in this menu and also choose include non indexed and let Bridge start to index your files again.
    However, when I clicked on an individual file in the Content pane, some of my Keywords started to appear in italics below the rest of my Keyword tree. There doesn't appear to be any rhyme or reason as to why some images will return the Keywords normally and others in italics. Also, sometime the italicized keyword tree will include keywords I edited due to typos and thus no longer existing my normal Keyword tree. I gave the "Make Persistent" command a try. It converts the italics to regular case, but it also doubles the tag so I now have two of that tag (one in the normal keyword tree, and the now converted italics keyword tree.)
    Don't know about that.
    Here's two short videos of what happens when I navigate a folder with NEF files by manually searching:
    http://www.youtube.com/watch?v=WDjUDZzULKQ
    http://www.youtube.com/watch?v=-Y9HkDK7DCs
    When I click on a NEF file, the one ahead of it in Content view processes into a more contrasty image and the loupe tool previews jump between 100% and 400% and then change to 100% when dragged or they just process themselves right then and there.
    As you can see the black border around some file that disappear after a while or when you select them they have not been cached. You used purge cache so most of your earlier cached results are gone and need to rebuild.

  • After updating Camera Raw to 8.2.0.94 cannot open .NEF files

    After updating my camera raw plugin today to 8.2.0.94, I can not open .NEF files from Nikon 7100
    I receive "Could not complete your request because an unexpected end-of-file was encountered." error.
    Photoshop CS 6, MacBook Pro OS 10.8.5

    That error message usually, practically always points to a damaged or corrupt image file.
    If you used Nikon software to copy the files to your Mac, be advised that said Nikon software is notorious for damaging files in the process.  Use the Mac Finder or, better, Bridge to download your images.
    A faulty card, a failing hard drive, a bad USB port or cable can also be the cause of damaged files.
    I have never seen or heard of that error message being generated on a Mac by a faulty Camera Raw installation or anything other than a corrupted or damaged file.

  • Problems opening & resaving NEF files with CS3/CS2

    I seem to be having problems sending my NEF files to Photoshop from Aperture. This started happening just today & I'm not sure what to do.
    What happens is that when I open a NEF file in external editor, instead of just opening up as a psd file in CS3 or CS2 directly like it used to do, it now opens Adobe Raw instead which means that I am unable to resave back into my Aperture Library. Is there anyone who has experienced this as well? Any suggetions as to the cause and a solution? I tried checking preferences for both Aperture as well as Photoshop but nothing seems to work.
    The only thing I can think of is having just updated Adobe Raw to the latest version, 4.3 I think. Other than that Aperture did start up about a week ago & declared my library corrupt & proceeded to rebuild my library. Other than that it was behaving normally until today. Its really irritating & counter productive to be unable to resave my edits in Aperture.
    Any help or suggestions will be very welcome indeed. Thanks in advance.

    Thanks for the tip Eduardo, but I checked the preferences and they seem to be correct.
    It seems that only images in certain projects were affected. Could be the ones that Aperture rebuilt earlier. I guess I may have to try exporting the raw files from the affected projects, then deleting and reimporting the projects again. I did try to rebuild the thumbnails but it doesn't seem to help.
    Does anyone have any other suggestions for me to try before I do this?

Maybe you are looking for