- This topic has 17 replies, 9 voices, and was last updated 3 days, 1 hour ago by
.
-
Posts
-
I’m not sure how to debug this. I think this is an issue with windows displaycal 3.8.9.3. Everything works when using argyll command line. Does not happen in displaycal flatpak for linux.
Did it happen on first run of 3.0.0 or it happens all the time? Has Windows requested ypu to update firewall policy due to new dispcal.exe?
Doesn’t work with Windows 11, first stuck at after setting up instrument, reboot helped, but again stops working at about 10 min.
I’ve tested it in W11 (VM), it happens as Voicemail describes, BUT if you run argyllcms in commandline, for example a (un)caibrated display report it runs without issue so it seems that there is an issue in DisplayCAL + W11.
In W10 DisplayCAL + ArgyllCMS 3.0 works fine, at least with my i1d3. Mine is i1d3 rev A and Voicemail is rev B so it is not related to some colorimeter issue.Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.i got same problem on diffent PC and laptop
Equipment:i1d3+display pro (I rent it)
WIN10+5900X+3080Ti
WIN11+ASUS TX GAMING 2023(only sell in China,13700H+4060)
WIN11+CLEVO V15-17（i7 12650H+4060）
all of these will stop at “setting up instrument” in normal operation. But if i change back to 2.3.9, every problem solved.
i got same problem on diffent PC and laptop
Equipment:i1d3+display pro (I rent it)
WIN10+5900X+3080Ti
Non happening for me on 3 computers, seems to be dependent on your particular setup or drivers
WIN11+ASUS TX GAMING 2023(only sell in China,13700H+4060)
WIN11+CLEVO V15-17（i7 12650H+4060）
all of these will stop at “setting up instrument” in normal operation. But if i change back to 2.3.9, every problem solved.
Happens to me in a VM machine with W11, same error as other users reported… but only with DisplayCAL, not with argyllcms commandline, so this one seems to be repated to DisplayCAL + w11 and its a generalized issue.
i got same problem on diffent PC and laptop
Equipment:i1d3+display pro (I rent it)
WIN10+5900X+3080Ti
all of these will stop at “setting up instrument” in normal operation. But if i change back to 2.3.9, every problem solved.
after downgrading to Windows 10, I had the same problem as Mike. Turns out the error only happens with 64 bit version of argyll 3.0.0. using 32 bit version works. I’m not 100% sure if this is also the case with windows 11.
I did not see that on W10 but I just saw “Colorant -N” issue when making an HDR LUT3D with Argyll3.0 as sombody pointed in a thread not long ago.
I did not see that on W10 but I just saw “Colorant -N” issue when making an HDR LUT3D with Argyll3.0 as sombody pointed in a thread not long ago.
I pointed it out, why do you think, it gives the error?
I did not see that on W10 but I just saw “Colorant -N” issue when making an HDR LUT3D with Argyll3.0 as sombody pointed in a thread not long ago.
I pointed it out, why do you think, it gives the error?
I need to try if this happens in SDR Rec709 simulation.
IDNK the output command to collink by DisplayCAL. If you run standalone LUT3D creator I think that it does not write to main log. The point is getting actual commandline sent to “collink”, execute it commandline and if i does not run without errors chop some params till it run smooth. Then report it to ArgyllCMS.
But IDNK if this issue is in argyllcms new functionality or in DIsplayCAL interaction with ArgyllCMS, like the issues I saw in W11 with Argyll 3. Commandline I can run an uncalibrated display reprot but i cannot do that using DIsplayCAL (w11 virtualized).
This will happen if running commandline the whole collink line with params it runs without errors.
