Processed PSD files noticably unsharp compared to RAW file

PikkieChick

Member
Messages
37
Reaction score
2
Hi there - I am using CS6 shoot with a Canon 5D3. Can anyone tell me what I might be doing wrong, or if I need to tweak some settings but my PSD files seem quite unsharp in comparison to the CR2 file after processing, even the tack sharp CR2 files (the jpeg is understandably not as sharp after compression but the PSD file looks more like the jpeg !).

I use windows photo viewer to flick through the images quickly as I find bit of a lag with CS6, but have also viewed the 3 different files in other viewers and I can still see the issue. I have taken into consideration the noise reduction settings etc and always save the jpeg at the highest setting. Should there be such a difference ?

Link to dropbox with the PSD, JPEG and RAW file:

https://www.dropbox.com/sh/rw2r30i154thp02/AACfuRKzwDs8pYGmPi2J7yE0a?dl=0
 
Hi there - I am using CS6 shoot with a Canon 5D3. Can anyone tell me what I might be doing wrong, or if I need to tweak some settings but my PSD files seem quite unsharp in comparison to the CR2 file after processing, even the tack sharp CR2 files (the jpeg is understandably not as sharp after compression but the PSD file looks more like the jpeg !).

I use windows photo viewer to flick through the images quickly as I find bit of a lag with CS6, but have also viewed the 3 different files in other viewers and I can still see the issue. I have taken into consideration the noise reduction settings etc and always save the jpeg at the highest setting. Should there be such a difference ?
You are almost certainly seeing the difference between two different processing treatments of the same original capture.

One treatment was made inside the camera, from the Raw data, according to its current JPG settings, immediately the shot was taken. This was then embedded into the Raw file as a JPG preview. This is what was reviewed in the camera, and this is what the viewer software later extracted and displayed on the PC. It's the equivalent of viewing a camera JPG, on the fly.

The other treatment has been made by your Raw converter (e.g. ACR) according to its current conversion settings, as modified by any further edits in PS. This treatment will have simply ignored the camera's (JPG relevant) settings for contrastiness, tone etc.

So if the PSD has had (for example) less sharpening, or more noise reduction, or less contrastiness imposed - compared with how the camera was set in those respects - this is IMO your explanation.
 
Last edited:
I opened your fifth RAW image in PS 2014, with default settings, and clicked "open image", leaving it open as a CR2 file on the screen in PS. I then saved this file as a PSD file and compared the CR2 and the PSD in PS. There was no difference whatsoever.

Perhaps I'm misunderstanding your question?

Best wishes,

Art

Hi there - I am using CS6 shoot with a Canon 5D3. Can anyone tell me what I might be doing wrong, or if I need to tweak some settings but my PSD files seem quite unsharp in comparison to the CR2 file after processing, even the tack sharp CR2 files (the jpeg is understandably not as sharp after compression but the PSD file looks more like the jpeg !).

I use windows photo viewer to flick through the images quickly as I find bit of a lag with CS6, but have also viewed the 3 different files in other viewers and I can still see the issue. I have taken into consideration the noise reduction settings etc and always save the jpeg at the highest setting. Should there be such a difference ?

Link to dropbox with the PSD, JPEG and RAW file:

https://www.dropbox.com/sh/rw2r30i154thp02/AACfuRKzwDs8pYGmPi2J7yE0a?dl=0
 
I opened your fifth RAW image in PS 2014, with default settings, and clicked "open image", leaving it open as a CR2 file on the screen in PS. I then saved this file as a PSD file and compared the CR2 and the PSD in PS. There was no difference whatsoever.
Art maybe its the fact that I mainly view in windows photos viewer when I'm doing a quick browse. I should always browse in PS? I will hve another look, but I swear a couple of PSDs that I compared in PS were not sharp. Did u c anything with the other images??
 
I opened your fifth RAW image in PS 2014, with default settings, and clicked "open image", leaving it open as a CR2 file on the screen in PS. I then saved this file as a PSD file and compared the CR2 and the PSD in PS. There was no difference whatsoever.
Art maybe its the fact that I mainly view in windows photos viewer when I'm doing a quick browse. I should always browse in PS? I will hve another look, but I swear a couple of PSDs that I compared in PS were not sharp. Did u c anything with the other images??
Try Bridge. Bridge is the free image viewer and organizer that comes with Photoshop. It isn't a very good organizer but it is better than Windows Photos Viewer when viewing images and it is a better organizer than Windows Browser.
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.

