or Connect
AVS › AVS Forum › Display Devices › Display Calibration › HCFR - Open source projector and display calibration software
New Posts  All Forums:Forum Nav:

HCFR - Open source projector and display calibration software - Page 59

post #1741 of 3434
Thread Starter 
This is an LED correct? Are you using full field patterns? It looks like a real non-linearity in your CMS. Try calibrating at 75% luminance and see what the changes are in the saturation scan. Also try calibrating at 75% luminance and 75% saturation. It's a fairly large error but might be confined to a relatively small portion of the gamut and not really an issue, everything else looks great.

For 75% luminance calibration use the same Rec. 709 color space but use primary/secondary + white patterns at 75% luminance.

For 75% luminance/75% saturation use the Rec. 709(75%) color space and use primary/secondary + white patterns at 75% amplitude/75% saturation. These are available on the GCD disk.
post #1742 of 3434
Yes. This is an LED and I used the HCFR full patterns on the AVSHD709 disk. I have tried using the 75% color, 100% color, and the saturation patterns at 75% from the AVSHD709 disk. I will have to see what some of the other color spaces on the TV look like too. I am using Standard now on the TV because it seems to calibrate easiest without big swings in the CMS. I also have Wide and REC709 to choose from, but they seem to have those bigger number swings to them than standard did. I do not have the GCD disk currently. I think for some reason, I was not able to get that to burn last time I tried it. User error I am sure.

So is there a certain pattern on AVSHD709 disk that I should definitely be using to zero in on this? If I used the saturation patterns at 75% and went and did a 6 color run, then do I use 75% white also or change to 100% when HCFR asks for white pattern?

I also must add if it makes any difference to this. Blue does nothing on my CMS at all. I have -30 to +30 adjustments for Color and Tint and blue barely moves no matter what I do. Visually on the saturation sweeps on the AVSHD disk, blue is a definite purple tint at 25, 50, and 75%. It only looks blue by eye at 100% saturation. Not sure if that would have anything to do with the green not lining up or not.
post #1743 of 3434
Thread Starter 
Quote:
Originally Posted by eghill1125 View Post

Yes. This is an LED and I used the HCFR full patterns on the AVSHD709 disk. I have tried using the 75% color, 100% color, and the saturation patterns at 75% from the AVSHD709 disk. I will have to see what some of the other color spaces on the TV look like too. I am using Standard now on the TV because it seems to calibrate easiest without big swings in the CMS. I also have Wide and REC709 to choose from, but they seem to have those bigger number swings to them than standard did. I do not have the GCD disk currently. I think for some reason, I was not able to get that to burn last time I tried it. User error I am sure.

If that 75% green is pulled toward blue in all of the TV presets then it is probably inherent in the display and not the CMS itself. Also, if you don't see it in cyan then it is probably not related to the problem you are having with blue.
Quote:
So is there a certain pattern on AVSHD709 disk that I should definitely be using to zero in on this? If I used the saturation patterns at 75% and went and did a 6 color run, then do I use 75% white also or change to 100% when HCFR asks for white pattern?

I think the AVSHD 75% saturation patterns are at 100% luminance but I haven't used it in awhile so I'm not sure. Adjusting the primaries to get the 75% saturation points lined up should correct your green problem, then you'll have to see if that messed up the rest of the green tracking.
post #1744 of 3434
Yes, the AVSHD709 saturation patterns (0-100% in 25% increments) are at 100% luminance. The "75% color" patterns are 100% saturation 75% luminance. So if you use the saturation patterns, use 100% white. If you use the 75% color patterns, use 75% white. Or just the GCD disc...
post #1745 of 3434
I just did a quick look and wasn't able to really dig into it, but I used the 75% amplitude/ 75% saturation patterns on the GCD disk and my points are way inside the targets of the triangle. What does this mean? do I need to increase my color then. If I do that, my color goes from default of 50 to 60. Maybe that is right, but I have never put it up there before and have yet to see anyone who has..
post #1746 of 3434
Thread Starter 
Set the color space to Rec709(75%)
post #1747 of 3434
How much closer to white are they?

The color control basically controls color luminance... if your points are inside the targets (ie closer to white) then you need to increase color saturation in the CMS.

edit: if you didn't change it to Rec709 75% as zoyd said above, that would explain why they're way inside.
post #1748 of 3434
Well I was not successful last night in doing anything with the CMS. So I did the only thing I knew would work, but not really what I wanted to do.

