There's no mystery to it other than that you need to understand colorspaces better.
ProPhoto RGB describes a much larger color gamut than Adobe RGB or sRGB. If you have subtle colors in ProPhoto RGB and they disappear when you convert to sRGB or Adobe RGB, they've been clipped as they cannot be represented in the target colorspace. Once clipped, they cannot be recovered by converting back to the larger colorspace ... the data has been lost, you need to go to the original file to retrieve them. You might try different rendering intents ... Relative Colorimetric basically moves all 'out of bound' colors to the limits of a particular colorspace where Perceptual attempts to translate all colors into the target colorspace as best can be arranged. Here's a way to see what's going on: convert a RAW file to a [EMAIL PROTECTED], ProPhoto RGB file and open it in Photoshop. Have the Histogram palette open, full RGB display. Then convert the colors to the Adobe RGB profile with Relative Colorimetic intent ... toggle the action with the "undo" command a couple of times and watch the histograms. You'll see where the clipping is. Do the same with the Perceptual intent. Once you see where the clipping is, go back to the ProPhoto RGB rendering and adjust the color rendering to move values in those areas back into the "safe" zone. Then you can convert to a smaller profile with greater ease. (When you're working with a printer output profile, you can do the same thing using the proofing setup and even turn on gamut warning flags, but I don't recall that Photoshop 7 has these features. I have PS CS2.) Godfrey On Jul 9, 2008, at 11:18 AM, P. J. Alling wrote: > Raw Shooter Essentials, it's much better looking, without any > Photoshop > work before export as a TIKF. I recently started using ProPhoto color > space in my work flow which seems to give better results, if I > remember > to convert the profile in Photoshop before output, so I changed > back to > the Adobe RGB profile and it made no difference. The last set of > fireworks I processed, some time ago looked exactly the same when > imported into Photoshop after conversion. > > http://home.earthlink.net/~morephotos/fireworks/PESO_-- > _fireworks1a.html > > It's really quite annoying. > > David J Brooks wrote: >> I like the pattern of the blast, very good. >> >> What do you convert with.? >> >> Dave >> >> On Wed, Jul 9, 2008 at 11:38 AM, P. J. Alling >> <[EMAIL PROTECTED]> wrote: >> >>> I went with a friends to the 4th of July fireworks in NY this >>> last week >>> and in spite of the rain it was a very good time. I carried the >>> Dx with >>> an A 24 FA 43 and vacillated between a 55 f1.8 or 85 f2.0 and >>> finally >>> decided on the real telephoto. I didn't take a tripod, was really >>> looking to do some crowd/people shooting but I shot quite a lot >>> of the >>> fireworks anyway. Some of them weren't half bad. >>> >>> Just a bit of carping, I noticed when I opened almost all the >>> fireworks >>> files into any raw converter I could get some very subtle colors >>> in the >>> actual fireworks. However when I loaded them into Photoshop >>> (7.0) for >>> final editing, when they were converted to the working color >>> space many >>> of those colors were lost. This image had much more vibrant >>> blues and >>> reds, which Photoshop just washed out. I tried a number of >>> different >>> color spaces in the raw converter including sRGB and every one >>> did the >>> same thing. Oh well, another damned mystery. >>> >>> http://home.earthlink.net/~morephotos/fireworks/PESO%20--% >>> 20fwny2008_01.html >>> -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
