#34107 (Bug) Profile created is named after display that was calibrated the last time DisplayCAL ran instead of the most recent display
It’s possible for DisplayCAL to create a profile named after the display that was calibrated the last time DisplayCAL ran rather than being named after the display that was just calibrated.
Steps to Reproduce the Issue:
- Turn on computer.
- Plug in the ColorMunki Photo (spectrophotometer).
- Start DisplayCAL (last monitor calibrated was a Dell P2418D).
- Change the Display to “Web @ localhost”.
- Do the whitepoint/brightness part of the calibration.
- Stop the calibration.
- Exit DisplayCAL.
- Possibly restart the entire computer/disconnect and reconnect the ColorMunki.
- Make the secondary monitor (Asus VS229) the primary monitor using the Display window in the Windows Settings.
- Turn off the Dell P2418D, which used to be the primary monitor.
- Start DisplayCAL.
- Change the Display to “ASUS VS229”.
- Do a full normal calibration.
The name of the profile’s folder & files should include “ASUS VS229”.
The calibration folder and files have names that begin with “Web 2022-02-04 00-08 D6500 sRGB F-S XYZLUT+MTX”.
Rename the profile’s folder and all the files inside as described in https://hub.displaycal.net/forums/topic/rename-a-profile/.
- DisplayCAL 220.127.116.11
- Windows 10 Version 21H1 (OS Build 19043.1348), EN-US
- Primary monitor: Dell P2418D (2560×1440, 60Hz)
- Secondary monitor: Asus V229 (1080×1920, 60Hz)
Logs are attached.
logs (application/zip | 2022-02-04 22:39:08)