Argyll Usage Scenarios

In some situation there is no access to a displays VideoLUT - hardware, and this hardware is what is usually used to implement - display calibration. This could be because the display is being - accessed via a web server, or because the driver or windowing - system doesn't support VideoLUT access.
-

1) Don't attempt to calibrate, just profile the display.
- 2) Calibrate, but incorporate the calibration in some other - way in the workflow.
-

2a) Use dispcal to create a calibration and a quick profile - that incorporates the calibration into the profile.
- 2b) Use dispcal to create the calibration, then dispread and - colprof to create a profile, and then incorporate the calibration - into the profile using applycal.
- 2c) Use dispcal to create the calibration, then dispread and - colprof to create a profile, and then apply the calibration after - the profile in a cctiff workflow.
-

The first case requires nothing special, use dispcal in a normal - fashioned with the -o - option to generate a quick profile.The profile created will not contain a 'vcgt' - tag, but instead will have the calibration curves incorporated - into the profile itself. If calibration parameters are chosen that - change the displays white point or brightness, then this will - result in a slightly unusual profile that has a white point that - does not correspond with device R=G=B=1.0. Some systems may not - cope properly with this type of profile, and a general shift in - white point through such a profile can create an odd looking - display if it is applied to images but not to other elements on - the display say as GUI decoration elements or other application - windows.
-

In the second case, the calibration file created using dispcal - should be provided to dispread using the -K flag:
-

Create the profile as - usual using colprof. but note that colprof will ignore the - calibration, and that no 'vcgt' tag will be added to the profile.
- You can then use applycal to combine - the calibration into the profile. Note that the resulting profile - will be slightly unusual, since the profile is not made completely - consistent with the effects of the calibration, and the device - R=G=B=1.0 probably not longer corresponds with the PCS white or - the white point.
-

Profiling Scanners and other input devices - such as cameras
-

Types of test charts

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

In some situation there is no access to a displays VideoLUT + hardware, and this hardware is what is usually used to implement + display calibration. This could be because the display is being + accessed via a web server, or because the driver or windowing + system doesn't support VideoLUT access.
+

1) Don't attempt to calibrate, just profile the display.
+ 2) Calibrate, but incorporate the calibration in some other + way in the workflow.
+

2a) Use dispcal to create a calibration and a quick profile + that incorporates the calibration into the profile.
+ 2b) Use dispcal to create the calibration, then dispread and + colprof to create a profile, and then incorporate the calibration + into the profile using applycal.
+ 2c) Use dispcal to create the calibration, then dispread and + colprof to create a profile, and then apply the calibration after + the profile in a cctiff workflow.
+

The first case requires nothing special, use dispcal in a normal + fashioned with the -o + option to generate a quick profile.The profile created will not contain a 'vcgt' + tag, but instead will have the calibration curves incorporated + into the profile itself. If calibration parameters are chosen that + change the displays white point or brightness, then this will + result in a slightly unusual profile that has a white point that + does not correspond with device R=G=B=1.0. Some systems may not + cope properly with this type of profile, and a general shift in + white point through such a profile can create an odd looking + display if it is applied to images but not to other elements on + the display say as GUI decoration elements or other application + windows.
+

In the second case, the calibration file created using dispcal + should be provided to dispread using the -K flag:
+

Create the profile as + usual using colprof. but note that colprof will ignore the + calibration, and that no 'vcgt' tag will be added to the profile.
+ You can then use applycal to combine + the calibration into the profile. Note that the resulting profile + will be slightly unusual, since the profile is not made completely + consistent with the effects of the calibration, and the device + R=G=B=1.0 probably not longer corresponds with the PCS white or + the white point.
+

Profiling Scanners and other input devices + such as cameras
+

Types of test charts

Taking readings from a scanner or camera
-

