- This topic has 37 replies, 10 voices, and was last updated 5 months ago by
.
-
Posts
-
Not sure what an ‘N-component Input Colorant Identification’ is. Maybe ask on the ArgyllCMS mailing list?
I think there are some breaking changes with v3.0.0 with DisplayCAL. DisplayCAL gets stuck at “setting up instrument” when profiling with a Calibrite Colorchecker, in Windows.
Separately, DisplayCAL crashes on MacOS Sonoma upon boot. So the compatibility issues are getting real.
ArgyllCMS v3 is working fine with DisplayCAL, I’ve done a complete calibration + profile run without any issues.
ArgyllCMS v3 is working fine with DisplayCAL, I’ve done a complete calibration + profile run without any issues.
Hard to believe, but ok. I guess some of us will stick with argyll 2.3.1.
The problem is when trying to create a BT.2020 3dlut hdr to sdr from previous calibration. Creating BT.709 3dlut works ok.
ArgyllCMS v3 is working fine with DisplayCAL, I’ve done a complete calibration + profile run without any issues.
Don’t think I’m alone, see here. Will get some debug logs when I’ve got the time.
Displaycal Windows Argyll 3.0.0 stuck after setting up instrument
BTW, good to see you back online.
Have you tried re-creating the 3D LUT with Argyll v3? The tag it’s complaining about is an Argyll v2.x tag, v3 doesn’t write it.
I noticed that when making BT.709 3dlut form previous calibration is 3 times faster with argyll 3.0.0, but why there is a problem with BT.2020 hdr to sdr 3dlut from the same previous calibration?
Argyll v3.0.1 should solve any remaining problems with creating devicelink profiles and thus 3D LUTs.
Argyll v3.0.1 should solve any remaining problems with creating devicelink profiles and thus 3D LUTs.
Thank you, Florian. I’ll test the new version.
tried with 32 and 64 bit same error, native Windows 11, no problems with 2.3.1.
Did you try to run it command line? dispcal -r or spotread. I mean, try to find the source of the error: ArgyllCMS 3.0.1 or Argyllcms<->DisplayCAL communication.
