Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Message

Re: [datacolor_group] Problem calibrating HP LP3065

2009-06-14 by Cdtobie

Support is the right place to sort this out. They are usually quite  
prompt in replying.

C. D. Tobie
Global Product Technology Mngr.
Digital Imaging & Home Theater
Datacolor.com
CDTobie@...

On Jun 13, 2009, at 11:52 PM, Pierre-Henri Jondot <phjondot@...>  
wrote:

> Hi,
>
> I bought yesterday a spyder3 pro to calibrate two monitors (both a few
> weeks old). The results have been unusable so far.
>
> My setup :
> Mac pro (osx 10.5.7), with ati 3870 mac edition video card, with two
> monitors connected to it :
> - iiyama prolite E2607WS
> - HP LP3065
>
> spyder3 pro software is supposedly the current version : 3.0.4
>
> The buttons on the HP only control the source and brightness (no osd)
>
> The native color temp on the HP is supposedly 6500K from what I could
> read on the net.
>
> I supposed the default target with gamma 2.2 and 6500K for color temp
> should be ok, but it gives me a very strong reddish/magenta tint.
>
> No such thing calibrating the IIyama (using same gamma and color
> temp), and the difference is striking.
>
> By using gamma 2.2 and native white point as a target for the HP, the
> magenta tint disappears, but the IIyama and HP are far from looking
> the same and I can't have any confidence in the colors I see, on
> either monitor...
>
> I did write to datacolor support, but I am not sure I will get an
> answer soon, so, learning about this group, I thought that maybe
> someone here could enlighten me.
>
> Regards,
>
> Pierre-Henri
>
> N.B. : browsing the group archives for <<magenta>>, it looks someone
> else encountered a similar problem, with a 22" dell and a HP 2475w,
> but I didn't read an explanation...
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.