This repository was archived by the owner on Apr 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 84
Expand file tree
/
Copy pathREADME.html
More file actions
2363 lines (1896 loc) · 243 KB
/
README.html
File metadata and controls
2363 lines (1896 loc) · 243 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<!--[if lte IE 8 ]>
<html class="ie_lte_8">
<![endif]-->
<!--[if (gt IE 8)|!(IE) ]><!-->
<html lang="en">
<!--<![endif]-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width" />
<title>DisplayCAL—Display Calibration and Characterization powered by ArgyllCMS</title>
<meta name="description" content="Display calibration and profiling with a focus on accuracy and versatility" />
<meta property="og:description" content="Display calibration and profiling with a focus on accuracy and versatility" />
<meta property="fb:app_id" content="210635659357680" />
<meta property="og:url" content="http://displaycal.net/" />
<meta property="og:image" content="http://displaycal.net/theme/icons/256x256/displaycal.png" />
<link rel="shortcut icon" href="theme/icons/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" href="https://displaycal.net/shariff/shariff.complete.css?version=7.1.1&ts=2018-02-28T01:27" />
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato%3A400%2C700%2C900%2C400italic%2C700italic&subset=latin%2Clatin-ext" type="text/css" media="all" />
<link rel="stylesheet" href="theme/readme.css?ts=2019-12-14T13:00" />
<link rel="stylesheet" href="theme/slimbox2/slimbox2.css?ts=2018-01-17T17:39" />
<link rel="stylesheet" href="theme/prism.css" />
<script type="text/javascript" src="theme/jquery.js?ts=2018-09-17T15:00"></script>
<script type="text/javascript" src="theme/jquery.scrollTo.js?ts=2018-09-17T15:00"></script>
<script type="text/javascript" src="theme/jquery.localscroll.js?ts=2018-09-17T15:00"></script>
<script type="text/javascript" src="theme/slimbox2/slimbox2.js?ts=2015-09-01T14:54"></script>
<script type="text/javascript" src="theme/readme.js?ts=2018-09-17T15:30"></script>
</head>
<body>
<div id="header">
<div id="title-wrapper">
<div id="title">
<h1><img src="theme/icon-reflection.png" alt="" /> <a href="https://displaycal.net/"><span class="appname">Display<span>CAL</span></span></a><span><span class="dash">—</span><!--span class="formerly-known-as">Formerly known as dispcalGUI<br /></span-->Display Calibration and Characterization powered by <a href="https://www.argyllcms.com">ArgyllCMS</a></span></h1>
<p class="shariff" data-lang="en" data-services="["facebook","googleplus","linkedin","twitter","info"]" data-theme="white" data-backend-url="https://displaycal.net/shariff/index.php" data-url="http://displaycal.net/" data-info-url="https://github.com/heiseonline/shariff"></p>
</div>
<div id="site-navigation">
<ul>
<li><a href="https://displaycal.net/news/">News</a></li>
<li><a href="https://displaycal.net/forums/">Forums</a></li>
<li><a href="https://displaycal.net/issues/">Issue Tracker</a></li>
<li><a href="https://displaycal.net/wiki/">Wiki</a></li>
</ul>
</div>
</div>
<div id="header-inner-overlay"></div>
</div>
<div id="intro">
<div id="friendlybox">
<div id="get">
<h2 id="version">3.8.9.3 </h2>
<p>2019-12-14 12:14 UTC</p>
<ul>
<li class="download"><a href="#download">Get DisplayCAL</a></li>
<li class="requirements"><a href="#requirements">System requirements</a></li>
<li class="changelog"><a href="CHANGES.html" target="_blank">What's new in this version</a></li>
</ul>
</div>
<ul class="complementary">
<li class="about"><a href="#about">About</a></li>
<li class="quickstart"><a href="#quickstart">Quickstart guide</a></li>
<li class="toc"><a href="#toc">Documentation</a></li>
<li class="help"><a href="#help">Get help</a></li>
<li class="reportbug"><a href="#reportbug">Report a bug</a></li>
<li class="donate"><a href="#donate">Contribute</a></li>
</ul>
</div>
<p id="teaser">
<a href="#screenshots" title="View screenshots"><img src="theme/DisplayCAL-adjust-reflection.png" alt="" /></a>
</p>
</div>
<div id="donation-box">
<div id="donate">
<h2 style="margin-top: 0">Your support is appreciated!</h2>
<p>If you would like to support the development of, technical assistance with, and continued availability of DisplayCAL and ArgyllCMS, please consider a financial contribution.
As DisplayCAL wouldn't be useful without ArgyllCMS, all contributions received for DisplayCAL will be split between both projects.<br />
For light personal non-commercial use, a one-time contribution may be appropriate.
If you're using DisplayCAL professionally, an annual or monthly contribution would make a great deal of difference in ensuring that both projects continue to be available.</p>
<p>If you have decided to contribute (many thanks!), but you'd like to give to <a href="https://www.argyllcms.com">ArgyllCMS</a> directly on your own behalf (visit <a href="https://www.argyllcms.com">argyllcms.com</a> and scroll down a bit to get to its contribution links), please leave a message on your DisplayCAL contribution if contributing to both projects. Please note that if your contribution should be put towards adding a certain feature in ArgyllCMS, like support for a specific instrument, it will be more appropriate and efficient to <a href="https://www.argyllcms.com">contribute to ArgyllCMS only</a>, and directly.</p>
<form id="donationform" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<fieldset style="border: 1px solid #ccc; border-radius: 5px; padding: 0 9px;">
<legend style="padding: 0 3px;">Contribute using PayPal</legend>
<noscript><strong>Please enable JavaScript!</strong></noscript>
<p>
<input id="credit_card" type="checkbox" onchange="document.forms['donationform'].elements['cmd'].value = this.checked ? '_xclick' : '_donations'" style="margin-left: 0; vertical-align: text-top;" /> <label for="credit_card" style="display: inline-block; max-width: 90%; vertical-align: top;"><span>(Optional)</span> Use a credit card or bank transfer without a PayPal account</label><br />
<span style="display: inline-block; line-height: 1.4em; margin-bottom: .5em; padding-left: 1.6em;">(PayPal does not guarantee the availability of payment via credit card or bank transfer)</span><br />
<input id="public_thanks_opt_in" type="checkbox" onchange="document.forms['donationform'].elements['item_name'].value = this.checked ? 'DisplayCAL Contribution (show name publicly)' : 'DisplayCAL Contribution'" style="margin-left: 0; vertical-align: text-top;" /> <label for="public_thanks_opt_in" style="display: inline-block; max-width: 90%; vertical-align: top;"><span>(Optional)</span> Include my name in the “<a href="#thanks">Thanks and acknowledgements</a>” section</label><br />
<input type="hidden" name="cmd" value="_donations" />
<input type="hidden" name="business" value="CEZVJ89TTS6FY" />
<input type="hidden" name="item_name" value="DisplayCAL Contribution" />
<input type="hidden" name="no_shipping" value="1" />
<input type="hidden" name="lc" value="US" />
<input type="hidden" name="return" value="https://displaycal.net/contribution_thank_you.html">
<input type="hidden" name="image_url" value="https://displaycal.net/theme/icons/48x48/displaycal.png">
<input type="hidden" name="cpp_header_image" value="https://displaycal.net/theme/displaycal-paypal-cpp_header_image.png">
<select id="contribution_amount" name="amount">
<option disabled="disabled">Home / Enthusiast Use</option>
<option value="10">10</option>
<option value="20" selected="selected">20</option>
<option value="30">30</option>
<option value="40">40</option>
<option value="50">50</option>
<option value="75">75</option>
<option disabled="disabled">Professional / Business Use</option>
<option value="100">100</option>
<option value="150">150</option>
<option value="200">200</option>
<option value="250">250</option>
<option value="300">300</option>
<option value="350">350</option>
</select>
<select name="currency_code">
<option value="EUR" selected="selected">€ Euro</option>
<option value="GBP">£ Pound</option>
<option value="AUD">$ Australian Dollar</option>
<option value="CAD">$ Canadian Dollar</option>
<option value="USD">$ US Dollar</option>
</select> 
<button type="submit" class="paypal" disabled="disabled">Contribute</button>
<button type="button" class="paypal" disabled="disabled" onclick="contribute_own_amount(); jQuery(this).remove()">Own amount</button>
</p>
</fieldset>
</form>
<script type="text/javascript">
//<![CDATA[
(function () {
document.forms['donationform'].elements['lc'].value = (navigator.language || navigator.userLanguage || 'US').split('-').pop().toUpperCase();
setTimeout(function () {
var btns = document.getElementsByTagName('button'), i;
for (i = 0; i < btns.length; i ++) {
btns[i].disabled = false;
}
}, 1500);
})();
function contribute_own_amount() {
jQuery('#contribution_amount').replaceWith('<input type="number" name="amount" min="5" value="' + jQuery('#contribution_amount').val() + '" />')
}
//]]>
</script>
<span>(For other means of contributing, please <a href="https://displaycal.net/?fhpe=x52nps3G0aGVoafU0cTalJmgktPI1Q%3D%3D" rel="nofollow">contact me</a>)</span>
<p>Thanks to all contributors!</p>
<p>Special thanks to the following people and organizations:</p>
<p>Riley Brandt Photography—<a href="http://www.rileybrandt.com/lessons/">The Open Source Photography Course</a></p>
</div>
</div>
<div class="infobox" style="margin-top: 78px">
<p><a href="https://www.argyllcms.com/pro/" title="ArgyllPRO ColorMeter"><img src="https://displaycal.net/img/argyllpro-small.png" alt="" style="float: left; margin-left: -38px; margin-right: 8px; margin-top: -64px" /></a> <strong>If you'd like to measure color on the go</strong>, you may also be interested in <a href="https://www.argyllcms.com/pro/"><strong>ArgyllPRO ColorMeter</strong></a> by Graeme Gill, author of ArgyllCMS. <strong>Available for Android</strong> from the Google Play store. <a href="https://youtu.be/ODfCoUH0euQ" title="ArgyllPRO ColorMeter 2 Minute Overview + Guided Tour Video">Check out the 2 Minute Overview + Guided Tour Video.</a></p>
</div>
<div id="content">
<div id="toc">
<h2>Table of contents</h2>
<ul>
<li><a href="#about">About DisplayCAL</a>
</li>
<li><a href="#disclaimer">Disclaimer</a></li>
<li><a href="#download">Download</a></li>
<li><a href="#quickstart">Quickstart guide</a></li>
<li><a href="#requirements">System requirements and other prerequisites</a>
<ul>
<li><a href="#requirements">General system requirements</a></li>
<li><a href="#argyll">ArgyllCMS</a></li>
<li><a href="#instruments">Supported instruments</a></li>
<li><a href="#requirements-unattended">Additional requirements for unattended calibration and profiling</a></li>
<li><a href="#requirements-source">Additional requirements for using the source code</a></li>
</ul>
</li>
<li><a href="#install">Installation</a></li>
<li><a href="#concept">Basic concept of display calibration</a></li>
<li><a href="#colorimeter-corrections">A note about colorimeters, displays and DisplayCAL</a></li>
<li><a href="#usage">Usage</a>
<ul>
<li><a href="#usage">General usage</a></li>
<li><a href="#settingsfile">Settings</a></li>
<li><a href="#presets">Predefined settings (presets)</a></li>
<li><a href="#display_instrument">Choosing a display and measurement device</a></li>
<li><a href="#settings_calibration">Calibration settings</a></li>
<li><a href="#settings_profiling">Profiling settings</a></li>
<li><a href="#testchart_editor">Testchart editor</a></li>
<li><a href="#calibrating">Calibrating / profiling</a></li>
<li><a href="#create-3dlut">Creating 3D LUTs</a></li>
<li><a href="#verify-profile">Verification / measurement report</a></li>
<li><a href="#special">Special functionality</a>
<ul>
<li><a href="#special">Overview of special functionality</a></li>
<li><a href="#remote">Remote measurements and profiling</a></li>
<li><a href="#madvr">madVR test pattern generator</a></li>
<li><a href="#resolve">Resolve (10.1+) as pattern generator</a></li>
<li><a href="#untethered">Untethered display measurement and profiling</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#menu">Menu commands</a>
<ul>
<li><a href="#menu">List of menu commands</a></li>
<li><a href="#menu-file">File menu</a></li>
<li><a href="#menu-options">Options menu</a></li>
<li><a href="#menu-tools">Tools menu</a></li>
<li><a href="#menu-lang">Language menu</a></li>
</ul>
</li>
<li><a href="#scripting">Scripting</a></li>
<li><a href="#userdata">User data and configuration file locations</a></li>
<li><a href="#issues">Known issues & solutions</a></li>
<li><a href="#help">Get help</a></li>
<li><a href="#reportbug">Report a bug</a></li>
<li><a href="#discuss">Discussion</a></li>
<li><a href="#todo">To-Do / planned features</a></li>
<li><a href="#thanks">Thanks and acknowledgements</a></li>
<li><a href="CHANGES.html">Version history / changelog</a></li>
<li><a href="#definitions">Definitions</a></li>
</ul>
</div>
<div id="about">
<h2>About DisplayCAL</h2>
<p>DisplayCAL (formerly known as dispcalGUI) is a display calibration and profiling solution with a focus on <strong>accuracy</strong> and <strong>versatility</strong> (in fact, the author is of the honest opinion it may be the most accurate and versatile ICC compatible display profiling solution available anywhere). At its core it relies on <a href="https://www.argyllcms.com">ArgyllCMS</a>, an advanced open source color management system, to take measurements, create calibrations and profiles, and for a variety of other advanced color related tasks.</p>
<p>Calibrate and characterize your display devices using one of <a href="#instruments">many supported measurement instruments</a>, with support for multi-display setups and a variety of available options for advanced users, such as verification and reporting functionality to evaluate ICC profiles and display devices, creating video 3D LUTs, as well as optional CIECAM02 gamut mapping to take into account varying viewing conditions. Other features include:</p>
<ul>
<li>Support of colorimeter corrections for different display device types to increase the absolute accuracy of colorimeters. Corrections can be imported from vendor software or created from measurements if a spectrometer is available.</li>
<li>Check display device uniformity via measurements.</li>
<li>Test chart editor: Create charts with any amount and composition of color patches, easy copy & paste from CGATS, CSV files (only tab-delimited) and spreadsheet applications, for profile verification and evaluation.</li>
<li>Create synthetic ICC profiles with custom primaries, white- and blackpoint as well as tone response for use as working spaces or source profiles in device linking (3D LUT) transforms.</li>
</ul>
<div>DisplayCAL is developed and maintained by <a href="https://hoech.net/about/">Florian Höch</a>, and would not be possible without <a href="https://www.argyllcms.com">ArgyllCMS</a>, which is developed and maintained by Graeme W. Gill.</div>
<div id="screenshots">
<h3>Screenshots</h3>
<p>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME.png" class="imagelink" data-lightbox="lightbox-set" title="Display & instrument settings"><img src="screenshots/DisplayCAL-screenshot-GNOME-thumb.png" alt="" class="opaque" /></a><br />
<small>Display & instrument settings</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-calibration-settings.png" class="imagelink" data-lightbox="lightbox-set" title="Calibration settings"><img src="screenshots/DisplayCAL-screenshot-GNOME-calibration-settings-thumb.png" alt="" class="opaque" /></a><br />
<small>Calibration settings</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-profiling-settings.png" class="imagelink" data-lightbox="lightbox-set" title="Profiling settings"><img src="screenshots/DisplayCAL-screenshot-GNOME-profiling-settings-thumb.png" alt="" class="opaque" /></a><br />
<small>Profiling settings</small><br /></span>
</p>
<p>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-3DLUT-settings.png" class="imagelink" data-lightbox="lightbox-set" title="3D LUT settings"><img src="screenshots/DisplayCAL-screenshot-GNOME-3DLUT-settings-thumb.png" alt="" class="opaque" /></a><br />
<small>3D LUT settings</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-verification-settings.png" class="imagelink" data-lightbox="lightbox-set" title="Verification settings"><img src="screenshots/DisplayCAL-screenshot-GNOME-verification-settings-thumb.png" alt="" class="opaque" /></a><br />
<small>Verification settings</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-edit-testchart.png" class="imagelink" data-lightbox="lightbox-set" title="Testchart editor"><img src="screenshots/DisplayCAL-screenshot-GNOME-edit-testchart-thumb.png" alt="" class="opaque" /></a><br />
<small>Testchart editor</small><br /></span>
</p>
<p>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-adjust.png" class="imagelink" data-lightbox="lightbox-set" title="Display adjustment"><img src="screenshots/DisplayCAL-screenshot-GNOME-adjust-thumb.png" alt="" class="opaque" /></a><br />
<small>Display adjustment</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-profile-information.png" class="imagelink" data-lightbox="lightbox-set" title="Profile information"><img src="screenshots/DisplayCAL-screenshot-GNOME-profile-information-thumb.png" alt="" class="opaque" /></a><br />
<small>Profile information</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-GNOME-view-curves.png" class="imagelink" data-lightbox="lightbox-set" title="Calibration curves"><img src="screenshots/DisplayCAL-screenshot-GNOME-view-curves-thumb.png" alt="" class="opaque" /></a><br />
<small>Calibration curves</small><br /></span>
</p>
<p>
<span><a href="screenshots/DisplayCAL-screenshot-KDE5.png" class="imagelink" data-lightbox="lightbox-set" title="DisplayCAL under KDE5"><img src="screenshots/DisplayCAL-screenshot-KDE5-thumb.png" alt="" class="opaque" /></a><br />
<small>KDE5</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-Mac.png" class="imagelink" data-lightbox="lightbox-set" title="DisplayCAL under Mac OS X"><img src="screenshots/DisplayCAL-screenshot-Mac-thumb.png" alt="" class="opaque" /></a><br />
<small>Mac OS X</small><br /></span>
<span><a href="screenshots/DisplayCAL-screenshot-Win10.png" class="imagelink" data-lightbox="lightbox-set" title="DisplayCAL under Windows 10"><img src="screenshots/DisplayCAL-screenshot-Win10-thumb.png" alt="" class="opaque" /></a><br />
<small>Windows 10</small><br /></span>
</p>
</div>
</div>
<div id="disclaimer">
<h2>Disclaimer</h2>
<p>This program is free software; you can redistribute it and/or modify it
under the terms of the <a href="LICENSE.txt">GNU General Public License</a> as published by the
<a href="https://fsf.org/">Free Software Foundation</a>; either <a href="LICENSE.txt">version 3 of the License</a>, or (at your
option) any later version.</p>
<p>This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <a href="LICENSE.txt">GNU General Public License</a> for more details.</p>
<p>DisplayCAL is written in <a href="https://python.org/">Python</a> and uses the 3rd-party packages <a href="https://www.numpy.org/">NumPy</a>, <a href="https://wxpython.org/">wxPython</a> (<abbr title="Graphical User Interface">GUI<sup><a href="#definition_GUI">[4]</a></sup></abbr> toolkit), <a href="https://pypi.org/project/certifi/">Certifi</a>, <a href="https://pypi.org/project/PyGObject/">PyGObject</a> or <a href="https://pypi.org/project/dbus-python/">dbus-python</a> for Linux (required for Wayland support with colord), as well as <a href="https://pypi.org/project/pywin32/">Python extensions for Windows</a>, <a href="https://pypi.org/project/comtypes/">comtypes</a> and the <a href="https://pypi.org/project/WMI/">Python WMI module</a> to provide Windows-specific functionality. Other minor dependencies include <a href="https://pypi.org/project/faulthandler/">faulthandler</a>, <a href="https://pypi.org/project/psutil/">psutil</a>, <a href="https://pypi.org/project/PyChromecast/">PyChromecast</a> and <a href="https://pypi.org/project/pyglet/">pyglet</a> (macOS/Windows) or libSDL2 (Linux). It makes extensive use of and depends on functionality provided by <a href="https://www.argyllcms.com/">ArgyllCMS</a>. The build system to create standalone executables additionally uses <a href="https://pypi.org/project/py2app/">py2app</a> on Mac OS X or <a href="https://pypi.org/project/py2exe/">py2exe</a> on Windows. All of these software packages are © by their respective authors.</p>
</div>
<div id="download">
<h2 id="standalone">Get DisplayCAL</h2>
<ul>
<li>
<h3 id="packages">For Linux</h3>
<div>
<p>Native packages for several distributions are available via <a href="https://build.opensuse.org">openSUSE Build Service</a>:</p>
<ul class="packages">
<li>
<span>Arch Linux</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/Arch_Community/x86_64/DisplayCAL.pkg.tar.xz">x86_64</a></span>
</li>
<li>
<span>CentOS 7</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/CentOS_CentOS-7/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Debian 8 (Jessie)</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Debian_8.0/i386/DisplayCAL.deb">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/Debian_8.0/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Debian 9 (Stretch)</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Debian_9.0/i386/DisplayCAL.deb">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/Debian_9.0/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Debian 10 (Buster)</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Debian_10/i386/DisplayCAL.deb">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/Debian_10/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Fedora 29</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/Fedora_29/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Fedora 30</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/Fedora_30/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Fedora 31</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/Fedora_31/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Mageia 6</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Mageia_6/i586/DisplayCAL.rpm">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/Mageia_6/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Mageia 7</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/Mageia_7/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>openSUSE Leap 15.0</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/openSUSE_Leap_15.0/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>openSUSE Leap 15.1</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/openSUSE_Leap_15.1/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>openSUSE Factory</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/openSUSE_Factory/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>openSUSE Tumbleweed</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/openSUSE_Tumbleweed/x86_64/DisplayCAL.rpm">x86_64</a></span>
</li>
<li>
<span>Raspbian 9</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Raspbian_9.0/armhf/DisplayCAL.deb">armv7l</a></span>
</li>
<li>
<span>Raspbian 10</span>
<span><a rel="nofollow" href="https://displaycal.net/download/Raspbian_10/armhf/DisplayCAL.deb">armv7l</a></span>
</li>
<li>
<span>Ubuntu 16.04 (Xenial)</span>
<span><a rel="nofollow" href="https://displaycal.net/download/xUbuntu_16.04/i386/DisplayCAL.deb">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/xUbuntu_16.04/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Ubuntu 18.04 (Bionic)</span>
<span><a rel="nofollow" href="https://displaycal.net/download/xUbuntu_18.04/i386/DisplayCAL.deb">x86</a> |
<a rel="nofollow" href="https://displaycal.net/download/xUbuntu_18.04/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Ubuntu 19.04 (Disco)</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/xUbuntu_19.04/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
<li>
<span>Ubuntu 19.10 (Eoan)</span>
<span>
<a rel="nofollow" href="https://displaycal.net/download/xUbuntu_19.10/amd64/DisplayCAL.deb">x86_64</a></span>
</li>
</ul>
<p>Packages made for older distributions may work on newer distributions as long as nothing substantial has changed (i.e. Python version). Also there are several distributions out there that are based on one in the above list (e.g. Linux Mint which is based on Ubuntu). This means that packages for that base distribution should also work on derivatives, you just need to know which version the derivative is based upon and pick your download accordingly.</p>
<!--p>In all other cases, you can try this universal install that should work on a multitude of distributions:</p-->
</div>
</li>
<li>
<h3>For Mac OS X (10.6 or newer)</h3>
<div>
<p>
<a rel="nofollow" href="https://displaycal.net/download/standalone/DisplayCAL.pkg">Installer Package</a>
</p>
<p><small>If you want to verify the integrity of the downloaded file, compare its SHA-256 checksum to that of the respective entry in the <a href="https://displaycal.net/sha256sums.txt">SHA-256 checksum list</a>. To obtain the checksum of the downloaded file, run the following command in Terminal: <code>shasum -a 256 /Users/<var>Your Username</var>/Downloads/DisplayCAL-3.8.9.3.pkg</code></small></p>
</div>
</li>
<li>
<h3>For Windows</h3>
<div>
<p>
<a rel="nofollow" href="https://displaycal.net/download/standalone/DisplayCAL-Setup.exe">Installer (recommended)</a> or <a rel="nofollow" href="https://displaycal.net/download/standalone/DisplayCAL-win32.zip">ZIP archive</a>
</p>
<p><small>If you want to verify the integrity of the downloaded file, compare its SHA-256 checksum to that of the respective entry in the <a href="https://displaycal.net/sha256sums.txt">SHA-256 checksum list</a> (case does not matter). To obtain the checksum of the downloaded file, run the following command in a Windows PowerShell command prompt: <code>get-filehash -a sha256 C:\Users\<var>Your Username</var>\Downloads\DisplayCAL-3.8.9.3-[Setup.exe|win32.zip]</code></small></p>
</div>
</li>
<li>
<h3>Source code</h3>
<div>
<p>You need to have a working Python installation and all <a href="#requirements-source">requirements</a>.</p>
<p><a rel="nofollow" href="https://displaycal.net/download/DisplayCAL.tar.gz">Source Tarball</a></p>
<p><small>If you want to verify the integrity of the downloaded file, compare its SHA-256 checksum to that of the respective entry in the <a href="https://displaycal.net/sha256sums.txt">SHA-256 checksum list</a>. To obtain the checksum of the downloaded file, run the following command:<br />
Linux: <code>sha256sum /home/<var>Your Username</var>/Downloads/DisplayCAL-3.8.9.3.tar.gz</code><br />
macOS: <code>shasum -a 256 /Users/<var>Your Username</var>/Downloads/DisplayCAL-3.8.9.3.tar.gz</code><br />
Windows (PowerShell command prompt): <code>get-filehash -a sha256 C:\Users\<var>Your Username</var>\Downloads\DisplayCAL-3.8.9.3.tar.gz</code></small></p>
<p>
Alternatively, if you don't mind trying out development code, <a href="https://sourceforge.net/p/dispcalgui/code/">browse the </a><abbr title="Subversion"><a href="https://sourceforge.net/p/dispcalgui/code/">SVN</a><sup><a href="#definition_SVN">[8]</a></sup></abbr><a href="https://sourceforge.net/p/dispcalgui/code/"> repository of the latest development version</a> (or do a full checkout using <code>svn checkout svn://svn.code.sf.net/p/dispcalgui/code/trunk displaycal</code>). But please note that the development code might contain bugs or not run at all, or only on some platform(s). Use at your own risk.
</p>
</div>
</li>
</ul>
<p>Please continue with the <a href="#quickstart">Quickstart Guide</a>.</p>
</div>
<div id="quickstart">
<h2>Quickstart guide</h2>
<p>This short guide intends to get you up and running quickly, but if you run into a problem, please refer to the full <a href="#requirements">prerequisites</a> and <a href="#install">installation</a> sections.</p>
<ol>
<li>
<p>Launch DisplayCAL. If it cannot find ArgyllCMS on your computer, it will prompt you to automatically download the latest version or select the location manually.</p>
</li>
<li>
<p class="info"><strong>Windows only:</strong> If your measurement device is <strong>not</strong> a ColorMunki Display, i1 Display Pro, Huey, ColorHug, specbos, spectraval or K-10, you need to install an Argyll-specific driver before continuing (the specbos, spectraval and K-10 may require the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI virtual COM port driver</a> instead). Select “Instrument” › “Install ArgyllCMS instrument drivers...” from the “Tools” menu. See also <a href="#install-windows-driver">“Instrument driver installation under Windows”.</a></p>
<p class="info"><strong>Mac OS X only:</strong> If you want to use the HCFR colorimeter, follow the instructions in the “HCFR Colorimeter” section under “<a href="https://www.argyllcms.com/doc/Installing_OSX.html">Installing ArgyllCMS on Mac OS X</a>” in the ArgyllCMS documentation before continuing.</p>
<p>Connect your measurement device to your computer.</p>
</li>
<li>
<p>Click the small icon with the swirling arrow <img src="theme/refresh.svg" alt="" /> in between the “Display device” and “Instrument” controls to detect connected display devices and instruments. The detected instrument(s) should show up in the “Instrument” dropdown.</p>
<p class="info"><strong>If your measurement device is a Spyder2</strong>, a popup dialog will show which will let you enable the device. This is required to be able to use the Spyder2 with ArgyllCMS and DisplayCAL.</p>
<p class="info"><strong>If your measurement device is a i1 Display 2, i1 Display Pro, ColorMunki Display, DTP94, Spyder2/3/4/5</strong>, a popup dialog will show and allow you to import generic <a href="#colorimeter-corrections">colorimeter corrections</a> from the vendor software which may help measurement accuracy on the type of display you're using. After importing, they are available under the “Correction” dropdown, where you can choose one that fits the type of display you have, or leave it at “Auto” if there is no match. <em>Note:</em> Importing from the Spyder4/5 software enables additional measurement modes for that instrument.</p>
</li>
<li>
<p>Click <strong>“Calibrate & profile”</strong>. That's it!</p>
<p>Feel free to check out the <a href="https://displaycal.net/wiki/">Wiki</a> for guides and tutorials, and refer to the <a href="#concept">documentation</a> for advanced usage instructions (optional).</p>
<p class="info"><strong>Linux only:</strong> If you can't access your instrument, choose “Install ArgyllCMS instrument configuration files...” from the “Tools” menu (if that menu item is grayed out, the ArgyllCMS version you're currently using has probably been installed from the distribution's repository and should already be setup correctly for instrument access). If you still cannot access the instrument, try unplugging and reconnecting it, or a reboot. If all else fails, read “<a href="https://www.argyllcms.com/doc/Installing_Linux.html">Installing ArgyllCMS on Linux: Setting up instrument access</a>” in the ArgyllCMS documentation.</p>
</li>
</ol>
</div>
<div id="requirements">
<h2>System requirements and other prerequisites</h2>
<div>
<h3>General system requirements</h3>
<ul>
<li>A recent Linux, macOS (10.6 or newer, recommended 10.7 or newer) or Windows (recommended Windows 7 or newer) operating system.</li>
<li>“True color” 24 bits per pixel or higher graphics output.</li>
</ul>
<h3>Hardware requirements</h3>
<ul>
<li>Minimum: 1 GHz single core processor, 1.5 GB RAM, 500 MB free storage space.</li>
<li>Recommended: 2 GHz dual core processor or better, 4 GB RAM or more, 1 GB free storage space or more.</li>
</ul>
</div>
<div id="argyll">
<h3>ArgyllCMS</h3>
<p>To use DisplayCAL, you need to download and install <a href="https://www.argyllcms.com">ArgyllCMS</a> (1.0 or newer).</p>
</div>
<div id="instruments">
<h3>Supported instruments</h3>
<p>You need one of the supported instruments to make measurements. All instruments supported by ArgyllCMS are also supported by DisplayCAL. For display readings, these currently are:</p>
<h4>Colorimeters</h4>
<ul>
<li>CalMAN X2 (treated as i1 Display 2)</li>
<li>Datacolor/ColorVision Spyder2</li>
<li>Datacolor Spyder3 (since ArgyllCMS 1.1.0)</li>
<li>Datacolor Spyder4 (since ArgyllCMS 1.3.6)</li>
<li>Datacolor Spyder5 (since ArgyllCMS 1.7.0)</li>
<li>Datacolor SpyderX (since ArgyllCMS 2.1.0)</li>
<li>Hughski ColorHug (Linux support since ArgyllCMS 1.3.6, Windows support with newest ColorHug firmware since ArgyllCMS 1.5.0, fully functional Mac OS X support since ArgyllCMS 1.6.2)</li>
<li>Hughski ColorHug2 (since ArgyllCMS 1.7.0)</li>
<li>Image Engineering EX1 (since ArgyllCMS 1.8.0)</li>
<li>Klein K10-A (since ArgyllCMS 1.7.0. The K-1, K-8 and K-10 are also reported to work)</li>
<li>Lacie Blue Eye (treated as i1 Display 2)</li>
<li>Sencore ColorPro III, IV & V (treated as i1 Display 1)</li>
<li>Sequel Imaging MonacoOPTIX/Chroma 4 (treated as i1 Display 1)</li>
<li>X-Rite Chroma 5 (treated as i1 Display 1)</li>
<li>X-Rite ColorMunki Create (treated as i1 Display 2)</li>
<li>X-Rite ColorMunki Smile (since ArgyllCMS 1.5.0)</li>
<li>X-Rite DTP92</li>
<li>X-Rite DTP94</li>
<li>X-Rite/GretagMacbeth/Pantone Huey</li>
<li>X-Rite/GretagMacbeth i1 Display 1</li>
<li>X-Rite/GretagMacbeth i1 Display 2/LT (the HP DreamColor/Advanced Profiling Solution versions of the instrument are also reported to work)</li>
<li>X-Rite i1 Display Pro, ColorMunki Display (since ArgyllCMS 1.3.4. The HP DreamColor, NEC SpectraSensor Pro and SpectraCal C6 versions of the instrument are also reported to work)</li>
</ul>
<h4>Spectrometers</h4>
<ul>
<li>JETI specbos 1211/1201 (since ArgyllCMS 1.6.0)</li>
<li>JETI spectraval 1511/1501 (since ArgyllCMS 1.9.0)</li>
<li>X-Rite ColorMunki Design/Photo (since ArgyllCMS 1.1.0)</li>
<li>X-Rite/GretagMacbeth i1 Monitor (since ArgyllCMS 1.0.3)</li>
<li>X-Rite/GretagMacbeth i1 Pro (the EFI ES-1000 version of the instrument is also reported to work)</li>
<li>X-Rite i1 Pro 2 (since ArgyllCMS 1.5.0)</li>
<li>X-Rite/GretagMacbeth Spectrolino</li>
<li>X-Rite i1Studio (since ArgyllCMS 2.0)</li>
</ul>
<div class="infobox">
<p>If you've decided to buy a color instrument because ArgyllCMS supports it, please let the dealer and manufacturer know that “You bought it because ArgyllCMS supports it”—thanks.</p>
</div>
<p>Note that the <em>i1 Display Pro</em> and <em>i1 Pro</em> are very different instruments despite their naming similarities.</p>
<p>Also there are currently (2014-05-20) five instruments (or rather, packages) under the ColorMunki brand, two of which are spectrometers, and three are colorimeters (not all of them being recent offerings, but you should be able to find them used in case they are no longer sold new):</p>
<ul>
<li>The <em>ColorMunki Design</em> and <em>ColorMunki Photo</em> spectrometers differ only in the functionality of the bundled vendor software. There are no differences between the instruments when used with ArgyllCMS and DisplayCAL.</li>
<li>The <em>ColorMunki Display</em> colorimeter is a less expensive version of the i1 Display Pro colorimeter. It comes bundled with a simpler vendor software and has longer measurement times compared to the i1 Display Pro. Apart from that, the instrument appears to be virtually identical.</li>
<li>The <em>ColorMunki Create</em> and <em>ColorMunki Smile</em> colorimeters are similar hardware as the i1 Display 2 (with the ColorMunki Smile no longer having a built-in correction for CRT but for white LED backlit LCD instead).</li>
</ul>
</div>
<div id="requirements-unattended">
<h3>Additional requirements for unattended calibration and profiling</h3>
<p>When using a spectrometer that is supported by the unattended feature (see below), having to take the instrument off the screen to do a sensor self-calibration again after display calibration before starting the measurements for profiling may be avoided if the menu item “Allow skipping of spectrometer self-calibration” under the “Advanced” sub-menu in the “Options” menu is checked (colorimeter measurements are always unattended because they generally do not require a sensor calibration away from the screen, with the exception of the i1 Display 1).</p>
<p>Unattended calibration and profiling currently supports the following spectrometers in addition to most colorimeters:</p>
<ul>
<li>X-Rite ColorMunki Design/Photo</li>
<li>X-Rite/GretagMacbeth i1 Monitor & Pro</li>
<li>X-Rite/GretagMacbeth Spectrolino</li>
<li>X-Rite i1 Pro 2</li>
<li>X-Rite i1Studio</li>
</ul>
<p>Be aware you may still be forced to do a sensor calibration if the instrument requires it. Also, please look at the possible <a href="#issue-samplereadfail">caveats</a>.</p>
</div>
<div id="requirements-source">
<div id="requirements-source-basic">
<h3>Additional requirements for using the source code</h3>
<div>
<p>You can <a href="#install">skip</a> this section if you downloaded a package, installer, ZIP archive or disk image of DisplayCAL for your operating system and do not want to run from source.</p>
<h4>All platforms:</h4>
<ul>
<li><a href="https://python.org/">Python</a> >= v2.6 <= v2.7.x (2.7.x is the recommended version. Mac OS X users: If you want to compile DisplayCAL's C extension module, it is advisable to <strong>first</strong> install XCode and <strong>then</strong> the official python.org Python)</li>
<li><a href="https://www.numpy.org/">NumPy</a></li>
<li><a href="https://wxpython.org/">wxPython</a> <abbr title="Graphical User Interface">GUI<sup><a href="#definition_GUI">[4]</a></sup></abbr> toolkit</li>
<li><a href="https://pypi.org/project/certifi/">Certifi</a></li>
<li><a href="https://pypi.org/project/psutil/">psutil</a> (optional but recommended)</li>
<li><a href="https://pypi.org/project/faulthandler/">faulthandler</a> (optional)</li>
<li><a href="https://pypi.org/project/PyChromecast/">PyChromecast</a> (if you want to use a Chromecast device)</li>
</ul>
<h4>Linux:</h4>
<ul>
<li><a href="https://pypi.org/project/PyGObject/">PyGObject</a></li>
</ul>
<h4>Windows:</h4>
<ul>
<li><a href="https://pypi.org/project/pywin32/">pywin32</a></li>
<li><a href="https://pypi.org/project/WMI/">WMI</a></li>
<li><a href="https://pypi.org/project/comtypes/">comtypes</a></li>
<li><a href="https://pypi.org/project/pyglet/">pyglet</a></li>
</ul>
<h4>macOS:</h4>
<ul>
<li><a href="https://pypi.org/project/pyglet/">pyglet</a></li>
</ul>
</div>
</div>
<div id="requirements-source-compile">
<h3>Additional requirements for compiling the C extension module</h3>
<div>
<p>Normally you can <a href="#install">skip</a> this section as the source code contains pre-compiled versions of the C extension module that DisplayCAL uses.</p>
<h4>Linux:</h4>
<ul>
<li>GCC and development headers for Python + X11 + Xrandr + Xinerama + Xxf86vm if not already installed, they should be available through your distribution's packaging system</li>
</ul>
<h4>Mac OS X:</h4>
<ul>
<li><a href="https://developer.apple.com/xcode/">XCode</a></li>
<li><a href="https://pypi.org/project/py2app/">py2app</a> if you want to build a standalone executable. On Mac OS X before 10.5, install setuptools first: <code>sudo python util/ez_setup.py setuptools</code></li>
</ul>
<h4>Windows:</h4>
<ul>
<li>a C-compiler (e.g. <a href="https://www.visualstudio.com/vs/visual-studio-express/">MS Visual C++ Express</a> or <a href="http://www.mingw.org/">MinGW</a>. If you're using the official python.org Python 2.6 or later I'd recommend Visual C++ Express as it works out of the box)</li>
<li><a href="https://pypi.org/project/py2exe/">py2exe</a> if you want to build a standalone executable</li>
</ul>
</div>
</div>
<div id="requirements-source-run">
<h3 id="runsource">Running directly from source</h3>
<div>
<p>After satisfying all <a href="#requirements-source">additional requirements for using the source code</a>, you can simply run any of the included <code>.pyw</code> files from a terminal, e.g. <code>python2 DisplayCAL.pyw</code>, or install the software so you can access it via your desktop's application menu with <code>python2 setup.py install</code>. Run <code>python2 setup.py --help</code> to view available options.</p>
<p>One-time setup instructions for source code checked out from SVN:</p>
<p>Run <code>python2 setup.py</code> to create the version file so you don't see the update popup at launch.</p>
<p>If the pre-compiled extension module that is included in the sources does not work for you (in that case you'll notice that the movable measurement window's size does not closely match the size of the borderless window generated by ArgyllCMS during display measurements) or you want to re-build it unconditionally, run <code>python2 setup.py build_ext -i</code> to re-build it from scratch (you need to satisfy the <a href="#requirements-source-compile">requirements for compiling the C extension module</a> first).</p>
</div>
</div>
</div>
</div>
<div id="install">
<h2>Installation</h2>
<div id="install-windows-driver">
<h3>Instrument driver installation under Windows</h3>
<div>
<p class="info">You only need to install the Argyll-specific driver if your measurement device is <strong>not</strong> a ColorMunki Display, i1 Display Pro, Huey, ColorHug, specbos, spectraval or K-10 (the latter two may require the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI virtual COM port driver</a> instead).</p>
<p>To automatically install the Argyll-specific driver that is needed to use some instruments, launch DisplayCAL and select “Instrument” › “Install ArgyllCMS instrument drivers...” from the “Tools” menu. Alternatively, follow the manual instructions below.</p>
<div class="info">
<p>If you are using Windows 8, 8.1, or 10, you need to <strong>disable driver signature enforcement</strong> before you can install the driver.
If <a href="https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Secure_boot">Secure Boot</a> is enabled in the <abbr title="Unified Extensible Firmware Interface">UEFI<sup><a href="#definition_UEFI">[12]</a></sup></abbr> setup, you need to disable it first. Refer to your mainboard or firmware manual how to go about this. Usually entering the firmware setup requires holding the DEL key when the system starts booting.</p>
<p><strong>Method 1: Disable driver signature enforcement temporarily</strong></p>
<ol>
<li>Windows 8/8.1: Go to “Settings” (hover the lower right corner of the screen, then click the gear icon) and select “Power” (the on/off icon).<br />
Windows 10: Click the “Power” button in the start menu.</li>
<li>Hold the SHIFT key down and click “Restart”.</li>
<li>Select “Troubleshoot” → “Advanced Options” → “Startup Settings” → “Restart”</li>
<li>After reboot, select “Disable Driver Signature Enforcement” (number 7 on the list)</li>
</ol>
<p><strong>Method 2: Disable driver signature enforcement permanently</strong></p>
<ol>
<li>Open an elevated command prompt. Search for “Command Prompt” in the Windows start menu, right-click and select “Run as administrator”</li>
<li>Run the following command: <code>bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS</code></li>
<li>Run the following command: <code>bcdedit /set TESTSIGNING ON</code></li>
<li>Reboot</li>
</ol>
</div>
<p>To install the Argyll-specific driver that is needed to use some instruments, launch Windows' Device Manager and locate the instrument in the device list. It may be underneath one of the top level items.
Right click on the instrument and select “Update Driver Software...”, then choose “Browse my computer for driver software”, “Let me pick from a list of device drivers on my computer”, “Have Disk...”, browse to the Argyll_VX.X.X\usb folder, open the ArgyllCMS.inf file, click OK, and finally confirm the Argyll driver for your instrument from the list.</p>
<p>To switch between the ArgyllCMS and vendor drivers, launch Windows' Device Manager and locate the instrument in the device list. It may be underneath one of the top level items.
Right click on the instrument and select “Update Driver Software...”, then choose “Browse my computer for driver software”, “Let me pick from a list of device drivers on my computer” and finally select the desired driver for your instrument from the list.</p>
</div>
</div>
<div id="install-deb-rpm">
<h3>Linux package (.deb/.rpm)</h3>
<div>
<p>A lot of distributions allow easy installation of packages via the graphical desktop, i.e. by double-clicking the package file's icon. Please consult your distribution's documentation if you are unsure how to install packages.</p>
<p class="info">If you cannot access your instrument, first try unplugging and reconnecting it, or a reboot. If that doesn't help, read “<a href="https://www.argyllcms.com/doc/Installing_Linux.html">Installing ArgyllCMS on Linux: Setting up instrument access</a>”.</p>
</div>
</div>
<div id="install-mac">
<h3>Mac OS X</h3>
<div>
<p>Use the Installer Package to install DisplayCAL to your “Applications” folder. Afterwards open the “DisplayCAL” folder in your “Applications” folder and drag DisplayCAL's icon to the dock if you want easy access.</p>
<p class="info">If you want to use the HCFR colorimeter under Mac OS X, follow the instructions under “<a href="https://www.argyllcms.com/doc/Installing_OSX.html">installing ArgyllCMS on Mac OS X</a>” in the ArgyllCMS documentation.</p>
</div>
</div>
<div id="install-windows-setup">
<h3>Windows (Installer)</h3>
<div>
<p>Launch the installer which will guide you trough the required setup steps.</p>
<p class="info">If your measurement device is <strong>not</strong> a ColorMunki Display, i1 Display Pro, Huey, ColorHug, specbos, spectraval or K-10, you need to install an Argyll-specific driver (the specbos, spectraval and K-10 may require the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI virtual COM port driver</a> instead). <a href="#install-windows-driver">See “Instrument driver installation under Windows”.</a></p>
</div>
</div>
<div id="install-windows-zip">
<h3>Windows (ZIP archive)</h3>
<div>
<p>Unpack and then simply run DisplayCAL from the created folder.</p>
<p class="info">If your measurement device is <strong>not</strong> a ColorMunki Display, i1 Display Pro, Huey, ColorHug, specbos, spectraval or K-10, you need to install an Argyll-specific driver (the specbos, spectraval and K-10 may require the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI virtual COM port driver</a> instead). <a href="#install-windows-driver">See “Instrument driver installation under Windows”.</a></p>
</div>
</div>
<div id="install-src">
<h3>Source code (all platforms)</h3>
<div>
<p>See the “Prerequisites” section to <a href="#runsource">run directly from source</a>.</p>
<p>Starting with DisplayCAL 0.2.5b, you can use standard distutils/setuptools commands with setup.py to build, install, and create packages. <code>sudo python setup.py install</code> will compile the extension modules and do a standard installation. Run <code>python setup.py --help</code> or <code>python setup.py --help-commands</code> for more information. A few additional commands and options which are not part of distutils or setuptools (and thus do not appear in the help) are also available:</p>
<h4>Additional setup commands</h4>
<div class="info">
<dl>
<dt><code>0install</code></dt>
<dd>Create/update 0install feeds and create Mac OS X application bundles to run those feeds.</dd>
<dt><code>appdata</code></dt>
<dd>Create/update <a href="https://people.freedesktop.org/~hughsient/appdata/">AppData</a> file.</dd>
<dt><code>bdist_appdmg</code> (Mac OS X only)</dt>
<dd>Creates a DMG of previously created (by the py2app or bdist_standalone commands) application bundles, or if used together with the <code>0install</code> command.</dd>
<dt><code>bdist_pkg</code> (Mac OS X only)</dt>
<dd>Creates an Installer Package (.pkg) of previously created (by the py2app or bdist_standalone commands) application bundles.</dd>
<dt><code>bdist_deb</code> (Linux/Debian-based)</dt>
<dd>Create an installable Debian (.deb) package, much like the standard distutils command bdist_rpm for RPM packages. Prerequisites:
You first need to install alien and rpmdb, create a dummy RPM database via <code>sudo rpmdb --initdb</code>, then edit (or create from scratch) the setup.cfg (you can have a look at misc/setup.ubuntu9.cfg for a working example). Under Ubuntu, running utils/dist_ubuntu.sh will automatically use the correct setup.cfg. If you are using Ubuntu 11.04 or any other debian-based distribution which has Python 2.7 as default, you need to edit /usr/lib/python2.7/distutils/command/bdist_rpm.py, and change the line <code>install_cmd = ('%s install <span style="color: #c00">-O1</span> --root=$RPM_BUILD_ROOT '</code> to <code>install_cmd = ('%s install --root=$RPM_BUILD_ROOT '</code> by removing the <code><span style="color: #c00">-O1</span></code> flag. Also, you need to change /usr/lib/rpm/brp-compress to do nothing (e.g. change the file contents to <code>exit 0</code>, but don't forget to create a backup copy first) otherwise you will get errors when building.</dd>
<dt><code>bdist_pyi</code></dt>
<dd>An alternative to <code>bdist_standalone</code>, which uses <a href="http://www.pyinstaller.org/">PyInstaller</a> instead of bbfreeze/py2app/py2exe.</dd>
<dt><code>bdist_standalone</code></dt>
<dd>Creates a standalone application that does not require a Python installation. Uses bbfreeze on Linux, py2app on Mac OS X and py2exe on Windows. setup.py will try and automatically download/install these packages for you if they are not yet installed and if not using the --use-distutils switch. Note: On Mac OS X, older versions of py2app (before 0.4) are not able to access files inside python “egg” files (which are basically ZIP-compressed folders). Setuptools, which is needed by py2app, will normally be installed in “egg” form, thus preventing those older py2app versions from accessing its contents. To fix this, you need to remove any installed setuptools-<version>-py<python-version>.egg files from your Python installation's site-packages directory (normally found under <code>/Library/Frameworks/Python.framework/Versions/Current/lib</code>). Then, run <code>sudo python util/ez_setup.py -Z setuptools</code> which will install setuptools unpacked, thus allowing py2app to acces all its files. This is no longer an issue with py2app 0.4 and later.</dd>
<dt><code>buildservice</code></dt>
<dd>Creates control files for openSUSE Build Service (also happens implicitly when invoking <code>sdist</code>).</dd>
<dt><code>finalize_msi</code> (Windows only)</dt>
<dd>Adds icons and start menu shortcuts to the MSI installer previously created with <code>bdist_msi</code>. Successful MSI creation needs a <a href="https://bugs.python.org/file15898/msilib_make_short.diff">patched msilib</a> (<a href="https://bugs.python.org/issue1128">additional</a> <a href="https://bugs.python.org/issue7639">information</a>).</dd>
<dt><code>inno</code> (Windows only)</dt>
<dd>Creates <a href="http://www.jrsoftware.org/isinfo.php">Inno Setup</a> scripts which can be used to compile setup executables for standalone applications generated by the <code>py2exe</code> or <code>bdist_standalone</code> commands and for 0install.</dd>
<dt><code>purge</code></dt>
<dd>Removes the <code>build</code> and <code>DisplayCAL.egg-info</code> directories including their contents.</dd>
<dt><code>purge_dist</code></dt>
<dd>Removes the <code>dist</code> directory and its contents.</dd>
<dt><code>readme</code></dt>
<dd>Creates README.html by parsing misc/README.template.html and substituting placeholders like date and version numbers.</dd>
<dt><code>uninstall</code></dt>
<dd>Uninstalls the package. You can specify the same options as for the <code>install</code> command.</dd>
</dl>
</div>
<h4>Additional setup options</h4>
<div class="info">
<dl>
<dt><code>--cfg=<name></code></dt>
<dd>Use an alternate setup.cfg, e.g. tailored for a given Linux distribution. The original setup.cfg is backed up and restored afterwards. The alternate file must exist as misc/setup.<name>.cfg</dd>
<dt><code>-n</code>, <code>--dry-run</code></dt>
<dd>Don't actually do anything. Useful in combination with the uninstall command to see which files would be removed.</dd>
<dt><code>--skip-instrument-configuration-files</code></dt>
<dd>Skip installation of udev rules and hotplug scripts.</dd>
<dt><code>--skip-postinstall</code></dt>
<dd>Skip post-installation on Linux (an entry in the desktop menu will still be created, but may not become visible until logging out and back in or rebooting) and Windows (no shortcuts in the start menu will be created at all).</dd>
<dt><code>--stability=stable | testing | developer | buggy | insecure</code></dt>
<dd>Set the stability for the readme and/or implementation that is added/updated via the <code>0install</code> command.</dd>
<dt><code>--use-distutils</code></dt>
<dd>Force setup to use distutils (default) instead of setuptools. This is useful in combination with the bdist* commands, because it will avoid an artificial dependency on setuptools. This is actually a switch, use it once and the choice is remembered until you specify the <code>--use-setuptools</code> switch (see next paragraph).</dd>
<dt><code>--use-setuptools</code></dt>
<dd>Force setup to try and use setuptools instead of distutils. This is actually a switch, use it once and the choice is remembered until you specify the <code>--use-distutils</code> switch (see above).</dd>
</dl>
</div>
</div>
</div>
</div>
<div id="install-2">
<h3>Instrument-specific setup</h3>
<p><strong>If your measurement device is a i1 Display 2, i1 Display Pro, ColorMunki Display, DTP94, Spyder2/3/4/5</strong>, you'll want to import the colorimeter corrections that are part of the vendor software packages, which can be used to better match the instrument to a particular type of display. <em>Note:</em> The full range of measurement modes for the Spyder4/5 are also only available if they are imported from the Spyder4/5 software.</p>
<p>Choose “Import colorimeter corrections from other display profiling software...” from DisplayCAL's “Tools” menu.</p>
<p><strong>If your measurement device is a Spyder2</strong>, you need to enable it to be able to use it with ArgyllCMS and DisplayCAL. Choose “Enable Spyder2 colorimeter...” from DisplayCAL's “Tools” menu.</p>
</div>
<div id="concept">
<h2>Basic concept of display calibration and profiling</h2>
<p>If you have previous experience, <a href="#colorimeter-corrections">skip ahead</a>. If you are new to display
calibration, here is a quick outline of the basic concept.</p>
<p>First, the display behavior is measured and adjusted to meet
user-definable target characteristics, like brightness, gamma and white point.
This step is generally referred to as <em>calibration</em>. Calibration is done by
adjusting the monitor controls, and the output of the graphics card (via
<em>calibration curves</em>, also sometimes called <em>video <abbr title="Look Up Table">LUT<sup><a href="#definition_LUT">[7]</a></sup></abbr> curves</em>—please don't confuse these with <em>LUT profiles</em>, the <a href="#difference_lutcurves_lutprofile" title="Difference between LUT (calibration) curves and LUT profiles">differences are explained here</a>) to get as
close as possible to the chosen target.<br />
To meet the user-defined target characteristics, it is generally advisable to
get as far as possible by using the monitor controls, and only thereafter by
manipulating the output of the video card via calibration curves, which are loaded into the <em>video card gamma table</em>, to get the best
results.</p>
<p>Second, the calibrated displays response is measured and an <abbr title="International Color Consortium">ICC<sup><a href="#definition_ICC">[5]</a></sup></abbr> profile
describing it is created.</p>
<p>Optionally and for convenience purposes, the calibration is stored in the profile, but both
still need to be used together to get correct results. This can lead to some ambiguity,
because loading the calibration curves from the profile is generally the
responsibility of a third party utility or the OS, while applications using
the profile to do color transforms usually don't know or care about the calibration (they don't need to). Currently, the only OS that
applies calibration curves out-of-the-box is Mac OS X (under <a href="#issue-win7-autoloadcalibration">Windows 7 or later you can enable it</a>, but it's off by default and doesn't offer the same high precision as the DisplayCAL profile loader)—for other OS's, DisplayCAL takes care of creating an appropriate loader.</p>
<p>Even non-color-managed applications will benefit from a loaded
calibration because it is stored in the graphics card—it is “global”. But the calibration alone will not yield accurate colors—only fully color-managed applications will make use of display
profiles and the necessary color transforms.</p>
<p>Regrettably there are several image viewing and editing applications that
only implement half-baked color management by not using the system's display profile (or any display profile at all), but an internal and often unchangeable “default”
color space like sRGB, and sending output unaltered to the display after converting to that default colorspace. If the
display's actual response is close to sRGB, you might get pleasing (albeit not
accurate) results, but on displays which behave differently, for example wide-color-gamut displays, even mundane colors can
get a strong tendency towards neon.</p>
</div>
<div id="colorimeter-corrections">
<h2>A note about colorimeters, displays and DisplayCAL</h2>
<p>Colorimeters need a correction in hardware or software to obtain correct measurements from different types of displays (please also see <a href="https://www.argyllcms.com/doc/WideGamutColmters.html">“Wide Gamut Displays and Colorimeters”</a> on the ArgyllCMS website for more information). The latter is supported when using ArgyllCMS >= 1.3.0, so if you own a display and colorimeter which has not been specifically tuned for this display (i.e. does not contain a correction in hardware), you can apply a correction that has been calculated from spectrometer measurements to help better measure such a screen.<br />
You need a spectrometer in the first place to do the necessary measurements to create such a correction, or you may query DisplayCAL's <a href="https://colorimetercorrections.displaycal.net/">Colorimeter Corrections Database</a>, and there's also a <a href="https://www.argyllcms.com/doc/ccmxs.html">list of contributed colorimeter correction files on the ArgyllCMS website</a>—<strong>please note</strong> though that a matrix created for one particular instrument/display combination may not work well for different instances of the same combination because of display manufacturing variations and generally low inter-instrument agreement of most older colorimeters (with the exception of the DTP94), newer devices like the i1 Display Pro/ColorMunki Display seem to be less affected by this.<br />
Starting with DisplayCAL 0.6.8, you can also <a href="#import-correction-matrices">import generic corrections</a> from some profiling softwares by choosing the corresponding item in the “Tools” menu.</p>
<p>If you buy a screen bundled with a colorimeter, the instrument may have been matched to the screen in some way already, so you may not need a software correction in that case.</p>
<h3>Special note about the X-Rite i1 Display Pro, ColorMunki Display and Spyder4/5 colorimeters</h3>
<p>These instruments greatly reduce the amount of work needed to match them to a display because they contain the spectral sensitivities of their filters in hardware, so only a spectrometer reading of the display is needed to create the correction (in contrast to matching other colorimeters to a display, which needs two readings: One with a spectrometer and one with the colorimeter).<br />
That means anyone with a particular screen and a spectrometer can create a special <em>Colorimeter Calibration Spectral Set</em> (<code>.ccss</code>) file of that screen for use with those colorimeters, without needing to actually have access to the colorimeter itself.</p>
</div>
<div id="usage">
<h2>Usage</h2>
<p>Through the main window, you can choose your settings. When running calibration measurements, another window will guide you through the interactive part of display adjustment.</p>
<div id="settingsfile">
<h3>Settings file</h3>
<p>Here, you can load a preset, or a calibration (<code>.cal</code>) or ICC profile (<code>.icc</code> / <code>.icm</code>) file from a previous
run. This will set options to
those stored in the file. If the file contains only a subset of settings, the other options will automatically be reset to defaults (except the 3D LUT settings, which won't be reset if the settings file doesn't contain 3D LUT settings, and the verification settings which will never be reset automatically).</p>
<p>If a calibration file or profile is loaded in this way, its name will
show up here to indicate that the settings reflect those in the file.
Also, if a calibration is present it can be used as the base when “Just Profiling”.<br />
The chosen settings file will stay selected as long as you do not change any of the
calibration or profiling settings, with one exception: When a <code>.cal</code> file with the same base name as the settings file
exists in the same directory, adjusting the quality and profiling controls will not cause unloading of the settings file. This allows you to use an existing calibration with new profiling settings for “Just Profiling”, or to update an existing calibration with different quality and/or profiling settings. If you change settings in other situations, the file will get unloaded (but current settings will be retained—unloading just happens to remind you that the settings no longer match those in the file), and current display profile's calibration curves will be restored (if present, otherwise they will reset to linear).</p>
<p>When a calibration file is selected, the “Update calibration”
checkbox will become available, which takes less time than a calibration from scratch.
If a <abbr title="International Color Consortium">ICC<sup><a href="#definition_ICC">[5]</a></sup></abbr> profile is selected, and a calibration file with the same base name
exists in the same directory, the profile will be updated with the new calibration. Ticking the “Update calibration” checkbox will gray out
all options as well as the “Calibrate & profile” and “Just profile” buttons, only the quality level will be changeable.</p>
</div>
<div id="presets">
<h3>Predefined settings (presets)</h3>
<p>Starting with DisplayCAL v0.2.5b, predefined settings for several use cases are selectable in the settings dropdown. I strongly recommend to NOT view these presets as the solitary “correct” settings you absolutely should use unmodified if your use case matches their description. Rather view them as starting points, from where you can work towards your own, optimized (in terms of your requirements, hardware, surroundings, and personal preference) settings.</p>
<h4>Why has a default gamma of 2.2 been chosen for some presets?</h4>
<p>Many displays, be it CRT, LCD, Plasma or OLED, have a default response characteristic close to a gamma of approx. 2.2-2.4 (for CRTs, this is the actual native behaviour; and other technologies typically try to mimic CRTs). A target response curve for calibration that is reasonably close to the native response of a display should help to minimize calibration artifacts like banding, because the adjustments needed to the video card's gamma tables via calibration curves will not be as strong as if a target response farther away from the display's native response had been chosen.</p>
<p>Of course, you can and should change the calibration response curve to a value suitable for your own requirements. For example, you might have a display that offers hardware calibration or gamma controls, that has been internally calibrated/adjusted to a different response curve, or your display's response is simply not close to a gamma of 2.2 for other reasons. You can run “Report on uncalibrated display device” from the “Tools” menu to measure the approximated overall gamma among other info.</p>
</div>
<div id="tabs">
<h3>Tabs</h3>
<p>The main user interface is divided into tabs, with each tab containing a sub-set of settings. Not all tabs may be available at any given time. Unavailable tabs will be grayed out.</p>
</div>
<div id="display_instrument">
<h3>Choosing the display to calibrate and the measurement device</h3>
<p>After connecting the instrument, click the small icon with the swirling arrow <img src="theme/refresh.svg" alt="" /> in between the “Display device” and “Instrument” controls to detect connected display devices and instruments.</p>
<h4 id="settings_display_device">Choosing a display device</h4>
<p>Directly connected displays will appear at the top of the list as entries in the form “Display Name/Model @ x, y, w, h” with x, y, w and h being virtual screen coordinates depending on resolution and DPI settings. Apart from those directly connected displays, a few additional options are also available:</p>
<dl>
<dt>Web @ localhost</dt>
<dd>
<p>Starts a standalone web server on your machine, which then allows a local or remote web browser to display the color test patches, e.g. to calibrate/profile a smartphone or tablet computer.</p>
<p>Note that if you use this method of displaying test patches, then colors will be displayed with 8 bit per component precision, and any screen-saver or power-saver will <strong>not</strong> be automatically disabled. You will also be at the mercy of any color management applied by the web browser, and may have to carefully review and configure such color management.</p>
</dd>
<dt>madVR</dt>
<dd>
<p>Causes test patches to be displayed using the madVR Test Pattern Generator (madTPG) application which comes with the <a href="http://madvr.com/">madVR video renderer</a> (only available for Windows, but you can connect via local network from Linux and Mac OS X). Note that while you can adjust the test pattern configuration controls in madTPG itself, you should not normally alter the “disable videoLUT” and “disable 3D LUT” controls, as these will be set appropriately automatically when doing measurements.</p>
<p>Note that if you want to create a 3D LUT for use with madVR, there is a “Video 3D LUT for madVR” preset available under “Settings” that will not only configure DisplayCAL to use madTPG, but also setup the correct 3D LUT format and encoding for madVR.</p>
</dd>
<dt>Prisma</dt>
<dd>
<p>The Q, Inc./Murideo Prisma is a video processor and combined pattern generator/3D LUT holder accessible over the network.</p>
<p>Note that if you want to create a 3D LUT for use with a Prisma, there is a “Video 3D LUT for Prisma” preset available under “Settings” that will not only configure DisplayCAL to use a Prisma, but also setup the correct 3D LUT format and encoding.</p>
<p>Also note that the Prisma has 1 MB of internal memory for custom LUT storage, which is enough for around 15 17x17x17 LUTs. You may occasionally need to enter the Prisma's administrative interface via a web browser to delete old LUTs to make space for new ones.</p>
</dd>
<dt>Resolve</dt>
<dd>
<p>Allows you to use the built-in pattern generator of DaVinci Resolve video editing and grading software, which is accessible over the network or on the local machine. The way this works is that you start a calibration or profiling run in DisplayCAL, position the measurement window and click “Start measurement”. A message “Waiting for connection on IP:PORT” should appear. Note the IP and port numbers. In Resolve, switch to the “Color” tab and then choose “Monitor calibration”, “CalMAN” in the “Color” menu (Resolve version 11 and earlier) or the “Workspace” menu (Resolve 12).<br />
Enter the IP address in the window that opens (port should already be filled) and click “Connect” (if Resolve is running on the same machine as DisplayCAL, enter <code>localhost</code> or <code>127.0.0.1</code> instead). The position of the measurement window you placed earlier will be mimicked on the display you have connected via Resolve.</p>
<p>Note that if you want to create a 3D LUT for use with Resolve, there is a “Video 3D LUT for Resolve” preset available under “Settings” that will not only configure DisplayCAL to use Resolve, but also setup the correct 3D LUT format and encoding.</p>
<p><strong>Note</strong> that if you want to create a 3D LUT for a display that is <strong>directly connected</strong> (e.g. for Resolve's GUI viewer), you should <strong>not</strong> use the Resolve pattern generator, and select the actual display device instead which will allow for quicker measurements (Resolve's pattern generator has additional delay).</p>
</dd>
<dt>Untethered</dt>
<dd>
<p>See <a href="#untethered">untethered display measurements</a>. <em>Please note that the untethered mode should generally only be used if you've exhausted all other options.</em></p>
</dd>
</dl>
<h4 id="settings_measurement_modes">Choosing a measurement mode</h4>
<p>Some instruments may support different measurement modes for different types of display devices. In general, there are two base measurement modes: “LCD” and “Refresh” (e.g. CRT and Plasma are refresh-type displays). Some instruments like the Spyder4/5 and ColorHug support additional measurement modes, where a mode is coupled with a predefined colorimeter correction (in that case, the <a href="#settings_colorimeter_correction">colorimeter correction</a> dropdown will automatically be set to “None”).<br />
Variations of these measurement modes may be available depending on the instrument: “Adaptive” measurement mode for spectrometers uses varying integration times (always used by colorimeters) to increase accuracy of dark readings. “HiRes” turns on high resolution spectral mode for spectrometers like the i1 Pro, which may increase the accuracy of measurements.</p>
<h4 id="settings_drift_compensation">Drift compensation during measurements (only available if using ArgyllCMS >= 1.3.0)</h4>
<p>White level drift compensation tries to counter luminance changes of a warming up display device. For this purpose, a white test patch is measured periodically, which increases the overall time needed for measurements.</p>
<p>Black level drift compensation tries to counter measurement deviations caused by black calibration drift of a warming up measurement device. For this purpose, a black test patch is measured periodically, which increases the overall time needed for measurements. Many colorimeters are temperature stabilised, in which case black level drift compensation should not be needed, but spectrometers like the i1 Pro or ColorMunki Design/Photo/i1Studio are not temperature compensated.</p>
<h4 id="display-update-delay">Override display update delay (only available if using ArgyllCMS >= 1.5.0, only visible if “Show advanced options” in the “Options” menu is enabled)</h4>
<p>Normally a delay of 200 msec is allowed between changing a patch color in software, and that change appearing in the displayed color itself. For some instuments (i.e. i1 Display Pro, ColorMunki Display, i1 Pro, ColorMunki Design/Photo/i1Studio, Klein K10-A) ArgyllCMS will automatically measure and set an appropriate update delay during instrument calibration. In rare situations this delay may not be sufficient (ie. some TV's with extensive image processing features turned on), and a larger delay can be set here.</p>
<h4 id="display-settle-time">Override display settle time multiplier (only available if using ArgyllCMS >= 1.7.0, only visible if “Show advanced options” in the “Options” menu is enabled)</h4>
<p>Normally the display technology type determines how long is allowed between when a patch color change appears on the display, and when that change has settled down, and as actually complete within measurement tolerance. A CRT or Plasma display for instance, can have quite a long settling delay due to the decay characteristics of the phosphor used, while an LCD can also have a noticeable settling delay due to the liquid crystal response time and any response time enhancement circuit (instruments without a display technology type selection such as spectrometers assume a worst case).<br />
The display settle time multiplier allows the rise and fall times of the model to be scaled to extend or reduce the settling time. For instance, a multiplier of 2.0 would double the settling time, while a multiplier of 0.5 would halve it.</p>
<h4 id="display-settle-time">Output levels (only visible if “Show advanced options” in the “Options” menu is enabled)</h4>
<p>The default value of “Auto” detects the correct output levels automatically during measurements. This usually takes a few seconds. If you know the correct output levels for the selected display, you can set it here.</p>
<h4 id="display-settle-time">Full field pattern insertion (only for select pattern generators, only visible if “Show advanced options” in the “Options” menu is enabled)</h4>
<p>Full field pattern insertion can help with displays that employ ASBL (automatic static brightness limiting), like some types of OLED and HDR displays. A full field pattern is shown every few seconds (the minimum interval can be set with the respective control) for a given duration, at a given signal level, if this option is enabled.</p>
<h4 id="settings_colorimeter_correction">Choosing a colorimeter correction for a particular display</h4>
<p>This can improve a colorimeters accuracy for a particular type of display, please also see <a href="#colorimeter-corrections">“A note about colorimeters, displays and DisplayCAL”</a>. You can import generic matrices from some other display profiling softwares, as well as check the online <a href="https://colorimetercorrections.displaycal.net/">Colorimeter Corrections Database</a> for a match of your display/instrument combination (click the small globe next to the correction dropdown)—<strong>please note</strong> though that all colorimeter corrections in the online database have been contributed by various users, and their usefulness to your particular situation is up to you to evaluate: They may or may not improve the absolute accuracy of your colorimeter with your display.</p>
<p>Please note this option is only available if using ArgyllCMS >= 1.3.0 and a colorimeter.</p>
<h4>Colorimeter correction information</h4>
<p>For correction matrices, a visual simulation of the effect of the correction will be shown (“flower”). Note that this is not meant to be color accurate, but give you a rough idea about the impact on the measurements of your colorimeter. The six outer circles of primary and secondary colors (clockwise: green, yellow, red, magenta, blue, cyan) and center white circle all have an outer part as well as a smaller inner area. The outer part of each circle represents what the colorimeter would “see” (i.e. measure) without the correction, the inner part of each circle represents the corrected result.<br />
Below this visual representation you will find the matrix values, as well as optional further information, like the reference instrument or source used, the method used to create the correction (“perceptual” or “minimize xy chromaticity difference”), as well as the average and maximum fit error (the lower the fit error, the better the corrected instrument should match the reference instrument).</p>