|
| Author | Thread |
|
|
06/26/2006 10:45:30 AM · #1 |
Here's what I want to do, tell me if I'm crazy.
1. Drop a AdobeRGB .NEF file from my camera on to my computer.
2. Organize that file and its cohorts in Bridge, seeing them as they will appear on anyone elses screen (calibration issues aside).
3. Deal with the file in Camera Raw, seeing/modifying its appearance as it would appear on anyone elses screen.
4. Save as a .PSD or .JPG and see both looking the same.
5. Save for web and see both looking the same (SFW window overlaying the workspace usually shows massive differences).
6. Print the file from .PSD or .JPG and have it look the same as the original RAW file.
If I set Photoshop to "Working CMYK" in the proof setup, all three programs look the same until I hit a Save for Web dialog. If I set Photoshop to Windows RGB or Monitor RGB then I can see what my online friends, blog readers, and website viewers are seeing but it is desperately different from the image in Bridge or Camera Raw. I've yet to find a similar "Proof Setup" setting in either of those programs.
If I was simply printing, obviously "Working CMYK" would work fine, go straight from .NEF to .PSD and simply work with that. But I shoot digital for the added benefit of being able to instantly share photos, host online, and generally view in multiple formats (electronic and print).
How do I make this work?
|
|
|
|
06/26/2006 11:31:08 AM · #2 |
Forgive me if I'm talking out my nether regions, but I believe that if you are processing in batch, you might want to start in RGB and include a quick 'web process (resize, contrast, sharpening whatever you usually do)', then do a save for web (still retaining the RGB), then REVERT, and carry on your process...
I seem to think that if you do this, the save for web will not switch you to the web saved image, but keep you in the original image... this is different from doing a 'save as', which will carry you over to the newly saved image...
I think you could probably make an action to do this, then fire the action in batch?
Message edited by author 2006-06-26 11:31:46. |
|
|
|
06/26/2006 11:47:40 AM · #3 |
Hmmm. Let me start at the beginning.
Your RAW file has *no* color space inherently, only the space your camera tells the RAW converter to interpret the conversion in. Adobe RGB is a good color space if you want a wide gamut in your converted (TIFF or JPEG) files. It *will* require that you proof in the desired output space, which is nearly always sRGB, in order to see what others will see. Photoshop can do this, as well as display out-of-gamut colors (those colors that are within the Adobe RGB space, but outside sRGB).
Before you save for web, you'll need to do a color space conversion, otherwise you'll end up displaying an Adobe RGB image as sRGB, and you *will* see undesirable changes in color.
Regarding proofing in CMYK, that's really not recommended. CMYK is a very small color space, and should be used only where the intended output device is truly CMYK. This typically means pre-press applications.
The bottom line is, if you are not completely comfortable with all the ins and outs of a color managed workflow, convert your RAW files using sRGB and work in that space. You'll have much fewer issues with inconsistent results. |
|
|
|
06/26/2006 12:03:48 PM · #4 |
Originally posted by kirbic:
The bottom line is, if you are not completely comfortable with all the ins and outs of a color managed workflow, convert your RAW files using sRGB and work in that space. You'll have much fewer issues with inconsistent results. |
I'll second that. And most of the time color managed work-flow just isn't worth the extra hassle.
Message edited by author 2006-06-26 12:07:35.
|
|
|
|
06/26/2006 01:07:19 PM · #5 |
| Thanks, that calms my fears. I look forward to trying it tonight. |
|
|
|
07/05/2006 11:20:45 PM · #6 |
I am at an utter loss right now, I've tried every combination and cannot get photos to look the same between Photoshop, Save for Web (in Photoshop), and Windows/Irfan/Picasa.
I shoot AdobeRGB .NEF files on my camera (though I've been told the color space deoesn't matter for RAW so this probably is inconsequential). I work with the .NEF file through Adobe Bridge and Adobe Camera Raw. I set the working space to sRGB and save the processed .NEF as a .JPG file. I open the jpeg in PS and it looks like it did in Bridge/RAW/Camera. I click on File > Save for web and the resulting photo looks different, major color shifts.
My Proof Setup has been tried in Monitor/Windows/Custom (pure sRGB emulation). My color space for the program is "North American General Purpose 2" where the RGB display is sRGB but I've also tried it under "... Web Internet" and "Monitor Color".
I do not have any monitor calibration software or hardware, I am not going to buy these until I can figure out how to get everything looking the same between programs (then I'll worry about getting stuff looking the same as everyone else's screens). Even if my monitor is horribly calibrated right now, the issue at hand is the software issue and I simply want all of my photos to look exactly the same (however horrible) in every program.
How is yours set up? |
|
|
|
07/06/2006 05:21:29 AM · #7 |
Proofing should not be enabled unless you are, well ... proofing. The proofing option can be thought of as a filter that allows you to see how your image would look if converted to the proofed color-space -- it is only of use when you want to see what the image will look like on something other than your monitor. Just make sure 'Proof Colors' under the View menu is unchecked and what you see is what the image is. With proofing enabled ('Proof Colors' checked) you are not seeing what the image actually looks like. Leave it unchecked until you have a specific reason to need to see your image in a color-space other than what it is in.
Likewise, put everything from camera on in the sRGB color-space and leave it alone until you have a specific reason to change it. The more specific the reason the better -- and the easier it is the understand what effect the change has.
|
|
|
|
Current Server Time: 09/06/2025 03:10:15 AM  |
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 09/06/2025 03:10:15 AM EDT.
|