I zeroed out the CMS completely and redid the grayscale. Took measurments and called it quits. Numbers look good. The tinkerer in me wants some kind of numbers on the CMS, but it is of no use now. If I even try to adjust my CMS, I completely screw it up. So at this point I am calling it done with no CMS adjustments at all. The LG seems really good with just the grayscale adjustments.. Just wanted to try and adjust the CMS for purely the idea that I did it.

Here is my charts with grayscale adjustment and measurments. Look ok leaving the CMS unaltered?

This seems to be the only thing in HCFR that I struggle with. I guess that it is because I do not see nice little bars showing 105% red and 109% blue like the grayscale. Other than that, I can not find any reason that HCFR did not do the job real well for me. The CMS stuff is just me not figuring it out without the changes showing like the grayscale does. Great software and thank you Zoyd for what you have done with this.

Final Expert 1.zip 29k .zip file
post #1749 of 3434
Thread Starter 
yes, you aren't going to squeeze much more out of that CMS as-is, looks great. How do flesh tones look visually?
post #1750 of 3434
It was around 2 in the morning when I finished and had to be at work at 7, so I didn't get a long look after. From what I saw this morning before work on regular TV, the faces look like they have more natural color than what I was coming up with before. Everything I had done in the past calibrations had either a greenish tone to cheeks or some kind of strange lining look almost. The lining ( dumb word to use but ) is almost like I could see 4 different colors to a persons face. All the colors were close to each other, but some would be a faint tinted yellow on a cheek above a faint tinted pink above a tinted orange. Only if I was being critical and really looking at a persons face would I see it. The family would have no idea.

I did not see that this morning at all. The wife had on GMA and that George S. and the others on that set all had a nice realistic look to them.

So I guess I will put away the meter for a while and enjoy some blu-rays. I think this is about the best I will be able to do with the limited experience I have and no clue on how this LG CMS works. Default is the best option and I think visually looks best too.

Thanks again for helping me learn some of this stuff.
post #1751 of 3434
Hello everyone on the forum. I would like to show you the results of my calibration.



Uploaded with ImageShack.us



Uploaded with ImageShack.us

This is LED TV Samsung C6500 series. What do you think?

04042013.zip 11k .zip file
Edited by jjccckk - 4/4/13 at 11:40am
post #1752 of 3434
Thread Starter 
hey that looks really good, did you measure the primaries at 75% stimulus or do any saturation tracking runs?
post #1753 of 3434
Hi Zoyd, I'd like to try HCFR but I'm unable to load the Argyll CMS drivers for my Spyder3 Elite.

The Spyder was running on v3.1.5 of Datacolor's software. When I remove the drivers and select the Spyd3.inf file from HCFR's directory, I first get a message saying that the Spyder3 (Argyll) drivers aren't properly signed 'Authenticode signature not found'; I OK that and it appears to copy a libusb0 or similar file, then the driver installation fails with the message "An error ocurred during the installation of this device. A service installation section in this INF is invalid".

I'm running Windows XP Pro, x64, SP2. Microsoft User Mode Driver Framework Feature Pack 1.0 is installed.

I've looked around but haven't found much that's relevant and I'd appreciate if you could suggest what the problem might be. Thanks!
post #1754 of 3434
Thread Starter 
I don't know what that problem means, you can also try using the vendor drivers like this person.
post #1755 of 3434
Quote:
Originally Posted by zoyd View Post

hey that looks really good, did you measure the primaries at 75% stimulus or do any saturation tracking runs?
I did the normal calibration. According to this: http://www.curtpalme.com/forum/viewtopic.php?t=10457:). The only difference is White Balance measured at 20% instead of 30%. After some time I will calibrate the boards by 75% and 75% amplitude saturation. But my TV is only average. I do not think it will be a noticeable difference.
Edited by jjccckk - 4/5/13 at 11:09am
post #1756 of 3434
Thanks for the suggestion. I wonder if it's connected to the fact that the latest version of XP's 64-bit WdfCoInstaller appears to be WdfCoInstaller01001.dll whereas the Spyd3.inf file is written for WdfCoInstaller01009.dll? Anyway I tried switching it but it didn't help.

The vendor drivers work fine with the Datacolor software and Spyder3 sensor, but I'm still struggling to get HCFR to recognise the sensor.