(By the way, when posting images to be viewed on the web you should use sRGB not Adobe RGB as your color space --with associated profile -- the web doesn't do Adobe RGB.)

I opened your fifth RAW image in PS 2014, with default settings, and clicked "open image", leaving it open as a CR2 file on the screen in PS. I then saved this file as a PSD file and compared the CR2 and the PSD in PS. There was no difference whatsoever.
Art maybe its the fact that I mainly view in windows photos viewer when I'm doing a quick browse. I should always browse in PS? I will hve another look, but I swear a couple of PSDs that I compared in PS were not sharp. Did u c anything with the other images??
 
Sorry ArtMar for being dense, but I do that when I save ? Im still learning the ins and outs ! I will also try what u have suggested above.

Another question - do I work in 8 bit or 16 bit ? Or is that a whole new ballgame ???
 
Last edited:
These issues are surprisingly controversial --

Some folks work in Prophoto, some in Adobe RGB, and others in sRGB. Some work in 16 bit and others 8 bit. Dan Margulis, the expert on these matters I, and many others, trust the most, recommends working in 8-bit, sRGB. That is, set ACR (at the bottom) to sRGB, and your working space in Photoshop to sRGB. There's also the issue of whether or not your monitor can display Adobe RGB. (In any event, it's highly recommended that you calibrate it.)

Here's a recent article by Dan M that delves into these issues that you may find helpful:


The web displays sRGB only, so anything intended for the web should be saved in that space with "preserve profile" checked. An Adobe RGB file may not look very good on the web -- desaturated colors among other problems.

Good luck!

Art

Sorry ArtMar for being dense, but I do that when I save ? Im still learning the ins and outs ! I will also try what u have suggested above.

Another question - do I work in 8 bit or 16 bit ? Or is that a whole new ballgame ???
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
Sorry but you can't do that. You can only open a RAW file in ACR, not in Photoshop. When you finish editing a RAW image in ACR it is can then be saved in Photoshop as either a PSD or TIFF depending on the Save Image setting or it can be opened in Photoshop as a TIFF.

You then use Bridge to open both the RAW and TIFF images (not PSD) in ACR where you can switch back and forth between the two images to compare them.

Even easier is to use Bridge to view the RAW and PSD/TIFF images side by side or flip back and forth between them.

Photoshop comes with aSRG selected as the default Working Color Space. When you view a aRGB color space image in a non-color space controlled program (Windows Viewer?) or browser the colors won't display correctly since they are set up to only show sRGB images correctly.

I recommend that the OP use the free FastStone Image Viewer instead of Widows Viewer since you can set FastStone to be color space aware. To set FastStone to be color aware go to Settings>Settings>CMS and check the Enable Color Management System box.

FastStone Image Viewer - Powerful and Intuitive Photo Viewer, Editor and Batch Converter

If you shoot only JPGs then I recommend you use the Photoshop Edit>Color Settings>Working Space command and select sRGB so that your saved JPGs will be compatible with the web and smart devices.

If you only shoot RAW then select ProPhoto RGB but be sure to check all the boxes in the Color Management Policies area to avoid color space mismatches when importing images without an embedded color space or with any other embedded color space.



Note that using the aRGB or ProPhoto color working space in Photoshop will cause a problem if you try to save your images as JPGs using just the File>Save As>JPEG command - it will embed the working color space in the image file, not sRGB.This will cause the image colors to display incorrectly.

To avoid this color space mismatch problem use the Edit>Convert to Profile>Destination Space>sRGB command before saving the file as a JPG using the File>Save As>JPEG command.

The File>Save for Web command can also be used and it will automatically convert the image to the sRGB color space but it also automatically adjusts sharpening, contrast, and saturation for the web.

--
Living and loving it in Pattaya, Thailand. Canon 7D - See the gear list for the rest.
 
Last edited:
A small point, but just to clarify: the latest version of ACR has an "open image" button at the bottom to bring it into PS. That is what I was referring to, not opening a RAW file directly in PS (not to confuse matters further, but in PS CC 2014, Camera Raw is available as a filter).

Your many suggestions, from using FastStone viewer to Prophoto workspace, are of course useful, and represent your personal preferences. You no doubt know there are a plethora of diverse opinions about many of these issues. Some of these are discussed in the Dan Margulis article I linked to.

