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 107

post #3181 of 3436
Quote:
Originally Posted by BobearQSI View Post


Okay, it shows up as "USB Input Device," I will see if I can get it to show up as "HID-compliant device"


is that in the Human Interface Devices group? if it is, you may be good to go. be sure to select meter once again, and select your meter when you start hcfr. mine appears like this

 

post #3182 of 3436
Quote:
Originally Posted by vega509 View Post

The i1display pro does not need any drivers installed, the driver from windows 7 shows it as a HID compliant device. The NEC version I'm not familiar with, I would try removing the NEC driver, and the Argyl driver, then plug the meter in and see if windows detects it. open device manager, and expand human Interface Devices, then plug in the meter, if its like the OEM version, another HID-compliant device will appear.

I uninstalled the device and then manually removed the Argyll driver from Windows' inf folder so it didn't exist anymore, and then rebooted. Then I plugged in the device, and Windows 7 automatically assigned it "USB Input Device." I can not remove this driver because it is part of windows and used for many other input devices. Same error again on HCFR. This is Windows 7 Ultimate x64, btw.
post #3183 of 3436
Quote:
Originally Posted by BobearQSI View Post


I uninstalled the device and then manually removed the Argyll driver from Windows' inf folder so it didn't exist anymore, and then rebooted. Then I plugged in the device, and Windows 7 automatically assigned it "USB Input Device." I can not remove this driver because it is part of windows and used for many other input devices. Same error again on HCFR. This is Windows 7 Ultimate x64, btw.


that is the windows driver, it identifies your meter as you see. there must be something NEC changed in the firmware. you may want to contact them or wait for zoyd to pop in.

post #3184 of 3436
Quote:
Originally Posted by vega509 View Post
 


I thought I was the only one with this problem. I also find when using the "view images" in continuous read the patterns continuously change with each reading. I can't remember which version it last worked correctly in, as I was away from this since 3.0.1.2.


just found the F8 key will halt the continuous readings. now to solve the other issues ......

post #3185 of 3436
Quote:
Originally Posted by vega509 View Post

that is the windows driver, it identifies your meter as you see. there must be something NEC changed in the firmware. you may want to contact them or wait for zoyd to pop in.

I contacted the Argyll mailing list, and the new revision B series of all i1d3 sensors (not just NEC) are currently broken, and they're working on it.
post #3186 of 3436
So the next question is, when Argyll releases an update, does it require a rebuild and new version of HCFR, or are there files I can copy over?
post #3187 of 3436
In the HCFR Drivers folder there are drivers for the following meters. (This is a snip from the ArgyllCMS.inf file found there.)

Quote:
; ==== Manufacturers ====

[Manufacturer]
"HCFR Association"=HCFR_Devices,NTx86,NTamd64
"Sequel Imaging"=Sequel_Devices,NTx86,NTamd64
"X-Rite"=X_Rite_Devices,NTx86,NTamd64
"ColorVision"=ColorVision_Devices,NTx86,NTamd64
"Gretag Macbeth/X-Rite"=GM_X_Rite_Devices,NTx86,NTamd64
"Hughski Ltd"=Hughski_Devices,NTx86,NTamd64

; ==== Devices ====

[HCFR_Devices]
"Colorimtre HCFR V3.1 (Argyll)" = LIBUSB0_DEV, USB\VID_04DB&PID_005B
"Colorimtre HCFR V4.0 (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_FE17

[Sequel_Devices]
"Eye-One Display 1 (Argyll)" = LIBUSB0_DEV, USB\VID_0670&PID_0001

[X_Rite_Devices]
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5001
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5010
"Eye-One Display 3 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5020
"ColorMunki Smile (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_6003
"DTP20 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D020
"DTP92Q (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D092
"DTP94 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D094

[ColorVision_Devices]
"Spyder1 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0100
"Spyder2 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0200
"Spyder3 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0300
"Spyder4 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0400

[GM_X_Rite_Devices]
"Eye-One Pro (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2000
"Eye-One Monitor (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2001
"Eye-One Display 2 (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2003
"Huey (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2005
"ColorMunki (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2007

[Hughski_Devices]
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_273F&PID_1001
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_F8DA


[HCFR_Devices.NTx86]
"Colorimtre HCFR V3.1 (Argyll)" = LIBUSB0_DEV, USB\VID_04DB&PID_005B
"Colorimtre HCFR V4.0 (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_FE17

[Sequel_Devices.NTx86]
"Eye-One Display 1 (Argyll)" = LIBUSB0_DEV, USB\VID_0670&PID_0001

[X_Rite_Devices.NTx86]
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5001
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5010
"Eye-One Display 3 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5020
"ColorMunki Smile (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_6003
"DTP20 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D020
"DTP92Q (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D092
"DTP94 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D094

[ColorVision_Devices.NTx86]
"Spyder1 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0100
"Spyder2 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0200
"Spyder3 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0300
"Spyder4 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0400

[GM_X_Rite_Devices.NTx86]
"Eye-One Pro (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2000
"Eye-One Monitor (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2001
"Eye-One Display 2 (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2003
"Huey (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2005
"ColorMunki (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2007

[Hughski_Devices.NTx86]
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_273F&PID_1001
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_F8DA


[HCFR_Devices.NTamd64]
"Colorimtre HCFR V3.1 (Argyll)" = LIBUSB0_DEV, USB\VID_04DB&PID_005B
"Colorimtre HCFR V4.0 (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_FE17

[Sequel_Devices.NTamd64]
"Eye-One Display 1 (Argyll)" = LIBUSB0_DEV, USB\VID_0670&PID_0001

[X_Rite_Devices.NTamd64]
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5001
"HueyL (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5010
"Eye-One Display 3 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_5020
"ColorMunki Smile (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_6003
"DTP20 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D020
"DTP92Q (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D092
"DTP94 (Argyll)" = LIBUSB0_DEV, USB\VID_0765&PID_D094

[ColorVision_Devices.NTamd64]
"Spyder1 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0100
"Spyder2 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0200
"Spyder3 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0300
"Spyder4 (Argyll)" = LIBUSB0_DEV, USB\VID_085C&PID_0400

[GM_X_Rite_Devices.NTamd64]
"Eye-One Pro (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2000
"Eye-One Monitor (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2001
"Eye-One Display 2 (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2003
"Huey (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2005
"ColorMunki (Argyll)" = LIBUSB0_DEV, USB\VID_0971&PID_2007

[Hughski_Devices.NTamd64]
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_273F&PID_1001
"ColorHug (Argyll)" = LIBUSB0_DEV, USB\VID_04D8&PID_F8DA



Larry
post #3188 of 3436
Quote:
Originally Posted by BobearQSI View Post

Just received my i1 Display Pro (NEC SpectraSensor) and I'm getting the "External EEPRom checksum doesn't match" error.

In Device Manager, the device is listed as "Eye-One Display 3 (Argyll)" which I believe is the correct driver I'm supposed to be using. Any idea what's wrong?

HCFR 3.1.0.5, Argyll 1.6.2

Zoyd will have to update the i1d3 driver code from Argyll_dev_src.zip to fix this.

(It seem like X-Rite have completely abandoned setting a valid EEProm checksum on the Rev B i1d3's. I don't think their driver ever checked it, so they haven't noticed and/or don't care.)
post #3189 of 3436
Quote:
Originally Posted by LarryInRI View Post

In the HCFR Drivers folder there are drivers for the following meters. (This is a snip from the ArgyllCMS.inf file found there.)

......

Larry

Note that while you can assign the i1d3 (i1display pro, colormunki display) to the libusb-win32 USB system driver, this is not the normal way of doing it. Normally you just use the default HID USB system driver.
post #3190 of 3436
I dropped the matching folders in the unreleased/unstable argyll development code on top of zoyd's branch of HCFR and built it, and can confirm it works and I can read values with the meter now.

Thanks everyone for your help.
post #3191 of 3436
Quote:
Originally Posted by gwgill View Post

Note that while you can assign the i1d3 (i1display pro, colormunki display) to the libusb-win32 USB system driver, this is not the normal way of doing it. Normally you just use the default HID USB system driver.

Graeme,

Right and agreed to. I was just noting all the meters that are supported by Argyll in the drivers directory of the HCFR program itself.

Larry
post #3192 of 3436
Quote:
Originally Posted by 10k View Post

.

The reason I did it this way is because on my Samsung my CMS controls are RGB controls for each primary and secondary. It was far easier for me to understand which of R,G,B needed adjusting using this method instead of looking at xyY coordinates and targets.