I followed your advice to Satsok and, after testing the sensor worked with the Datacolor software, I copied CVSpyder3.dll and Spyder3.dll to \Program Files\HCFR Calibration. I went back through several older versions of the Spyder software: 3.1.5, 3.0.7, 3.0.4 and 3.0.1-4, as I understand HCFR doesn't work with later versions of Spyder3.dll. The oldest version contains the CVSpyder.dll file.

However HCFR now comes up with the error "Incorrect driver - Starting communications with the meter failed with severe error. Argyll error". Satsok had the same error which disappeared after reinstalling HCFR and Datacolor software but not for me. "Sensor selection" doesn't list the Spyder3, however it functions with the Datacolor software.

Can you suggest where I'm going wrong?
post #1757 of 3434
Quote:
Originally Posted by jrussell88 View Post

Thanks for the suggestion. I wonder if it's connected to the fact that the latest version of XP's 64-bit WdfCoInstaller appears to be WdfCoInstaller01001.dll whereas the Spyd3.inf file is written for WdfCoInstaller01009.dll? Anyway I tried switching it but it didn't help.

The vendor drivers work fine with the Datacolor software and Spyder3 sensor, but I'm still struggling to get HCFR to recognise the sensor.

I followed your advice to Satsok and, after testing the sensor worked with the Datacolor software, I copied CVSpyder3.dll and Spyder3.dll to \Program Files\HCFR Calibration. I went back through several older versions of the Spyder software: 3.1.5, 3.0.7, 3.0.4 and 3.0.1-4, as I understand HCFR doesn't work with later versions of Spyder3.dll. The oldest version contains the CVSpyder.dll file.

However HCFR now comes up with the error "Incorrect driver - Starting communications with the meter failed with severe error. Argyll error". Satsok had the same error which disappeared after reinstalling HCFR and Datacolor software but not for me. "Sensor selection" doesn't list the Spyder3, however it functions with the Datacolor software.

Can you suggest where I'm going wrong?

when you go into device manager, do you have an Argyll device? or a DataColor device?
post #1758 of 3434
Quote:
Originally Posted by jrussell88 View Post

Can you suggest where I'm going wrong?

Unpack this file and copy "Spyder3.dll" to HCFR folder, someone wrote that got it working. However it may still give some error notes but it´s working.
post #1759 of 3434
Device Manager shows a Datacolor Spyder3 with drivers Spyder3.sys and WdfCoInstaller01001.dll from 10/09/2007.

These are Datacolor's drivers from the Spyder3Elite_3.0.1-4_Setup.exe installer - as I ran that first to connect the sensor.

If I try to update the driver to the Argyll one, I get: "An error ocurred during the installation of this device. A service installation section in this INF is invalid" and it fails. However Device Manager shows an ArgyllLibUSB-1.0A devices section, with the Datacolor Spyder3 and a warning that the drivers are not installed.

The error message points to the INF file, but is there any logging?
post #1760 of 3434
OK there is logging: For XP it's setupapi.log in the Windows directory.

That reports:
#-035 Processing service Add/Delete section [WINUSBCO_DEV.NTAMD64.Services].
#E339 Add Service: Binary "C:\WINDOWS\system32\DRIVERS\WinUSB.sys" for service "WinUSB" is not present.
#E032 Error 0xe0000217: A service installation section in this INF is invalid.
#E275 Error while installing services. Error 0xe0000217: A service installation section in this INF is invalid.
#E122 Device install failed. Error 0xe0000217: A service installation section in this INF is invalid.
#E157 Default installer failed. Error 0xe0000217: A service installation section in this INF is invalid.

So the failure is that WinUSB isn't in my WINDOWS\system32\DRIVERS folder.

WinUSB is provided by Microsoft with more recent OS' than XP. WinUSBCoInstaller2.dll which Spyd3.inf uses assumes that WinUSB.sys is present.

Microsoft advise in
Quote:
WinUSB (Winusb.sys) Installation
http://msdn.microsoft.com/en-us/library/windows/hardware/ff540283(v=vs.85).aspx
Note Because Windows XP doesn't provide WinUSB.inf, the file must either be copied to Windows XP systems by the co-installer, or you should provide a separate decorated section for Windows XP.

That explains the problem, and why it surfaces intermittently on XP systems. If another driver places WinUSB.sys in the Drivers folder, then the problem won't arise.

Is there any way of reporting this bug to the devs?

