View Full Version : eyeone dll version is important for hcfr !


jojodyne
04-01-08, 03:05 AM
Hi,
I just purchased an eye-one display 2 and encountered a strange problem with the software out of the box. Everything seemed alright until i copied the eyeone.dll (2.0.0.4) to the hcfr directory and started doing grayscale measurements with hcfr 2.0.1.

Up to a certain luminance level everything looked alright then the readings went haywire for an IRE Step or two and then everything went back to normal for higher IREs. It claimed there was no red (0% !)at all between 15<Y<25 which was visibly wrong as such a strong cyan cast cannot be missed.

This was totally independent of testpatterns source, direct/indirect measurements or position of the probe. If i put the projector in high lamp mode i could shift the problem to lower IREs which read fine on the lower lamp mode before.

At first it seemed to me the probe was simply faulty and had a problem at a certain luminance level. I was about to send the probe back when i tried one more thing - updating the software from the site to colormatch 3.6.2. and using the new eyeone.dll (3.4.0.131).

With the new eyeone.dll all problems were gone and it read the grayscale about 3 times faster then before. I did about 10 readings from different positions just to make sure (the readings outside the problem luminance were about the same as before). I hope this wasn't just luck and if its a real solution, maybe this will save others some time.

I am still curious if this is a known issue and if somebody else had this problem before?


regards,

jojodyne

csamos
05-13-08, 05:48 PM
I am so glad I found your post. I was having similar issues with mine. I am using the i1d2 to calibrate my Marquee 8500 CRT projector. At 80 IRE and above, it would hang or take a very long time to respond. I would often have to unplug and plug the D2 back into my laptop to get it to respond.

I just updated my Eye One Match 3 to version 3.6.2, and got a much updated version of eyeone.dll. It is absolutely much faster to collect data now.

Thanks!

-Carl

FernandoF
05-14-08, 11:13 PM
I may be wrong, but I believe you guys had the incorrect "Calibration Mode" for the D2/LT within HCFR. This setting hasn't been mentioned in your posts.

There are 4 modes : "CRT", "LCD", "Plasma", and "Pro". If you try to measure a CRT display in, say, Plasma mode, you get the exact weird behaviour that you guys experienced. I know that because I did it myself... :o

My theory is that, when you guys changed the EyeOne.dll version, the "CRT" Calibration Mode was selected as the new default (since it is the very first one on the list), and then everything started to work.

Could this be what was happening ? If you want to test my theory, just change the Calibration Mode back to "Plasma", measure your CRT displays, and let us know ! :)

Regards,

Fernando

nashou66
05-15-08, 07:55 AM
You can not use the Eye one to test a CRT front projector with HCFR unless they some make it possible to add two more HCFR's to the program so you could place each probe on each crt. When in CRT mode for a front projector it can not read the scan rate, it needs to be right up on the face of the tube or lens. LCD is the correct setting for HCFR and a front projector. The only question I have is the setting for "ambient light" using it with front projector. at first i tried it with it checked even though i did not have the difusor on the probe and got good results regarding the ftL reading, around 9-11. but with the Ambient box left unchecked I only got about 1.7-2.3 ftL's , which is the correct setting?

Athanasios