From f6b8e0eae4374f339487a33e3e4fe5462d5816e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Sat, 25 Nov 2017 10:16:00 +0100 Subject: New upstream version 2.0.0 --- doc/Scenarios.html | 224 +++++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 207 insertions(+), 17 deletions(-) mode change 100644 => 100755 doc/Scenarios.html (limited to 'doc/Scenarios.html') diff --git a/doc/Scenarios.html b/doc/Scenarios.html old mode 100644 new mode 100755 index 8aa5d64..9a55e88 --- a/doc/Scenarios.html +++ b/doc/Scenarios.html @@ -75,7 +75,7 @@ handled when calibration is being used

Linking Profiles

-

    Image dependent gamut +

    Image dependent gamut mapping using device links

    Soft Proofing Link
@@ -179,6 +179,12 @@ + + + + + + @@ -263,6 +269,12 @@ + + + + + + @@ -660,6 +672,12 @@ + + + + + + @@ -736,6 +754,12 @@ + + + + + + @@ -751,6 +775,16 @@ style="font-weight: bold;">ccmx files is here.

+ Another, more general approach to correcting Colorimeters is to + store the spectral sensitivities for each individual instrument in + the instrument itself, and then combine that with spectral samples + for a particular display type to compute a specific instrument + + display correction matrix on the fly (i.e. the i1d3 * Spyder 4 & + 5 instruments). The display spectral samples can be stored in a Colorimeter Correction Spectral + Sample file. A list of contributed ccss files is here.

Calibrating and profiling a display that doesn't have VideoLUT access.

In some situation there is no access to a displays VideoLUT @@ -825,7 +859,7 @@ href="cctiff.html#p1">DisplayA.icm DisplayA.cal infile.jpg outfile.jpg

-

+

Profiling Scanners and other input devices such as cameras

@@ -910,6 +944,12 @@ + + + + + + @@ -924,6 +964,12 @@ width="200" height="122"> ColorChecker SG

+ A chart provided for camera profiling is the X-Rite ColorCheckerPassport:
+
+ ColorChecker Passport
+
The GretagMacbeth Eye-One Pro Scan Target 1.4 can also be used:

Eye-One Scan Target 1.4spec2cie ColorCheckerSG.ti3 ColorCheckerSG.cie

+ For the full ColortChecker Passport chart, the ref/ColorCheckerPassport.cht + file should be used, or if just the 24 patches corresponding to + the original ColorChecker are in the shot, the ref/ColorCheckerHalfPassport.cht + should be used. A user has kindly provided their measured values + for this chart, and they are available in ref/ColorCheckerPassport.cie + and ref/ColorCheckerHalfPassport.cie respectively.
+
For the Eye-One Pro Scan Target 1.4 chart, the ref/i1_RGB_Scan_1.4.cht file should be used, and as there is no reference file @@ -1429,6 +1512,12 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + file made from measuring a sample chart is also available. Alternately you could create your own reference file by @@ -1503,6 +1592,12 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + @@ -1553,10 +1648,11 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t linearly additive in behaviour.

If the purpose of the input profile is to use it as a substitute for - a colorimeter, then the -u flag should be used to avoid - clipping values above the white point. Unless the shaper/matrix type - profile is a very good fit, it is probably advisable to use a LUT - type profile in this situation.
+ a colorimeter, then the -ua flag should be used to force + Absolute Colorimetric intent, and avoid clipping colors above the + test chart white point. Unless the shaper/matrix type profile is a + very good fit, it is probably advisable to use a LUT type profile in + this situation.

To create a matrix/shaper profile, the following suffices:

@@ -1576,7 +1672,7 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t
colprof -v -D"Scanner A" -qm - -ax -u -ax -ua scanner

Make sure you check the delta E report at the end of the profile @@ -1602,7 +1698,7 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t href="colprof.html#p1">scanner


-
+

Profiling Printers

