AVS Forum banner

1761 - 1780 of 13608 Posts

·
Registered
Joined
·
1,156 Posts

Quote:
Originally Posted by jrussell88  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23167367


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.
 

·
Registered
Joined
·
8 Posts
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:
Code:
[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.
[/CODE]


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.
 

·
Registered
Joined
·
1,156 Posts

Quote:
Originally Posted by jrussell88  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23174564

Code:
Code:
[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.
[/CODE]

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.
 

·
Registered
Joined
·
607 Posts

Quote:
Originally Posted by zoyd  /t/1393853/fork-of-hcfr-started-whats-needed/1710#post_23147330


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.
 

·
Registered
Joined
·
6,804 Posts
Discussion Starter #1,765

Quote:
Originally Posted by Make73  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23179041




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.
 

·
Registered
Joined
·
607 Posts

Quote:
Originally Posted by zoyd  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23179622


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


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?
 

·
Registered
Joined
·
6,804 Posts
Discussion Starter #1,767

Quote:
Originally Posted by Make73  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23181847



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
 

·
Registered
Joined
·
8 Posts
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?
 

·
Registered
Joined
·
110 Posts
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.
 

·
Registered
Joined
·
1,043 Posts

Quote:
Originally Posted by SnkEyez95  /t/1393853/fork-of-hcfr-started-whats-needed/1740#post_23187819


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.
 

·
Registered
Joined
·
110 Posts
Thanks Vega,


I have the P58V10 plasma. From what your response indicates I should be using the refresh setting and APL patterns. W/B adjustments with regards to light areas are referring to the 50%-100%, with dark representing the 0-50%range. I have all enhancements turned off except for those where it's not an option to turn off.


With W/B based on your information, if I'm checking 80%iRE with HCFR and red is less than 100% should adjust W/B high R to get as close to 100%, and similarly for the blue? I will recheck tonight and see what I can dial in. Would it be inappropriate to post graphs for suggestions or comments on what I might do to further correct the calibration?


Thanks again...Your comments are greatly appreciated.
 

·
Registered
Joined
·
1,043 Posts

Quote:
Originally Posted by SnkEyez95  /t/1393853/fork-of-hcfr-started-whats-needed/1770#post_23188738


Thanks Vega,


I have the P58V10 plasma. From what your response indicates I should be using the refresh setting and APL patterns. W/B adjustments with regards to light areas are referring to the 50%-100%, with dark representing the 0-50%range. I have all enhancements turned off except for those where it's not an option to turn off.


With W/B based on your information, if I'm checking 80%iRE with HCFR and red is less than 100% should adjust W/B high R to get as close to 100%, and similarly for the blue? I will recheck tonight and see what I can dial in. Would it be inappropriate to post graphs for suggestions or comments on what I might do to further correct the calibration?


Thanks again...Your comments are greatly appreciated.

I had limited success with the apl patterns on both my Panasonic and my Pioneer. Small windows, 4%, worked best for me. When adjusting the RGB, since you do not have any adjustment for green, move the red and blue to line up with the green line, both for rgb and for the gamma. Starting with the 80% and 20% gray points is just that. Look over the whole spectrum and find where the best fit will be as you only have 2 point w/b controls from what you have posted.


In the end, what is important more than anything is that the picture is pleasing to you in your viewing environment. I've calibrated a few sets that had great graphs and numbers, but less than optimal picture. Sometimes small changes can make a very big difference. Don't be afraid to experiment. If you are so inclined keep a log of changes you made, and the effects they had in HCFR, and what you see on the set. Its a learning process, and to me it seems you never stop learning.


most definitely post your graphs, and the raw data, it makes it a lot easier to see what you are seeing. each graph can be saved as a graphic file by right clicking on the graph, then save as. you can then attach it as a photo in your post.
 

·
Registered
Joined
·
110 Posts
Alright...Here is my first attempt. Played around for quite some time. Not sure if it's the nature of calibrating or my Spyder4 budget meter, but I was getting some inconsistent retest readings. This was my most consistent results. Any suggestions? Weak ares? Areas for improvement?





 

·
Registered
Joined
·
1,043 Posts

looks pretty good for the controls you have available. you may want to try moving red high down a notch. The gamma at 2.48 seems a little high, unless you are viewing the set in a dark room. This may also be an effect of the patterns you used, and the limiting circuit in the set. With the APL patterns I can get a gamma of 2.37 and a light output of 32fL. Without making any changes to the controls, using the 4% patterns, light output jumps to 38fL, and gamma reads at 2.23. Obviously the effect of the limiting circuits with the APL patterns. Which is correct? What ever looks best to you.

 

how does actual content look?
 

·
Registered
Joined
·
110 Posts

Quote:
Originally Posted by vega509  /t/1393853/fork-of-hcfr-started-whats-needed/1770#post_23196220


looks pretty good for the controls you have available. you may want to try moving red high down a notch. The gamma at 2.48 seems a little high, unless you are viewing the set in a dark room. This may also be an effect of the patterns you used, and the limiting circuit in the set. With the APL patterns I can get a gamma of 2.37 and a light output of 32fL. Without making any changes to the controls, using the 4% patterns, light output jumps to 38fL, and gamma reads at 2.23. Obviously the effect of the limiting circuits with the APL patterns. Which is correct? What ever looks best to you.


how does actual content look?

I did calibrate on my PS3 for blue rays. I traditionally watch at night in an unlit room. Is a higher gamma more appropriate for dark viewing environments?


Is there a magic or a target fL I should be keying towards?


The set does look considerably better. A nice natural look.


Next I'm looking to calibrate for a "day" mode on another hdmi input, is there a different approach for day vs night calibration? Higher contrast for higher fL? I know a lot of this stuff is subjective, just curious if there a general area of focus.
 

·
Registered
Joined
·
3,645 Posts

Quote:
Originally Posted by SnkEyez95  /t/1393853/fork-of-hcfr-started-whats-needed/1770#post_23197451


I did calibrate on my PS3 for blue rays. I traditionally watch at night in an unlit room. Is a higher gamma more appropriate for dark viewing environments?
Typically yes. I like 2.3-2.35 for a dark room. If your set has poor black levels (which I don't think is the case here), bt.1886 is probably better.
Quote:
Is there a magic or a target fL I should be keying towards?
Everyone's eyes are different. Typically you want to be in the 30-35fL range for a dark room.
Quote:
Next I'm looking to calibrate for a "day" mode on another hdmi input, is there a different approach for day vs night calibration? Higher contrast for higher fL? I know a lot of this stuff is subjective, just curious if there a general area of focus.
Not really... just target a higher brightness. Seeing as how you have a plasma, use the contrast control as you said. You'll probably want to target a lower gamma, too.
 

·
Registered
Joined
·
815 Posts
Did anybody manage to compile the code with Visual Studio 2012 under Windows 8 x64?

First I got this error:
Quote:
Error 1 error RC1015: cannot open include file 'l.esp\afxres.rc'. C:\Users\János\Documents\hcfr\CHCFR21_ESPANOL.rc 3163 1 CHCFR21_ESPANOL
And I got a countless number of type definition errors when I removed the entire ESPANOL project from the solution.


I just wanted to update the ArgyllCMS code. But I faild to build the vanilla code to start with.
 

·
Registered
Joined
·
110 Posts
Thanks for the reply rahzel. I set my fL in the 39-40 range. It was jumping up and down between the two. Would lowering that to something closer to 35fL have a decreasing effect on gamma. I'm obviously still very new at this, and trying to figure out what settings or changes produce the greatest changes to gamma. Thanks everyone for you help.


Anything to try next? I also wasn't very certain on what your comment on bt.1886 referred to. Probably something to advanced for my current knowledge.


When tweaking W/B should I be targeting R and B to 100% or to match G?


Thanks again!
 

·
Registered
Joined
·
815 Posts

Quote:
Originally Posted by SnkEyez95  /t/1393853/fork-of-hcfr-started-whats-needed/1700_100#post_23197739


When tweaking W/B should I be targeting R and B to 100% or to match G?

The usual "rule of thumb" is: Do not touch green! = Always keep the green channel contrast at it's default neutral maximum setting (unlimited but unclipped) and balance the gray-scale with the red and blue components around green.

But the real rule in the digital world is to keep one channel contrast (the one which should be the brightest of them all) at it's neutral maximum setting (unlimited but unclipped) and lower the other two.

On many flat screens, it's usually still the green channel though. But, for example, red should be max out on Samsung PDPs when you start from the real neutral settings in the Service Menu (because of this, unfortunately there is no other way to calibrate those TVs objectively). And Panasonic PDPs have failsafe controls anyway (they scale everything back if you move the Green Gain in the user menu to get the G-DRV back to neutral max.)
 

·
Registered
Joined
·
3,645 Posts
Ya, generally it's recommended to leave green alone. But if you know what you're doing, it should be ok to change green. If your set has a 10pt white balance and no gamma gain control, then that's the only way to change the gamma... by grouping RGB up and down. But if you only have a 2pt W/B system or you have a gamma gain control, you generally don't need to change green.
 
1761 - 1780 of 13608 Posts
Top