AVS Forum banner

HCFR - Open source projector and display calibration software

2M views 16K replies 1K participants last post by  nathan_h 
#1 · (Edited)
Hi and welcome to the open source HCFR software thread.
Updated Jan. 27th - 2018

I love working and tinkering on the program but given the amount of time I've invested over the past year on improvements I'm going to start accepting donations. If you feel the program has been of value to you since I started working on it about 3 years ago please consider a contribution via the link below. Thanks!

https://www.paypal.me/zoyd
(or via direct paypal to vze262tr@verizon.net if paypal.me is not supported in your country)

Thanks to the following for recent donations! [LarryInRI, Barsk, 22point, LastButNotLeast, Dominic Chen, Brian M., Wayne L., Andrej S., Arturs J., Douglas P., John G., mo949, Eric V., David S., BlueChris, EXT64, Nihat S., Luis E., J. F., Miiku Joao F., Luis M., Nate W., Don H., Stahinja M., Jeff H., Pedro C., Howell A., Myat M., Carlos F., Webster D., SiegeX, Jörg O., Enrico B., Gert M., Marlon K., Jacob R., John G., Kari T., Ryan T., Franck P. ]

HCFR uses ArgyllCMS for the operation of the probes, so please help ensure that ArgyllCMS remains available in the future, by making a financial contribution to the argyllcms project:

www.argyllcms.com

---

This thread was originally started by JohnAd who had the nice idea of creating an open source fork of the original HCFR Colormeter software to integrate the existing GUI and all of it's calibration features, with the meter handling code of ArgyllCMS. Since ArgyllCMS is continually adding and improving meter support, HCFR benefits by staying current with these developments. The software is frequently referred to as HCFR or colorHCFR where HCFR is short for "Home Cinema-FR", a French forum where some of it's members originally developed the code to support their home-brew colorimeter in 2005. Along with the meter handling improvements introduced by ArgyllCMS, I have been working on improving and adding features to the color engine and internal pattern generator. Please use this thread for bug reports, usage questions and suggestions for improvement. Anyone wishing to help with code development should join the developers mailing list.

The latest version of HCFR (3.5.1.4) can be found here. Changelog

Help Wanted (pm zoyd)
  • Language translation
  • Update French and German with recent changes
  • Full Spanish, Italian, others? needed
  • Help file updates
  • PDF Quick Guide

User wl1 has provided some useful links for beginners to display calibration as well as links to helpful posts within the thread. Please take a look before posting to see if your question has already been answered. There is also a FAQ section below that may be helpful.

Useful Links
Display Calibration - Part I
Curtpalme - Calibration Guide for Dummies
Basic Guide to Color Calibration using a CMS (updated and enhanced)
ArgyllCMS Probe installation notes
Spears and Munsil
Choosing a Color Space | Spears & Munsil
The Secrets Blu-ray Player HDMI Benchmark Part 1 and Part 2
Original version 2 avsforum discussion thread
Another version 2 discussion thread
How-to: Use HCFR to profile your colorimeter

Links to Tools & Utilities
AVSHD709 Test Disk
GCD Disk
Mascior's Calbration Disc
dispcalGUI (front-end to ArgyllCMS)
Ted's LightSpace CMS Calibration disk (now with pointers for use with HCFR) [Set-up Instructions]

Thread Summary (from Post 792, New Scientist)
Post No. Comment
#151 to #155 - installing i1Display Pro

#159 - use of i1Display 3 3/1/2012 (march 1st)

#161 - removal of non-free code (for accessing meter)

#162 - x-rite driver (.dll) use

#165 - spotread

#167 - spotread

#174 - problems with i3D3

#180 - observations re use of i1D3

#183 - reply to #180

#189,#196 - x-rite drivers

#198 - x-rite drivers

#202 - installation i3D3

#226 - a first attempt at calibration

#227,#236 - i1D3 not requiring calibration

#231 - ccss

#248,#253 - i1D3 not requring drivers from x-rite to work with HCFR

#257,#258 - i3D3 with HCFR

#263 to #270 - analysis of #258

#275 - spreadsheet for setting gamma

#277 - spreadsheet uses

#325 - HCFR v3.0.1.0

#397 - using i1D3

