I'm also using CalMAN's autocal for the 1D gamma cal of my JVC PJ via DDC, and LS for the big LUT cal of video processors.
CalMAN has lot's of indicators to check any kind of measured data. Maybe too much.
But because of it's "target approximation" autocal system / each cal point, I have only limited use for CM.
An autocal of 3D LUTs with thousands of points who needs to run over many, many hours isn't working for me.
Even if I start calibrating 2 hrs after powering ON, my PJ's lamp isn't stable enough in CCT and brightness over the next 3 hours.
But if I go calibrating my PJ, then the result should be as best as possible.
So for making big calibrated LUT's I'm using LS.
LS is fast because of it's profiling concept - each point need's to get only 1-times measured.
Using the final profiling data, I can play with parameters like different gamma coefficients or different targets like BT601/709 for making a new LUT, as many times I want, w/o having the need to run the entire measurement / autocal process again.
If desired, a final quick profiling can be done to check the result.
Every SW solution has it's pro and cons and we just should respect everybody's own decision, what's best for him in his case.
To be honest, I've learnd a lot about PJ calibration using CalMAN since V3. Had lot of fun with ... not only with it's bugs ...
So I'm using CM+LS in combination, playing with both is part of my crazy hobby ... sitting next to a ****ing expensive PJ, watching dump-making test patterns over hours and hours ... weird ...
Edited by *Harry* - 9/18/13 at 4:27pm