For an IT8.7/2 chart, this is the ref/it8.cht file - supplied with Argyll, and the manufacturer will will supply - an individual or batch average file along with the chart - containing this information, or downloadable from their web site. - For instance, Kodak Q60 target reference files are here.
- NOTE that the reference file for the IT8.7/2 chart supplied with Monaco EZcolor can be - obtained by unzipping the .mrf file. (You may have to make a copy - of the file with a .zip extension to do this.)
-
- For the ColorChecker 24 patch chart, the ref/ColorChecker.cht file - should be used, and there is also a ref/ColorChecker.cie file provided that is based - on the manufacturers reference values for the chart. You can also - create your own reference file using an instrument and chartread, - making use of the chart reference file ref/ColorChecker.ti2:
- chartread -n - ColorChecker.ti2
- Note that due to the small number of patches, a profile created - from such a chart is not likely to be very detailed.
-
- For the ColorChecker DC chart, the ref/ColorCheckerDC.cht file should be used, and - there will be a ColorCheckerDC reference file supplied by - X-Rite/GretagMacbeth with the chart.
-
- The ColorChecker SG is relatively expensive, but is preferred by - many people because (like the ColorChecker and ColorCheckerDC) its - colors are composed of multiple different pigments, giving it - reflective spectra that are more representative of the real world, - unlike many other charts that are created out of combination of 3 - or 4 colorants.
- A limited CIE reference file is available from X-Rite here, - but it is not in the usual CGATS format. To convert it to a CIE - reference file useful for scanin, - you will need to edit the X-Rite file using a plain text editor, - first deleting everything before the line starting with "A1" and + + + + 202:
+
+ QPCard201

+
+

Taking readings from a scanner or camera
+

+ The test chart you are using needs to be placed on the scanner, and + the scanner needs to be configured to a suitable state, and restored + to that same state when used subsequently with the resulting + profile. For a camera, the chart needs to be lit in a controlled and + even manner using the light source that will be used for subsequent + photographs, and should be shot so as to minimise any geometric + distortion, although the scanin -p flag + may be used to compensate for some degree of distortion. As with any + color profiling task, it is important to setup a known and + repeatable image processing flow, to ensure that the resulting + profile will be usable.
+
+ The chart should be captured and saved to a TIFF format file. I will + assume the resulting file is called scanner.tif. The raster file + need only be roughly cropped so as to contain the test chart + (including the charts edges).
+
+ The second step is to extract the RGB values from the scanner.tif + file, and match then to the reference CIE values. To locate the + patch values in the scan, the scanin tool needs to be given + a template .cht file that + describes the features of the chart, and how the test patches are + labeled. Also needed is a file containing the CIE values for each of + the patches in the chart, which is typically supplied with the + chart, available from the manufacturers web site, or has been + measured using a spectrometer.
+
+

