AVS Forum banner

1321 - 1340 of 13608 Posts

·
Registered
Joined
·
1,124 Posts

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


There is some esoteric usb com problem with the i1pro. The current status is:


1. Initial version 3.0.0.0 of the argyll wrapper code works fine with the i1pro but supports only one meter at a time and doesn't support the d3 or colormunki.

2. Versions >3.0.0.0 which support multiple meters (including the d3/colormunki) but throws an error in icoms when trying to open the i1pro. Spotread works fine.

3. If I modify the i1pro inf to include the standard winusb.dll as a required device driver everybody's happy but so far working on win32xp only.
Just to clarify a few things..


In my tests using using your modified (winusb) i1pro.inf, windows can't start the device, so it's doesn't work in Windows 7 with your HCFR build or spotread. I looked at the inf, and as far as I can tell (not my area of expertise), it looks okay, although the related oemxx.inf copies the ptlibusb0 section. This doesn't occur with the (not DTP94, but "C5-ish") MonacoOptix.inf installation, which uses winusb and works fine. I did some googling and found some mention of the i1Pro revision D and later being incompatible with winusb on Windows 7, with some other references to device descriptors and max packet size issues.


I may be confused a little by our usage of "multiple" vs. "simultaenous" meters. The 3.0.4 code I compiled from Git seems to work with multiple meters that I have - the i1Pro, MonacoOptix, and DTP94 using the regular Argyll 1.4 drivers. I don't know if the D3 works since I don't own one yet - but that's the big question. I don't think that build supports simultaneously connected meters, but this is not something I use often, and it can be worked around by unplugging and maybe restartingHCFR.


I would be happy with a build that supports the i1Pro, D3, and other meters separately on Windows 7 using the Argyll 1.40 drivers, and also contained your fix for the D3 stability. Do you think that's possible?
 

·
Registered
Joined
·
6,804 Posts
Discussion Starter #1,322
Sorry for the lack of clarity regarding multiple vs. simultaneous, I've used them interchangeably so yes the current build supports simultaneous meters in the same program instance including the D3 and the i1pro. The D3 meter fix is there regardless of which drivers get loaded so that will work as well.
 

·
Registered
Joined
·
1,043 Posts
The Argyll v 1.4 drivers for the i1pro work in Windows7 64 bit, it can be tested using the spotread.exe in the lib directory. HCFR throws an error when trying to access the driver.
 

·
Registered
Joined
·
1,124 Posts

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


..so yes the current build supports simultaneous meters in the same program instance including the D3 and the i1pro. .
Yes, in Win XP 32. But we've concluded that this build will not support the i1Pro in Windows 7 with 1.40 libusb0 or winusb drivers.


My point is that I would prefer to forgo the simultaneously connected meters feature if I can have a 3.0.4.x version that supports the (stability fixed) D3 and i1Pro meters in Windows 7. Could you post or PM the adaptive integration changes you made to the D3 code? I'm planning on purchasing a D3, so I would like to add your changes to what I have and see if it works for both meters in Win7.
 

·
Registered
Joined
·
26 Posts
Hello

I have a problem by intalling the Spyder 3 driver


1. Install hcfr

2. Plug in Spyder

3. Selecting Spyder at the device manager

4. Selecting the driver folder


Windows finds the driver, but it didnt install the driver.


I get this Message (german Windows)
http://db.tt/CNmwurbq



It says something like: Cant finde hash , driver damaged.


Its the same on 2 Windows8 x64 machines.


Thanks for your help.
 

·
Registered
Joined
·
1,043 Posts

Quote:
Originally Posted by Spinnenschwein  /t/1393853/fork-of-hcfr-started-whats-needed/1320#post_22910978


Hello

I have a problem by intalling the Spyder 3 driver


1. Install hcfr

2. Plug in Spyder

3. Selecting Spyder at the device manager

4. Selecting the driver folder


Windows finds the driver, but it didnt install the driver.


I get this Message (german Windows)
http://db.tt/CNmwurbq



It says something like: Cant finde hash , driver damaged.


Its the same on 2 Windows8 x64 machines.


Thanks for your help.

when you install the driver use the driver in the libusb1 folder in the HCFR directory
 

