- This topic has 4 replies, 3 voices, and was last updated 1 year ago by
.
-
Posts
-
Hello,
I have an issue with display cal, using a laptop + 3 monitors.
Once i press the button to start calibration on the main UI, display cal shows 3 to 4 patches to test the monitor/calibrator interaction, it will read if anything is being picked up. After this, you can adjust your RGB, brightness, and go into the actual calibration proces. If nothing is picked up, a popup is being displayed to “retry”.
Now, i am forced to always place the calibrator on my laptop screen first, during this pre-calibration period, to make it get to the next RGB/brightness window, regardless of which monitor i have selected for calibration. It simply won’t display the pre-calibration patches on any other monitor other than my main (laptop). Once i get through this process, i remove the calibrator from the laptop screen and place it on the monitor i actually selected to calibrate, and can continue the process just fine.
My concern is the pre-calibration fase is relevant to the calibration itself, and/or somehow registered/stored into the profile. Or perhaps the laptop screen is being addjusted in this fase, instead of the monitor i am going to actually calibrate consecutively. Is this the case? if not, my workaround for the issue is sufficient.
For your info, changing the monitor to “main display” or disconnecting any of the other 2 won’t fix the issue.
Thanks :- )
How do you connect 3 monitors to a laptop? I think the only thing to do is make 1 monitor connected a time and calibrate it. Rember which profile goes to which monitor and then set the profiles up to the right monitor with Displaycal profiler.
That’s not the issue here, the issue remains with just 1 monitor connected.
I guess its a bug in display cal, for which i have found a way to circumvent. I just need to know whether my solution affects my calibration.
I have logged the following github issue for the Python (updated) version of displaycal: https://github.com/eoyilmaz/displaycal-py3/issues/566
I’ve never seen such issue. Try to run basic “dispcal” argyll app with -R or -r and the parameter for your display number and see if this happens and window shows in your chosen display.
If it does, it seems a DisplayCAL argument bug, passed to argyllCMS, although I have not seen such issue on multimonitor macintel with 3.9.16. If it does not it’s an Argylll app issue on your setup and must be directed to argyllcms mailist.As a general rule when you encounter a measurement issue, first of all check commandline on ArgyllCMS.
