[argyllcms] Re: Newbie question: is dispcal supposed to be so slow?

  • From: Graeme Gill <graeme@xxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Thu, 08 Mar 2012 09:32:44 +1100

Chris Dennis wrote:

> It takes from a few seconds to a few minutes per patch, and because it does 
> so many patches it
> takes a couple of hours for a full calibration and profile generation.
> Is that normal?  Is there a way so speed it up other than opting for 'low 
> quality'?


As Florian notes, it is rather instrument dependant. The next release may speed
the Spyder up a bit if that's any help. But you have many other possibilities in
speeding things up yourself.

The term "quality" was perhaps a bad choice on my part. Perhaps I
should have labelled that parameter "effort" or "time" or "speed",
since there is no guarantee that reading extra patches or creating
larger grids will noticeably improve the calibration or profile accuracy,
particularly if a device is well behaved. So perhaps I should fix this
by changing to "-speed: very fast, fast, medium, slow, excruciatingly ultra 
rather than "-quality: very low, low, medium, high, ultra high".

Matrix profiles need a fraction of the number of patches as cLUT profiles,
so that is a choice if it is a good fit for your device. So my
usual advice applies: Just because Argyll has an "11" setting,
don't feel like you have to use it. Start with medium. Experiment
with high. Try low if it's all taking too long. Compare the results,
and decide what you can live with."

Graeme Gill.

Other related posts: