<qt>

## A Quick Start Guide to Monitor Profiling with littlecms

#### Overview

Author's note, the littlecms profilers are no longer directly available from littecms, nor are they supported by the littlecms author. Some distros do have them in package form, as well as source mirrors. Google is your friend. However, nothing else on Linux is capable of the profile creation so easily as the profile construction tools. They are worth tracking down in rpm or other package form.

One of the best tools with littlecms is the profile construction tools. . There are five separate tools included in the package:

- A monitor profiler
- A scanner profiler
- A measurement tool
- A profile checker
- A utility ICC2IT8 for working with IT8 targets which are used for profiling scanners

Here, we are going to focus on creation a monitor profile with qtmonitorprofiler. Without some sort of accurate monitor profiler, you will find it difficult to obtain good results from the other tools. Before starting, you need to find if possible, your monitor manual or a spec sheet from your vendor's website. In addition, you might wish to locate the factory ICC profile, which we will use for comparison purposes later on.

#### Installation

It is simple to untar and simply type `make` in the source directory. This will build all five tools and leave the executables in the root source directory. If you are fussy like me, you can go in an hand edit the make files to taste. There is an option to compile this as a KDE application, but if KDE is in a non standard location, it will not compile in this manner. There is also available a patch availabe which enables correct compiling on Qt 3.x. Note: lprof as the package of tools is known is now a separate project. See: http://lprof.sourceforge.net

#### Preparation

First steps:

- You should have your monitor on for at least a half hour to stabilize the temperature.
- In addition, for optimum results, set your desktop to a neutral gray background without any bitmaps or images. This is one of those times, when all that beautiful eye candy on Xfree is definitely not helpful. The switch to a gray desktop, helps to prevent your eyes from being being fooled by a lack of balance in the colors. My desktop is usually a darkish blue, but for color critical work - back to boring gray.
- Configure, if possible, your monitor's color temperature to 6500k through the on-screen controls. Your monitor manual should have directions to set this for your individual monitor.

Explanation: This step, helps to get your monitor to display with a closer match to the standards which are used in color measurement. Typically, most monitors are set at the factory to 9300k, which is too "cold" or bluish to depict colors in a balanced manner. After changing your monitor temperature to 6500k, you might think it has a yellowish cast, but walk away for a few minutes and return. Your eyes will adjust.

Next, set monitor contrast to nearly 100%. Then you want to use the brightness controls to adjust the brightness, so you can see the following, so that each of the shades of gray is distinct. KDE 3.3+ now ships with Kgamma, which is in the KDE Control Center. This is equally useful for your setup.

#### Using qtmonitorprofiler

The first tab will bring up the panel. Check: "I want build a coarse monitor profile."

Then switch to one the below:

Now that we have switched the monitor temperature to 6500K, set the same in the white point drop down list. Unless you know there is a specific reason to over ride the default sRGB, leave this as is. You do not need to name the profile as indicated just yet. Knowledgeable folks in India indicate 7500K is a more common setting for that area.

Next adjust the slider to adjust the gamma so the two shades of gray blend together with the closest color match possible. Most IBM compatible PC's have a gamma setting between 2.1 and 2.4. Macs are generally 1.8. This the reason it is common to find images on edited on a PC looking darker on a Mac. If you monitor is older, it might have a slight color cast and you can try adjusting the individual color channel settings. Don't overdo it. Slight subtle adjustments are better.

Next go to the Profile Identification tab. Add some additional info as shown below:

#### Using the monitor profile in Scribus

Next, go back to the main page, name your profile. You might want to name the profile something like: `/home/peter/d650023.icm` This gives you a quick reference to what the profile means. In this case, d= daylight 6500=the monitor is set to 6500k 23=gamma setting of 2.3. If you have colored walls or large windows, you might want to create two monitor profiles: One for daylight and a second one, when you have indoor lighting on during the night. The difference is subtle, but is noticeable. for this preliminary profile, you can leave the Parameters and Tweaking tab alone. The default is set to the icc default specs.

The last step is to click go and the profiler will create the icm file. This takes but a second or two. Now you can close the profiler for now.

Then, copy the profile to the Scribus profiles directory from a console to $home/.color/icc : `# cp ./d650023.icm $home/.color/icc` This is one the default directories Scribus will search for profiles.

Now Scribus can use this profile for more accurately managing screen previews. Start or restart Scribus and go Settings > Color Management. Enable color management and select the monitor profile as below:

By setting this monitor profile to be the default, you have enhanced the accuracy of your screen previews. You can selectively enable the gamut checking in your previews, but this is not quite perfected in littlecms. This is not a weakness in littlecms nor Scribus, but a limitation of the current icc specs. When enabling this consider the preview a warning - not definitive. The true test is what actually will print.

You can also use this profile to enhance the previews in Cinepaint, GIMP or other image editing programs which are color management savvy. Monitor colors and brightness vary over time, so re-profiling at least once every couple of months is a good idea. In professional settings, sometimes they are re-profiled every week.

Note: The latest beta profilers from littlecms adds new features, including support for profiling digital cameras and additional enhancements. However, it is a Windows only program. Fortunately, it includes the updated lcms 1.14 and it installs and runs fine under any recent version of Wine.

</qt>