dispcalgui-users Mailing List for DisplayCAL
Display Calibration and Characterization powered by Argyll CMS
Brought to you by:
fhoech
Menu
▾
▴
dispcalgui-users — Discussion and support
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(8) |
Oct
(1) |
Nov
(3) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(4) |
Feb
|
Mar
|
Apr
(4) |
May
(9) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
(9) |
| 2012 |
Jan
(1) |
Feb
(5) |
Mar
(13) |
Apr
(1) |
May
(2) |
Jun
(11) |
Jul
(3) |
Aug
(1) |
Sep
(2) |
Oct
(10) |
Nov
(1) |
Dec
|
| 2013 |
Jan
(4) |
Feb
|
Mar
(6) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(6) |
Aug
(2) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
(5) |
Mar
(12) |
Apr
(25) |
May
(1) |
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(14) |
Oct
|
Nov
(11) |
Dec
(3) |
| 2015 |
Jan
|
Feb
(4) |
Mar
|
Apr
(5) |
May
(12) |
Jun
(7) |
Jul
(4) |
Aug
(1) |
Sep
(8) |
Oct
|
Nov
(2) |
Dec
(15) |
| 2016 |
Jan
(13) |
Feb
(4) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2017 |
Jan
(4) |
Feb
(14) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(1) |
| 2018 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2019 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(3) |
Oct
(1) |
Nov
(2) |
Dec
(4) |
|
From: Florian H. <fl...@di...> - 2019-12-14 12:51:23
|
Fixed in this release: * [Cosmetic] [UI] Improve PCS to device gamut outline plot. * [Blocker] Linux, macOS: Fix failure to launch if initial install (regression of lockfile change in 3.8.9.2) -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-12-12 23:15:56
|
Fixed in this release: * [Minor] When previous instance was force quit, override leftover lockfile. * [Trivial] When using a custom profiling testchart with very few or no dark RGB gray patches, try to better maintain slope of existing points during shaper curve generation. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-12-08 01:59:24
|
Fixed in this release: - [Moderate] Fix SpyderX calibration issue when using 32-bit ArgyllCMS executables. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-12-07 17:20:45
|
Changed in this release:
* [Enhancement] Show the instrument serial number (if available) when
prompting to physically interact with the instrument.
* [Enhancement] Check SpyderX dark offset calibration and abort if it is
too high (user error).
* [Enhancement] Adjust perceptual device to PCS table black point to
match perceptual PCS to device table.
* [Enhancement] Warn during automatic output levels detection if the
display device input range or graphics driver output range look to be
misconfigured.
* [Enhancement] Profile loader (Windows): Use an alternate method to
enforce single instance if local IPC is blocked.
* Tone response curve plot now uses the illuminant-relative profile
whitepoint instead of D50 for input values if using absolute
colorimetric intent.
* Rename “LG OLED” (.dcl) 3D LUT format to “DeviceControl” and unlock
available resolutions.
Fixed in this release:
* [Trivial] Reload current calibration when cancelling profile
installation (regression of a change to profile installation dialog
handling in ${APPNAME} 3.8.8, SVN revision r6252).
* [Trivial] When loading settings from a profile, restore unused
CIECAM02 viewing conditions (if applicable).
* [Trivial] Prevent potential double prompt for instrument calibration.
* [Cosmetic] Do not re-use logfiles for standalone tools as long as
other instances are still running.
* [Moderate] Linux: Failure to launch with pre-release versions of
wxPython 4.
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-11-07 21:55:17
|
Fixed in this release:
* [Moderate] Work-around failure to launch if wxPython 3.0 /
wxWidgets 3.0 release number do not match (using wxPython 3.0
is deprecated).
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-11-07 00:27:35
|
Changed in this release: * [Enhancement] Detect and warn about malformed colorimeter corrections (e.g. from non-official sources). Move them to the trash automatically if they were previously (manually) installed. * [Enhancement] Always enumerate instruments on application startup if more than one instrument was detected the last time the application was used (cross-platform consistency). * [Enhancement] When prompting for instrument calibration, display the just now detected instrument name instead of the previously enumerated name (the latter might be stale if you forgot to refresh after changing connected instruments). * [Enhancement] Use a slightly improved smoothing method when creating high resolution PCS to device tables. * [Enhancement] Increase automatic PCS to device table resolution for L*a*b* LUT profiles to 45x45x45 if using smoothing. * [Enhancement] [UI] Only auto-close profile/3D LUT installation dialog after a successful installation. * [Enhancement] Don’t auto-close madTPG after 3D LUT installation. * [Enhancement] macOS: Warn if a black luminance calibration target is set. * [Enhancement] Profile loader (Windows): Use a minimally faster method to check for other running applications. Fixed in this release: * [Minor] madVR 3D LUT generation: Always write D65 white to 3D LUT input primaries metadata so madVR does not attempt to correct whitepoint differences on its own when using a custom whitepoint (the 3D LUT itself will map the custom whitepoint correctly). * [Minor] madVR 3D LUT installation: Don’t attempt to install 3D LUTs with unsupported input primaries metadata (i.e. not Rec. 709, SMPTE C, EBU/PAL, Rec. 2020 or DCI P3) as madVR will overwrite the metadata depending on the 3D LUT install slot. Such 3D LUTs should only be assigned manually in madVR instead. * [Trivial] [UI] When loading settings, always enable the 3D LUT tab if the display is virtual (consistent with display selection behavior). * [Trivial] Also apply black point correction when creating a matrix profile without black point compensation (consistency). * [Trivial] Do not create swapped matrix fallback tags for XYZ LUT profiles when using the alternate forward profiler and the used ArgyllCMS version is >= 2.1 (be consistent with ArgyllCMS). * [Trivial] madVR 3D LUT generation: Accept negative values for input primaries metadata. * [Trivial] madVR 3D LUT installation (Linux, macOS): Send the 3D LUT in chunks and increase the timeout to prevent the installation failing over a slow network (e.g. WiFi). * [Cosmetic] [UI] Profile loader (Windows): Prevent a stale tray icon remaining (until mouse over) in some rare cases after exiting the profile loader. * [Trivial] Profile loader (Windows 7): Skip incomplete display configuration registry entries. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-10-01 21:40:04
|
Fixed in this release: * [Trivial] [UI] Profile information (Linux): When using wxPython 3.0 instead of 4.0, clicking the sash would throw an error (using wxPython 3.0 is deprecated). * [Trivial] macOS: Only automatically re-enable black point compensation if restoring defaults or loading a non-3D-LUT preset. * [Trivial] Profile loader (Windows): Work-around two instances of the profile loader being started after powering on the system if fast startup was enabled in Windows power settings. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-09-22 14:33:41
|
Changed in this release: * [Enhancement] macOS: Automatically enable not using the video card gamma table to apply calibration during characterization measurements if using limited range (16..235). This should mitigate issues with older graphics chipsets and/or macOS versions that use the wrong output range internally when connected to some monitors that expect to receive limited range signals. * [Enhancement] Profile loader (Windows): A scheduled task now restarts the profile loader after resume from standby/hibernation as well as daily at 04:00 AM (whichever comes first), to mitigate the Windows GDI SetDeviceGammaRamp API leaking memory since Windows 10 1903. Fixed in this release: * [Trivial] Don't automatically disable interactive display adjustment when setting calibration tone curve to “As measured” (unintended behavioral change introduced in DisplayCAL 3.8.6, SVN revision r6194). * [Minor] Linux (GNOME on Wayland): Latency incurred by a large measurement window size was not accounted for, introducing the possibility of measurements failing due to loss of synchronization. * [Minor] Linux (GNOME on Wayland): Limited range (16..235) support. * [Cosmetic] [UI] macOS: Get rid of brief profile installation dialog flicker after installation. -- Florian Höch https://displaycal.net |
|
From: Andreas M. <and...@we...> - 2019-09-06 11:03:33
|
I want to mention it at least some time: Thank you! > -----Ursprüngliche Nachricht----- > Von: Florian Höch <fl...@di...> > Gesendet: Freitag, 6. September 2019 13:01 > An: dispcalgui-news <dis...@li...>; dispcalgui- > users <dis...@li...> > Betreff: [dispcalGUI-users] DisplayCAL 3.8.6 released > > Changed in this release: > > * [Enhancement] If the graphics drivers or hardware do not support > loadable gamma ramps or calibration, show a more descriptive error > message. > * [Enhancement] Increase the timeout for display & instrument detection > during application startup from 10 to 20 seconds, to allow for slow > opening of legacy serial ports. > * [Enhancement] Windows 10 1903: Always do instrument detection during > application startup if more than one instrument was connected the last > time the application was used, as the list of instruments is not > guaranteed to be consistent between sessions under 1903. > * [Enhancement] Profile loader (Windows): Apply smoothing to calibration > if the quantization bitdepth is set to 8. > * [Enhancement] Profile loader (Windows): No longer require running > elevated to be able to detect changes in the display configuration > under Windows 10 1903. > > Fixed in this release: > > * [Minor] Do not attempt to access properties of non-existent objects if > a subprocess is not succesfully terminated after reaching a timeout > during display & instrument detection at application startup > (unexpected failure). > * [Trivial] [UI] Disable the profile installation button if no displays > have been detected. > * [Trivial] [UI] Disable the measurement report menu item if no > instruments have been detected. > * [Trivial] Profile loader (Windows): Work around Windows 10 1903 handle > leaks in Windows Color System APIs. > > -- > Florian Höch > https://displaycal.net > > > _______________________________________________ > dispcalGUI-users mailing list > dis...@li... > https://lists.sourceforge.net/lists/listinfo/dispcalgui-users |
|
From: Florian H. <fl...@di...> - 2019-09-06 11:01:23
|
Changed in this release: * [Enhancement] If the graphics drivers or hardware do not support loadable gamma ramps or calibration, show a more descriptive error message. * [Enhancement] Increase the timeout for display & instrument detection during application startup from 10 to 20 seconds, to allow for slow opening of legacy serial ports. * [Enhancement] Windows 10 1903: Always do instrument detection during application startup if more than one instrument was connected the last time the application was used, as the list of instruments is not guaranteed to be consistent between sessions under 1903. * [Enhancement] Profile loader (Windows): Apply smoothing to calibration if the quantization bitdepth is set to 8. * [Enhancement] Profile loader (Windows): No longer require running elevated to be able to detect changes in the display configuration under Windows 10 1903. Fixed in this release: * [Minor] Do not attempt to access properties of non-existent objects if a subprocess is not succesfully terminated after reaching a timeout during display & instrument detection at application startup (unexpected failure). * [Trivial] [UI] Disable the profile installation button if no displays have been detected. * [Trivial] [UI] Disable the measurement report menu item if no instruments have been detected. * [Trivial] Profile loader (Windows): Work around Windows 10 1903 handle leaks in Windows Color System APIs. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-08-14 13:41:37
|
This is a bugfix release for 3.8.4. Changed in this release: * [Enhancement] macOS: Use `caffeinate` to prevent display sleep and screensaver. Fixed in this release: * [Moderate] DisplayCAL 3.8.4 broke video levels (16..235) output encoding/decoding for video card gamma table tags (profiles using calibration with video output levels created by 3.8.4 can be fixed by re-creating via menu “File”, “Create profile from measurement data...” and selecting the existing profile). -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-08-10 22:32:53
|
Changed in this release: * [Enhancement] Do early detection of highly non-monotonic luminance responses when doing on-the-fly generation of the preconditioning profile for auto-optimized testcharts with 425 or more patches. * [Enhancement] Always create a single shaper curve for the fallback matrix tags of cLUT profiles with nonlinear calibration. * [Enhancement] Profile loader (Windows): Only try to restore profile associations on exit if they had to be fixed on launch to begin with. Fixed in this release: * [Minor} Work-around Argyll applycal bug with gamma value TRC curve tags in profiles (fixes generating HDR 3D LUTs from display profiles with such tags). * [Trivial] [UI} Windows with display scaling above 100% (HiDPI): Prevent occasional text cutoff/wrapping issues on dialog messages by adding one pixel to the minimum width of the message text area (wxWidgets bug). -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-07-02 21:58:53
|
- Profile loader (Windows): Work around Windows 10 1903 (May 2019 update) severe banding bug and automatically disable Microsoft Windows Color System Calibration Loader task. Logging out and back in is required, and may be required each time a display's default associated profile is changed. - [Minor] Verification: Prevent unintended mixing of unicode and binary strings when a device link profile is used. - [Cosmetic] [UI] Linux (KDE): Centering the measurement window would increase its size slightly and resetting its size would move the window down and right (regression of SVN revision r6137). -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2019-06-09 16:17:01
|
* [Enhancement] Always try to skip initial colorimeter
calibration for uniformity measurements (e.g. SpyderX).
* [Enhancement] Use GObject Introspection for DBus access (if
available).
* [Enhancement] Use a default timeout of 500 ms for DBus calls.
* [Enhancement<span>] Profile loader (Windows): If registry
access to the display configuration fails (e.g. due to running
non-elevated), log a warning only once.
* Windows: Only log Windows exceptions that are actually errors.
* [Minor] If invoked from the main application's “Tools” menu,
the synthetic ICC profile creator HDR configuration could
affect the main application's 3D LUT HDR configuration.
* [Minor] Successive requested instrument calibration during
uniformity measurements did not wait for the calibration to
complete before continuing (e.g. SpyderX).
* [Trivial] Prevent potential blocking of socket binding if a
previous instance exited unexpectedly.
* [Trivial] [UI] Change parent inheritance for pathdialog
wrappers so interacting with the parent is appropriately
prevented when the wrapper dialog is shown via a scripting
request.
* [Trivial] [UI] Always prefer the global DPI value (Xft.dpi) for
HiDPI scaling with wxGTK2.
* [Trivial] [UI] Windows: Work-around wxPython Phoenix bug:
Destroying a frame loaded from XRC affects subsequently
loaded XRC resources (leading to instantiated controls being
of the wrong type and failing initialization due to not having
the expected interfaces).
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-05-24 03:02:01
|
Fixed in this release:
* [Minor] [UI] Linux: Some custom widgets had a size of zero when
org.gnome.desktop.interface scaling-factor was set to 0
(regression of a change in DisplayCAL 3.8.1, SVN revision
r5979).
* [Minor] [UI] Linux: No scaling for some custom widgets with wxGTK2
and HiDPI unless org.gnome.desktop.interface scaling-factor was set
to a value of 2 or higher (regression of a change in DisplayCAL
3.8.1, SVN revision r6005). HiDPI scaling with wxGTK2 under X11
is now handled entirely by the global DPI value (Xft.dpi).
* [Minor] [UI] Linux: Too small size for the contents of some custom
widgets with wxGTK2 and HiDPI.
* [Cosmetic] [UI] Linux: Too much padding inside some custom widgets
with wxGTK2 and HiDPI.
* [Cosmetic] [UI] Linux: Occasional glitchy window sizing under
Wayland.
* [Cosmetic] [UI] Linux: Added workaround for double window
decorations when the environment variable GTK_CSD is set to a
nonzero value under X11 (e.g. elementary OS Juno with Phanteon
desktop).
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-05-19 00:19:43
|
Added in this release:
* [Feature] Preliminary experimental Wayland support under GNOME
3 using colord (requires ArgyllCMS 2.1 or newer as well).
Caveats do apply:
* Window placement and ordering is completely up to the
compositor under Wayland. There is generally no way for an
application to place its own windows at specific relative
locations or z-orders. As a result of this, the measurement
window cannot stay always on top or be automatically centered.
* Extra care needs to be taken that other windows are not placed
on top.
* Video card gamma table (videoLUT) access is handled by colord.
Some functions like viewing current videoLUT contents may not
be available.
* The measurement window color depth is limited to 8 bits per
channel per pixel (but dithering is used to achieve a higher
effective color depth).
* The measurement window may be subject to desktop-wide color
management in upcoming versions of Wayland (although the
display device is inhibited during measurements via the
org.freedesktop.ColorManager.Device[1] D-Bus API which should
prevent this, and as a fallback a linear calibration sRGB
profile is temporarily installed during measurements if the
D-BUs API is unavailable, which should result in an identity
transform, i.e. effectively no color management, as well as
linear video card gamma tables).
* Application support for color management under Wayland via
colord still seems to lacking[2] (although the list may well be
out-of-date).
* Only tested under GNOME 3 (Fedora 30, Ubuntu 19.04). Support
for other desktop environments will need to be implemented
separately until Wayland gains a color management and
calibration/profiling protocol.
* [Feature] LG OLED 3D LUT format.
[1] https://www.freedesktop.org/software/colord/gtk-doc/Device.html
[2] https://www.freedesktop.org/software/colord/faq.html#application-support
Changed in this release:
* [Enhancement] If the currently used ArgyllCMS version is not a
standard version, but also not a beta, do not offer to switch
to an installed official stable version if it's otherwise the
same version number.
* [Enhancement] Include Quantum Dot LED (Samsung QLED Q9F)
spectral sample colorimeter correction when importing for i1
Display Pro and ColorMunki Display (sourced from community
colorimeter corrections database).
* [UI] (Debian, Fedora, Ubuntu) Use wxPython Phoenix if
installed.
* Prisma, Resolve: Set pattern generator background color to
pattern color if using fullscreen patterns.
Fixed in this release:
* [Moderate] UnicodeDecodeError when a CCSS file contains unicode
characters in the display device description (regression of a
change in DisplayCAL 3.8 to use localized technology
descriptions, SVN revision r5810).
* [Minor] APL calculation for Prisma and Resolve pattern
generators was off by a few percent depending on pattern area
and current pattern color.
* [Minor] Quick reporting on calibrated or uncalibrated display
did not try to detect output levels if set to “Auto”.
* [Trivial] More gracefully deal with faulty tags in ICC profiles
(fixes ICC profile information unhandled exception for colord-
created profiles with malformed targ tags).
* [Trivial] [UI] Correctly update the audio button state on
progress dialogs when changed on a previous window.
* [Cosmetic] [UI] Various minor potential rendering glitches.
* [Cosmetic] [UI] Add work-arounds for various Wayland-related
wxPython rendering quirks and bugs (e.g. spacing around
windows, popup menu placement).
* [Trivial] Try to work around sporadic colord profile
installation quirks (“The profile was not added in time”).--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-04-26 02:53:39
|
Added in this release:
* [Feature] SpyderX support (requires ArgyllCMS 2.1.0 or newer,
use ArgyllCMS 2.1.0_mod to be able to skip instrument self-
calibration).
* [Feature] Colorimeter correction information with graph.
* [Feature] Synthetic ICC profile creator: Drag & drop support
for TI3 measurement files.
* [Enhancement] Rudimentary support for hypothetical future
instruments and their measurement modes (any new instrument
support added to ArgyllCMS in the future should be fully usable
in DisplayCAL right away without needing an update for
instrument-specific measurement modes).
* [Enhancement] Prefer colorimeter corrections from “ArgyllCMS”
folder and ignore duplicate (spectral) colorimeter corrections
from “color” folder (e.g. installed by HCFR under Windows).
* [Enhancement] Display technology information to aid in the
choice of a suitable measurement mode or correction.
* [Enhancement] Default to high-resolution spectrum mode (if
available) for spectrometers that support it.
* [Enhancement] Include some additional spectral sample
colorimeter corrections when importing for i1 Display Pro and
ColorMunki Display (e.g. MacBook Pro 2016 Retina with PFS
Phosphor WLED “P3” display, LG OLED 6-series WOLED based on
samples from LG C6 and E6 OLED TVs, sourced and combined from
community colorimeter corrections database contributions).
Changed in this release:
* [UI] Updated simplified chinese localization (thanks to Mars).
* [UI] Updated french localization (thanks to Jean-Luc Coulon).
* [Enhancement] Implicitly try to skip repeat instrument self-
calibration for colorimeters that want it if already done at
least once per measurement run.
* [Enhancement] Converted translation file format from JSON to
YAML for better readability.
* [Enhancement] Use a localized description for known quality
spectral sample colorimeter corrections.
* Use an application-specific download directory for updates and
supporting files.
Fixed in this release:
* [Minor] Not all programmed measurement modes were enumerated
for the K10-A colorimeter (regression of a change in DisplayCAL
3.7, SVN revision r5557).
* [Minor] ColorHug/ColorHug2 “auto” measurement mode was not
working anymore.
* [Trivial] Curve viewer: Re-introduced being able to view the
current contents of the video card gamma table if no display
profile is set or the profile used does not contain
calibration.
* [Cosmetic] Curve viewer, profile information: Curve graphing
identical channel detection was not working properly in some
cases (only affected synthetic curves).
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-03-20 22:51:26
|
Hi, Am 20.03.2019 um 23:01 schrieb Andreas Mock: > currently I can't define a pattern, but since installing > version 3.7.2 it happens reallly often under Windows 10 64bit 1809 > that I see how the currently defined profile is NOT used. > Most of the times the profile gets loaded after a short time, > but also sometimes the profile gets not load automatically. > I've never seen that in the versions before 3.7.2. It's not related to DisplayCAL or the profile loader, but some 3rd party utility that clears the calibration (which you have to find, could be a graphics driver, motherboard, or peripheral utility, or Windows itself if you're using a Surface laptop). The profile loader will periodically re-apply the calibration, but it can take several seconds in between those intervals. Cheers, Florian -- https://displaycal.net |
|
From: Andreas M. <and...@we...> - 2019-03-20 22:01:35
|
Hi Florian,
currently I can't define a pattern, but since installing
version 3.7.2 it happens reallly often under Windows 10 64bit 1809
that I see how the currently defined profile is NOT used.
Most of the times the profile gets loaded after a short time,
but also sometimes the profile gets not load automatically.
I've never seen that in the versions before 3.7.2.
Can I supply any additional data to find a hint for that
current new behaviour?
Best regards
Andreas
-----Ursprüngliche Nachricht-----
Von: Florian Höch <fl...@di...>
Gesendet: Sonntag, 17. März 2019 21:04
An: dispcalgui-news <dis...@li...>; dispcalgui-users <dis...@li...>
Betreff: [dispcalGUI-users] DisplayCAL 3.7.2 released
Phasing out 0install support. While the 0install version of DisplayCAL, which was originally introduced as a replacement for the long-defunct Autopackage system under Linux, has had its uses, the low distribution (around 6%) of 0install versus the standalone version does no longer warrant the additional time and work needed to maintain this separate deployment path. 0install support will thus be phased out with this version, which is only available as “standalone” installation. Windows and macOS users will be updated automatically to the standalone version.
Linux users should switch to a standalone package at their earliest convenience.
There will be a transition period of a few months during which old 0install versions will continue to run, but after which the respective online infrastructure will be decommissioned.
Added in this release:
* [UI] Russian and ukrainian localization (thanks to Alex
Sikorsky).
Changed in this release:
* [Enhancement] Apply black point correction/compensation to
measurement data directly instead of device-to-PCS table
(improves smoothness of profiles for displays with not very
neutral black).
* [Enhancement] Optimize single gamma curve without offset to
single gamma value.
* [Enhancement] Network: Get rid of gethostbyname usage because
it can have a long delay.
* [UI] Updated traditional chinese localization (thanks to 楊添明).
Fixed in this release:
* [Minor] Fallback TRC tags were created using a wrong backward
matrix when using ArgyllCMS 2.0.2b or newer.
* [Trivial] When connecting to a pattern generator, closing the
connection dialog should be equivalent to cancelling.
* [Cosmetic] [UI] Show a dialog while the UI is blocked when
connecting to madTPG.
* [Cosmetic] [UI] Do not show the visual whitepoint editor
fullscreen warning if using a pattern generator.
* [Cosmetic] [UI] Synthetic ICC creator: Set chromatic adaptation
up/down arrow increment to 0.0001.
* [Cosmetic] [UI] Synthetic ICC creator: Hide (unused) hue &
saturation controls for SMPTE 2084 hard clip.
--
Florian Höch
https://displaycal.net
_______________________________________________
dispcalGUI-users mailing list
dis...@li...
https://lists.sourceforge.net/lists/listinfo/dispcalgui-users
|
|
From: Florian H. <fl...@di...> - 2019-03-17 20:16:41
|
Phasing out 0install support. While the 0install version of DisplayCAL,
which was originally introduced as a replacement for the long-defunct
Autopackage system under Linux, has had its uses, the low distribution
(around 6%) of 0install versus the standalone version does no longer
warrant the additional time and work needed to maintain this separate
deployment path. 0install support will thus be phased out with this
version, which is only available as “standalone” installation. Windows
and macOS users will be updated automatically to the standalone version.
Linux users should switch to a standalone package at their earliest
convenience.
There will be a transition period of a few months during which old
0install versions will continue to run, but after which the respective
online infrastructure will be decommissioned.
Added in this release:
* [UI] Russian and ukrainian localization (thanks to Alex
Sikorsky).
Changed in this release:
* [Enhancement] Apply black point correction/compensation to
measurement data directly instead of device-to-PCS table
(improves smoothness of profiles for displays with not very
neutral black).
* [Enhancement] Optimize single gamma curve without offset to
single gamma value.
* [Enhancement] Network: Get rid of gethostbyname usage because
it can have a long delay.
* [UI] Updated traditional chinese localization (thanks to 楊添明).
Fixed in this release:
* [Minor] Fallback TRC tags were created using a wrong backward
matrix when using ArgyllCMS 2.0.2b or newer.
* [Trivial] When connecting to a pattern generator, closing the
connection dialog should be equivalent to cancelling.
* [Cosmetic] [UI] Show a dialog while the UI is blocked when
connecting to madTPG.
* [Cosmetic] [UI] Do not show the visual whitepoint editor
fullscreen warning if using a pattern generator.
* [Cosmetic] [UI] Synthetic ICC creator: Set chromatic adaptation
up/down arrow increment to 0.0001.
* [Cosmetic] [UI] Synthetic ICC creator: Hide (unused) hue &
saturation controls for SMPTE 2084 hard clip.
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2019-01-26 18:17:26
|
Changed in this release: * [Enhancement] Changed full field pattern insertion interval and duration granularity to 0.1 seconds. * [Enhancement] Store and read full field pattern insertion parameters from profile. Fixed in this release: * [Minor] Full field pattern insertion should not run during display update delay measurements and requires an extra delay after being shown. * [Cosmetic] [UI] Include full field pattern insertion in estimated measurement time calculation. -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2018-12-03 01:57:46
|
Changed in this release: * [Cosmetic] [UI] Show ColorMunki spectrometer as “ColorMunki Design/Photo, i1Studio” in instrument dropdown for better differentiation from “ColorMunki Display” and “ColorMunki Smile” colorimeters. Fixed in this release: * [Minor]: UnicodeError when trying to access 3rd-party ICC v4 profiles MultiLocalizedUnicodeType tags with non-US/UK country code(s) for english language. * [Minor] Profile loader (Windows): Work-around an incompatibility with Wacom tablets (tray icon right-click popup menu didn't work). * [Minor] macOS: Creating a colorimeter correction didn't work if the display manufacturer couldn't be determined automatically (regression of autocomplete change in DisplayCAL 3.7 due to undocumented wxPython incompatibility). -- Florian Höch https://displaycal.net |
|
From: Florian H. <fl...@di...> - 2018-11-14 22:19:33
|
Fixed in this release:
* [Regression]: Display enumeration didn't work correctly due to
3.7.1 full field pattern insertion change for ArgyllCMS 2.0.2b.
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2018-11-02 00:30:37
|
* [Enhancement] Measurement report: Updated Fogra Media Wedge V3
evaluation criteria to ISO 12647-7:2016 version of the standard
(use ΔE*00 and ΔCh for CMY gray).
* [Enhancement] Measurement report: Moved ΔICtCp to general
evaluation criteria so it can be shown in the additional
statistics for all available criteria.
* [Enhancement] Updated simplified chinese translation (thanks to
Mars).
* [Enhancement] Full field pattern insertion: Support the latest
ArgyllCMS 2.0.2 Beta development code.
* [Enhancement] [UI] Consistency: When changing the verification
chart, set the simulate whitepoint relative to display profile
whitepoint option according to the simulation profile (just as
when changing the simuation profile itself) and don't reset the
simulate whitepoint option when changing the simulation
profile.
* [Cosmetic] Automatically fall back to the default verification
chart if the selected one no longer exists (due to the chart
file having been moved or deleted).
* [Cosmetic] Detect highly non-monotonic luminance responses when
creating shaper curves (intended to let creating a profile from
highly non-monotonic measurements fail just as before, but with
a nicer, more descriptive error message instead of the raw
exception from the underlying fitting function).
* [Cosmetic] When creating a profile fails and results in an
error dialog, do not show the superfluous additional “profiling
not finished” message.
* [Minor] Restored the ability to create colorimeter corrections
for virtual displays, which was accidentally removed in
DisplayCAL 3.7.
--
Florian Höch
https://displaycal.net
|
|
From: Florian H. <fl...@di...> - 2018-10-10 23:07:54
|
Added in this release: * [Feature] Full field pattern insertion option for selected pattern generators (madTPG*, Prisma and Resolve). Note that madTPG on Windows requires using a modified version of ArgyllCMS. * [Feature] Chromatic adaptation control for the synthetic ICC profile creator. * Resolve HDR 3D LUT preset (SMPTE 2084 hard clip, no tonemapping). Changed in this release: * [Enhancement] Show a column with the spectral resolution and range of the reference measurements when listing colorimeter corrections from the online database (if available). * [Enhancement] Improved support for (3rd party) profiles with chromatic adaptation transforms other than Bradford, e.g. for use as 3D LUT source profiles. * [Enhancement] Early abort when cancelling video level detection measurements. * [Enhancement] Early abort if connecting to madTPG fails. * [Enhancement] Updated simplified chinese translation (thanks to Mars). * [Enhancement] If using madTPG and continuing from interactive adjustment to iterative grayscale calibration, wait three seconds after switching to fullscreen and exclusive fullscreen respectively, to give the display time to complete the switch, before commencing measurements. * [Enhancement] Show messages from instrument related popup dialogs during measurements on the madTPG on-screen display as well. * Hue preservation less than 100% for HDR SMPTE 2084 3D LUTs with roll- off tonemapping now only affects red-orange/orange/amber hues (i.e. match madVR’s “color tweaks for fire & explosions”). * [Enhancement] Verification: Before attempting to create a measurement report, automatically check the PCS to device table resolution for LUT profiles if necessary and warn about low resolution tables. * [Enhancement] 3D LUT verification: When using a different whitepoint target for a 3D LUT, use the altered source profile as simulation profile for verification. * [Enhancement] 3D LUT verification: When creating a self check report, automatically use the device link profile. * [Enhancement] Measurement report: Show weighted ΔL, ΔC and ΔH for ΔE*94 and ΔE*00. * [Enhancement] Measurement report: Signed values for ΔL*76, ΔL*94, ΔC*76 and ΔC*94 are now always relative to the nominal values (match ΔE*00 and ΔICtCp). * [Enhancement] Measurement report: Measured vs display profile whitepoint is now a purely informational statistic, no longer a pass criteria. * [UI] When creating a colorimeter correction, allow selecting a display manufacturer via autocomplete if not set. * [UI] [Cosmetic] Minor UI spacing adjustments. * [Cosmetic] For HDR 3D LUTs with SMPTE 2084 (hard clip) tone curve, set the mastering display peak luminance in the simulation profile description to the target peak. * [Enhancement] macOS: For iMacs, use the model identifier as display description. Fixed in this release: * [Minor] Interpolation between clipping and roll-off for HDR 3D LUTs with SMPTE 2084 tone curve was not as smooth as intended with mastering display peak luminance below 10000 cd/m² or just above target peak. * [Minor] HDR 3D LUTs with SMPTE 2084 (hard clip) tone curve did reproduce slightly too low luminance in a limited region below the chosen target peak. * [Minor] Verification controls were not being initialized if loading settings before switching to the verification tab. * [Trivial] Also update verification tone curve controls if a matrix profile with non-identical shaper curves is selected as simulation profile. * [Trivial] Make eeColor to madVR converter exit cleanly when receiving SIGBREAK. * [Trivial] Correctly escape/unescape quotes in CGATS. * [Trivial] Reset enumerated measurement modes when changing Argyll version. * [Trivial] Do not automatically disable interactive display adjustment after visual whitepoint editor measurement. * [Trivial] When using madTPG, restore fullscreen and OSD button states when continuing on to calibration after interactive adjustment. * [Trivial] madTPG did not automatically enter fullscreen if enabled when skipping interactive display adjustment and detecting video levels. * [Trivial] Only show the place instrument on screen countdown in madTPG if we don’t temporarily leave fullscreen for interactive adjustment during calibration anyway. * [Trivial] Always force HDR 3D LUT SMPTE 2084 mastering display peak luminance to be greater than or equal to target peak luminance. * [Cosmetic] Do not show HDR 3D LUT tone mapping hue/saturation controls for SMPTE 2084 (hard clip). * [Minor] Measurement report: Measured vs assumed/profile whitepoint delta ICtCp should always be referenced to assumed/profile whitepoint. * [Minor] Measurement report: Using absolute values without display profile whitepoint as reference in ICtCp mode referenced the values to D50 instead of the natural ICtCp whitepoint of D65. * [Cosmetic] Measurement report: RGB color comparison swatches when using absolute values and display profile whitepoint as reference were not referenced to chosen whitepoint. * [Trivial] Profile information: Whitepoint delta E to locus should always be referenced to locus, not D50. * [Cosmetic] Profile information: Use correct axis labels for DIN99b 2D gamut plot. * [Minor] Standalone 3D LUT maker: Unmatched Thaw() call when setting abstract profile. * [Minor] Linux: Prevent potential subprocess memory leak. * [Minor] Linux, macOS: When connecting to madTPG, don’t send ‘bye’ commands when closing duplicate connections so madTPG doesn’t close the main connection prematurely. * [Trivial] Linux with wxPython Phoenix, Windows: Menu item labels in submenus weren’t updated until restarting the application after switching to a different language. * [Trivial] Profile loader (Windows): Use Unicode APIs for creating the popup menu items, so that they are displayed correctly regardless of Windows codepage (makes non-western languages display correctly on western versions of Windows). * [Trivial] Windows: Restore compatibility of measurement report with MSIE 11. * [Cosmetic] macOS: When creating a colorimeter correction for a MacBook, correctly unescape backslashes in the automatically filled description. -- Florian Höch |
2 messages has been excluded from this view by a project administrator.