#416 - graphs from testing i1D3

#425 - EDR and i1D3ccss too
l
#426 - v3.0.2.0 issues re i1D3

#428 - generate .ccss files from i3D3 disk

#442 - v3.0.3.0

#487 - v3.0.4.0

#507 - what is .ccss

#509 - refresh and i1D3ccss.exe

#514 - what is .ccss and .EDR

#519 - i1D3ccss usage

#528 - where should the .ccss files go?
#534 - ARGYLL_COLMTER_CAL_SPEC_SET environment variable
#540 - some addtional ccss file info (plasma displays)

#552 - ccmx file

#600 - i1D3 not showing in Sensor list

#610 - "Use measured colors", in Preferences -> General, option

#678 - i1D3 and i1 Display Pro differences

#682 - comment re issue with v3.0.4.0 and i1D3

#688 - which driver to use

#717 - i1D3ccss tool

#732 - do I need drivers or not?

#786 - spectral sample files

#824 – Steps to load Driver

#841 – i1D3 reds on Plasma - matrix

#876 – ColorMunki Display guide

#898 - 904 – Pana Window sizes

#1008 – Comparison of HCFR 2.1 and 3.0.4.0

#1083 – HTPC Cal. Suggestion

#1105 – Updating and removing Argyll Drivers

#1114 – Plasma Essential Reading

#1122 –i1D3Pro - initial accuracy study/background to meter matrices

#1146 – Matric Correction file info

#1150 – Import Matrix file into HCFR

#1205 – 2 point V 10 point Calibration

#1215 – Warming up meter

#1241 – profiling Meters

#1250 – Matrix file for Display LT2

#1258 – errors in HCFR ? Red push?

#1260 – GT30/VT30 Experiences

#1270 – WARNING – HCFR Matrix different than CP or CM

#1280 – Zoyd Steps in - Installation package and baseline Integration value

#1285 and 1299 – The fixes explained – instability @30%IRE

#1303 – Argyll Driver suggestions

#1336 –build from Zoyd – USB fixes

#1337 – Plasma/LCD – definitive Refresh settings and Calibration of meter (>50%)

#1344 – Lots of changes to HCFR

#1352 – List of more changes – BT1886 gamma target

#1354 – More info link on BT1886

#1357 & 1360 & 1370 – Answers about changes – and gamma recommendations

#1380, 1390 – another build

#1398 – Fork of a Fork

#1411 – Luminance and Delta E – Yes or No? Colour or Grey?

#1420 & 1426 – 3.0.4.1 Changes

#1424 – Use of GCD Disk Colour Checker Pattern

#1512 & 1515 & 1558– Version 3.0.4.2 Changes

#1521 – Run HCFR with Admin Privileges

#1523 – Projector questions and suggestions
#1537 – Explanation of Change to HCFR calculation of gamma
#1647 – LCD and LD ON/OFF? Plasma and ABL – guidleines
#1648 – Preferences -> General -> gray levels rounding assumption to unchecked? AVCHD,DVD=checked, GCD,internal patterns=unchecked
#1650 – Can I use matrix from D3 for LT2? No – see 1651

#1663 – BT.1886 or not? Depends on if you have 10 point control

#1702 – BT1888 is not meant to be flat

#1722 – Samsung D & E -75%A and 75%S recommended

#1774 – Explanation of affect of Patterns to gamma and light output results


FAQ:
Do I need to install a driver for the i1Display Pro (i1D3)?
No. This meter as well as the Huey, ColorMunki Display, and ColorHug use the system HID driver.

Which probes are supported?
Any probe that ArgyllCMS supports.

How do I install the right driver for my probe?
Assuming your device is not one of those above, the driver .inf file is located in the drivers sub-directory of the main HCFR folder (by default this is c:\Program Files (x86)\HCFR Calibration\Drivers). You do not need to install the full ArgyllCMS program but useful driver installation hints can be found here. After plugging in your meter go to the system devices in your control panel, find the meter and right click to update the driver. Point the update dialog to the HCFR drivers folder.

