[argyllcms] Re: Display Calibration Hardware Capabilities

  • From: adam k <aak1946@xxxxxxxxx>
  • To: "argyllcms@xxxxxxxxxxxxx" <argyllcms@xxxxxxxxxxxxx>
  • Date: Tue, 3 May 2011 18:52:24 -0400

I think the guy who test CM should test another one. The one he has is
definitely bad one.

Sent from iPhone

On Apr 29, 2011, at 10:21 PM, Rishi Sanyal <rishi.j.sanyal@xxxxxxxxx> wrote:

> I'm not so sure I believe the ColorMunki is that bad. Ethan doesn't
> talk about using longer integration times via ArgyllCMS/dispcalGUI
> with the ColorMunki. I have done this, & get much more accurate
> shadows with my ColorMunki. Prior to using longer integration times,
> my ColorMunki was *horrible*. Its profile brightened all shadows
> (didn't map input 0 to output 0 like my colorimeter did). You *have*
> to use the longer integration times with the ColorMunki. Perhaps this
> is the reason his CM performed poorly.
>
> Another reason his CM may have performed poorly could be because
> ColorMunki software is just silly. It only measures primaries. I
> didn't find its profile to be at all accurate. Which is why I switched
> to using dispcalGUI. I'm happy with my profiles now, but I haven't
> objectively tested how accurate the colors are (how do you do that
> anyway? I don't believe you can use one hardware device to test
> itself...).
>
> I will email Ethan & ask him if he could redo the test with CM +
> dispcalGUI (using longer integration times).
>
> Also, Ethan talks about the user-unfriendliness of command-line
> ArgyllCMS, but doesn't mention the very user-friendly (IMHO)
> dispcalGUI.
>
> FYI wide-gamut displays are very problematic. My Dell U2711 just
> couldn't be profiled with my i1 Display 2. because it just estimated
> the red primary (& perhaps the others too, but not as obviously)
> completely wrong. The resulting profile completely hue-shifted &
> desaturated my reds such that I just couldn't see red on my monitor. I
> could literally make a color patch in Adobe Photoshop of 255,0,0 &
> it'd look like a desaturated orange. The ColorMunki profile fixes
> this.
>
> Interestingly enough, when I used the CM to make a new correction
> matrix for my i1 Display 2 (you can do this using ArgylllCMS, which
> shows a bunch of colors to both your colorimeter & your CM or any
> other spectrophotometer, separately of course, & creates a 3x3
> correction matrix that helps the colorimeter more accurately assess
> that monitor's primaries), my i1 Display 2 behaved quite well. Reds
> came back. The profile looks pretty similar to the CM profile, not
> surprisingly.
>
> Best,
> Rishi
>
> On Fri, Apr 29, 2011 at 7:02 PM, adam k <aak1946@xxxxxxxxx> wrote:
>> I'm sorry to find out about CM now after I bought it. How can I test it?
>>
>> Sent from iPhone
>>
>> On Apr 29, 2011, at 9:58 PM, edmund ronald <edmundronald@xxxxxxxxx> wrote:
>>
>>> I wonder whether the bad showing of ColorMunki on blacks is a one-unit 
>>> failure?
>>> The Spyder guys seem to have reinvested the cashflow from their
>>> mediocre products into making perfectly acceptable products.
>>>
>>> Edmund
>>>
>>> On Sat, Apr 30, 2011 at 3:07 AM, Iliah Borg <ib@xxxxxxxxxxx> wrote:
>>>> An updated review of the hardwares is published today by Ethan Hansen here:
>>>> http://www.drycreekphoto.com/Learn/Calibration/MonitorCalibrationHardware.html
>>>>
>>>> It contains some interesting references to Argyll CMS too.
>>>> Ethan suggested some additional explanations here
>>>> http://www.luminous-landscape.com/forum/index.php?topic=53825.0
>>>>
>>>> --
>>>> Iliah Borg
>>>> ib@xxxxxxxxxxx
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>

Other related posts:

  1. Home
  2. argyllcms
  3. Archive
  4. 05-2011