Thanks....actually it seems I understood right then, but for me RGB references are exactly the white luminance value for each component (say, if measured white is Y=120 then it's R=120, G=0, B=0 for red)...and I don't get reference RGB values in the bottom left table (the one next to the bullseye target?) from the reference window, just the currently measured ones or the ones from the uppermost big table on the same window when I click on a specific color tab in it...

I hoped this would help me to somehow fix luminance errors I get when I do primaries/secondaries...(my CMS is hue/saturation/luminance based but can't quite figure out how to balance the three although I do try target the luminance in "delta luminance" row, but then I get very off with xy so I settle for the smallest combined error, and when I do saturation sweeps, results are for some colors quite different from when I took single prim/sec measures/adjustments...

Sent from my ALCATEL ONE TOUCH 6030X using Tapatalk
post #3193 of 3436
Thread Starter 
Quote:
Originally Posted by vega509 View Post


just found the F8 key will halt the continuous readings. now to solve the other issues ......

If you are running patterns on the same screen as the main window it will lose focus so you can alt-tab back to the main window and hit the stop (red X) button or use the F8 hotkey. Also, the color displayed in one shot or continuous mode is determined first by which column you have selected in the gray scale or primaries/secondaries sheets. If no column has been selected and you have "detect primaries during user measures" selected in preferences the program will try to determine which primary/secondary color is being measured.
post #3194 of 3436
Thread Starter 
Quote:
Originally Posted by gwgill View Post

Zoyd will have to update the i1d3 driver code from Argyll_dev_src.zip to fix this.

(It seem like X-Rite have completely abandoned setting a valid EEProm checksum on the Rev B i1d3's. I don't think their driver ever checked it, so they haven't noticed and/or don't care.)

I'll update to Argyll 1.6.3 code this weekend.
post #3195 of 3436
Quote:
Originally Posted by zoyd View Post


If you are running patterns on the same screen as the main window it will lose focus so you can alt-tab back to the main window and hit the stop (red X) button or use the F8 hotkey. Also, the color displayed in one shot or continuous mode is determined first by which column you have selected in the gray scale or primaries/secondaries sheets. If no column has been selected and you have "detect primaries during user measures" selected in preferences the program will try to determine which primary/secondary color is being measured.


thanks again zoyd .

post #3196 of 3436

 

has anyone tried the overlay in the generator setup? I get this error when clicking test overlay.

post #3197 of 3436
Thread Starter 
Code updated to Argyll 1.6.3 - HCFR ver. 3.1.0.6
post #3198 of 3436
Thanks zoyd for your great work wink.gif
post #3199 of 3436
Quote:
Originally Posted by realzven View Post

Thanks zoyd for your great work wink.gif

+1

downloading now.

question, do i need to uninstall earlier version?
post #3200 of 3436
Thread Starter 
No, you can install over the old one
post #3201 of 3436
Thanks.

I have over 100 hours of running slides on my Plasma and will do some calibrating today with the updated HCFR.
post #3202 of 3436
Quote:
Originally Posted by nathan_h View Post

Cool. So the drivers folder should look like this? Sorry to be missing the basics....


Do I need to make updates to the drivers for the new version? Or will the i1 LT work with what I have in the screen shot?
post #3203 of 3436
Thread Starter 
If your meter is working with current version then no action is required when upgrading
post #3204 of 3436
Quote:
Originally Posted by zoyd View Post

If your meter is working with current version then no action is required when upgrading

Cool. That's very user friendly!

For me it was working fine with 2.x. Doesn't work with 3. I am sure it is user error. (Unless the eye 1 display lt is no longer compatible.
post #3205 of 3436
Thread Starter 
yes, for upgrading from 2.x you need update the meter driver and point your driver manager to that folder in your screen cap. You can delete the .dll files if you want, they are no longer needed.
post #3206 of 3436

I've created a meter correction file using simultaneous measures, but cannot save the file anywhere on the PC, this dialog appears when saving the file

 

 

how do I get around this?

 

thanks

post #3207 of 3436
Thread Starter 
The file must be saved to it's default directory, which is the HCFR sub-folder called Etatlon_Argyll, so that it is available for the meter initialization dialog.
post #3208 of 3436
Quote:
Originally Posted by zoyd View Post

The file must be saved to it's default directory, which is the HCFR sub-folder called Etatlon_Argyll, so that it is available for the meter initialization dialog.

thanks for the reply zoyd,
that is where I tried, also the root of HCFR, the root of the drive, the measurements folder, and the user color folder, it will not save anywhere at this point. I've copied the matrix to a text file so as not to lose the data. I tried closing HCFR, reopening, creating a new file, paste the matrix into the meter settings, I still cannot save the file anywhere.

 

strange .......

post #3209 of 3436
Thread Starter 
I think you also have to run the program as admin to save files to the HCFR directories if you have used default installation location.
post #3210 of 3436
Quote:
Originally Posted by zoyd View Post

I think you also have to run the program as admin to save files to the HCFR directories if you have used default installation location.


thanks zoyd,

 

I've already set HCFR to be run as administrator. I ended up rebooting the system and can now save the file.

 

another question, which is more accurate, using a spectral sample created from my i1pro, or a meter correction file created from my i1pro and my i1display? I created both today on a Samsung LCD I'm calibrating for a friend, and see some differences both in grayscale and gamut between the 2 methods.

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