Which deltaE formula is the most accurate?
All the deltaE formulas represent a measure of the distance between your measured color and the reference color. So they are just rulers with different scales, use the one recommended if you aren't sure. For gray scale measurements the recommended formula provides more sensitivity to chromaticity (x,y) errors so it's easier to use for "tuning" your controls. The dE94 or dE2000 formulas are generally the most acceptable for "proofing" as they are the most uniform in perceptual space and a unit of error in one part of the gamut has the same visual impact as the rest of the gamut.

How can I import Chromapure probe profile data in HCFR?
Calculate the matrix correction using the spreadsheet from this post where z=1-x-y and then enter it in the sensor matrix tab.


How do I use the Casino Royale images to check my calibration?
There is a nice guide here on what to look for at those particular timecodes.


What do the different parameters for the BT.1886 gamma formula do?
The recommended value (default) for the exponent in the formula is 2.4. This value will be used when you enter 0 for absolute in the BT.1886 box. If you want to tailor the function to make the picture have a little more or less contrast then enter a different number here. If you enter 2.4 for example the actual exponent used will be adjusted so that the target gamma has a value of 2.4 at 50% stimulus. You might use that for a dark environment and 2.2 for a brighter environment.

The other parameter (% Input Offset) will change the shape of the curve near black up through about 20% stimulus. The default value will target a gamma that should provide plenty of detail in the shadows. If you find the shadow detail is being lifted too much when you calibrate to this curve, adjust this value lower (try 50%) and this will raise the target gamma near black and darken the shadows. Note that in most cases you must have multipoint gamma adjustment ability to get a good match to a BT.1886 curve. Also note that if you have a zero black level (e.g. OLED) the target point gamma curve will be flat.


What should I use to generate test patterns?
Most people start out using DVD/Blu-ray test disks to generate their test patterns and run HCFR in manual mode. The assumption being that the BD player is somehow altering the test pattern and not following industry standards for the rendering and transmission of video and that these errors must be "calibrated out". However, this assumption is usually overblown and most often you'll find that while there may be some single bit rounding errors being generated they are not large enough to have any perceptual effect on the signal. I recommend that once you get a good feel for the calibration process using a DVD/BD that you move on to automatic pattern generation (see next question) and then cross-check against your BD player results for sanity.


How do I set-up automatic test patterns?
HCFR has three options for automatic test pattern generation, it's own generator, madTPG, and the Chromecast device. The first two require some set-up of the video card to ensure accuracy while the third requires no set-up. All three options are very accurate test pattern generators with the following characteristics:

HCFR generates all of it's triplet targets in 8-bit video levels (16-235) so when used in a video level path both the internal generator and madTPG will provide technically reference triplets. When used in a PC level (0-255) path the internal generator will expand the video levels to PC level and this will produce rounding errors. While small it is recommended that you use madTPG if you want to calibrate in PC levels because it will dither the output levels and reduce or eliminate any rounding errors. A good summary of the various levels combinations can be found here(h/t @SiegeX).

The Chromecast device produces Y'C'C' output and while not technically a reference device because the levels it produces have rounding errors, it is also dithered to reduce these errors below perceptual limits. The advantage to this device is cost ($30) and ease of set-up (it really is "plug-and-play")

To set-up your laptop/PC for pattern generation (either internal or madTPG) you will need to ensure your video card has linear gain tables loaded (i.e. no profile installed). madTPG does this for you automatically, otherwise you'll need to research your card settings to determine how to do this. It is also easiest to get the correct levels set-up if you force the card to output it's normal 0-255 range when connected to your display over HDMI as some cards will default to 16-235 levels, which in some cases is undesirable. The madVR package has a utility for doing this (madLevelsTweaker) or your card may have this option in it's control panel.

Once you have the card set-up select 16-235 in the HCFR view images settings (or 16-235 in the madVR settings) for a display set to video levels. If the display is set to expect PC levels choose 0-255 in HCFR or the same in madVR. There are no level settings required when using the Chromecast as your pattern generator.

All three pattern generators have settings for window size as percent of screen area and background level as percent average picture level. Which settings you use depends on your particular display so it's best to consult an owners thread for specific recommendations.
 
