AVS › AVS Forum › Display Devices › Display Calibration › Fork of HCFR Started - What's needed?
New Posts  All Forums:Forum Nav:

Fork of HCFR Started - What's needed?

post #1 of 1957
2/13/12 at 7:28am
Thread Starter 

Hi – welcome to the developing HCFR Thread.

 

The bottom of this post is the original post by JohnAd, but I have been allowed to modify this Opening Post to try and summarise and organise the thread to make it more manageable.

 

If you have seen a post you think should be added here, PM me.

 

The latest HCFR “Fork” has been taken up by Zoyd – and can be found here;-

 

 

Useful Links

- Display Calibration - Part I

- Curtpalme - Calibration Guide for Dummies

- Basic Guide to Color Calibration using a CMS (updated and enhanced)

- Spears and Munsil

- Choosing a Color Space | Spears & Munsil

- The Secrets Blu-ray Player HDMI Benchmark Part 1  and Part 2 

 

 

 

Links to Tools & Utilities

AVSHD709 Test Disk

GCD Disk

Mascior's Calbration Disc 

 

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 tool
#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

# – 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 Matric different to 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 Privilleges

#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:-

To follow.

 

Thanks, Wayne

User: Wl1

 

 

 

 

JohnAd, the Thread Starters Original Post, follows:

 

===========================================================================================

 

HCFR Fork

The latest windows version is now 3.0.4.0

Get it from the project page

http://hcfr.sourceforge.net/

The changelog is here

http://sourceforge.net/p/hcfr/wiki/Changelog/

The Mac version is still being developed but is not ready for a public release yet.

Original Post

I've started a fork of the HCFR code at

http://sourceforge.net/projects/hcfr/

So far the code for version 2.1 is up and compiling cleanly under Visual Studio 2008, (VS 2010 support in a day or two)

My plan over the next few weeks is to:

1) Allow use of GPL meter code/drivers from Argyllcms
2) remove current non-free meter code for spyder and eye-one devices
3) Correct any major bugs
4) Add support for meter plug-ins

What does everybody think are the biggest issues with the current code?

Dan has posted a few bugs http://www.avsforum.com/avs-vb/showt...0#post15611490

Are there any other bug reports/major issues with 2.1 that I should be aware of?

http://hcfr.sourceforge.net/

This is where the latest versions will be posted as well as meter specific documentation.

John


Edited by wl1 - 5/5/13 at 2:02pm
Reply
Reply

AVS Top Picks

post #2 of 1957
2/13/12 at 7:34am
Any developers with a good knowledge of C++ and MFC who wish to help out, add features or test particular meters should join the development mailing list

https://lists.sourceforge.net/lists/...hcfr-developer

Look forward to hearing from you.

John
Reply
Reply
post #3 of 1957
2/13/12 at 1:29pm
Cool. Good luck. I'm loving HCFR so much more now that I own a i1pro and Display2.

Support for display3 should be a priority.

Something easy could be more graph options and maybe report generation.

Long live the legend, HCFR!
Reply
Reply
post #4 of 1957
2/13/12 at 1:49pm
Quote:
Originally Posted by Brian Hampton View Post

Cool. Good luck. I'm loving HCFR so much more now that I own a i1pro and Display2.

Support for display3 should be a priority.

Something easy could be more graph options and maybe report generation.

Long live the legend, HCFR!

It's not bad for freeware but cost aside I much prefer CalMAN or ChromaPure.
Reply
Reply
post #5 of 1957
2/13/12 at 1:54pm
To each his own I guess. HCFR is a lot free-er.

( I don't think I'll ever choose CalMan but I would be happy to use Chromapure eventually. )



Back to suggestions: it's easy to profile my dispay2 to my i1 pro in HCFR, but it could be even easier if the process was better integrated.
Reply
Reply
post #6 of 1957
2/13/12 at 1:55pm
I can test with ver 5.1 of the HCFR TAOS based probes as I have several. I subscribed to the dev forum. I can hack in VB and have 2008 visual studio that I would be interested in having a build environment working.

