On Saturday 05 August 2006 18:33, Hal V. Engel wrote: > I am not so sure that images in GIMP are "edited in sRGB colorspace".
You are right: I forgot that Gimp let the user choose working colorspace... But as you explain later, Gimp is not able to read embedded profiles. So you have to choose the working colorspace, which much match the colorspace of the image. Usually, sRGB, as most DSRL cameras output files in this colorspace. I hope that the final 2.4 version will handle all the conversions between colorspaces, the embedded profiles, and all problems it can produce when loading image with different profiles... > > If you are not using Gimp-2.3, then, yes, I think your are right, and > > you have to use the monitor profile as source profile. > > No this is not correct. You need to use whatever color space is correct > for the image. If you captured the image with a camera or scanner then > you need to use a profile for that camera/scanner to either work > directly in that color space or to convert the image from that color > space to some standard working color space of your choice such as > AdobeRGB, ProPhotoRGB, BetaRGB.... But what to do when using an application which doesn't support profiles (here, not using Gimp-2.3) ? Then, all corrections you are going to do will bring your image in the monitor colorspace, because you will try to have this image looking good on the monitor. Am I wrong ? This case is not very clear to me... > If you do use a standard working color space avoid sRGB as it is simply > too small to handle the gamut/dynamic range of most source material. > This is particularly true for DSRL cameras where you process the raw > data and for high dynamic range film scanners. Friends don't let > friends use sRGB. Yes, it is true. And even when I don't use RAW files, my Canon 20D let me output jpeg in AdobeRGB colorspace :o) > I have been using CinePaint more lately. It has full CM awareness (it > knows how to use embedded profiles for example) and will handle images > with higher bit depths (16, 32 bits/channel as well as images with float > and double values). GIMP is currently limited to 8 bits/channel. The > disadvantage of CinePaint is that it's tool set is somewhat limited. > But it does have all of the basic tools you need for most things and if > your work flow consists of making basic image adjustments (color > balance, contrast, brightness, curves, levels...) and cropping then it > will do the job very nicely. When processing RAW files, all color corections are made in a linear space, on the 12bits/channel. So, once the tiff/jepg file is produced, you only need to use geometric tools in Gimp. It can be done without to much damages, even in 8bits. -- Frédéric http://www.gbiloba.org
pgpUPZ7beT2Xy.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