For an IT8.7/2 chart, this is the ref/it8.cht file + supplied with Argyll, and the manufacturer will will supply + an individual or batch average file along with the chart + containing this information, or downloadable from their web site. + For instance, Kodak Q60 target reference files are here.
+ NOTE that the reference file for the IT8.7/2 chart supplied with Monaco EZcolor can be + obtained by unzipping the .mrf file. (You may have to make a copy + of the file with a .zip extension to do this.)
+
+ For the ColorChecker 24 patch chart, the ref/ColorChecker.cht file + should be used, and there is also a ref/ColorChecker.cie file provided that is based + on the manufacturers reference values for the chart. You can also + create your own reference file using an instrument and chartread, + making use of the chart reference file ref/ColorChecker.ti2:
+    chartread -n + ColorChecker.ti2
+ Note that due to the small number of patches, a profile created + from such a chart is not likely to be very detailed.
+
+ For the ColorChecker DC chart, the ref/ColorCheckerDC.cht file should be used, and + there will be a ColorCheckerDC reference file supplied by + X-Rite/GretagMacbeth with the chart.
+
+ The ColorChecker SG is relatively expensive, but is preferred by + many people because (like the ColorChecker and ColorCheckerDC) its + colors are composed of multiple different pigments, giving it + reflective spectra that are more representative of the real world, + unlike many other charts that are created out of combination of 3 + or 4 colorants.
+ A limited CIE reference file is available from X-Rite here, + but it is not in the usual CGATS format. To convert it to a CIE + reference file useful for scanin, + you will need to edit the X-Rite file using a plain text editor, + first deleting everything before the line starting with "A1" and everything after "N10", then prepending this @@ -1308,92 +1347,108 @@ href="http://www.xrite.com/documents/apps/public/digital_colorchecker_sg_l_a_b.t - header, and appending this footer, - making sure there are no blank lines inserted in the process. - There are reports that X-Rite have experimented with different ink - formulations for certain patches, so the above reference may not - be as accurate as desired, and it is preferable to measure your - own chart using a spectrometer, if you have the capability.
- If you do happen to have access to a more comprehensive instrument - measurement of the ColorChecker SG, or you have measured it - yourself using a color instrument,
- then you may - need to convert the reference information from spectral ColorCheckerSG.txt file to CIE - value ColorCheckerSG.cie - reference file, follow the following steps:
-      txt2ti3 - ColorCheckerSG.txt ColorCheckerSG
-      spec2cie - ColorCheckerSG.ti3 ColorCheckerSG.cie
-
- 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 - accompanying this chart, the chart needs to be read with an - instrument (usually the Eye-One Pro). This can be done using - chartread, making use of the chart reference file ref/i1_RGB_Scan_1.4.ti2:
-     chartread -n - i1_RGB_Scan_1.4
- and then rename the resulting i1_RGB_Scan_1.4.ti3 - file to i1_RGB_Scan_1.4.cie
-
- For the HutchColor HCT chart, the ref/Hutchcolor.cht - file should be used, and the reference .txt file downloaded from the HutchColor website.
-
- For the Christophe Métairie's Digital TargeT 003 chart with 285 - patches, the ref/CMP_DT_003.cht - file should be used, and the cie reference files come with the chart.
-
- For the Christophe Métairie's Digital Target-4 chart with 570 - patches, the ref/CMP_Digital_Target-4.cht - file should be used, and the cie reference files come with the chart.
-
- For the LaserSoft DCPro chart, the ref/LaserSoftDCPro.cht file should be used, and - reference .txt file - downloaded from the Silverfast - website.
-
- For the Datacolor SpyderCheckr, the ref/SpyderChecker.cht file should be used, and a - reference ref/SpyderChecker.cie - file made from measuring a sample chart is also available. - Alternately you could create your own reference file by - transcribing the values - on the Datacolor website.
-
- For the Datacolor SpyderCheckr, the ref/SpyderChecker24.cht file should be used, and a + + + + header, and appending this footer, + making sure there are no blank lines inserted in the process. Name + the resulting file ColorCheckerSG.cie.
+ There are reports that X-Rite have experimented with different ink + formulations for certain patches, so the above reference may not + be as accurate as desired, and it is preferable to measure your + own chart using a spectrometer, if you have the capability.
+ If you do happen to have access to a more comprehensive instrument + measurement of the ColorChecker SG, or you have measured it + yourself using chart reading software other than ArgyllCMS, then + you may need to + convert the reference information from spectral only ColorCheckerSG.txt file to CIE + value ColorCheckerSG.cie + reference file, follow the following steps:
+      txt2ti3 + ColorCheckerSG.txt ColorCheckerSG
+      spec2cie + ColorCheckerSG.ti3 ColorCheckerSG.cie
+
+ 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 + accompanying this chart, the chart needs to be read with an + instrument (usually the Eye-One Pro). This can be done using + chartread, making use of the chart reference file ref/i1_RGB_Scan_1.4.ti2:
+     chartread -n + i1_RGB_Scan_1.4
+ and then rename the resulting i1_RGB_Scan_1.4.ti3 + file to i1_RGB_Scan_1.4.cie
+
+ For the HutchColor HCT chart, the ref/Hutchcolor.cht + file should be used, and the reference .txt file downloaded from the HutchColor website.
+
+ For the Christophe Métairie's Digital TargeT 003 chart with 285 + patches, the ref/CMP_DT_003.cht + file should be used, and the cie reference files come with the chart.
+
+ For the Christophe Métairie's Digital Target-4 chart with 570 + patches, the ref/CMP_Digital_Target-4.cht + file should be used, and the cie reference files come with the chart.
+
+ For the Christophe Métairie's Digital Target-7 chart with 570 + patches, the ref/CMP_Digital_Target-7.cht + file should be used, and the spectral .txt file should be + converted to a cie reference file:
+     txt2ti3 + DT7_XXXXX_Spectral.txt temp
+     spec2cie temp.ti3 + DT7_XXXXX.cie
+
+ For the LaserSoft DCPro chart, the ref/LaserSoftDCPro.cht file should be used, and + reference .txt file + downloaded from the Silverfast + website.
+
+ For the Datacolor SpyderCheckr, the ref/SpyderChecker.cht file should be used, and a + reference ref/SpyderChecker.cie + file made from measuring a sample chart is also available. + Alternately you could create your own reference file by + transcribing the values + on the Datacolor website.
+
+ For the Datacolor SpyderCheckr, the ref/SpyderChecker24.cht file should be used, and a reference ref/SpyderChecker24.cie - file made from measuring a sample chart is also available. - Alternately you could create your own reference file by - transcribing the values - on the Datacolor website.
-
- For the QPCard 201, the ref/QPcard_201.cht - file should be used, and a reference ref/QPcard_201.cie file made from measuring a - sample chart is also available.
-
- For the QPCard 202, the ref/QPcard_202.cht - file should be used, and a reference ref/QPcard_202.cie file made from measuring a - sample chart is also available.
-

