dispcalGUI Display Calibration powered by Argyll CMS and Python

About

dispcalGUI is a GUI frontend for several utilities from the open source color management system Argyll CMS by Graeme Gill, specifically dispcal, dispread, colprof and dispwin, which when used together allow you to calibrate and profile your display using a measurement device. Of course, you can do a lot more with Argyll CMS, but this is not the scope of this document—refer to the Argyll CMS documentation for in-depth information and usage scenarios.
dispcalGUI opens two windows when run, a terminal and the GUI. The terminal is used for status messages and keyboard input during calibration. The GUI is used to set options and access functionality.

Disclaimer

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

dispcalGUI is written in Python and uses the 3rd-party packages appscript (AppleScript library, only on Mac OS X), demjson (JSON library) and wxPython (GUI toolkit). It also makes extensive use of several Argyll CMS utilities. The build system to create standalone executables additionally uses setuptools on all platforms, bbfreeze on Linux/Windows, py2app on Mac OS X, py2exe on Windows, or an included, modified version of pyinstaller trunk on Linux/Windows (see pyinstaller/README1ST.txt for a list of changes to the stock version). All of these software packages are © by their respective authors.

Download

Linux Autopackage

Universal install that should work on a multitude of distributions.

Autopackage (Python 2.5 and 2.6, x86 and x86_64)

Stand-alone executable

This is what you should get if you don't have Python installed or cannot satisfy all prerequisites. Linux users should preferably get the Autopackage install instead, unless they want to run dispcalGUI on a system where they can't install software, or from removable media (like an USB stick).

Linux (x86) Tarball
Mac OS X DMG
Windows Installer | ZIP

Source code

This is what you need to compile from source. You need to have a working Python installation and all prerequisites.

All platforms Tarball

Alternatively, if you don't mind trying out development code, browse the SVN repository of the latest development version (or do a full checkout using svn co https://dispcalgui.svn.sourceforge.net/svnroot/dispcalgui dispcalGUI). But please note that the code is in constant flow, things may break from one hour to the other. Use at your own risk.

Quick setup guide

This short guide intends to get you up and running quickly, but if you run into a problem, you should refer to the full Prerequisites and Installation sections.

1. Get and install the latest release of dispcalGUI. It is recommended to first remove all previous versions.
2. Download and unpack the Argyll CMS archive file: Linux | Mac OS | Windows. Put the extracted directory (Argyll_VX.X.X) in a convenient place on your harddisk.
   If you want to use the HCFR colorimeter on Mac OS X: Follow the instructions under Installing Argyll CMS on Mac OS X to enable it.
3. Launch dispcalGUI. If it cannot determine the path to the Argyll CMS binaries, it will prompt you to select the location manually on first launch.
   If your measurement device is a Spyder 2: Choose “Enable Spyder 2 colorimeter...” from dispcalGUI's “Extra” menu, insert the driver CD that came with the instrument and select the setup executable to enable it.
4. Connect your measurement device to your computer.
   Driver installation - Windows only: If you already have drivers for your measurement device installed, read “Adding Argyll drivers to existing drivers” or “Updating Argyll drivers” in Installing Argyll CMS on Microsoft Windows. If this is a fresh install, a “Found new hardware” dialog should appear:

   • Under Vista...
     • Select “Locate and install driver software (recommended)”.
     • If a “User Account Control” window pops up, select “Continue”.
     • Select “Don't search online”.
     • Select “I don't have the disc, show me other options”.
     • Select “Browse my computer for driver software (advanced)”.
   • Under XP...
     • In the window “Can Windows connect to Windows Update to search for software?” select “No, not this time” and “Next”.
     • Select “Install from a list or specific location (advanced)” then “Next”.
     • Select “Search for the best driver in these locations”, “Include this location in the search” and “Browse...”.
   • Under 2000...
     • Select “Next”, then “Search for a suitable driver for my device (recommended)”, and “Next” again.
     • Tick the “Specify a location” box, then select “Next”.
     • In the window “Insert the manufacturer's installation disk” select “Browse...”.
   • Locate the “argyll\libusbw” subdirectory in your Argyll_VX.X.X directory (under Windows 2000, you also need to select the .inf file that corresponds to your device, then select “Open” and “OK”). Select “Next”.
   • Under Vista, if a “Windows Security” dialog pops up, select “Install this driver software anyway”.
   • A window stating the successful installation of the driver should show. Click “Finish”/“Close”.