·
Registered
Joined
·
1,043 Posts

Quote:
Originally Posted by Spinnenschwein  /t/1393853/fork-of-hcfr-started-whats-needed/1320#post_22911497


I cant find the folder


I have version 3.0.4.0 installed

............ \Colorimeter_HCFR 3\libusb1
 

·
Registered
Joined
·
3 Posts
Hi,

I am trying to use HCFR to calibrate my 65lw6500 tv (led backlit lcd tv) with i1 display pro. Am I right to say that I should use the i1D3 NON-refresh display type? How about spectral sample? Does it matter which one i choose? I saw there are 2 LED options: LCD RGB LED IPS and LCD White LED IPS. But the samples seem to be more applicable for computer monitors. Which one should I choose?


thanks a lot for any advice.
 

·
Registered
Joined
·
3,645 Posts

Quote:
Originally Posted by ganymede123  /t/1393853/fork-of-hcfr-started-whats-needed/1320#post_22913151


Hi,

I am trying to use HCFR to calibrate my 65lw6500 tv (led backlit lcd tv) with i1 display pro. Am I right to say that I should use the i1D3 NON-refresh display type? How about spectral sample? Does it matter which one i choose? I saw there are 2 LED options: LCD RGB LED IPS and LCD White LED IPS. But the samples seem to be more applicable for computer monitors. Which one should I choose?


thanks a lot for any advice.
Yes, use non-refresh on an LCD.


If your LW6500 is an IPS panel, then I would use the White LED IPS spectral sample. That's what I used on my LG LH90.
 

·
Registered
Joined
·
6,804 Posts
Discussion Starter #1,336
Here is a new build which works with both my D3 and i1pro 2 using the ArgyllCMS 1.4 driver code libusb0 instead of winusb0. This version also has the D3 tweaks to improve low-light precision. Update your i1pro drivers from the Drivers directory and let me know if it works on win7.


I can't help with the spyder installation since I don't have one to test but the general procedure for installation is to:


1. Load the Argyll driver using the spyder.inf file from the Drivers directory

2. copy the driver .dll file from the vendor software to the HCFR directory and then run either spyd2en or spyd4en on that file.




HCFRsetup.exe
 

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

Quote:
Originally Posted by rahzel  /t/1393853/fork-of-hcfr-started-whats-needed/1320#post_22913192


Yes, use non-refresh on an LCD.

Regarding refresh vs. non-refresh mode and the D3. In the current code it makes absolutely no difference which mode you use with LCDs because after failing to find sync it will default to the non-refresh integration time anyway. As for plasmas, I also found it makes no measurable difference which mode you use. The probe will sync to patterns with luma values >40% (~30 Hz is a typical value it finds on my plasma) but measurements with it synced and in non-refresh mode are identical (within probe precision) throughout the gray scale. I made it a little easier to test this in the current code so if you want to sync it with your plasma display:


1. When you open the probe page click calibrate.

2. Display a bright white pattern (50% or more)

3. Take measurements (the probe will retain the measured refresh period until you click calibrate again)
 

·
Registered
Joined
·
1,043 Posts

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


Here is a new build which works with both my D3 and i1pro 2 using the ArgyllCMS 1.4 driver code libusb0 instead of winusb0. This version also has the D3 tweaks to improve low-light precision. Update your i1pro drivers from the Drivers directory and let me know if it works on win7.


I can't help with the spyder installation since I don't have one to test but the general procedure for installation is to:


1. Load the Argyll driver using the spyder.inf file from the Drivers directory

2. copy the driver .dll file from the vendor software to the HCFR directory and then run either spyd2en or spyd4en on that file.




HCFRsetup.exe

works on windows 7 64bit. thanks zoyd
 

·
Registered
Joined
·
3,645 Posts

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


Here is a new build which works with both my D3 and i1pro 2 using the ArgyllCMS 1.4 driver code libusb0 instead of winusb0. This version also has the D3 tweaks to improve low-light precision. Update your i1pro drivers from the Drivers directory and let me know if it works on win7.

HCFRsetup.exe
Thanks zoyd.
 
1321 - 1340 of 13608 Posts
Top