By the way, I don't want to precipitate a discussion of the advantages and disadvantages of working in x or y or z color space. The OP will have to decide for herself what is best for her.

Art
 
I checked my PS and ACR settings and ACR was set to aRGB, but my working space in Photoshop was set to sRGB. Would that variation make any difference ?
 
Even easier is to use Bridge to view the RAW and PSD/TIFF images side by side or flip back and forth between them.

I recommend that the OP use the free FastStone Image Viewer instead of Widows Viewer since you can set FastStone to be color space aware. To set FastStone to be color aware go to Settings>Settings>CMS and check the Enable Color Management System box.

FastStone Image Viewer - Powerful and Intuitive Photo Viewer, Editor and Batch Converter

If you shoot only JPGs then I recommend you use the Photoshop Edit>Color Settings>Working Space command and select sRGB so that your saved JPGs will be compatible with the web and smart devices.

If you only shoot RAW then select ProPhoto RGB but be sure to check all the boxes in the Color Management Policies area to avoid color space mismatches when importing images without an embedded color space or with any other embedded color space.



Note that using the aRGB or ProPhoto color working space in Photoshop will cause a problem if you try to save your images as JPGs using just the File>Save As>JPEG command - it will embed the working color space in the image file, not sRGB.This will cause the image colors to display incorrectly.

To avoid this color space mismatch problem use the Edit>Convert to Profile>Destination Space>sRGB command before saving the file as a JPG using the File>Save As>JPEG command.
Sailor Blue
Ive checked out the Faststone image viewer, very nice. like the ability to compare 3-4 images side by side at 100% and other various sizes.
Ive looked at Bridge again and finding it a bit fiddly trying to flick between a CR2, PSD, jpeg file at 100% for comparisons (I guess its just learning the shortcut buttons etc). I keep on accidentally clicking on the image and opening it up by mistake !
As for my images - I always shoot RAW only, but my husband shoots jpegs. Im also processing a few older images from a few years back they are only jpegs. With this being the case, would changing all my settings to ProPhoto be to painful considering what I have said above. Would I have to change it back each time depending on whether Im working on a RAW or JPEG ?
I have changed my ACR to sRGB to start with ? Good option ?
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
UNLESS FastStone is merely extracting and displaying an embedded preview from the Raw file, and not making its own conversion and processing of the picture (this is a common method used by image browsers, as well as by the camera itself).

Such a preview will reflect the results of in-camera JPG settings e.g. sharpening and contrastiness.

Also depending on the JPG settings in the camera, an embedded preview may be made at a reduced resolution (fewer megapixels). That too can affect the perception of sharpness, on screen, in practice.
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
UNLESS FastStone is merely extracting and displaying an embedded preview from the Raw file, and not making its own conversion and processing of the picture (this is a common method used by image browsers, as well as by the camera itself).

Such a preview will reflect the results of in-camera JPG settings e.g. sharpening and contrastiness.

Also depending on the JPG settings in the camera, an embedded preview may be made at a reduced resolution (fewer megapixels). That too can affect the perception of sharpness, on screen, in practice.
Richard, your explanation as to what is being observed is the right one (i.e. this is about file-viewers showing the camera-shot JPEG embedded to the RAW).

I looked using EXIFTool, Photoshop CC 2014, and FastStone (looking at image 2, and all of the CR2, PSD, and the JPEG crop of that).

The PSD and JPEG in the Dropbox to me look basically the same when opened into ACR and then through into Photoshop CC 2014. I did not replicate the exact ACR Sharpening and NR applied by the OP on opening the CR2 in ACR (I can read the actual values the OP used in ACR from the XMP in the PSD and JPEG - the processing was ACR8.7.1). In general though, there is only moderate sharpening applied as well as some NR on an ISO100 image.