See less See more
#4,141 ·
This, I don't understand. What is the point of keeping track of expected luminance targets based on differential encoding of patterns if the end result is not to obtain similar calibrations using any of the supported test pattern sources? Let's say we know that 40% gray on AVS709 actually translates to 39% (for simplicity sake) in PC Levels due to the way it is encoded. If HCFR supports AVS709 and is aware of the way it is encoded (which it does), then shouldn't it internally determine the luminance target assuming this is a 39% gray pattern, not a 40% Gray pattern? That way, you have a much better chance of tracking correctly when switching between AVS709 and the HCFR or madTPG pattern sources. My guess is that perhaps it does this correctly for video levels and that using AVS709 v/s HCFR pattern for video levels would result in the same curve, but I have no way of testing it myself.
The AVS-HD (et. al.) disks were encoded with the assumption that "video" levels are being used. Period. One should *not* being using "PC" levels to display sources encoded with "video" levels. Period. :)

If you want to calibrate to "PC" levels you need to use a source pattern that was encoded at PC levels ... It should be simple to construct these targets yourself with any PC "paint" or photoshop-type program.

PS: In my earlier post, when I said "luminance level(s)," I really meant "video/stimulus" level.
 
#4,143 ·
Hello to all.
As it is impossible to read all 139 pages...is it possible for someone to point me to the right direction please? I need to find instructions for how to use Spyder 4 in Mac OS 10.9.4 with HCFR. Some searching in the wiki didn't help as I have found instructions only for windows...and I am a newbie in Mac environment as well :confused:

thank you in advance :)
 
#4,144 ·
I have just bought an i1Display Pro to use with HCFR to calibrate my Pioneer Kuro 5020 with an 111FD board in it. I also purchased ControlCal to unlock and calibrate the ISF modes. I have gotten my grey-scale almost perfect but I am a little unsure of how to calibrate the Primary and Secondary Colors on my display. My Kuro does have the Color Management System. If someone could help me understand how to do this, that would be great! My deltaE values are already pretty low for these colors but I really would like to get them under 1.0.
 
#4,145 ·
I totally disagree. Outputting "video" content in "PC" levels is just fine, as long as the source device (respectively test pattern generator) uses proper dithering - which it should use, anyway.
But why make life harder for yourself? Especially when doing the calibration. :D

BTW, AFAIK, HCFR can generate the proper test patterns for you ... in theory ... I've never bothered to verify that the pattern generator is operating bug-free.

You're not gaining anything by scaling Video to PC. OTOH, you will lose any superwhite detail that might have been in the source. Just because you "can" do something doesn't mean that you should do it. ;)
 
#4,146 · (Edited)
You're not gaining anything by scaling Video to PC. OTOH, you will lose any superwhite detail that might have been in the source. Just because you "can" do something doesn't mean that you should do it. ;)
I think you are overlooking a sizeable percentage of folks such as myself who use HTPCs to view all video content at home. GPUs operate at PC levels and forcing them to operate at video levels leads to inaccuracies. The reason being that even if your renderer sends video level input to the GPU, it will internally convert to PC levels, process the data and then output back to video levels...resulting in a compounding of inaccuracies. Renderers like madVR can provide far better image scaling/PQ for lower resolution content than your typical hardware players. Moreover, it also supports 3D LUT processing to get pretty much perfect color accuracy within the limitations of your meter.

I could use ArgyllCMS + dispcalGUI to profile my display and get near perfect results using 3D LUT, but then my display would only be calibrated for video content rendered via madVR. I would prefer to use HCFR to get as close to reference levels using hardware tweaks so that I can enjoy this calibrated display for all content viewed via my HTPC. The 3D LUT is more of a 2nd order correction that I would prefer to use just in MPC-HC when using madVR.

All of these reasons are why some of us would prefer to calibrate to PC levels. It isn't just a science experiment for the sake of it :). Since HCFR seems to support PC levels, I figured that it would make sense to compare results. At the moment, I'm not sure if there is some slight bug in the implementation/interpretation of data when measuring at PC levels. As madshi pointed out, there is some discrepancy that doesn't quite seem to make sense. Would love to get zoyd's thoughts on this.

Edit - PS, we don't have to lose superwhite detail when using PC levels at least with madVR. We can set custom level ranges that let us choose with great granularity what black/white levels we would wish to clip at. We could easily set things up so that a few levels of BTB and WTW were visible in video content.
 