5. The instrument should show up in the dropdown menu within about 10 seconds.
   If you cannot access your instrument, first try unplugging and reconnecting it, or a reboot.
   Linux only: If that doesn't help, read Installing Argyll CMS on Linux: Setting up instrument access.
6. Refer to the Usage instructions.

Prerequisites

Installation

It is recommended to first remove all previous versions.

Basic concept of display calibration and profiling

If you have previous experience, skip to Usage. If you are new to display calibration, here is a quick outline of the basic concept.

First, the display behavior is measured and adjusted to meet user-definable target characteristics, like brightness, gamma and white point. This step is generally referred to as calibration. Calibration is done by adjusting the monitor controls, and the output of the graphics card (via calibration curves, also called LUT curves [LUT = Look Up Table]) to get as close as possible to the chosen target.
To meet the user-defined target characteristics, it is generally advisable to get as far as possible by using the monitor controls, and only thereafter by manipulating the output of the graphics card via LUT curves, to get the best results.

Second, the calibrated displays behavior is measured and an ICC profile describing the response of the display is created.

Optionally and for convenience purposes, the calibration is stored in the profile, but both still need to be used together to get correct results. This can lead to some ambiguity, because loading the calibration curves from the profile is generally the responsibility of a third party utility or the OS (currently, the only OS that applies calibration curves out-of-the-box is Mac OS X), while applications using the profile to do color transforms usually rely on the calibration being already loaded. Even non-color-managed applications will benefit from a loaded calibration because it is stored in the graphics card—it is “global”. But the calibration alone will not yield accurate colors—only fully color-managed applications will make use of display profiles and the necessary color transforms. Regrettably there are several image viewing and editing applications that only implement half-baked color management by not using the system's display profile (or any display profile at all), but an internal and often unchangeable “default” color space like sRGB, and sending output unaltered to the display after converting to that default colorspace. If the display's actual response is close to sRGB, you might get pleasing (albeit not accurate) results, but on displays which behave differently, for example wide-color-gamut displays, even mundane colors can get a strong tendency towards neon.

Usage