-
- For any other type of chart, a chart recognition template file will - need to be created (this is beyond the scope of the current + + + + file made from measuring a sample chart is also available. + Alternately you could create your own reference file by + transcribing the values + on the Datacolor website.
+
+ For the QPCard 201, the ref/QPcard_201.cht + file should be used, and a reference ref/QPcard_201.cie file made from measuring a + sample chart is also available.
+
+ For the QPCard 202, the ref/QPcard_202.cht + file should be used, and a reference ref/QPcard_202.cie file made from measuring a + sample chart is also available.
+

Creating a scanner or camera input profile

Profiling Printers
-

Creating a print profile test chart

Printing a print profile test chart
-
-

Reading a print test chart using an instrument

Reading a print test chart using a scanner or - camera
-

Creating a scanner or camera input profile

Profiling Printers
+

Creating a print profile test chart

Printing a print profile test chart
+
+

Reading a print test chart using an instrument

Reading a print test chart using a scanner or + camera
+

Creating a printer profile
-

Creating a printer profile
+

Choosing a black generation curve (and other - CMYK printer options)
-

Choosing a black generation curve (and other + CMYK printer options)
+

Overriding the ink limit
-

Calibrating Printers
-

Calibrated print workflows

Creating a print calibration test chart

Creating a printer calibration
-

Using a printer calibration

Overriding the ink limit
+

Calibrating Printers
+

Calibrated print workflows

Creating a print calibration test chart

Creating a printer calibration
+

Using a printer calibration

How profile ink limits are handled when - calibration is being used.

Linking Profiles

Image dependent gamut mapping using device - links
-

Soft Proofing Link

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

1) How to display test patches.
-

How profile ink limits are handled when + calibration is being used.

Linking Profiles

Image dependent gamut mapping using device + links
+

Soft Proofing Link

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

1) How to display test patches.
+

2) White point calibration & neutral axis calibration.

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 - to use ArgyllCMS tools to do this. It is only possible to expect - perfect verification if a colorimetric intent was used during - linking - currently it's not possible to exactly verify a - perceptual or CIECAM02 viewing condition adjusted link.
-
-

The first step is to create a set of test points. This is - essentially the same as creating a set of test points for the - purposes of profiling, although it is best not to create exactly - the same set, so as to explore the colorspace at different - locatioins. For the purposes here, we'll actually create a regular - grid test set, since this makes it easier to visualize the - results, although a less regular set would probably be better for - numerical evaluation:
-

We make sure there is at least one white patch usin g -e1, a 20% - increment grid using -m6, no full spread patches, and create an - X3DOM 3d visualization of the point set using the -W flag. It is - good to take a look at the verifyd.x3d.html file using a Web - browser. You may want to create several test sets that look at - particular aspects, ie. neutral axis response, pure colorant - responses, etc.
-

Next we create a reference file by simulating the expected - response of the perfect video display system. Assuming the collink - options were "-et -Et -Ib -G -ir Rec709.icm TV.icm HD.icm" then we - would:-

You should adjust the parameters as necessary, so that the - reference matches the link options. For instance, if your link - 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:
-

If you used collink -a, then the calibration incorporated in the - device link needs to be undone to match what the display profile - expects:

If you have targeted some other white point rather than video D65 - for the display, then use the -N flag instead of -n to align the - white points. [ Note that there can be some small discrepancies in - this case in some parts of the color space if a CIECAM02 linking - intent was used, due to the slightly different chromatic - adaptation algorithm it uses compared to the one used by verify to - match the white points.]-