#4,147 ·
But why make life harder for yourself? Especially when doing the calibration. :D

You're not gaining anything by scaling Video to PC.
Then how do you suggest should an HTPC user who wants to use the PC for video playback, photo display, games etc, setup his playback chain? Do you recommend to set the GPU to 16-235 output? If you really recommend that, then you seemingly don't know much about HTPCs work inside. Windows internally thinks/works in PC levels. If you set the GPU to 16-235 output, the GPU will stretch all the rendered desktop/video/game pixels from PC levels to TV levels behind the back of the applications and behind the back of Windows itself, and usually the GPU does this in 8bit without using dithering. Which means you'll get banding artifacts.

There's nothing wrong with using PC output levels, as long as your display properly supports that. Ok, so maybe HCFR needs to be tweaked a bit to fix the issues we discovered, but I'm sure this will be fixed soon enough.

Btw, you're saying "by scaling Video to PC". But in reality it's rather the other way round: Since the PC natively works in PC levels, if you set the GPU to TV output, video will first be rendered to PC levels, and then stretched afterwards to TV levels. So this way you have more stretching and more conversions going on than when using PC output levels. The thing is: Video is encoded in YCbCr. This needs to be converted to RGB first, anyway, and this YCbCr -> RGB conversion consists of a matrix multiplication. You can in one step convert YCbCr to either TV RGB or PC RGB. It's the same operation, just with a different matrix multiplication. So basically you can render video in either TV RGB or PC RGB without stretching or scaling anything at all. Rendering a YCbCr video in PC RGB does not require any additional scaling or stretching operations. However, if you set the GPU to TV levels output, you introduce an additional stretching operation (and that often in low bitdepth without dithering).
 
#4,149 ·
Hello there,

First of all, thanks for keeping maintained this great software. I'm just trying to calibrate my LCD monitor and plasma tv time to time on 'hobby' level, so a shareware software is really not for me :)

I have an i1Display2 since ~4 years. I know that this device is far from being perfect in terms of precision and stability over time. Yet, I'd like to know if it is still possible in a way to use it? So, I have some questions:

- I've read here, and other sites as well that it is somehow possible to calibrate colorimeters to a better reference. I have an access to an i1DisplayPro. Is it possible to make the i1D2 back on track for a while with this device?

- So far what I've understood, I'll need to create a correction matrix, and provide this to HCFR when calibrating next time with i1D2..? Is there a description available somewhere how to do this procedure?

- I have a Panasonic VT60(VT65) plasma TV, which is famous for its high precision, and high configurability.
Do you think it makes sense to try to do the job with the i1D2?

- If I am not mistaken, this colorimeter referencing should be done on a certain display. I am not sure if I can borrow the DisplayPro from the guy who has it. So I might need to go to his place, and compare the two devices on an LCD screen. Can this work, or the result would not give me an i1D2 that could be used on my plasma screen?

I think you know get the point what I'd like to achieve. If you could give me advice how to go on, that would be really great!

Thanks!
Gabor
 
#4,150 ·
#4,152 ·
Then how do you suggest should an HTPC user who wants to use the PC for video playback, photo display, games etc, setup his playback chain? Do you recommend to set the GPU to 16-235 output?
No ... In this case, what I'm saying, is that for *calibration* you should not be trying to convert "Video" targets (AVS-HD, et al.) to "PC" targets ... Start with PC targets and skip the conversion/scaling.

If you were to run HCFR on the *same* HTPC as you use for video playback, then you can just use the "internal" HCFR pattern generator. Much easier and faster ... Assuming you set HCFR to expect 0-255 (PC Levels.)

Still, this leaves you with a fundamental problem for playback: So do you scale 16-235 up to 0-255? ... 16-255 to 0-255? ... or preserve the entire BtB to WtW range (no scaling) and adjust "black-level" (and gamma/EOTF) as necessary? .... Exactly :D ... This is the problem with mixing and matching Video level sources with PC level displays.
 
#4,153 · (Edited)
This is an excellent guide I've found regarding this:
http://avforum.no/forum/attachments...cfr-probe-software-hcfr_calibration_files.pdf
@zoyd - Perhaps it might be good to include a link to this guide in the OP?
I've been posting this method periodically over the past few years:

For HCFR, profiling a colorimeter to the i1 Pro spectrometer is a simple matter. I'll use the i1 Display 3 as an example. The object is to create a correction color matrix which is to be used with the LT D3. It's explained, not too clearly, in the HCFR Help Menu/Advanced/XYZ Adjustment/Compute section.


1. Set up a calibration DVD to display the primary (red, green, blue) colors and white windows sequentially.
Use a 10% window at 100% amplitude.

2. Put both the D3 and the Pro on the TV panel so the meter sensor holes are vertically in the center of the window and right next to one another. (Or you can do each meter sequentially so that both are reading the same area.)

3. Set up HCFR for the i1 Pro meter and do a normal sensor black level calibration (Measures/Sensor/Calibrate...)

4. Run the primary colors and the white windows reading the data with HCFR set up for the i1 Pro meter. Save the run as something like "pro meter calibration.chc"

5. Set up HCFR for the D3 meter and do a normal sensor black level an 80% white level sync calibration (Measures/Sensor/Calibrate...)

6. Run the primary colors and the white windows reading the data with HCFR set up for the D3 meter. Save the run as something like "D3 meter calibration.chc"

7. Display the i1 Pro results on your computer and check the "Reference measure" box in the upper right hand corner.

8. Display the D3 results and click Advanced/Meter correction file/Create using existing reference measures.

9. Display the D3 results and click Advanced/Meter correction file/Save meter correction file... Save it with a name like "D3 calibration matrix 08-17-2014"



Larry
 
#4,154 ·
I've been posting this method periodically over the past few years:

For HCFR, profiling a colorimeter to the i1 Pro spectrometer is a simple matter. I'll use the i1 Display 3 as an example. The object is to create a correction color matrix which is to be used with the LT. It's explained, not too clearly, in the HCFR Help Menu/Advanced/XYZ Adjustment/Compute section.


1. Set up a calibration DVD to display the primary (red, green, blue) colors and white windows sequentially.
Use a 10% window at 100% amplitude.

2. Put both the D3 and the Pro on the TV panel so the meter sensor holes are vertically in the center of the window and right next to one another. (Or you can do each meter sequentially so that both are reading the same area.)

3. Set up HCFR for the i1 Pro meter and do a normal sensor black level calibration (Measures/Sensor/Calibrate...)

4. Run the primary colors and the white windows reading the data with HCFR set up for the i1 Pro meter. Save the run as something like "pro meter calibration.chc"

5. Set up HCFR for the D3 meter and do a normal sensor black level calibration (Measures/Sensor/Calibrate...)

6. Run the primary colors and the white windows reading the data with HCFR set up for the D3 meter. Save the run as something like "D3 meter calibration.chc"

7. Display the i1 Pro results on your computer and check the "Reference measure" box in the upper right hand corner.

8. Display the D3 results and click Advanced/Meter correction file/Create using existing reference measures.

9. Display the D3 results and click Advanced/Meter correction file/Save meter correction file... Save it with a name like "D3 calibration matrix 08-17-2014"



Larry
yes you have.
you helped me 3 years ago with this.
thumbs up
 