And I'm trying to find a copy of WinUSB.sys...

And thanks Make73 - I'll try the 2008 Spyder3.dll once I've got WinUSB.sys.
post #1761 of 3434
Quote:
Originally Posted by jrussell88 View Post

Hi Zoyd, I'd like to try HCFR but I'm unable to load the Argyll CMS drivers for my Spyder3 Elite.

The Spyder was running on v3.1.5 of Datacolor's software. When I remove the drivers and select the Spyd3.inf file from HCFR's directory, I first get a message saying that the Spyder3 (Argyll) drivers aren't properly signed 'Authenticode signature not found'; I OK that and it appears to copy a libusb0 or similar file, then the driver installation fails with the message "An error ocurred during the installation of this device. A service installation section in this INF is invalid".

That's odd, because it should be running the WinUSB co-installer, rather than using libusb0.sys. Unfortunately I don't have a WinXP 64 bit system to test on, so it's hard to know what went wrong. Perhaps the log files in c:/Windows/inf could give a clue. The ArgyllCMS drivers have all been tested and work on on WinXP 32 bit, Vista 32 & 64 bit and Win7 32 & 64 bit, so I would guess that there is some small peculiarity to WinXP 64 bit .inf files that has been missed.
post #1762 of 3434
Thanks for the suggestion - I'm not sure which log file you mean; I can't see any relevant log files in c:/Windows/inf.

I've searched for any files containing winusb and the only apparently relevant one is setupapi.log. The full text of setupapi.log is:
Code:
[2013/04/06 10:27:49 1128.43227]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" "C:\WINDOWS\system32\compmgmt.msc" /s
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_085c&pid_0300&rev_0106,usb\vid_085c&pid_0300
#-018 Searching for compatible ID(s): usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#I022 Found "USB\VID_085C&PID_0300" in C:\WINDOWS\inf\oem14.inf; Device: "Datacolor Spyder3"; Driver: "Datacolor Spyder3"; Provider: "Datacolor"; Mfg: "Datacolor"; Section name: "SpyderInstall".
#I023 Actual install section: [SpyderInstall.NT]. Rank: 0x00000001. Driver date: 09/10/2007. Version: 1.0.0.3.
#-019 Searching for hardware ID(s): usb\vid_085c&pid_0300&rev_0106,usb\vid_085c&pid_0300
#-018 Searching for compatible ID(s): usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-019 Searching for hardware ID(s): usb\vid_085c&pid_0300&rev_0106,usb\vid_085c&pid_0300
#-018 Searching for compatible ID(s): usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-019 Searching for hardware ID(s): usb\vid_085c&pid_0300&rev_0106,usb\vid_085c&pid_0300
#-018 Searching for compatible ID(s): usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#I439 Verifying file "c:\program files (x86)\hcfr calibration\drivers\Spyd3.inf" (key "Spyd3.inf") against specific Authenticode(tm) catalog "c:\program files (x86)\hcfr calibration\drivers\Spyd3_x64.cat" failed. Error 0x800b0100: No signature was present in the subject.
#I022 Found "USB\VID_085C&PID_0300" in c:\program files (x86)\hcfr calibration\drivers\Spyd3.inf; Device: "Spyder3 (Argyll)"; Driver: "Spyder3 (Argyll)"; Provider: "ArgyllCMS"; Mfg: "DataColor"; Section name: "WINUSBCO_DEV".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [WINUSBCO_DEV.NTAMD64]. Rank: 0x00008001. Driver date: 02/27/2012. Version: 1.0.0.1.
#-124 Doing copy-only install of "USB\VID_085C&PID_0300\5&25482455&0&2".
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem30.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem31.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem36.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem66.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem67.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I439 Verifying file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf") against specific Authenticode(tm) catalog "c:\program files (x86)\hcfr calibration\drivers\spyd3_x64.cat" failed. Error 0x800b0100: No signature was present in the subject.
#W366 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" for driver "Spyder3 (Argyll)" will be installed (Policy=Warn, user said ok). Error 0x800b0100: No signature was present in the subject.
#-024 Copying file "c:\program files (x86)\hcfr calibration\drivers\libusb-1.0A.dll" to "C:\WINDOWS\syswow64\libusb-1.0A.dll".
#W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\program files (x86)\hcfr calibration\drivers\libusb-1.0A.dll" for driver "Spyder3 (Argyll)" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-336 Copying file "c:\program files (x86)\hcfr calibration\drivers\libusb-1.0A_x64.dll" to "C:\WINDOWS\system32\libusb-1.0A.dll" via temporary file "C:\WINDOWS\system32\SET5C3.tmp".
#W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\program files (x86)\hcfr calibration\drivers\libusb-1.0A_x64.dll" for driver "Spyder3 (Argyll)" will be installed (Policy=Warn). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [WINUSBCO_DEV.NTAMD64.Interfaces] from "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_085C&PID_0300\5&25482455&0&2".
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem30.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem31.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem36.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem66.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem67.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I443 No installed Authenticode(tm) catalogs matching catalog name "oem83.CAT" were found that validated file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf"). Error 1168: Element not found.
#I439 Verifying file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" (key "spyd3.inf") against specific Authenticode(tm) catalog "c:\program files (x86)\hcfr calibration\drivers\Spyd3_x64.cat" failed. Error 0x800b0100: No signature was present in the subject.
#W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\program files (x86)\hcfr calibration\drivers\spyd3.inf" for driver "Spyder3 (Argyll)" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-035 Processing service Add/Delete section [WINUSBCO_DEV.NTAMD64.Services].
#E339 Add Service: Binary "C:\WINDOWS\system32\DRIVERS\WinUSB.sys" for service "WinUSB" is not present.
#E032 Error 0xe0000217: A service installation section in this INF is invalid.
#E275 Error while installing services. Error 0xe0000217: A service installation section in this INF is invalid.
#E122 Device install failed. Error 0xe0000217: A service installation section in this INF is invalid.
#E157 Default installer failed. Error 0xe0000217: A service installation section in this INF is invalid.
#I060 Set selected driver.
#I125 Installing NULL driver for "USB\VID_085C&PID_0300\5&25482455&0&2".
#I121 Device install of "USB\VID_085C&PID_0300\5&25482455&0&2" finished successfully.

