Before starting the calibration process, you must allow the monitor to warm up for at least 30 minutes, disable any calibration software such as Adobe Gamma in the start-up menu and turn off all anti-virus, screen savers and energy savers on your PC so the screen remains active. Clicking on the Easy mode automates the process and defaults to the native settings for the monitor, operating system and video card without taking account of room lighting or other monitor adjustments. The Advanced mode gives full control over contrast, brightness and individual colour channel settings.
On test, we calibrated a CRT monitor in just five minutes, using the Easy mode. The Advanced mode took more than twice as long, due to the need to adjust monitor settings manually. After Advanced calibration, Eye-One Match displays the specified calibration aim points, along with the aim points actually produced, enabling users to see how close their profile is to the ideal.
It also shows a gamut map of the current display profile. The software also has a reminder which alerts the user after one to four weeks to create a new monitor profile to ensure true and reliable colour over time. For quick and painless calibration and profiling, the Eye-One Display 2 is hard to beat. Eye-One Display can only calibrate one monitor per video card. Information on profiling multi-monitor set-ups can be found at www. A free download of Eye-One Match 3. Being a Windows guy I still use v3. So, you could do that.
Thank you for the expansive answer. Or the GretagMacbeth for that matter. I haven't used the newer model you've updated the question to so I don't know how it compares. Ok, thank you. Sorry for changing the model after your answer, but the seller didn't provide the correct information at first.
Michael C Michael C k 7 7 gold badges silver badges bronze badges. I had to figure out the correct order to install the drivers and different modules of the software first and that was a little confusing. It's been so long but I think I found some help in that regard in an on line discussion board.
Calibrating with an i1Display2
Once I got that straight I've installed it on several other machines without a hitch. The last thing you want to do is plug it in before the drivers and software are correctly installed. In Windows 7 I had to roll back the entire OS to the restore point I created just before my first try at installing it. But once I did everything in the correct order it works. There were some issues with Snow Leopard prior to the Those were reportedly resolved in It was caused by a bug in ColorSync in the early Apple releases prior to The big change in Mountain Lion was that 32 bit apps that required kernel extensions were DOA and it wouldn't surprise me if these were needed given the purpose.
It's not really analogous to Windows in this respect. Create synthetic ICC profiles with custom primaries, white- and blackpoint as well as tone response for use as working spaces or source profiles in device linking 3D LUT transforms. Installer Package If you want to verify the integrity of the downloaded file, compare its SHA checksum to that of the respective entry in the SHA checksum list.
Installer recommended or ZIP archive If you want to verify the integrity of the downloaded file, compare its SHA checksum to that of the respective entry in the SHA checksum list case does not matter. Source Tarball If you want to verify the integrity of the downloaded file, compare its SHA checksum to that of the respective entry in the SHA checksum list. Quickstart guide This short guide intends to get you up and running quickly, but if you run into a problem, please refer to the full prerequisites and installation sections. Connect your measurement device to your computer. That's it! Hardware requirements Minimum: 1 GHz single core processor, 1.
Supported instruments You need one of the supported instruments to make measurements. Additional requirements for using the source code You can skip this section if you downloaded a package, installer, ZIP archive or disk image of DisplayCAL for your operating system and do not want to run from source. Additional requirements for compiling the C extension module Normally you can skip this section as the source code contains pre-compiled versions of the C extension module that DisplayCAL uses.
On Mac OS X before If you're using the official python. Running directly from source After satisfying all additional requirements for using the source code , you can simply run any of the included. One-time setup instructions for source code checked out from SVN: Run python2 setup. Linux package. Windows Installer Launch the installer which will guide you trough the required setup steps.
Prerequisites: You first need to install alien and rpmdb, create a dummy RPM database via sudo rpmdb --initdb , then edit or create from scratch the setup. If you are using Ubuntu This is no longer an issue with py2app 0. Successful MSI creation needs a patched msilib additional information. You can specify the same options as for the install command. The original setup. Useful in combination with the uninstall command to see which files would be removed.
This is actually a switch, use it once and the choice is remembered until you specify the --use-setuptools switch see next paragraph. This is actually a switch, use it once and the choice is remembered until you specify the --use-distutils switch see above. Basic concept of display calibration and profiling If you have previous experience, skip ahead. Usage Through the main window, you can choose your settings. Settings file Here, you can load a preset, or a calibration.
Why has a default gamma of 2. Tabs The main user interface is divided into tabs, with each tab containing a sub-set of settings. Apart from those directly connected displays, a few additional options are also available: Web localhost Starts a standalone web server on your machine, which then allows a local or remote web browser to display the color test patches, e. Prisma The Q, Inc. Resolve Allows you to use the built-in pattern generator of DaVinci Resolve video editing and grading software, which is accessible over the network or on the local machine.
Untethered See untethered display measurements. Choosing a measurement mode Some instruments may support different measurement modes for different types of display devices. Calibration settings Interactive display adjustment Turning this off skips straight to calibration or profiling measurements instead of giving you the opportunity to alter the display's controls first. You will normally want to keep this checked, to be able to use the controls to get closer to the chosen target characteristics. Observer To see this setting, you need to have an instrument that supports spectral readings i.
White point Allows setting the target white point locus to the equivalent of a daylight or black body spectrum of the given temperature in degrees Kelvin, or as chromaticity co-ordinates. Visual whitepoint editor The visual whitepoint editor allows visually adjusting the whitepoint on display devices that lack hardware controls as well as match several displays to one another or a reference.
For table based profiles LUT  , it sets the main lookup table size, and hence quality in the resulting profile. White point If your screen has RGB gain, colortemperature or other whitepoint controls, the first step should be adjusting the whitepoint. Look at the bars shown during the measurements to adjust RGB gains and minimize the delta E to the target whitepoint.
White level Continue with the white level adjustment. If you have set a target white level, you may reduce or increase the brightness of your screen ideally using only the backlight until the desired value is reached i. If you haven't set a target, simply adjust the screen to a visually pleasing brightness that doesn't cause eye strain.
You may reduce or increase the brightness of your screen until the desired black level is reached i. White point The next step should be adjusting the whitepoint, using the display's RGB gain controls or other means of adjusting the whitepoint. If you have set a target white level, you may reduce or increase contrast until the desired value is reached i.
If you haven't set a target, simply adjust the screen to a visually pleasing level that doesn't cause eye strain. Black point If your display has RGB offset controls, you can adjust the black point as well, in much the same way that you adjusted the whitepoint. Select one of the pre-baked testcharts to use as base and bring up the testchart editor.
It should automatically select the previous profile you've chosen. Then place a check in the checkbox. Make sure adaptation is set to a high level e. Create the chart and save it. Start the profiling measurements e. Profile installation When installing a profile after creating or updating it, a startup item to load its calibration curves automatically on login will be created on Windows and Linux, Mac OS X does not need a loader.
Profile loader Windows Under Windows, the profile loader will stay in the taskbar tray and keep the calibration loaded unless started with the --oneshot argument, which will make the loader exit after loading calibration.
A right-click menu allows you to set the desired calibration state and a few other options: Load calibration from current display device profile s. Reset video card gamma table. This periodically checks if the video card gamma tables match the desired calibration state. It may take up to three seconds until the selected calibration state is automatically re-applied.
Fix profile associations automatically when only one display is active in a multi-display setup. This is a work-around for applications and Windows itself querying the display profile in a way that does not take into account the active display, which can lead to a wrong profile being used. A pre-requisite for this working correctly is that the profile loader has to be running before you switch from a multi-display to a single-display configuration in Windows, and the profile associations have to be correct at this point. Note that quitting the profile loader will restore profile associations to what they were honoring any changes to profile associations during its runtime.
Also note that profile associations cannot be fixed and the respective option will be disabled in display configurations with three or more displays where some of them are deactivated. Some graphics drivers may internally quantize the video card gamma table values to a lower bitdepth than the nominal 16 bits per channel that are encoded in the video card gamma table tag of DisplayCAL-generated profiles. If this quantization is done using integer truncating instead of rounding, this may pronounce banding.
In that case, you can let the profile loader quantize to the target bitdepth by using rounding, which may produce a smoother result. You can override the global profile loader state on a per application basis. Profile associations. Brings up a dialog where you can associate profiles to your display devices. Open Windows display settings. If this box is unchecked, you can create a 3D LUT from an existing profile. Predefined settings are Rec. Black output offset To accomodate a non-zero black level of a real display, the tone response curve needs to be offset and scaled accordingly.
A split between input and output offset is also possible. Target peak luminance only available for SMPTE This allows you to adjust the clipping point when not using roll-off or roll-off to the desired target peak luminance. A way to do this is to specify the mastering display black and peak luminance levels. This is achieved by taking into account the ambient luminance as per BT. Note that there is usually no need to change this from the default DCI P3 , and that this setting has most impact on non-colorimetric rendering intents.
Normally, this should always be enabled if the profile contains a non-linear 1D LUT calibration, otherwise you have to make sure the 1D calibration is loaded whenever the 3D LUT is used. Out of gamut colors will be clipped to the closest possible match. The destination whitepoint will be altered to match the source whitepoint if possible, which may get clipped if it is out of gamut.
The destination whitepoint is not altered to match the source whitepoint. As much as possible, clipping is avoided, hues and the overall appearance is maintained. This intent is useful if the destination gamut is smaller than the source gamut. The destination whitepoint is altered to match the source whitepoint. No contrast enhancement is used if the dynamic range is reduced.
This intent may be of use where preserving the tonal distinctions in images is more important than maintaining overall colorfulness or contrast. This intent is useful if you have calibrated a display to a custom whitepoint that you want to keep. Note that in most cases, sensible defaults will be chosen depending on selected 3D LUT format, but may be application- or workflow-specific. Checking the accuracy of a display profile evaluating how well the profile characterizes the display In this case, you want to use a testchart with RGB device values and no simulation profile.
Whitepoint simulation. To explain the latter option: Let's assume a reference has a whitepoint that is slightly blueish compared to D50 , and a display profile has a whitepoint that is more blueish compared to D If you do not choose to simulate the reference white relative to the display profile whitepoint, and the display profile's gamut is large and accurate enough to accomodate the reference white, then that is exactly what you will get.
Depending on the adaptation state of your eyes though, it may be reasonable to assume that you are to a large extent adapted to the display profile whitepoint assuming it is valid for the device , and the simulated whitepoint will look a little yellowish compared to the display profile whitepoint. In this case, choosing to simulate the whitepoint relative to that of the display profile may give you a better visual match e. Whitepoint simulation does not apply here because color management will not be used and the display device is expected to be in the state described by the simulation profile.
This may be accomplished in several ways, for example the display may be calibrated internally or externally, by a 3D LUT or device link profile. This allows you to check how well the 3D LUT transforms the simulation colorspace to the display colorspace. Note this setting can not be used together with a DeviceLink profile. DeviceLink profile. This allows you to check how well the DeviceLink transforms the simulation colorspace to the display colorspace. Tone response curve. To check a display that does not have an associated profile e. How were the nominal and recommended aim values chosen?
How are the results of the profile verification report to be interpreted? Keep all that in mind when admiring or pulling your hair out over verification results : How are profiles evaluated against the measured values? How is a testchart or reference file used?
How is the assumed vs. Resolve Untethered display measurements Please note that the untethered mode should generally only be used if you've exhausted all other options. The procedure is as follows: Select the desired testchart, then open the testchart editor. Burn the images to a DVD, copy them on an USB stick or use any other available means to get them to display onto the device that should be measured. Show the first image on the remote display, and attach the instrument. Choose testchart file Loads a testchart. Edit testchart Choose save path Create profile from measurement data Allows you to re- create a profile from existing measurement data existing profiles created with ArgyllCMS or DisplayCAL can also be selected as source with the current profiling settings.
Create profile from extended display identification data Allows you to create a profile from your display's EDID  if available. Install display device profile Install an existing profile for the currently selected display. Upload profile This will only work for profiles created from actual measurements by DisplayCAL 0. Profile information Show gamut plot, calibration and tone response curves, as well as header and tag information for the current profile.
Locate ArgyllCMS executables Use fancy progress dialog Use a fancy progress dialog with animations and sound while doing measurements and intense processing. Show advanced options Enabling this menu option will show some additional controls and menu options for advanced users. You may be able to calibrate one screen, and then share the calibration with another screen.
Profiling can be done independently to calibration on each screen. Normally DisplayCAL will automatically detect if separate video card gamma table access is needed and appropriate controls need to be displayed , but you may force it by selecting this menu entry. This is not normally the best way to profile a calibrated display, since the frame buffer may have lower precision than the video card gamma table. This is the way calibration should be applied if madVR is being used to display the test patches.
If this option is checked, DisplayCAL will try to skip this sensor calibration. Note even if this option is checked, you may be forced to do a sensor calibration if the instrument requires it. Useful for debugging. Warning: Very verbose. This allows review of the used command line parameters by checking the log.
Allows you to set additional options for the ArgyllCMS dispcal, dispread, spotread, colprof, collink and targen tools in the same way you would specify them on the commandline. Restore defaults Restores all settings except language, selected display, instrument, measurement mode and profile name to default. Detect displays and instruments To detect changes in display setup or connected instruments, use this menu entry. Linux: Install udev rules or hotplug scripts that configure instrument access you only need to install these if you cannot access your instrument.
The Spyder2 instrument cannot function without the presence of the instrument vendors PLD firmware pattern for the device. The purchaser of a Spyder2 instrument should have received a copy of this firmware along with their instrument from the original vendor, as part of the instrument setup files. On Microsoft Windows or Mac OS X, if the vendors software has been installed on the users machine, the firmware pattern can usually automatically be located from there.
If the vendors software have not been installed, or the user does not wish to install it, or no vendors software are available for the users platform i. In case no firmware files are found, the necessary binary can be downloaded automatically. You first need to measure the required test colors with a spectrometer, and in case you want to create a correction matrix instead of a spectral correction, also with the colorimeter. Upload a colorimeter correction to the online Colorimeter Corrections Database to share it with other users or download it later on another machine.
This will use the usual input parameters to establish the expected target characteristic. Note that if the initial calibration was modified due to it being out of gamut of the display, verify will show the resulting discrepancy. Measure the display at several points to evaluate evenness of illumination and color errors. The results are shown after all patches are measured, and include the luminance differences as well as delta E color differences, which are computed in comparison to the reference center point.
i1 Display 2 and i1 Display LT supported for Mac OS Lion
The evaluation is done according to ISO and , or by comparing the average luminance deviation and delta C, and you can switch between both criteria on-the-fly within the report itself. It's a handy way to get new or changed comparison features, updated layout and even bugfixes into old reports. A backup copy of the old report with a date extension will automatically be created. Show actual calibration curves from video card When this is enabled in the curve viewer window, it will show the actual calibration curves from the video card gamma table instead of showing the curves of the currently active profile.
Show log window automatically Shows the log window automatically after actions like measurements or creating a profile. This checks a measurement file for suspicious erroneous readings. An sRGB-like display is assumed, so this option will not work well if the display response is not so close to sRGB, and may report false positives. Non-UI functionality There is a bit of functionality that is not available via the UI and needs to be run from a command prompt or ternminal.
Change display profile and calibration whitepoint Note that this reduces the profile gamut and accuracy. The changed profile will be written to this file. Scripting DisplayCAL supports scripting locally and over the network the latter must be explicitly enabled by setting app. If a modal dialog is displayed, choose the OK option. Note that this is just an example and normally you should be very careful with this, as it could mean confirming a potentially destructive operation e.
List of supported commands Below is a list of the currently supported commands the list contains all valid commands for the main application, the standalone tools will typically just support a smaller subset. If it is minimized, restore it. If a file dialog is shown, using ok filename chooses that file. For non-virtual displays as well as pattern generators except madVR , call the measure command afterwards to commence measurements.
Note that this tries to abort any running operations first, so you may want to check application state via the getstate command. Relative paths are possible e. Optionally, load filename.
The returned format is classname ID name label state. Return value will be either idle , busy , dialogclassname ID dialogname [dialoglabel] state "messagetext" [path "path"] [buttons "buttonlabel" Most commands will not work if the UI is blocked—the only way to resolve the block is to non-programmatically interact with the actual UI elements of the application or closing it. Note that a state of blocked should normally only occur if an actual file dialog is shown. If using the scripting interface exclusively, this should never happen because it uses a replacement file dialog that supports the same actions as a real file dialog, but doesn't block.
Also note that a return value of blocked for any of the other commands just means that a modal dialog is currently waiting to be interacted with, only if getstate also returns blocked you cannot resolve the situation with scripting alone. Each returned line represents an UI element and has the format classname ID name ["label"] state [checked] [value "value"] [items "item" It can help you determine what type of UI element it is, and which interactions it supports.
ID is a numeric identifier.