The overall process is to create a set of device measurement target @@ -1902,7 +1998,7 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t component images, if the scanner or camera is capable of doing so; not setting white or black points, using a fixed exposure etc.). It is generally advisable to create a LUT type input profile, and use - the -u + the -ua flag to avoid clipping scanned value whiter than the input calibration chart.

@@ -1962,6 +2058,12 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t + + + + + + @@ -2055,6 +2157,16 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t the most different gamuts, and hence need the most gamut mapping to convert from one colorspace to the other.

+ Note that specifying a very large gamut colorspace as the + source gamut (i.e. ProPhoto etc.) is probably NOT + what you want to do, since unless the source images have a similar + very large gamut to that of the colorspace, they will end up getting + over compressed and come out looking dull. Instead use a source + profile that has a gamut more representative of the images gamut, or + you should provide a gamut using the the -g + + parameter.
+
If you are creating a profile for a specific purpose, intending to link it to a specific input profile, then you will get the best results by specifying that source profile as the source gamut.
@@ -2117,6 +2229,12 @@ then + + + + + + @@ -2264,6 +2382,12 @@ then + + + + + + @@ -2735,6 +2859,12 @@ chart, + + + + + + @@ -2807,6 +2937,12 @@ an + + + + + + @@ -2871,6 +3007,12 @@ an + + + + + + @@ -2943,6 +3085,12 @@ a + + + + + + @@ -3039,7 +3187,7 @@ a represent such a physical quantity.


-
+

Linking Profiles

Two device profiles can be linked together to create a device link profile, than encapsulates a particular device to device transform. @@ -3217,7 +3365,7 @@ a href="collink.html#d">-dmt options, then either leave them out or substitute values that do match your environment.
  -

+

Transforming colorspaces of raster files

Although a device profile or device link profile may be useful with other programs and systems, Argyll provides the tool infile.jpg outfile.jpg


-

+

Creating Video Calibration 3DLuts

Video calibration typically involves trying to make your actual display device emulate an ideal video display, one which matches @@ -3297,6 +3445,12 @@ a + + + + + + madvr" in dispcal, dispread and dispwin. Leave the MadTPG "VideoLUT" and "3dluts" buttons in their default  (enabled) @@ -3359,6 +3513,12 @@ a + + + + + + @@ -3401,6 +3561,12 @@ a + + + + + + @@ -3485,7 +3651,7 @@ a that the Video card has automatically or manually been configured to scale full range RGB values to Video levels for the TV. If the latter is not possible, then use the -E options on dispcal and - dispread. (See Signal encoding bellow for more details on + dispread. (See Signal encoding below for more details on this). It may also improve the accuracy of the display profile if you use the dispread -Z option to quantize the test values to the precision of the display @@ -3893,6 +4059,12 @@ a + + + + + + @@ -3924,6 +4096,12 @@ a + + + + + + @@ -3962,6 +4140,12 @@ a + + + + + + @@ -3993,6 +4177,12 @@ a + + + + + + @@ -4018,7 +4208,7 @@ a the graphics card VideoLUTs in some other fashion.

 -

+

Verifying Video Calibration

Often it is desirable to verify the results of a video calibration and profile, and the following gives an outline of how @@ -4060,7 +4250,7 @@ a options included "-I b:0.2:2.15" then the equivalent fakeread option "-b 0.2:2.15:TV.icm" should be used, etc.

-
+

A sanity check we can make at this point is to see what the expected result of the profiling & calibration will be, by simulating the reproduction of this test set:
@@ -4104,7 +4294,7 @@ a checkA.ti3

-
+

You can explicitly compare the gamuts of your video space and your display using the gamut tools:

@@ -4119,7 +4309,7 @@ a you should use iccgamut -ir instead of -ia, so as to align the white points.

-
+

The main verification check is to actually measure the display response and compare it against the reference. Make sure the display is setup as you would for video playback and then use -- cgit v1.2.3