#4,155 ·
I've been posting this method periodically over the past few years:
...
Larry
Thanks Larry for the description!
I tried to search the forum extensively, but somehow I was not successful :(

Some questions regarding this:
- can I perform this procedure on a different display and not on the one that I have? Eg. create this calibration matrix on an LCD screen, and then re-use it on my plasma screen? (I suppose not, but I I am not sure why)
- in my original post I mentioned i1DisplayPro. I think this is a colorimeter and not a real spectrometer. Does this mean my intention of profiling my i1d2 is meaningless, or does it make sense?

(sorry, as this is not strictly related to HCFR anymore)

Thanks!
 
#4,156 ·
- in my original post I mentioned i1DisplayPro. I think this is a colorimeter and not a real spectrometer. Does this mean my intention of profiling my i1d2 is meaningless, or does it make sense?
It's not meaningless, but you should recognize that you will be limited by the inherent accuracy of the i1 Display Pro. Your i1D2 should provide very similar readings to your i1 Display pro after profiling and applying the correction matrix. I've used a similar approach to profile my ancient Spyder 2 that had a major Red filter discrepancy (typical with aging) to my Colormunki Display. After profiling, the Spyder2 matches really well for >40% gray scale and has a slight issue with red at lower light levels (more likely due to the age of the Spyder 2 tech).

A spectrometer will give you more absolute certainty in the accuracy of your profiled meter.
 
#4,157 ·
There's nothing wrong with using PC output levels, as long as your display properly supports that. Ok, so maybe HCFR needs to be tweaked a bit to fix the issues we discovered, but I'm sure this will be fixed soon enough.
I'll take a look at it and adjust the targets for 0-255 use if needed. (Dithering is not needed for calibration purposes).

zoyd,

Any chance to add a "Keep previous 0% reading" option to skip the first step once its already measured?
Just to make the next Gray Scale readings quicker.

Or is there an option to that already?
No, that's too much special code for the sake of a few seconds worth of measurements. I have been considering "partial" grayscale measurement repeats however and that would accomplish the same thing. Basically you would click on a level and the scan would include from there on up.

Hello there,

First of all, thanks for keeping maintained this great software. I'm just trying to calibrate my LCD monitor and plasma tv time to time on 'hobby' level, so a shareware software is really not for me :)

I have an i1Display2 since ~4 years. I know that this device is far from being perfect in terms of precision and stability over time. Yet, I'd like to know if it is still possible in a way to use it? So, I have some questions:

- I've read here, and other sites as well that it is somehow possible to calibrate colorimeters to a better reference. I have an access to an i1DisplayPro. Is it possible to make the i1D2 back on track for a while with this device?

- So far what I've understood, I'll need to create a correction matrix, and provide this to HCFR when calibrating next time with i1D2..? Is there a description available somewhere how to do this procedure?

- I have a Panasonic VT60(VT65) plasma TV, which is famous for its high precision, and high configurability.
Do you think it makes sense to try to do the job with the i1D2?

- If I am not mistaken, this colorimeter referencing should be done on a certain display. I am not sure if I can borrow the DisplayPro from the guy who has it. So I might need to go to his place, and compare the two devices on an LCD screen. Can this work, or the result would not give me an i1D2 that could be used on my plasma screen?

I think you know get the point what I'd like to achieve. If you could give me advice how to go on, that would be really great!

Thanks!
Gabor
yes, I think it would be helpful to profile the D2 to an i1 display pro. If you want to do this you should choose the proper display type for the display pro (lcd or plasma) prior to profiling and your plasma correction will need to done on a plasma display.

This is an excellent guide I've found regarding this:
@zoyd - Perhaps it might be good to include a link to this guide in the OP?
Thanks but that doc might be confusing since it's specifically for the DIY probe, I'll add a link to Larry's post.
 
#4,158 ·
I'll take a look at it and adjust the targets for 0-255 use if needed. (Dithering is not needed for calibration purposes).
Thanks zoyd! I really appreciate it. It'd be great if you could post an update on this whenever you get the chance to look at it. It would be nice to know whether you had to make any changes or chose to leave things as is. Cheers.
 
#4,159 ·
I have an i1Display2 since ~4 years. I know that this device is far from being perfect in terms of precision and stability over time. Yet, I'd like to know if it is still possible in a way to use it?
I too use a 4 yr old i1d2 + HCFR for my calibrations. I've spent many hours attempting to properly calibrate my samsung F5300 plasma. I've been running into major issues with temperature based reading fluctuations. The i1d2 has no temperature compensation while the i1d3 (i1 Display Pro) does. This is the first time I've run into this issue as it's my first plasma (heat!) that I've spent any significant time calibrating.

I'm not sure if the i1d2 is more accurate with the plasma when heated up vs cold but you may want to take this into consideration when creating a correction profile.

I personally have given up on my i1d2 because of its inability to measure black levels, potentially degraded sensor, and lack of temperature compensation. An i1d3 is in my sights as a replacement.
 
#4,160 ·
Thinking of upgrading meters. I have an old Spyder 2 that I'm using to run calibration with HCFR... obviously it's old and not the most desirable meter to use. For the "home calibration hobbyist" what is generally recommended as the best consumer-grade meter to use with HCFR on a limited budget? Thanks!
 
Top