Luminous Landscape Forum
Raw & Post Processing, Printing => Colour Management => Topic started by: rcdurston on March 17, 2009, 03:16:53 pm
-
I have been using my EyeOne for two years now, mostly on my two 23 ACD's. I used to have the old Colorvision Spyders before that and Lacie Blue Eye.
My ACD's have been relatively unused for the past year since I moved ( been working mostly off my laptop). I'm now trying to get them profiled. I had them both replaced by Apple in fall of 2007. Now when I try to calibrate them I get this banding issue. I have calibrated 9 times in the past 6 hours and it has run from rainbow banding to fluorescent banding to almost perfect but about 30% too contrasty with 50% too much saturation. I am on a 8 core 3.2 MacPro running 10.5.2 and Nvidia 8800GT. I've tried it at Native White Point, 1.8 and 2.2 and luminance of 120. I'm frustrated
Any ideas?
r
(http://durstonphoto.com/photo/17_3_09_10.jpg)
-
Weird curve...
So is this an LED backlit unit? If so, that's the issue.
Also try using Native White Point and Native Gamma, that should reduce banding if that's the only issue. Usually the White Point is pretty ugly on LED displays using these Colorimeters expecting a CCFL, sRGB sized gamut to measure.
You really don't want to be using a 1.8 TRC for the target calibration!
-
The 23" ACD isn't LED backlit, they should calibrate fine...
Is it an i1display or 1i Pro? The profile shouldn't vary that much.
My only thoughts - i1 is full of dust or going bad? Video card problem?
One other possibility, there are some issues with i1 devices/USB and some HP drivers. Download and install Apple's HP printer drivers. This is documented somewhere on xRite's site.
-
You really don't want to be using a 1.8 TRC for the target calibration!
I didn't think so either but I was getting desparate and as you can see that is the 10th attempt.
Its a new EyeOne display thats been sitting in a baggie for its entire life.
Brand new Mac right out of the box but you never know the V card could be bad (?).
any other suggestions?
-
So I just did a new calibration with native targets. Came up looking horrible again.
r
(http://durstonphoto.com/photo/17_3_09_11.jpg)
-
For what it is worth, here are the profiles if you are interested.
here (http://durstonphoto.com/photo/profiles.zip)
-
For what it is worth, here are the profiles if you are interested.
here (http://durstonphoto.com/photo/profiles.zip)
It may be defected - try to check some other i1 colorimeter, they're sometimes broken out of the box these days.
-
MacPro running 10.5.2 and Nvidia 8800GT
I'd upgrade to 10.5.6 - that may or may not help your specific problem, but 10.5.2 is pretty old, and there have been a lot of security updates since then. And graphic driver updates.
Sandy
-
The "current" color temp shouldn't be close to 5000K or 4900K. With native as the target it should be closer to 6500K. Are you certain there isn't any other software that's trying to control the video?
Process of elimation is always a good way to troubleshoot. Try your device on another machine with the same software. Try your device on the same machine using different software (try the ColorEyesDisplayPro demo for example). As a side note, ColorEyesDisplayPro's iterative calibration process can go a long way towards reducing banding on displays without high bit LUT hardware. Certainly upgrade your OS software as mentioned.
If you have problems with all the options outlined above your EyeOneDisplay may have gone bad. There have been some serious QC issues with that device and I have seen a handful of good ones suddenly go bad myself. At that point you could consider having your device swapped out or upgrade to a better device like the DTP94 or Spyder3.
-
Well it looks like its the video card or something with this MacPro. The MacBookPro drives either monitor fine. It also seems that either monitor is fine by itself on the MacPro but when you plug the 2nd one it it loses its ability to render the custom profile. The only one that I can even close to use on both monitors is "Generic RGB"; obviously I know its wrong but its the only thing that works.