The embedded JPEG from the camera in the CR2 RAW is Large size, Sharpness level 3 (on a Canon 5D mk III; I think that's default mid-range on a scale of 7, but sharpening is applied - it would be 0 if none).

Now we have FastStone in the mix - and FastStone is a file-viewer with a RAW developer built on. In general, I am a Mac user with a Win machine only on the side and therefore I am not a FastStone expert by a long way. I think however FastStone installs as a default file-viewer showing the embedded JPEG. Under that default setting, then the CR2 (i.e. the embedded JPEG in it) does indeed look sharper than the ACR/PS JPEG also in the Dropbox.

If I then switch FastStone to RAW mode (in the Settings menu or by pressing A when viewing an image in the default embedded JPEG mode), then because I am now viewing sensor data, I loose the sharpness. I can use FastStone's own Sharpness adjust (under the Colors menu) to adjust the Sharpness back (and up higher) to make it quite a bit more sharp than the JPEG or PSD which are ACR processed.

If I work in Photoshop with (something like) Nik Sharpener, then again I can sharpen up the PSD a lot more.

So, basically, having investigated, we are seeing what you say - i.e. this is a not-very sharply processed PSD (and JPEG save from that), being compared in file-viewer application(s) to an in-camera embedded JPEG in a .CR2 which has 3 (out of a scale of 7) Sharpness applied by the camera.

[ It's then another discussion and will slightly affect things when viewed side-by-side in non color-managed applications, but the PSD and JPEG saved from that are in aRGB, but the embedded JPEG in the CR2 is as per the camera's setting which was sRGB. ]

--
Mark W.
http://500px.com/Mark_Wycherley
 
Last edited:
Even easier is to use Bridge to view the RAW and PSD/TIFF images side by side or flip back and forth between them.

I recommend that the OP use the free FastStone Image Viewer instead of Widows Viewer since you can set FastStone to be color space aware. To set FastStone to be color aware go to Settings>Settings>CMS and check the Enable Color Management System box.

FastStone Image Viewer - Powerful and Intuitive Photo Viewer, Editor and Batch Converter

If you shoot only JPGs then I recommend you use the Photoshop Edit>Color Settings>Working Space command and select sRGB so that your saved JPGs will be compatible with the web and smart devices.

If you only shoot RAW then select ProPhoto RGB but be sure to check all the boxes in the Color Management Policies area to avoid color space mismatches when importing images without an embedded color space or with any other embedded color space.



Note that using the aRGB or ProPhoto color working space in Photoshop will cause a problem if you try to save your images as JPGs using just the File>Save As>JPEG command - it will embed the working color space in the image file, not sRGB.This will cause the image colors to display incorrectly.

To avoid this color space mismatch problem use the Edit>Convert to Profile>Destination Space>sRGB command before saving the file as a JPG using the File>Save As>JPEG command.

Sailor Blue

Ive checked out the Faststone image viewer, very nice. like the ability to compare 3-4 images side by side at 100% and other various sizes.

Ive looked at Bridge again and finding it a bit fiddly trying to flick between a CR2, PSD, jpeg file at 100% for comparisons (I guess its just learning the shortcut buttons etc). I keep on accidentally clicking on the image and opening it up by mistake !

As for my images - I always shoot RAW only, but my husband shoots jpegs. Im also processing a few older images from a few years back they are only jpegs. With this being the case, would changing all my settings to ProPhoto be to painful considering what I have said above. Would I have to change it back each time depending on whether Im working on a RAW or JPEG ?

I have changed my ACR to sRGB to start with ? Good option ?
You don't have to change the Photoshop Color Working Space back and forth if you have the three Profile boxes checked as in the above image. When there is an image with a different color space, or no color space, embedded in the file you will be asked if you want to work on the file in the embedded color space or convert the file to the working color space.

If you don't check the Profile Mismatches: Ask When Opening box then with the setup shown above a JPG with the embedded sRGB color space would automatically open in the sRGB color space. I keep the box checked just because I'm a bit anal about wanting to control things myself.

I keep the working color space of ACR and Photoshop set to 16-bits and ProPhoto RGB as you see above for Photoshop and below for ACR.



Whenever I bring in a JPG I shot with one of my point and shoot camera or with my phone I tell Photoshop to work in the embedded sRGB color space. Frequently there isn't any embedded color space on a JPG from the web so I tell Photoshop to use the sRGB color space.

The exception is that I frequently open JPGs in ACR (or Lightroom) and work on them there before saving them or sending them to Photoshop for some advanced post processing. Doing all the editing you can in ACR is simply easier than doing it in Photoshop.

If you use the PS File>Open As>Camera Raw command you can only open one image at a time in ACR. You can open multiple images in ACR through Bridge and this is one good reason for learning how to use Bridge.

The reason I keep ACR and PS set to 16-bits and ProPhoto is that those settings use all the data from a RAW file and allow me to make changes to the image without having posterization problems. I try to work non-destructively as much as possible in PS and save my TIFF files with all layers intact to make it possible to go back and change things should I ever want to do so.

B&H - Tim Grey - Photoshop CS6 for the Photographer - YouTube

It is only when I save a copy of the image for the web or my phone/tablet that I do the conversion to an 8-bit JPG. Once I use the JPGs I usually delete them, it is just too easy to make new ones should I ever need another copy and I don't need the extra files using up disk space.

--
Living and loving it in Pattaya, Thailand. Canon 7D - See the gear list for the rest.
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
UNLESS FastStone is merely extracting and displaying an embedded preview from the Raw file, and not making its own conversion and processing of the picture (this is a common method used by image browsers, as well as by the camera itself).
You are absolutely right Richard.

FastStone is showing the JPG that is embedded in RAW files by the camera. FastStone doesn't have a RAW converter so that is all that it can do.
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
UNLESS FastStone is merely extracting and displaying an embedded preview from the Raw file, and not making its own conversion and processing of the picture (this is a common method used by image browsers, as well as by the camera itself).

Such a preview will reflect the results of in-camera JPG settings e.g. sharpening and contrastiness.

Also depending on the JPG settings in the camera, an embedded preview may be made at a reduced resolution (fewer megapixels). That too can affect the perception of sharpness, on screen, in practice.
If I then switch FastStone to RAW mode (in the Settings menu or by pressing A when viewing an image in the default embedded JPEG mode), then because I am now viewing sensor data, I loose the sharpness. I can use FastStone's own Sharpness adjust (under the Colors menu) to adjust the Sharpness back (and up higher) to make it quite a bit more sharp than the JPEG or PSD which are ACR processed.
So, basically, having investigated, we are seeing what you say - i.e. this is a not-very sharply processed PSD (and JPEG save from that), being compared in file-viewer application(s) to an in-camera embedded JPEG in a .CR2 which has 3 (out of a scale of 7) Sharpness applied by the camera.

[ It's then another discussion and will slightly affect things when viewed side-by-side in non color-managed applications, but the PSD and JPEG saved from that are in aRGB, but the embedded JPEG in the CR2 is as per the camera's setting which was sRGB. ]
 
I agree with Richard regarding JPEGS and Sailor Blue regarding using Bridge.

Your PSD's on Dropbox do not look as sharp as your Raw files, but I think that's because of the photo viewer you captured them from. But I still don't understand why there would be a difference when viewing in PS.

Try this. Select a RAW file you haven't processed yet, one with a fair amount of detail (like one of your architectural images). Open it in ACR. Don't make any adjustments. Open it in PS. Save it as a PSD. Then open the same RAW file in ACR with no adjustments, then in PS. Leave it as a CR2 file. Do you see any differences? If so, upload the RAW file and the PSD file to Dropbox so we can have a look.
No differences between the CR2 file and PSD file at all checking them in PS at 100%.

I did though open the RAW, CR2 and JPEG files in the faststone photo viewer and once again the JPEG and PSD look nearly identical. The CR2 is much sharper. Eeek I had them lined up side by side and could easily see the difference. What am I doing wrong !
You're not doing anything wrong -- FastStone is probably just applying a greater degree of default sharpening to the RAW file than ACR . If the CR2 file and PSD files look the same in PS at 100% then you're all set.
UNLESS FastStone is merely extracting and displaying an embedded preview from the Raw file, and not making its own conversion and processing of the picture (this is a common method used by image browsers, as well as by the camera itself).
You are absolutely right Richard.

FastStone is showing the JPG that is embedded in RAW files by the camera. FastStone doesn't have a RAW converter so that is all that it can do.
Sailor - FastStone (image Viewer, at least the latest 5.3) does have a RAW converter. This was something I was surprised to learn a while back also. In Settings you have these options under the RAW tab. This is the default using Embedded preview:

7f57d66500944836831a35935a9332b2.jpg


And then this to have it use its converter:

f007a79c219345bf9ad35ecaa95de5a9.jpg


You can also hit 'A' when it's in the first mode on any image to have it re-render using the RAW converter.

As far as I have read, it uses dcraw as its RAW conversion code library.

By togglling the above settings on the OP's CR2 images in her Dropbox you can see the sharpness rendering substantially change. That's in my reply above.

--
Mark W.
http://500px.com/Mark_Wycherley
 
Last edited:

Keyboard shortcuts

Back
Top