I’m happy to announce that I’ve just released DisplayCAL 3.3.

Highlights:

• Better multi CPU/multi core support and overall speed enhancement due to smaller default patch sets using an alternate forward profiling method.
• Calibration whitepoint targets other than “As measured” will now also be used as 3D LUT whitepoint target, allowing the use of the visual whitepoint editor to set a custom whitepoint target for 3D LUTs.
• The visual whitepoint editor is now compatible with Chromecast, Web @ localhost, madVR, Prisma and Resolve pattern generators.
• Automatic output levels detection, and manual output levels selection as an advanced option.
• New experimental profiling patch sequence advanced options.
• Profile loader (Windows): Windows 10 Creators Update compatibility.

See the changelog for the (huge!) full list of changes.

Enjoy!

Added in this release:

• Korean translation thanks to 김환(Howard Kim).

Changed in this release:

• Disable observer selection if observer is set by a colorimeter correction.
• 3D LUT maker: Enable black output offset choice for 16-bit table-based source profiles.
• Profile loader (Windows): “Automatically fix profile associations” is now enabled by default.
• Build system: Filter out “build”, “dist” as well as entries starting with a dot (“.”) to speed up traversing the source directory tree (distutils/setuptools hack).

Fixed in this release:

• Could not create colorimeter correction from existing measurements for instruments that don’t support alternative standard observers.
• ColorHug / ColorHug2 “Auto” measurement mode threw an error if the extended display identification data did not contain a model name.
• [Trivial/cosmetic] Testchart editor: When adding reference patches, resize row labels if needed.
• Profile loader (Linux): When errors occured during calibration loading, there was no longer any message popup.
• Profile loader (Windows): Filter non-existing profiles (e.g. ones that have been deleted via Windows Explorer without first disassociating them from the display device) from the list of associated profiles (same behavior as Windows color management settings).
• Profile loader (Windows): When changing the language on-the-fly via DisplayCAL, update primary display device identfier string.

This is a bugfix and maintenance release.

Changed in this release:

• Updated traditional chinese translation (thanks to 楊添明).
• Profile loader (Windows): When creating the profile loader launcher task, set it to stop existing instance of the task when launching to circumvent a possible Windows bug where a task would not start even if no previous instance was running.

Fixed in this release:

• When querying the online colorimeter corrections database for matching corrections, only query for corrections with a matching manufacturer ID in addition to a matching display model name (fixes corrections being offered for displays from different manufacturers, but matching model names).
• Profile loader (Windows): Fix unhandled exception if no profile is assigned to a display (regression of a change to show the profile description instead of just the file name in DisplayCAL 3.2.1).

Happy new year everyone!

This is a bugfix and maintenance release.

Changed in this release:

• Importing colorimeter corrections from other display profiling software now only imports from the explicitly selected entries in automatic mode.
• Profile loader launcher (Windows): Pass through --oneshot argument to profile loader.

Fixed in this release:

• Visual whitepoint editor: Opening a second editor on the same display without first dragging the previously opened editor to another display would overwrite the cached profile association for the current display with the visual whitepoint editor temporary profile, thus preventing the correct profile association being restored when the editor was closed.
• Mac OS X: Fall back to HTTP when downloading X3D viewer components to work around broken Python TLS support.
• Windows: When installing instrument drivers, catch WMI errors while trying to query device hardware IDs for instruments.
• Profile loader (Windows): Possibility of unhandled exception when resuming from sleep if the graphics chipset is an Intel integrated HD graphics with more than one attached display device (may affect other graphics chipsets as well).

This is a bugfix and maintenance release.

Changed in this release:

• Profile loader (Windows Vista and later): The profile loader process now auto-starts with the highest available privileges if installed as administrator. This allows changing system default profile associations whenever logged in with administrative privileges.
• Profile loader (Windows Vista and later): If running under a restricted user account and using system defaults, clicking any of the “Add…”, “Remove” and “Set as default” buttons will allow to restart the profile loader with elevated privileges.
• Profile loader (Windows): Show profile description in addition to profile file name in profile associations dialog.

Fixed in this release:

• Linux, Windows: Visual whitepoint editor was not working in HiDPI mode.
• Windows: Irritating “File not found” error after installing a profile with special characters in the profile name (note that the profile was installed regardless).
• [Cosmetic] Standalone executables (Windows): In HiDPI mode, taskbar and task switcher icons could be showing placeholders due to missing icon files.
• [Minor] Profile loader (Windows): Enable the profile associations dialog “Add…” button irrespective of the current list of profiles being empty.
• [Minor] Profile loader (Windows): Suppress error message when trying to remove a profile from the active display device if the profile is the system default for said device (and thus cannot be removed unless running as administrator) but not for the current one.
• Profile loader (Windows): Do not fail to close profile information windows if the profile associations dialog has already been closed.
• Profile loader (Windows): If logging into another user account with different DPI settings while keeping the original session running, then logging out of the other account and returning to the original session, the profile loader could deadlock.