This will give a numerical report of the delta E's, and also - generate an X3DOM plot of the errors in L*a*b* space. The - important thing is to take a look at the checkA.x3d.html file, to - see if gamut clipping is occurring - this is the case if the large - error vectors are on the sides or top of the gamut. Note that the - perfect cube device space values become a rather distorted cube - like shape in the perceptual L*a*b* space. If the vectors are - small in the bulk of the space, then this indicates that the link - is likely to be doing the right thing in making the display - emulate the video colorspace with a BT.1886 like black point - adjustment. You could also check just the in gamut test points - using:
-

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

iccgamut -ff -ia Rec709- iccgamut -ff -ia TV.icm- viewgam -i Rec709.gam TV.gam gamuts
-

and look at the gamuts.x3d.html file, as well as taking notice of - % of the video volume that the display intersects. The X3DOM solid - volume will be the video gamut, while the wire frame is the - display gamut. If you are not targetting D65 with your display, - 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 - dispread:
-

You would add any other options needed (such as -y etc.) - to set your instrument up properly. If you are using madTPG, then - configure madVR to use the 3dLut you want to measure as the - default, and also use the dispread -V flag to make sure that the - 3dLut is being used for the measurements: [Note that if the - version of MadVR you are using does not have radio buttons in its - calibration setup to indicate a default 3dLut, then the 3dLut - under test should be the only one set - all others should be - blank. ]
-

If your display does not cover the full gamut of your video - source, the errors are probably dominated by out of gamut colors. - You can verify just the in gamut test values by asking verify to - skip them, and this will give a better notion of the actual device - link and calibration accuracy:-

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 + to use ArgyllCMS tools to do this. It is only possible to expect + perfect verification if a colorimetric intent was used during + linking - currently it's not possible to exactly verify a + perceptual or CIECAM02 viewing condition adjusted link.
+
+

The first step is to create a set of test points. This is + essentially the same as creating a set of test points for the + purposes of profiling, although it is best not to create exactly + the same set, so as to explore the colorspace at different + locatioins. For the purposes here, we'll actually create a regular + grid test set, since this makes it easier to visualize the + results, although a less regular set would probably be better for + numerical evaluation:
+

We make sure there is at least one white patch usin g -e1, a 20% + increment grid using -m6, no full spread patches, and create an + X3DOM 3d visualization of the point set using the -W flag. It is + good to take a look at the verifyd.x3d.html file using a Web + browser. You may want to create several test sets that look at + particular aspects, ie. neutral axis response, pure colorant + responses, etc.
+

Next we create a reference file by simulating the expected + response of the perfect video display system. Assuming the collink + options were "-et -Et -Ib -G -ir Rec709.icm TV.icm HD.icm" then we + would:+

You should adjust the parameters as necessary, so that the + reference matches the link options. For instance, if your link + 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:
+

If you used collink -a, then the calibration incorporated in the + device link needs to be undone to match what the display profile + expects:

If you have targeted some other white point rather than video D65 + for the display, then use the -N flag instead of -n to align the + white points. [ Note that there can be some small discrepancies in + this case in some parts of the color space if a CIECAM02 linking + intent was used, due to the slightly different chromatic + adaptation algorithm it uses compared to the one used by verify to + match the white points.]+

This will give a numerical report of the delta E's, and also + generate an X3DOM plot of the errors in L*a*b* space. The + important thing is to take a look at the checkA.x3d.html file, to + see if gamut clipping is occurring - this is the case if the large + error vectors are on the sides or top of the gamut. Note that the + perfect cube device space values become a rather distorted cube + like shape in the perceptual L*a*b* space. If the vectors are + small in the bulk of the space, then this indicates that the link + is likely to be doing the right thing in making the display + emulate the video colorspace with a BT.1886 like black point + adjustment. You could also check just the in gamut test points + using:
+

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

iccgamut -ff -ia Rec709+ iccgamut -ff -ia TV.icm+ viewgam -i Rec709.gam TV.gam gamuts
+

and look at the gamuts.x3d.html file, as well as taking notice of + % of the video volume that the display intersects. The X3DOM solid + volume will be the video gamut, while the wire frame is the + display gamut. If you are not targetting D65 with your display, + 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 + dispread:
+