From your comments I read this as meaning that the installer identifies the missing WinUSB.sys, but has a problem with Spyd3.inf. Are there any other logs which might be relevant?

I'm still trying to get a copy of 64-bit WinUSB.sys in the hope that it sidesteps the issue.
post #1763 of 3434
Quote:
Originally Posted by jrussell88 View Post

Code:
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.

#E339 Add Service: Binary "C:\WINDOWS\system32\DRIVERS\WinUSB.sys" for service "WinUSB" is not present.
#E032 Error 0xe0000217: A service installation section in this INF is invalid.

Hmm. It's a bit of a guess on my part, but I'm wondering if your system thinks that there is a newer version of WinUSB already installed, and hence skips running the CoInstaller provided with the ArgyllCMS drivers. But it then can't find WinUSB.sys.

You could try uninstalling or updating WinUSB: http://support.microsoft.com/kb/971286,
and then try installing the ArgyllCMS Spyd3.inf again.
post #1764 of 3434
Quote:
Originally Posted by zoyd View Post

I think both D and E series are best calibrated with 75% amplitude/ 75% saturation using windows with constant APL (GCD) or constant energy (AVSHD small APL).

Tried re-calibrate colors with GCD 75% / 75%

GCD 75% / 75% APL Windows


AVS HD 709 100% APL (small windows)


I´m not sure is it better or not, 100% saturation is now under saturated, maby skin tones are with 75% little more natural.

With grayscale gone back to cell light 15-16 and higher contrast to get less agressive 10-point gamma tracking.
With GCD grayscale APL windows and AVS HD 709 APL small windows gave almost same results.
Edited by Make73 - 4/8/13 at 9:53am
post #1765 of 3434
Thread Starter 
Quote:
Originally Posted by Make73 View Post



I´m not sure is it better or not, 100% saturation is now under saturated, maby skin tones are with 75% little more natural.

It's hard to evaluate improvements at this level using HCFR since you are only looking at relative tracking and absolute errors at the primaries/secondaries. If you look at the CC6 colors the skin tone patch for 75% saturation based calibration should measure better than the 100% saturation based cal, and that's a good enough reason to go with that. If you want to take a statistics based approach to see which calibration gives you the best numbers over many different colors you need other software.
post #1766 of 3434
Quote:
Originally Posted by zoyd View Post

