Many thanks Claas. I've tried the Argyll method and it seems to work very well. I haven't tried the basICColor as I don't have it. Robert -----Original Message----- From: argyllcms-bounce@xxxxxxxxxxxxx [mailto:argyllcms-bounce@xxxxxxxxxxxxx] On Behalf Of Claas Bickeböller Sent: 05 October 2014 16:31 To: argyllcms@xxxxxxxxxxxxx Subject: [argyllcms] Re: Workspace mapping Sorry, of course: fakeread path_to_sRGB_profile rgbpatches Am 05.10.2014 um 17:25 schrieb Claas Bickeböller <lists@xxxxxxxxxxxxxxxxx>: > Hi, > > of course it is possible to create an sRGB profile with real gamut mapping. > The easiest way is to drag & drop the sRGB profile onto basICColor dropRGB. > It will create an RGB printer profile with gamut compression (instead of clipping) which you can use as destination profile. > After the conversion assign the original sRGB. > > Using Argyll sth. similar to this should do the job: > targen -d2 rgbpatches > fakeread rgbpatches > colprof -v -s path_to_your_AdobeRGB1998.icc rgbpatches > > Best regards > > Claas > > Am 05.10.2014 um 15:34 schrieb <robert@xxxxxxxxxxxxxxxxxx> <robert@xxxxxxxxxxxxxxxxxx>: > >> Is it also intended as a destination profile when mapping from another v2 >> workspace? If not, how does one get one's image into the sRGB v4? >> >> The issue I'm trying to address is converting to sRGB for web viewing when >> the normal relative colorimetric intent does a bad job. I would then like >> to be able to try a perceptual mapping (which isn't possible with the v2 >> matrix-based profiles). My original question was whether or not it would be >> possible to construct a v2 table-based sRGB profile so that a perceptual >> mapping could be used (with a final conversion to the standard matrix-based >> sRGB profile, presumably). >> >> Or perhaps it has already been done? >> >> Robert >> >> -----Original Message----- >> From: argyllcms-bounce@xxxxxxxxxxxxx [mailto:argyllcms-bounce@xxxxxxxxxxxxx] >> On Behalf Of Florian Höch >> Sent: 05 October 2014 12:28 >> To: argyllcms@xxxxxxxxxxxxx >> Subject: [argyllcms] Re: FW: Workspace mapping >> >> As I understand it, the ICCv4 "preference" sRGB profile is primarily >> meant to be used as source profile when mapping directly into an >> (preferably ICCv4, LUT-based) output/printer profile. >> When converting to a (matrix-based) working space, you'll loose the >> ability to get a true perceptual mapping. >> >> Am 05.10.2014 um 13:09 schrieb robert@xxxxxxxxxxxxxxxxxx: >>> The ICC has released a v4 sRGB profile (Beta release) that provides both >>> Relative and Perceptual mapping to other workspaces (although I see from >>> Graham's documentation that he says that: "The chief drawback (of v4), is >>> that only one (non colorimetric) intent can really be supported, that of >>> saturation"). >>> >>> I've tried out the ICC sRGB v4 profile and although I can't say that the >>> perceptual mapping works well in the images I've tried (the usual v2 RC >>> mapping to sRGB seems to give better results with LESS clipping!), it >> would >>> seem to be a step in the right direction. >>> >>> If I do a further conversion, from the v4 sRGB to v2 sRGB the image >>> improves, but it's still worse than the direct v2 mapped image. >>> >>> Could this be due to v2/v4 mismatching? My monitor profile for example, is >> a >>> v2.2 profile. I'm comparing the images in Photoshop. >>> >>> Any advice, explanations, insights? >> >> -- >> Florian Höch >> >> >> >> > >