You would add any other options needed (such as -y etc.) + to set your instrument up properly. If you are using madTPG, then + configure madVR to use the 3dLut you want to measure as the + default, and also use the dispread -V flag to make sure that the + 3dLut is being used for the measurements: [Note that if the + version of MadVR you are using does not have radio buttons in its + calibration setup to indicate a default 3dLut, then the 3dLut + under test should be the only one set - all others should be + blank. ]
+

If your display does not cover the full gamut of your video + source, the errors are probably dominated by out of gamut colors. + You can verify just the in gamut test values by asking verify to + skip them, and this will give a better notion of the actual device + link and calibration accuracy:+

Typical usage Scenarios and Examples

- Profiling Scanners and other input devices such as - cameras -

- Profiling Printers

Profiling Displays

Checking you can access your display -

Typical usage Scenarios and Examples

+ Profiling Scanners and other input devices such as + cameras +

+ Profiling Printers

Profiling Displays

Checking you can access your display +

Adjusting and Calibrating Displays

Adjusting and Calibrating Displays

Adjusting, calibrating and profiling in one - step.

Profiling in several steps: Creating display - test values

Profiling in several steps: Taking readings - from a display

Profiling in several steps: Creating a display - profile

Installing a display profile

Expert tips when measuring displays: -

Adjusting, calibrating and profiling in one + step.

Profiling in several steps: Creating display + test values

Profiling in several steps: Taking readings + from a display

Profiling in several steps: Creating a display + profile

Installing a display profile

Expert tips when measuring displays: +

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

Profiling Scanners and other input devices - such as cameras -

Types of test charts

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

Profiling Scanners and other input devices + such as cameras +

Types of test charts

Taking readings from a scanner or camera -

Taking readings from a scanner or camera +

Creating a scanner or camera input profile

Profiling Printers -

Creating a print profile test chart

Printing a print profile test chart - -

Reading a print test chart using an instrument

Reading a print test chart using a scanner or - camera -

Creating a scanner or camera input profile

Profiling Printers +

Creating a print profile test chart

Printing a print profile test chart + +

Reading a print test chart using an instrument

Reading a print test chart using a scanner or + camera +

Creating a printer profile -

Creating a printer profile +

Choosing a black generation curve (and other - CMYK printer options) -

Choosing a black generation curve (and other + CMYK printer options) +

Overriding the ink limit -

Calibrating Printers -

Calibrated print workflows

Creating a print calibration test chart

Creating a printer calibration -

Using a printer calibration

Overriding the ink limit +

Calibrating Printers +

Calibrated print workflows

Creating a print calibration test chart

Creating a printer calibration +

Using a printer calibration

How profile ink limits are handled when - calibration is being used.

Linking Profiles

Image dependent gamut mapping using device - links -

Soft Proofing Link

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

1) How to display test patches. -

How profile ink limits are handled when + calibration is being used.

Linking Profiles

Image dependent gamut mapping using device + links +

Soft Proofing Link

Transforming colorspaces of raster files

Creating Video Calibration 3DLuts

1) How to display test patches. +

2) White point calibration & neutral axis calibration.

2) White point calibration & neutral axis calibration.

4) Output device calibration and profiling.

5) Target colorspace -

6) Signal encoding

7) Black point mapping

- Profiling Scanners and other input devices such as - cameras
-

Checking you can access your display
-

+ Profiling Scanners and other input devices such as + cameras
+

Checking you can access your display
+

Expert tips when measuring displays:
-

Expert tips when measuring displays:
+

Profiling Scanners and other input devices - such as cameras
-

Profiling Scanners and other input devices + such as cameras
+

Taking readings from a scanner or camera
-

Taking readings from a scanner or camera
+

Profiling Printers
-

Printing a print profile test chart
-
-

Reading a print test chart using a scanner or - camera
-

Profiling Printers
+

Printing a print profile test chart
+
+

Reading a print test chart using a scanner or + camera
+

Creating a printer profile
-

Creating a printer profile
+

Choosing a black generation curve (and other - CMYK printer options)
-

Choosing a black generation curve (and other + CMYK printer options)
+

Overriding the ink limit
-

Calibrating Printers
-

Creating a printer calibration
-

Overriding the ink limit
+

Calibrating Printers
+

Creating a printer calibration
+

Image dependent gamut mapping using device - links
-

1) How to display test patches.
-

Image dependent gamut mapping using device + links
+

1) How to display test patches.
+

5) Target colorspace
-

5) Target colorspace
+