Photoshop CS2 RAW (NEF) Issue

Hi,
My RAW (.NEF) files will not open in Photoshop CS2. Everytime I try to open a raw image it says...
"Could not complete your request because Photoshop does not recognize this type of file"
Don't know what to do. CS2 on OSX 10.5.8 with Nikon D90 photos.
I'm going to take a guess here and it has something to do with the Nikon software provided to transfer the photos from the camera/sdhc card?
I'm assuming the software (Nikon Transfer/ViewNX) has overwritten some Adobe plugin or driver?
Anyways, someone please help! I need to edit my photos and this is a pain in the A!
Thanks
Cheers
Mike

Your camera needs the Adobe Camera Raw plug-in version 4.6 or 5.xx.
Neither will work with CS2 – you need to upgrade Photoshop or use the DNG converter.
Get it here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4619

Similar Messages

Photoshop CS2 Raw original is changed

Hi,
First I crop a section of a Raw image and save the crop as .jpg.
When I reload the Raw image it shows the crop with a tint of the original.
How do I restore the original Raw image?
Bill
[email protected]

i have a nikon D-200 camera , and the nef file from that camara does not open in adobe brige CS2 in spanish,before, i had this version of adobe brige, from the phortoshop cs explorer , right cli on the image they opened in adobe converter window..
how can i do it inside the early photoshop CS2?

Photoshop CS2 and windows issues! help!

Hi, I'm working with someone who is having issues with Adobe Photoshop CS2 among other Adobe problems. The problem is that after Photoshop is loaded, the interface is very messed up. You can't open a file because if you go to menu -> file nothing happens. If you try to create something new, most of the buttons will be invisible in the option for sizes. The program simply becomes unusable. After a restart, the program will work properly for a short period of time and being to behave oddly again. On loading Photoshop, windows gives an error beep but the program loads anyways and no error window comes up. This happens on illustrator as well as indesign. I have uninstalled everything and removed all shared files that adobe uses and reinstalled everything from scratch, the same problem happens. This only started happening recently.
OS is XP pro SP3.
I am about to wipe the computer and start from scratch but I would rather not have to do this if there is another solution!
Please help! Thank you!

No, it's a standard U.S. keyboard and the language is set to english. I believe the software is up to date.
It doesn't freeze when you click on the menu, it just refuses to pop open a window when you try to open a file. Also, many of the option boxes in some of the windows in photoshop are invisible. This only happens after the computer has been on for a short while. Right after a reboot, you can open photoshop fine... until it stops working.

Has anyone solved their LR4 / Nikon D800 RAW NEF issues?

I've done a lot of reading on this topic and think I have a handle on how easily the new D800 NEF files can be corrupted by the older versions of Nikon Transfer.
When I began using the camera I accidently made the mistake of corrupting them and haven't had any issues since... until yesterday.
I photographed last night, and imported about 160 RAW NEF files onto my brand new Macbook Pro with Retina for a same day preview for the host. I transfered the images using ViewNX2 & by association it's built-in Nikon Transfer 2 utility. I used the built in SD Card reader on the Macbook which has always worked in the past. But alas!!!!! While they imported fine, LR4 can't import them and gives me the error "Preview Unavailable at this Time". I should note... Nikon Transfer 2 was set to clear the card after the transfer .
Nikon ViewNX2 can see the images and I'd hoped to fix the issue by just converting them to JPEG's but, no bueno. It tells me it can't. This is the precise issue I can into when I accidently used the original version months ago on my iMac. But it's impossible that I have the old version on this unit. It's less than a month old and I'd downloaded the most recent version from Nikon. So I'm running under the assumption that the file is somehow corrupted.
I've seen a lot of people running into issues getting used to the new workflow requied to deal with these enormous RAW's.
Here's the all important question. After the files have an issue... is there anyway to recover them??? I can't retake them, the original shots were wiped from the card. So what do I do? At least Nikon View can see them, so I have to believe that there is some image information there.
Has anyone sucessfully fixed the issue?
Going forward I plan to just import everything directly through LR4, so I think that'll aliviate future heartburn... but what's my "undo" solution?
I know there's a lot that's been written on this topic and really appriciate the support!
-Jared