Upon launching dispcalGUI, you will see two windows: A terminal and the GUI. The terminal is mostly used for status information, and for the interactive part of display calibration. Through the GUI, you can choose your settings. Closing either window will quit the application, but I strongly recommend closing the GUI window first so the cleanup routines can run. On most systems, the terminal window will close automatically afterwards (if you were not running from a manually opened terminal to begin with).
Here's a caveat for Linux systems: Because even though this is a GUI application, it still needs a terminal window for the interactive part of display calibration. If not launched from a terminal or a .desktop shortcut with Terminal=true, it will try to find one (currently, it'll search for Terminal, gnome-terminal, konsole and xterm). If that fails, you will get a message box informing you about that. You can then either launch a terminal and run dispcalGUI from there or (preferably) create a .sh script or .desktop file to launch your desired terminal with dispcalGUI (refer to your system's documentation to find out how to do that). Also, feel free to mail me the name of your terminal application if dispcalGUI didn't detect it, so I can add it to the list of terminals that dispcalGUI will search for.

Known issues and solutions

Issue: Under Windows Vista, the installed display profile calibration cannot be loaded.
Solution: Open the Windows start menu, select “Control Panel”, then “Color Management”. Under the “Devices” tab, select your display device, then tick “Use my settings for this device”.

Issue: Under Windows Vista, the calibration gets unloaded when a “User Access Control” prompt is shown.
Solution: This is really a Windows Vista bug that hopefully gets fixed at some point, and can be remedied by either manually reloading calibration, or disabling UAC—but please note that you sacrifice security by doing this. To manually reload the calibration, either open dispcalGUI and select “Load LUT curves from current display profile” in the “Extra” menu, or (quicker) open the Windows start menu and select “dispcalGUI Calibration Loader (Display <number>)” in the “Startup” subfolder. To disable UAC, open the Windows start menu and enter “msconfig” in the search box. Click on the Tools tab. Select the line “Disable UAC” and click the “Launch” button. Close msconfig. You need to reboot your system for changes to apply.

Issue: Under Mac OS X, the brush cursor in Photoshop CS3 looks funny (box around brush).
Solution: This seems to be a Photoshop bug which shows with LUT-type profiles that have only one rendering intent. To overcome it, select “Advanced...” next to the profile type dropdown, select an existing ICC profile (probably the CMYK press profile you use most often) and tick at least one of the “Apply gamut mapping to” checkboxes before profiling. To fix an existing profile, choose “Create profile from measurement data...” from the “Extra” menu.

Issue: Under Linux, when opening a file selector, “Gtk-Message: ...” strings appear in the terminal.
Solution: These messages are generated from GTK, I have no influence on them, but they can be safely ignored if the full message is something like “Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color'”. If they really bother you and you don't mind using the shell and editing files by hand, you can get rid of these messages by changing the involved GTK theme file:

1. Open a shell and type export GTK_DEBUG=1
2. Run dispcalGUI and open a file selector.
3. In the familiar message, the path to the involved theme file should now be displayed.
4. Open that theme file in a text editor (you might need elevated rights to be able to edit it) and navigate to the line that was also shown in the message.
5. Replace the color value so that it is no longer a function call, e.g. if the old line was:
   GtkTreeView::odd-row-color = shade(0.9, @base_color)
   then change it to (look up a suitable color value in the file or specify your own):
   GtkTreeView::odd-row-color = "#eeeeee"
6. Save the theme file & exit the text editor.
7. Restart dispcalGUI and open a file selector to check if the message is gone.
8. Open a shell and type unset GTK_DEBUG

Issue: Some text is still in english, even though another language is selected in the menu.
Remark: All output from the Argyll utilities is always english, and on Mac OS X, also the menuitems in the application menu. This is not changeable by me.

Issue: The application does not look native under Linux with KDE.
Solution: You need the GTK-Qt Theme Engine for native KDE look. Most Linux distributions offer ready-made packages through their packaging systems, search for “gtk-qt” (there will likely be separate packages for KDE3 and KDE4).

To-Do / planned features (in no particular order)

• Complete the documentation in the README (partly done)
• German language README
• Profile verification (feed XYZ or Lab to display profile, display corresponding RGB values, measure, output Delta E)
• “Before” / “After” switch when calibration / profiling complete (implemented in v0.2+)
• Store all settings in profile, allow loading of settings from profile in addition to .cal file (implemented in v0.2+)
• Document the code (current code documentation severely lacks or is non-existent)
• Code cleanup (partly done)

Thanks

I would like to thank the following people:
Graeme Gill, for creating Argyll CMS.
Loïc Guégant (french translation).
Roberto Quintero (spanish translation).
Tommaso Schiavinotto (italian translation).
And everyone who sent me feedback or bug reports, suggested features, or simply uses dispcalGUI.

Version history / changelog

2009-07-16

• Fixed a glitch in the Linux Autopackage installer where it would install even if required libraries were missing.

2009-06-30 0.2.6b3

• fix (Windows): Fixed a critical bug in the Windows codepath which tried to access non-existent paths when certain settings were used.

2009-06-26 0.2.6b2

• fix: Only look at <major>.<minor> during the Python version check (fixes a critical error on Ubuntu 9.10 Beta, where the Python revision number has an unexpected value).
• fix: The LUT Viewer is now also able to plot curves from *.cal files.
• fix (Linux): If launched on an X display which is not the first display, the measurement window's location no longer determines the display which is used for measurements. This allows non-Xinerama multiscreen configurations to work with dispcalGUI. Note: You need to launch dispcalGUI on the display you want to measure, e.g. `DISPLAY=:0.1 dispcalGUI`.
• fix (Linux): Get the profile from the correct display when loading a display's LUT curves into the LUT Viewer.
• fix (Linux, cosmetic): Suppress CUPS warnings encountered on some systems when using the LUT Viewer.
• fix (Mac OS X): Do not offer 'Network' scope during profile installation if /Network/Library/ColorSync/Profiles does not exist.
• fix (Windows, cosmetic): Made sure the message "Debug: src/helpers.cpp(140): 'CreateActCtx' failed with error 0x0000007b (the filename, directory name, or volume label syntax is incorrect.)" is not shown when launching the standalone Windows executable, by changing the way *.pyd files are bundled (they are now copied to the executable's directory and are no longer part of the executable itself).
• chg: The LUT Viewer resets to linear if a display without associated profile is selected.

2009-06-22 0.2.6b

• fix: calibration preview checkbox in the “install profile” dialog should now correctly toggle between previous and new calibration.
• fix: profiling failed when creating a profile on top of an existing calibration.
• fix: correctly decode environment variables (should fix a failure when trying to create a profile and the username contains non-ASCII characters).
• fix: automatic restoration of defaults before loading settings from a profile or cal file should no longer restore “do not show again” dialogs.
• fix (Windows): several errors related to character encoding.
• chg: unattended calibration and profiling: wait 10 seconds instead of 5 after calibration before trying to start profiling measurements (some instruments seem to need longer to initialize than others, e.g. Spyder 2).
• chg (Python packages and source): instead of requiring wxPython 2.8.x specifically, only ensure a minimal version of 2.8.
• add: LUT viewer.

2009-06-11 21:33 (UTC)

• Added Linux Autopackage download.
• Renamed 55-Argyll.rules to 92-Argyll.rules, so it can work on Debian too.
• Removed “Creating a standalone executable from source” section from the ReadMe (the topic is still handled under “Installing from source” / “Additional setup.py commands”).

2009-06-07 0.2.5b4

• fix: “TypeError: coercing to Unicode: need string or buffer, instance found” when calling any of the get*Description() methods of an ICCProfile instance, which caused profile creation from existing profile to fail.
• fix: (Windows Vista) application exit on launch if autostart directory did not exist.
• fix: (source, Debian and RPM packages) use the correct wxPython version
• fix: tab-key traversal of calibration settings controls.
• fix: automatically scroll into view focused calibration settings controls if scrollbars are shown.
• fix: properly clean & remove temporary directory.
• fix: (cosmetic) added some padding to calibration settings right-hand side so scrollbar won't overlap if shown.
• chg: (cosmetic) enable auto-sizing (fit to contents) for colortemp locus, trc type and profile type selectors.
• chg: (cosmetic) do not show vendor name in instrument select dropdown (conserve some space).
• chg: (cosmetic) made the instrument selector a little narrower (needs less space now to display instrument name because the vendor name is stripped) and the measure mode selector a bit wider (to accommodate for projector mode).
• chg: only try to re-start within terminal if running as standalone executable.
• chg: show application restart request in the chosen language after changing it.
• chg: allow resizing/maximizing of main window (a minimal size is forced to prevent layout glitches).
• chg: (Linux) install from source or package will try to automatically setup access to your instrument. Some services (PolicyKit/HAL or udev) may need to be restarted to get the updated configuration recognized. If in doubt, a reboot should work in all cases.
• add: french translation (by Loïc Guégant, thanks!)
• add: bdist_deb command and --cfg option for setup.py

2009-05-16 0.2.5b3

• Fixed calibration loader autostart entry creation (“access denied” error) under Windows Vista and later with User Account Control enabled.

2009-05-07 0.2.5b2

• Fixed “error: nothing to repeat” when using a spectrometer.

2009-05-05 0.2.5b

• fix: encoding-related issues on all platforms and strange Unicode-related problems with AppleScript and Terminal on Mac OS X 10.4 (Details).
  Prerequisites to reproduce Unicode-related issues under Mac OS X 10.4: Terminal closed, or with atleast one window opened. Script inside an AppleScript bundle, the bundle filename contains UTF-8 characters. “main.command” (executable shell script) inside Contents/Resources subfolder of the bundle.
  
  Not working (messagebox “Resource not found”):

  tell application "Terminal"
  	activate
  	do script quoted form of (POSIX path of (path to resource "main.command"))
  end tell

  Not working (messagebox “Resource not found”):

  tell application "Terminal"
  	activate
  	do script quoted form of (POSIX path of (path to resource "main.command")) in first window
  end tell

  Not working (message “No such file or directory” printed to Terminal window):

  set shellscript to quoted form of (POSIX path of (path to resource "main.command"))
  tell application "Terminal"
  	activate
  	do script shellscript
  end tell

  Working:

  set shellscript to quoted form of (POSIX path of (path to resource "main.command"))
  tell application "Terminal"
  	activate
  	do script shellscript in first window
  end tell

• fix: (Windows) several actions unexpectedly failing under Windows 7 (dispcalGUI created temporary files via system calls on several occasions, but on Windows, this does not create the file in the user's temp directory as one would expect, but in the ROOT directory e.g. C:\ - a sane method is now being used instead).
• fix: bug in sorting function caused leading and trailing zeroes of numbers in testchart filenames to get lost, thus failing to load such files.
• fix: (Linux) “No module named _md5” error with the standalone executable on some Linux distros (apparently an OpenSSL-related issue, because normally it wouldn't fall back to the legacy _md5 module which is not even built by default in recent Python versions). The fallback _md5 module is now included.
• fix: calibration was not automatically added & selected in the dropdown menu when only calibrating.
• fix: dropping a profile which was not created in dispcalGUI onto the application window no longer results in an unhandled error.
• fix: when trying to load LUT curves from a profile which actually does not contain any, an error message is now shown instead of resetting the LUT to linear and erroneously stating the curves were succesfully loaded.
• fix: add display device name as device model description when profiling.
• fix: when creating a new profile from an existing profile, use that profile's device model description if present.
• fix: also create .app/.sh/.cmd files when creating a new profile from existing measurement data.
• fix: restore advanced gamut mapping options to default if selecting a profile which does not contain those settings.
• fix: allow free selection of source and target viewing conditions in advanced gamut mapping options for LUT profiles regardless of source profile type.
• fix: if the screen or instrument that was selected in a previous session is not available, select an available one.
• fix: (Mac) the “enable spyder 2” menu item would not allow to select files other than “setup.exe”.
• fix: [src] (Mac) if dispcalGUI was installed as application and then run from (separate) source, multiple copies were launched at certain occasions.
• fix: selecting a different Argyll binary directory than the previous one now actually works.
• chg: the previously empty entry at the top of the settings dropdown (settings which are not associated to a profile or .cal file) is now named “<current settings>”.
• chg: changed settings which are associated to a profile or .cal file are now marked with a leading asterisk in the settings dropdown.
• chg: default to a gamma of 2.4 (Argyll default).
• chg: warn before changed settings are discarded.
• chg: new default profile naming scheme.
• chg: new default file locations on all platforms.
  - On Linux, dispcalGUI now adheres to the XDG Base Directory Specification—the configuration file is saved as $XDG_CONFIG_HOME/dispcalGUI/dispcalGUI.ini ($XDG_CONFIG_HOME defaults to ~/.config if not set), all files created during calibration/profiling go into $XDG_DATA_HOME/dispcalGUI/storage/ ($XDG_DATA_HOME defaults to ~/.local/share if not set) by default, and logfiles into $XDG_DATA_HOME/dispcalGUI/logs/
  Any old (pre v0.2.5b) configuration data is retained in the file ~/.dispcalGUI and may be safely deleted after using v0.2.5b or newer for the first time.
  - On Mac OS, the configuration is saved as ~/Library/Preferences/dispcalGUI/dispcalGUI.ini, all files created during calibration/profiling go into ~/Library/Application Support/dispcalGUI/storage/ by default, and logfiles into ~/Library/Logs/dispcalGUI/
  Any old (pre v0.2.5b) configuration data is retained in the file ~/Library/Preferences/dispcalGUI Preferences and may be safely deleted after using v0.2.5b or newer for the first time.
  - On Windows, the configuration file is saved as %APPDATA%\dispcalGUI\dispcalGUI.ini, all files created during calibration/profiling go into %APPDATA%\dispcalGUI\storage\ by default, and logfiles into %APPDATA%\dispcalGUI\logs\
  Any old (pre v0.2.5b) configuration data is retained in the registry key HKEY_CURRENT_USER\Software\dispcalGUI.
• chg: [build/src] (Windows) removed MS Visual C++ 2008 Redistributable DLLs from the source package. Users who build under Windows will have them anyway as they are installed with Python 2.6, so they are now copied directly from %SystemRoot%\WinSxS (Windows side-by-side assemblies) if possible.
• chg: [build/src] SendKeys is now a dependency on Windows when running or building from source.
• chg: [build/src] made dispcalGUI a distutils package, so it can be built/installed via setup.py.
• chg: default locations are now also searched for resource files ($XDG_DATA_HOME/dispcalGUI, $XDG_DATA_DIRS/dispcalGUI on Linux, ~/Library/Application Support/dispcalGUI, /Library/Application Support/dispcalGUI on Mac OS X, %APPDATA%\dispcalGUI, %COMMONAPPDATA%\dispcalGUI and %COMMONPROGRAMFILES%\dispcalGUI on Windows) in addition to the current working directory (which is always searched first if it differs from the executable directory) and the executable directory (which is always searched last).
• chg: better error handling. For unhandled exceptions, a message box is shown and an entry is written to the logfile.
• chg: (Linux) the calibration loader will no longer try and handle gnome-screensaver quirks - it was working too unreliably, and should really be fixed in gnome-screensaver. The current recommendation is to not use a screensaver at all if possible, and instead rely on the system's energy saving options.
• chg: (Linux) there's no longer an installer for the Linux version.
• chg: cancelling of certain operations like profile calculation and testchart generation is now also supported when using Python 2.5
• chg: when searching for Argyll executables, also search for files with “argyll-” prefix or “-argyll” suffix (thanks to Mark Whitis for report).
• chg: disable measurement mode selection when using a spectrometer.
• add: logging (also see the change related to file-storage). Logfiles are created per-date. A maximum of 5 old ones is being kept as backup.
• add: placeholders like display name, measurement device, whitepoint etc. can now be used in the profile name.
• add: unattended calibration and profiling for some instruments, meaning it is no longer necessary to press a key after calibration to start the measurements for profiling (needs xautomation under Linux).
• add: settings and related files can be deleted.
• add: (Linux, Mac, Vista) profile install scope can be selected (note: local system scope install is broken with current Argyll versions under Linux).
• add: version and translation information in the about window.
• add: projector mode when using Argyll 1.1.0 Beta or newer with the X-Rite ColorMunki.

2009-01-01

Linux and sourcecode bugfix update: Creation of the autostart entry failed when the autostart directory did not yet exist.

2008-12-24 0.2.1b

• fix: video LUT access check always returned false when no display profile was set.
• chg: (Linux) dispcalGUI now uses the autostart specification from freedesktop.org for the profile loader under Linux when installing profiles. NOTE for users: This also means you should manually remove any autostarts from previous versions, e.g.
  rm ~/.gnome2/dispwin-*.sh
rm ~/.kde/Autostart/dispwin-*.sh
  and then re-install your current profile so the new loader is created. The new loader will be created in $XDG_CONFIG_HOME/autostart/ (if set) or ~/.config/autostart/ (if not set), with the filename dispcalGUI-Calibration-Loader-Display-x.desktop, where x is the display number.
• chg: the calibration loader will check if gnome-screensaver is running and if so, exit it before loading the calibration, then start it again to prevent resetting the calibration when activated.
• chg: .sh/.cmd file in profile folder is no longer created when just installing a profile.
• add: message box when selecting LUT as profile type with recommendation to use more samples for higher quality profiles.
• add: default to english locale if translation doesn't exist.

2008-12-18 0.2b

• fix: no longer possible to introduce invalid value types through a malformed config file (which could lead to dispcalGUI not launching).
• fix: windows can no longer be moved permanently out of the visible screen area.
• fix: spaces and special chars in the profile name should work now (should have from the start, but I had some superfluous code which broke it).
• fix: spaces in the path to dispcalGUI should work now under Linux and Mac OS X too (Windows had no problem)
• fix: measurement file no longer gets deleted after successful measurement if profile generation fails (was a simple oversight on my side).
• fix: [cosmetic] logo header now always spans the whole width of the window.
• fix: [cosmetic] (Mac OS X) on first launch, a second, unused, terminal window is no longer opened.
• fix: windows will now try to adjust its height to fit on small screens (scrollbars might appear).
• chg: “Calibration file” renamed to “Settings” and moved to the top, is now a dropdown box remembering the last 10 used files. Settings are stored in and loaded from profiles.
• chg: renamed “Display type” to “Measurement mode” and moved over to measurement device selector.
• chg: default to “LCD” for measurement mode.
• chg: default testchart file names are now localized.
• chg: new default testcharts, four flavours: matrix default (91 patches), LUT default (127 patches), large (512 patches) and massive (3012 patches).
• chg: testchart selector is now a dropdown box, shows all testchart files in chosen directory plus the default testcharts.
• chg: [build/src] new and improved build system.
• chg: [build/src] Python 2.6 is now the recommended version to run and/or build dispcalGUI. Python 2.5 is still supported, but you will not be able to cancel profile or testchart creation through the GUI.
• chg: (Linux) externally installed wxGTK is no longer a dependency for executables.
• chg: [build] Executables are now completely self-contained. The following paths are searched for additional language files: <user home directory>/dispcalGUI/lang, <dispcalGUI root directory>/lang
• add: all settings now stored in profile whenever possible.
• add: “Install” button next to settings dropdown to install selected profile.
• add: dropdown to choose the display to use for LUT access if all of the following applies:
  - more than one display connected
  - one of those displays seems to have non-working LUT access (detected on startup)
  - one of those displays seems to have working LUT access (detected on startup)
• add: show patch count of selected testchart next to dropdown.
• add: ability to select an icc profile (if it contains appropriate data) or measurement data file (.ti3) as testchart (converted on-the-fly).
• add: testchart generator with editing cabability (experimental)
  - to select patches, click and drag the mouse over table cells, or hold SHIFT (select range) or CTRL/CMD (add/remove single cells/rows to/from selection)
  - to add a patch, double-click a row label
  - to delete patches, select them, then hold CTRL or CMD and hit DEL or BACKSPACE (will always delete whole rows even if only single cells selected)
  - CTRL-C/CTRL-V/CTRL-A = copy/paste/select all
• add: advanced gamut mapping options for LUT-type profiles, can also be used to overcome an apparent Photoshop CS3 bug under Mac OS X where the brush cursor shows strange artifacts when using LUT-profiles with only one intent (thanks to Klaus Karcher for reporting this).
• add: ability to generate profile from existing measurement data, even from an existing profile (if it contains appropriate data).
• add: drag and drop calibration files (.cal), profiles (.icc/.icm), testcharts (.ti1) and measurement data files (.ti3) to the main window to process/select them (does not work very reliably on Mac OS X depending on where you drop the files, and you also get no optical feedback during the drag operation like the changed mouse cursor on Linux/Windows. Your best bet when dropping any files is perhaps the unoccupied area below “Settings”).
• add: fully movable/resizable measurement window.
• add: profile and testchart creation can be aborted (when running from source only if using Python >= 2.6).
• add: “Before” / “After” switch when calibration / profiling complete.
• add: menu item to enable Spyder 2 from within dispcalGUI.
• add: italian and spanish GUI translations (thanks contributors!)
• Numerous other small fixes/changes.

2008-08-21

Executable-only update for Linux (thanks to Patrice Vetsel for bug report): dispcalGUI is now built against wxGTK 2.8.7.1, which becomes a dependency.

2008-08-18 0.1b

First public release.