It's hard to evaluate improvements at this level using HCFR since you are only looking at relative tracking and absolute errors at the primaries/secondaries. If you look at the CC6 colors the skin tone patch for 75% saturation based calibration should measure better than the 100% saturation based cal, and that's a good enough reason to go with that. If you want to take a statistics based approach to see which calibration gives you the best numbers over many different colors you need other software.

I didn´t mean just numbers and how it looks with CIE diagram, maby if I´d make calibration with different methods to different viewing modes then comparing between those two would be easier (however you can´t set different settings for Warm2 with same source. You can use Warm1 instead of that but at least with game mode enabled Warm1 is not good as Warm2 or is it because of game mode?)
Skin tones are more natural yes but many colors seems to be too "rich", maby just because already used to watch oversaturated colors smile.gif
I let it be like this for next 100-200 hours, till next re-calibration.

Should I set "Colors to add when measuring primaries and secondaries" to "None" when using two different calibration disks with different amp and sat levels?
At first used GCD to grayscale and colors (75%/75%) then gone to AVS HD and measured near black, near white and contrast but also re-measured grayscale with 100% APL small windows just to check how it compares to GCD.
Afterward I noticed that HCFR copied that white (100%) reading from AVS HD to primaries and secondaries so it shows dE´s etc. wrong.
I can manually edit white reading for primaries and secondaries if I could remember what it was with GCD, calculated that from memory of dE´s.

btw, GCD is just great, I wish there would be also those few extra patterns so you don´t need to use AVS HD at all.
From HCFR preferences "Use round down levels" should I check or un-check that with GCD?
Edited by Make73 - 4/8/13 at 8:48pm
post #1767 of 3434
Thread Starter 
Quote:
Originally Posted by Make73 View Post


Should I set "Colors to add when measuring primaries and secondaries" to "None" when using two different calibration disks with different amp and sat levels?
At first used GCD to grayscale and colors (75%/75%) then gone to AVS HD and measured near black, near white and contrast but also re-measured grayscale with 100% APL small windows just to check how it compares to GCD.
Afterward I noticed that HCFR copied that white (100%) reading from AVS HD to primaries and secondaries so it shows dE´s etc. wrong.
I can manually edit white reading for primaries and secondaries if I could remember what it was with GCD, calculated that from memory of dE´s.

HCFR updates it 's reference white every time you measure it in the primaries/secondaries scan, so yes, if you don't want it to update check "none".
Quote:
btw, GCD is just great, I wish there would be also those few extra patterns so you don´t need to use AVS HD at all.
From HCFR preferences "Use round down levels" should I check or un-check that with GCD?

unchecked with GCD
post #1768 of 3434
I couldn't find any WinUSB files on my system at all prior to copying them to the relevant locations manually. It still reads to me like the absence of winusb.sys - which would occur only on some XP systems which hadn't previously had it installed - isn't being handled by the installation. When I manually put winusb.sys in place the installation stopped failing. I also provided a winusb.inf - it isn't clear to me that the coinstallers automatically provide that given MSDN's comments?

Thanks for the link by the way; it explains how to check whether WinUSB is installed, but doesn't apply to XP and I couldn't find a way to download or install the WinUSB v1.9 (KB971286) update they mention - which appears to be applicable to Vista and later.

Eventually I managed to extract the WinUSB files from 64-bit Windows 7 and put them in the following locations (following Windows 7):
  • /Windows/inf: winusb.inf & winusb.pnf
  • /Windows/System32: winusb.dll (64-bit version, 20.5kb)
  • /Windows/System32/Drivers: winusb.sys (64-bit version, 40.4kb)
  • /Windows/SysWOW64: winusb.dll (32-bit version 16.9kb)

This solved the problem of 'the service installation section in this INF is invalid' when installing the Spyder's drivers and the installer completed, after I told it where to find winusb.sys.

However it then reported a code 39 error with the driver:
Quote:
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

The drivers are:
  • \Windows\System32\Drivers\winusb.sys
  • \Windows\System32\libusb-1.0A.dll
  • \Windows\SysWOW64\libusb-1.0A.dll


I then accidentally installed the Argyll Spyder 2 driver. The installer worked, and the Device Manager shows a 'Spyder (Argyll)' device under 'Argyll LibUSB-1.0A devices'. Drivers are:
  • \Windows\System32\Drivers\libusb0.sys
  • \Windows\System32\libusb-1.0A.dll
  • \Windows\SysWOW64\libusb-1.0A.dll