It's great to see this arising again.
Reply
Reply
post #7 of 1957
2/13/12 at 1:57pm
Quote:
Originally Posted by Brian Hampton View Post

To each his own I guess. HCFR is a lot free-er.

( I don't think I'll ever choose CalMan but I would be happy to use Chromapure eventually. )



My main gripe is that it needs updating and support for newer hardware. I do like however that it supports the i1pro spectro.
Reply
Reply
post #8 of 1957
2/13/12 at 1:59pm
The killer notion would be: a Mac version!

CalMan and Chromapure are ignoring Apple.

I would help making an iPad version. (I'm not sure how but I would help anyway I could.)

-Brian
Reply
Reply
post #9 of 1957
2/13/12 at 2:00pm
Quote:
Originally Posted by Brian Hampton View Post

Support for display3 should be a priority.

Agreed that and the colormunki are the 2 main popular meters missing

Quote:
Originally Posted by Brian Hampton View Post

Something easy could be more graph options and maybe report generation.

Not sure about easy ...
At least initially I'll be focusing on opening the use meters up so the taking and sharing of readings is as easy as possible, this probably means dumping data out to spreadsheets for graphing/reports rather than building too many more screen in hcfr as at the moment each graph seems to be quite a lot of code.

John
Reply
Reply
post #10 of 1957
2/13/12 at 2:03pm
Quote:
Originally Posted by Brian Hampton View Post

The killer notion would be: a Mac version!

There was a mac version, I just haven't got the code for that, I'm happy to try and restart that though if anybody has the source let me know.

John
Reply
Reply
post #11 of 1957
2/13/12 at 2:05pm
Quote:
Originally Posted by dlarsen View Post

I can test with ver 5.1 of the HCFR TAOS based probes as I have several. I subscribed to the dev forum. I can hack in VB and have 2008 visual studio that I would be interested in having a build environment working.

Cool, should be just a question of installing git (I Use tortoisegit) and pulling the source from sourceforge and then building the project.
Reply
Reply
post #12 of 1957
2/13/12 at 2:09pm
Meters supported will be the same as

http://www.argyllcms.com/doc/ArgyllDoc.html

John
Reply
Reply
post #13 of 1957
2/13/12 at 2:18pm
Quote:
Originally Posted by JohnAd View Post

Meters supported will be the same as

http://www.argyllcms.com/doc/ArgyllDoc.html

John

That's awesome!

I have the Mac version (not the source code though) but I think it supports even fewer meters. Like just the spyders
Reply
Reply
post #14 of 1957
2/13/12 at 5:41pm
I read the above comments, and my main gripe with HCFR is that the red, green, and blue data on the luminance and gamma graphs is normalized. I think the non-normalized data when you choose the display RGB checkbox is a lot simpler to understand, but unfortunately new users typically find it easier to have graphs to represent the data. I consider it more intuitive to have one graph that represents the entire grayscale run, rather than trying to get new users to understand what two graphs represent (luminance and RGB levels). Maybe it's just me, but I think comparing non-normalized red, green, and blue plots to a target gamma curve is far simpler to comprehend the limitations of 2-point grayscale controls.
Reply
Reply
post #15 of 1957
2/13/12 at 10:03pm
Ah this is excellent to see. I'd be very keen on a mac port, and likely to contribute to it, so hopefully the source can be found...!
Reply
Reply
post #16 of 1957
2/13/12 at 10:06pm
Continuous real-time 11 point gamma display.
Reply
Reply
post #17 of 1957
2/14/12 at 2:24am
From what I remember, HCFR doesn't calculate dE's of colours correctly. You'd also have to manually calculate what the luminance level should be for each colour then adjust brightness to that.
Reply
Reply
post #18 of 1957
2/14/12 at 3:28am
Thanks for all the feedback so far, so quite a lot to do then

I've only really used it at a way of getting raw measurements so haven't really seen a lot of the issues metioned.

Correcting the dE and normalising side of things should be fairly straightforward, but I'd expect getting agreement on what's right to take longer....

John
Reply
Reply
post #19 of 1957
2/14/12 at 3:29am
Quote:
Originally Posted by 703 View Post

From what I remember, HCFR doesn't calculate dE's of colours correctly.

I think HCFR excludes Y errors from dE, is that what you mean or is there a bigger issue?

Quote:
Originally Posted by 703 View Post

You'd also have to manually calculate what the luminance level should be for each colour then adjust brightness to that.

Not sure what you mean here, is this for non-additive displays?

John
Reply
Reply
post #20 of 1957
2/14/12 at 4:13am
Quote:
Originally Posted by Kilgore View Post

Continuous real-time 11 point gamma display.

I don't know if that's possible. Wouldn't you need 11 measuring devices?
Reply
Reply
post #21 of 1957
2/14/12 at 4:23am
I don't think HCFR leaves Y out of color DE. Currently I have green with perfect xy and 30% Y error and de is high.

I'm not even convinced HCFR calculates color de wrong. This is something I could investigate. It's easy enough to manually put in the data thats correct and then modify it different ways.
Reply
Reply
post #22 of 1957
2/14/12 at 4:25am
Quote:
Originally Posted by Kilgore View Post

Continuous real-time 11 point gamma display.

Can you give a bit more of a description of what you mean, how you would see this working? Do you mean you pick which point you are doing and then working with continuous readings and a target?

Would you expect to normalize the luminance of the 100% or the 109% point?

So do 0% to get black, 109% to get peak and then do 100%, 90%... 10%

John
Reply
Reply
post #23 of 1957
2/14/12 at 5:08am
Sure would be nice to be able to put up 75%, 50% and 25% saturation points on the gamut chart since many use 75%.
This way using Continuous Measure to align hue and saturation would be simplified.
Reply
Reply
post #24 of 1957
2/14/12 at 5:11am
Quote:
Originally Posted by Brian Hampton View Post

I don't think HCFR leaves Y out of color DE. Currently I have green with perfect xy and 30% Y error and de is high.

I'm not even convinced HCFR calculates color de wrong. This is something I could investigate. It's easy enough to manually put in the data thats correct and then modify it different ways.

Looking through the code there seems to be some quite confusing labeling going on.

In the advanced tab, there are 2 settings at the bottom

The first of those "Do not use luminance in delta E formula (V1.x)" corresponds to the internal setting Use Old DeltaE so should be off.

The second of those is "Use gamma reference to compute gray scale delta E" should be on if you want Y to be included in dE and off if you don't.

The default for both is off so unless you change something Y is not included in dE.
Reply
Reply
post #25 of 1957
2/14/12 at 6:02am
Quote:
Originally Posted by JohnAd View Post

Can you give a bit more of a description of what you mean, how you would see this working? Do you mean you pick which point you are doing and then working with continuous readings and a target?

Would you expect to normalize the luminance of the 100% or the 109% point?

So do 0% to get black, 109% to get peak and then do 100%, 90%... 10%

John

I think what he means is actually a 9-point gamma real-time tracking for 10% - 90% (0% black and 100% white have no gamma value). Right now it is not convenient to do that because the target Y values are calculated only after a complete grayscale run from 0% to 100%. If I'm only adjusting the gamma of, say the 70% point, what I need to measure is the 0% Y value and the 100% Y value, and the target Y for my 70% point should be calculated and show up on the screen for me to shoot for that value (using continuous measure).
Reply
Reply
post #26 of 1957
2/14/12 at 6:11am
Quote:
Originally Posted by dominickwok View Post

I think what he means is actually a 9-point gamma real-time tracking for 10% - 90% (0% black and 100% white have no gamma value). Right now it is not convenient to do that because the target Y values are calculated only after a complete grayscale run from 0% to 100%. If I'm only adjusting the gamma of, say the 70% point, what I need to measure is the 0% Y value and the 100% Y value, and the target Y for my 70% point should be calculated and show up on the screen for me to shoot for that value (using continuous measure).

Yeah,... I use a secondary excel spreadsheet that I put in the 100% Y value and it gives me the rest for any gamma target. This way I can adjust other values without running the whole set of measurements.

There's no lack of things do suggest for HCFR since it's not been updated in years. Just enhancing the meter support would be HUGE.

-Brian
Reply
Reply
post #27 of 1957
2/14/12 at 2:17pm
[/QUOTE=Brian Hampton;21643233]Yeah,... I use a secondary excel spreadsheet that I put in the 100% Y value and it gives me the rest for any gamma target. This way I can adjust other values without running the whole set of measurements.


-Brian[/quote]

Same here - having to use a separate spreadsheet is a pain with HCFR, would be great to be able to use the HCFR 100%Y value and have the program calculate at least the 100% & 75% saturation levels for a gamma target, should not be too hard to do. Link to spreadsheet that shows how this is done: http://www.avsforum.com/avs-vb/showt...7#post15607437
Also support for the new Display-3 would be great. Just adding these two features would make HCFR useful for most of the basic DIY calibration tasks.
Reply
Reply
post #28 of 1957
2/14/12 at 5:49pm
Quote:
Originally Posted by JohnAd View Post

Can you give a bit more of a description of what you mean, how you would see this working? Do you mean you pick which point you are doing and then working with continuous readings and a target?

Would you expect to normalize the luminance of the 100% or the 109% point?

So do 0% to get black, 109% to get peak and then do 100%, 90%... 10%

John

I want it to be able to take the 100% Y reading and calculate the appropriate Y reading for each level down to 10% (90%, 80%, 70%, etc) so that I can adjust the level of Y at each level to match the calculated target to achieve the gamma I want at each level.

...and I want to be able to make these adjustments in real time without having to refer to a spreadsheet..

As it stands now, all you can do is do a full set of grayscale measures and see what the (average) gamma is and see the curve displayed on a chart. You can't see the results of any gamma corrections you make in real time. You can just guess at some corrections and then do another full set of grayscale measures, and keep repeating until you get a gamma reading you want.
Reply
Reply
post #29 of 1957
2/14/12 at 5:50pm
Quote:
Originally Posted by dominickwok View Post

I think what he means is actually a 9-point gamma real-time tracking for 10% - 90% (0% black and 100% white have no gamma value). Right now it is not convenient to do that because the target Y values are calculated only after a complete grayscale run from 0% to 100%. If I'm only adjusting the gamma of, say the 70% point, what I need to measure is the 0% Y value and the 100% Y value, and the target Y for my 70% point should be calculated and show up on the screen for me to shoot for that value (using continuous measure).

Yes, that is what I meant.
Reply
Reply
post #30 of 1957
2/14/12 at 10:40pm
Quote:
Originally Posted by Kilgore View Post

You can just guess at some corrections and then do another full set of grayscale measures, and keep repeating until you get a gamma reading you want.

This may not be necessary. You can display the %stimulus pattern in question, e.g. a 70% window, use free measurement to observe the measured xyY value while changing your gamma setting for 70% in the TV/projector, and align the measured Y to the target gamma Y as shown in the measurement table.

If you suspect the 100% luminance level is changed, you can check the box "Editable data" in the measurement table, do a free measurement at the 100% pattern, copy-and-paste the measured xyY data (on the left side of the screen) to the column of 100% data, and all the target gamma Y values for 10% - 90% will be refreshed.

Of course, this will work only if you have done a complete grayscale run; and the process is too clumbersome.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Display Calibration

AVS Top Picks

AVS › AVS Forum › Display Devices › Display Calibration › Fork of HCFR Started - What's needed?