What Bob Frost just posted (after fixing the hidden http// part of the URL) worked for the image you uploaded, so try that:
http://owl.phy.queensu.ca/~phil/exiftool/fix_corrupted_nef.html
BTW, I answered 14 to the bit-depth-12-or-14 question the utility asked, and it worked ok on the example corrupted NEF.
Below is what I was typing up and testing before posting, and works to extract the embedded JPG Preview, but does not actually fix the corrupted NEFs, which is a better solution. I am including it, below, for reference in case someone without corrupted NEFs also wants to extract JPGs from their raw files. It uses the same tool from Phil Harvey without his customizations to work specifically with corrupted NEFs.
== Original Message ==
The raw data in the NEF you uploaded appears corrupted or otherwise unusable because when viewing in Windows Explorer using the latest Nikon NEF Codec that supports the D800, all I see is a small thumbnail then black with a few parts of color, however for that one file, at least, the embedded JPG preview is intact, and 7360 x 4912 in size, enough to see the camera-shake blur.
https://dl.dropbox.com/u/9905000/JBR_20120910_175757.jpg
I’m on a PC and you’re on a Mac but the same tool is available - exiftool a command-line program you run in terminal (on a Mac) or in a Command Prompt window on a PC:
http://owl.phy.queensu.ca/~phil/exiftool/
If what you download includes a (-k) then remove it by renaming before attempting to run the command, below. On Windows I would rename exiftool(-k).exe to exiftool.exe without the (–k) part. The (-k) tells exiftool to display the exif information by default if you drag-and-drop to it. While this is normally useful, for the purpose of extracting JPGs from NEFs this might be confusing so I’m suggesting to rename the executable before using it.
Here is the command-line to extract the fullsize JPG from the NEFs and then copy the metadata tags from the NEF to the newly written JPG:
.\exiftool -b -JpgFromRaw -w %d%f_%ue.jpg -execute -tagsfromfile @ -srcfile %d%f_%ue.jpg -overwrite_original -common_args --ext jpg .
The above command assumes both the exiftool executable and all the NEFs are in the current folder. The current folder is designated by a single period both at the very beginning and the very end of the command-line. If exiftool is in a different folder, then supply that path instead of the initial period, and if the NEFs are in a different folder, substitute that folder-name for the final period. The final period has a space separating it from the preceding –ext jpg.
It is also assumed that only NEFs and the executable are in the current folder. If there are other files, they may confuse things so you might want to move things to a temporary working folder, and I’d suggest working with a copy of the NEFs just in case something goes haywire, you’re not overwriting the originals, corrupt as they may be.
For reference, the above command-line was simplified from a more complex example that didn’t quite work with your file, one that conditionally extracts either the full-size JPG or the tiny JPG-thumbnail. The example is the last one in the Copying Examples section, here:
http://owl.phy.queensu.ca/~phil/exiftool/exiftool_pod.html#copying_examples

CS2 Raw File issues with Nikon D90

Just saw the post on Nikon D90 non compatibility with CS2 raw file format. Questions are where to go from here. Running Windows XP with a AMD Athlon (tm) XP3000+ 2.16 ghz 448 mb ram. Is Cs4 or Cs5 compatible with my system. I used a D70 for years and had no problems. What is going on here? I can probably add ram to get the 1000 mb of ram but what about the rest? Is there another alternative other than a new system?

Caution!
Before plunking down the $$$ for CS5, look for the several threads around here where people are discovering their older AMD processors are not compatible with Photoshop CS5!
For example: http://forums.adobe.com/thread/630771
I'm not familiar with the processors in the AMD lineup, but it's possible yours will not run Photoshop CS5 until such time as Adobe releases an update.
-Noel

Photoshop CS2 RAW-Adobe Bridge

Bei Wahl des Freistellungswerkzeuges öffnet sich nicht das Popup-Menü.
Custom-Funktion nicht erreichbar.
Am Speicher kann es nicht liegen, RAM u. Festplattenkapazität ausreichend.
Wer kann mir weiterhelfen?
M.f.G. Manfred

zu Manfred Walsch:
ich arbeite immer noch mit Psh 7.
Aber ich hatte mal einen ähnlichen Effekt, als ich einen Canon-Scanner installierte. Nachdem ich Psh ohne die Canoc-Software neuinstalliert habe, war alles wieder normal, nach der Installation von Canon war der Effekt wieder da.
Gruß: Uwe

Can I install and run Photoshop CS2 on a Windows 7 64Bit OS?

I just purchased a computer It is a Windows 7 Ultimate 64 bit OS. Can I install and run Photoshop CS2? What issues would I have?

For what it's worth I have Photoshop CS2 running fine on Vista x64, but I've not moved it over to my Windows 7 x64 machine. Generally speaking, things that work fine on Vista x64 work fine on Windows 7 x64.
That said, you might want to wait until you hear from someone who's actually tried the exact combination themselves.
-Noel

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.

Can't open .NEF files in Photoshop CS2

Heres the deal: I've updated and installed my camera raw in Photoshop CS2, so I have the latest version of it (ACR 3.7). I still can not open my .NEF files in Photoshop and when I view the files from Bridge it shows the generic thumbnail image.
Information that might help:
PS Version: Photoshop CS2
ACR Version: Camera Raw 3.7
Camera: Nikon D60
Operating Sys: Mac OSX
Any help would be greatly appreciated. Thanks.

The D60 was not supported in ACR 3.7. In fact, that version was the first to support the D40. You will have to use the latest version of the DNG converter to convert your raw images to DNG. Then you can open those files in ACR 3.7.

Photoshop CS2 issues & Customer Relation's solution

i bought a g5 quad in June 06 that failed in july 06. they were unable to resolve the issue and gave me a replacement machine.
i was given a mac pro with 4GB of RAM and a terabyte of internal storage. the 2 oem 500GB Seagate 7200.10 hard drives took over 9+ hours to zero out: the apple store genius told me this was normal. i have since purchased 2 different hard drives. one of the same capacity which zero's out in under 2 hours. that number IS normal.
Adobe Photoshop CS2 Bridge and Camera RAW have never worked properly on this machine since i got it, quitting all the time when renaming files or browsing my hard drive folders in Bridge. i was told that this is normal and that CS3 and Leopard will fix all this. then the CS3 Beta came out and the machine quits even with the new version.
i contacted Adobe, they say it is my hardware. i went to the apple store and showed them the problem and was able to duplicate it on every mac pro in their store and they said it must be a software issue.
i bought more RAM from apple. the machine works somewhat better now, but it still crashes in photoshop and adobe camera raw and bridge. i purchased lightroom and have looked at changing my workflow, and this program too quits intermittently.
i called apple customer support again. they walked me through using a different user account. same issues. i asked to speak to customer relations. i got on the phone with the lady, and i asked if it was possible to send someone out to look at the machine since it is not working properly, and she said that it is not something they would do since it is not their problem. i asked if they would be able to help me decipher the crash logs so i can find out WHY the machine is crashing.
her exact words were, "well, maybe you can sell it? if it is giving you all these problems and since it is not our hardware, it might be best for you to sell it and buy something that works."
"sell it." i would like to say that "sell it" was not the answer i was looking for. i wasn't even mean to her. i was extremely polite and i got, "sell it" from customer relations. i hope none of you get "sell it"
good luck to all of you.

You use to use Windows but decided to move to Macs at some point, and not look or go back. And that the Quad G5 worked up until some point.
When I got my Mac Pro back in late August/early Sept, I ran into some oddities that no one could help me with. Drivers from Lexmark for their laser printers. Suffice to say that I spent weeks if not month trying to track down why etc. and doing the "clean install" but ended up with the original install disk image.
I'm always afraid if I am forced to install any drivers for now as a result.
I updated SoftRAID (I thought) and ran into every driver and extension conflict possible, known and unknown.
Clean install and avoided anything I could "live without" this time around, and it was stable. For a few days, any and every - and I mean absolutely anything I tried to launch, run or whatnot would CRASH.
I was ready to point fingers. But at whom? ah! must be the Ramjet. Passes all tests, but there must be a gremlin and nothing is good enough to find the cause.
System is now rock solid and stable.
I don't know really what or why. And whether it was SMC reset (I wish they would paint the button in RED!) or zapping PRAM/NVRAM.
I also installed Vista to see if it was OS X or hardware or not. But I never learned what is needed to really use and secure a Windows system - or troubleshoot it if it goes haywire. But you would.
I have spent 40+ yrs tinkering with computers, and 20 with Macs. I think I still remember some of the troubleshooting days from 1990 hunting down shareware bugs.
If it is hardware, it would fail running XP too, maybe? did you retain your license for and copies of Windows and CS2 or whatever you would use? (The Mac Pro really shines running Windows Vista from what I've seen).
It doesn't take a lot to turn a Mac into a crash-prone system. There are some bugs even with the OS update installer itself it seems.
Troubleshooting is as much art as science. Hunches based on what feels wrong with some sweat and guesses backed by some "CSI" sleuthing and detective work.
Only Apple or Intel would know if they have had to come out with re-designed chips, a newer motherboard, or cpus. Or the AMB used on the Risers.
As I said (5 pages ago?) a friend had a G5 Quad that would not run CS2 properly, was crashing etc. (and had on-site Care etc) and the latest logicboard (3rd) stopped the problems, CS2 runs faster and better, it doesn't crash, and the benchmarks show it.
There are revisions to logic-boards. I read it takes 3-6 months to get a pattern of a problem, and another 3-6 months to redesign parts, manufacturing, testing, between engineering prototypes and manufacturing.
I thought the whole idea of AppleCare was sort of the "care" in AppleCare. And to solve a problem.
It would take someone with access to what engineering errata is going on. What changes were made to G5s. There were other problems with Quad it seems as well, heat, the liquid cooling components (there are two varieties).
I don't have the stomach or temper to deal with customer service, phones, etc. But I would make an appointment (yes, again!). I don't know what terms there are for small business or customers to get premium care, probably not good.
We had a mainframe with a bad memory card or bank. We thought. We also swapped out every part trying to get it fixed. We even had to keep the room temp colder and controlled humidity. A new system for us would have been lower maintenance, lower energy bill, less strain on a/c even. And smaller (so we didn't need to use as much floor space). But government can be "penny wise and pound foolish" in such matters.
I know you are just getting familiar with things like "Onyx" and "Disk Warrior" and such. Those can be helpful.
Crashing does tend to lead to more crashes. Mac OS X is not immune to side effects of what they can do. And usually you want to finish a project, not get sidelined.
I wish you had a G5 Quad in there. Two systems. Maybe two G5s even if you have the work or so you can be running CS2 on one and CS3 on another. Or have a techie "gearhead" come in and test and insure that your systems are in working order. Something.
It ain't normal. And it should get more than a "brush off."

Camera Raw, Photoshop CS2 and Nikon D40

Can't open camera raw images from my Nikon D40 in Photoshop CS2.
I downloaded the camera raw plug-in (3.7) but still cannot open the images.
Many problems:
1) I don't have the folder described in the instructions Library>Application Support>Adobe>Plug-ins>CS2?File Formats. My plug-ins are located inside my Photoshop folder. Even after I put the camera raw 3.7 in the plug-ins folder, it doesn't show up under "About Plug-ins."
2) I don't have an NEF plug-in anywhere. I searched the places mentioned in forums as well as a my entire computer.
Help!

Just one note of clarification that you need to understand. You do NOT have to match the version of the DNG converter with your version of Photoshop. You always want to use the latest version of the DNG converter. It will convert images from all of the most recent cameras that ACR supports. So, currently (as of today) you want to be using DNG converter version 4.4.1. It will create DNG files that will be compatible with any version of ACR back to version 2.4 which works with Photoshop CS.
The other thing to verify is what version of Camera Raw is installed on your computer. You want to make sure you are using version 3.7, because that is the last version that was created for Photoshop CS2. If you are using a Windows computer, open Photoshop and then go to Help/About Plug-Ins and click on Camera Raw. It should only be listed once; if it is listed more than once you have a problem. A dialog will appear that will indicate what version is installed. If it is anything other than ACR 3.7, then you don't have the latest version available.
Be aware that there will never be another update of ACR for Photoshop CS2. But if you keep track of the updates and always keep the latest version of the DNG converter on your computer you will have support for every camera that is supported by ACR.
I don't know if any of this information is helpful to you. I just want to help you understand how to integrate DNG files into your workflow.

Using LR2 w/ Photoshop CS2 and Camera Raw 3.7

I am using Photoshop CS2 and Camera Raw 3.7 on a Mac G4, OS X 10.4.11.
I am about to install my upgrade to Lightroom 2. Is this a bad idea?
I have read about some compatibility issues re Camera Raw, and I have also read about how to solve the issue of exporting the keywords.
Will this keyword issue fix work on my system?
What are the real-world practical implications of still having Camera Raw 3.7? I usually adjust images in Lightroom, then any further adjustment is done in Photoshop (not CR). So is the only downside going to be that if I revisit the image in Camera Raw, the adjustments will not show up? Or will it also not show up in Bridge?? And if it is only in CR, is it that the image does not have the adjustments; or does it show the adjusted image, but has just all the sliders zeroed out?
I am hot to install LR2, but I want to make sure that I am not going to open a can of worms. And yes, I could buy PS CS4 (which would get me CR 4.5), and I would like to, but I don't have a G5. And I cannot afford to buy a new desktop computer right now.
Any input would be much appreciated. Thanks.
Dean Abramson

>so is the LR version of RAW as good as the one in CS3?
It's far better as it has local adjustments and such. Lightroom is more equivalent to the ACR in CS4. To make changes you make to images in ACR outside Lightroom show up in Lightroom, you need to sync the metadata. ACR does not write the changes to RAW images to the Lightroom database, but it writes it into xmp sidecars either right next to the RAW file or embedded into it. So Lightroom has no idea you did anything until you specifically ask it to check for updated metadata.
Note that trying to work with both bridge/ACR and Lightroom on the same set of data will inevitably make you lose data or edits at some point as you're dealing with a synchronization issue, so be careful.

Camera Raw Photoshop CS2 & Bridge Parsing Problem

I am having an issue with Photoshop CS2. I am trying to work on a .tiff file that I have used the HDR automate tool from. The HDR renders files in 32-bit and therefor I render back to 16-bit once I have compressed the files and save as a .tiff file.
I then use bridge to try and open the .tiff file and the camera raw file is shaded grey. I also have tried opening in PS CS2 and this message comes up when I try and force Camera Raw to Open..."Could not complete your request because the file-format module cannot parse the file".
PS will open the tiff file on a compressed version and not in the Camera Raw Function.
I have read numerous posts on this kind of problem and people say to update your camera raw plu-in and I have done that and am having the same problem.
Any suggestions I would very much appreciate it.

Hi Patrick,
You need CR 4.x and Ps CS3 in order to open non-camera raw TIFFs.

Nikon NEF Files will not Open in Photoshop CS2

In OS Leopard w/Aperture 2, there was never a problem opening RAW .NEF Files.
Now with Snow Leopard and Aperture 3...I get a message that the format is unrecognizable.
My system and PS2 are fully updated to current versions.
Thank in advance for any help.

Ernie,
You are correct in the RAW decoding engine used in Camera Raw (would be version 3.x in the CS2).
As you know, Adobe Camera Raw is included with each new release of Photoshop since CS came about. However, they generally only update the current version of ACR for new camera models.
The work-around (Adobe solution) for using older versions of ACR / PS is to convert the RAW files to DNG files using their free Adobe DNG converter, which allows compatibility for newer camera models (same solution offered to many with new unsupported cameras in Aperture).
Not sure whether this is the problem for the OP though, as the opening sentence indicates successful use with AP2 and 10.5?
Note - not sure what Adobe will do overall with Lightroom updates as they have been offering those at the same time as the ACR updates. LR3 and CS5 should clear some of this up.

"Use RAW files with external editor" greyed out for Photoshop CS2?

I've just upgraded from iPhoto 5, and the "Use RAW files with external editor" option in the advanced preferences is greyed out when I select Photoshop CS2 as my external editor (back in the General pane).
It works fine when Preview.app is selected. I can understand that pre-CS2 Photoshop wouldn't be available, but CS2 is capable of editing RAW images.
Has anyone been able to get iPhoto 6 to send a RAW image to Photoshop CS2 using this preference? I've written an Applescript to do it in iPhoto 5, but I'd rather use something cleaner...
15" PowerBook G4 Mac OS X (10.4.4)

Works great with Photoshop Elements, opens with Camera Raw. The issue is you can't save it so that iPhoto gets the changes.
You have to save it and then re-import. I tried all permutations of saving it in originals and modified folders in the library. No luck. The only thing I didn't try is to save it as a jpeg over the top of the full sized one iPhoto created on import.

Photoshop CS2 RAW (NEF) Issue

Similar Messages

Maybe you are looking for