Perhaps there's a problem with winusb.sys?
Edited by jrussell88 - 4/9/13 at 6:51pm
post #1769 of 3434
After reading through most of this thread, I still have a few questions that I need clarification on. A little background on what I have. I'm using the Spyder meter that came with Spyder4TV HD and the AVS HD709 disc. The display I'm calibrating is a Plasma. I've read the Grayscale for dumbies about 3-4 times prior to starting, it's been a great resource.

1. I've seen various answers to what display type I should choose in the HCFR meter setup. Refresh, generic refresh, crt etc. Which should I use?

2. Which test pattern should I use from the AVS HD709 disc? APL, Fields, Window? Something about a plasma requiring something specific.

3. I accidently hit the 'Calibrate Meter' button in HCFR. Did this screw up my meter?

4. In my standard picture settings I have the folloiwng:
W/B high R: Adjusts the white balance for light red areas.
W/B high B: Adjusts the white balance for light blue areas.
W/B low R: Adjusts the white balance for dark red areas.
W/B low B: Adjusts the white balance for dark blue areas.
Black extension: Adjusts the dark shades of the image in gradation.
Gamma adjustment: Gamma correction. Adjusts the intermediate brightness of the image. (Normal/Mid/Full 1/Full 2)
Panel brightness: Selects the display panel brightness.
(High: Vivid, Mid: Standard, Low: Studio ref)
Contour emphasis: Adjusts the contour emphasis of the image. (On/Off)
AGC: Increases the brightness of dark signal automatically. (On/Off)

Specfically the W/B adjustments. When it says dark areas, does that mean in the avove 50% gray scale and light below the 50 % gray scale? If I make an adjustment to red, does that change blue?


Thanks in advance. I know these quesitons are very remedial for most of you. After calibrating last night my Gamma was junk and I look forwad to dialing it in.
post #1770 of 3434
Quote:
Originally Posted by SnkEyez95 View Post

After reading through most of this thread, I still have a few questions that I need clarification on. A little background on what I have. I'm using the Spyder meter that came with Spyder4TV HD and the AVS HD709 disc. The display I'm calibrating is a Plasma. I've read the Grayscale for dumbies about 3-4 times prior to starting, it's been a great resource.

1. I've seen various answers to what display type I should choose in the HCFR meter setup. Refresh, generic refresh, crt etc. Which should I use?

refresh is the setting you should use.

2. Which test pattern should I use from the AVS HD709 disc? APL, Fields, Window? Something about a plasma requiring something specific.

plasmas have limiting circuits, most will try to minimize their effects by using the smallest patterns available. I have tried a wide array of APL's, and different sized windows on both my plasmas, and found Chad's 4% just about the best. You can find them on this board.

3. I accidently hit the 'Calibrate Meter' button in HCFR. Did this screw up my meter?

more than likely not

4. In my standard picture settings I have the folloiwng:
W/B high R: Adjusts the white balance for light red areas.
W/B high B: Adjusts the white balance for light blue areas.
W/B low R: Adjusts the white balance for dark red areas.
W/B low B: Adjusts the white balance for dark blue areas.
Black extension: Adjusts the dark shades of the image in gradation.
Gamma adjustment: Gamma correction. Adjusts the intermediate brightness of the image. (Normal/Mid/Full 1/Full 2)
Panel brightness: Selects the display panel brightness.
(High: Vivid, Mid: Standard, Low: Studio ref)
Contour emphasis: Adjusts the contour emphasis of the image. (On/Off)
AGC: Increases the brightness of dark signal automatically. (On/Off)

Specfically the W/B adjustments. When it says dark areas, does that mean in the avove 50% gray scale and light below the 50 % gray scale? If I make an adjustment to red, does that change blue?

dark areas are generally 0% to 50%, light 50% to 100%

Making an adjustment to any picture control could and most probably will affect some others. Its always best to go back to the beginning when you are finished to see if anything else changed, and needs readjustment



Thanks in advance. I know these quesitons are very remedial for most of you. After calibrating last night my Gamma was junk and I look forwad to dialing it in.

not knowing the brand or model of your set, all I can tell you is turn off any enhacements (dynamic contrast, AGC, Gamma Adjustemnt, etc) as more times than not they are detrimental to picture quality.
Edited by vega509 - 4/10/13 at 12:53pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Display Calibration
AVS › AVS Forum › Display Devices › Display Calibration › HCFR - Open source projector and display calibration software