Let me add one small bit of clarification. The SpyderCheckr does not disable the HSL adjustments.
Right. I should have said it keeps a end user from altering all those nice sliders as a creative or corrective tool after/on top of the so called “calibration” the SpyderCheckr just created. Jeff points out that:
when you use a preset, you are actually applying an absolute adjustment and once set, it limits the subsequent adjustments leftover after the preset is applied which seems a severe limitation. Not the case with a DNG profile (nor as I understand it, a DNG profile with tweaks to the DNG sliders which arguably are used differently, isn’t a preset and not used as often by users as the HSL controls). This goes back to Keith’s first post here (
I suppose the question many people will wonder, is how it compares to using DNG profiles from Passport?) which is putting the cart before the horse, the question I asked was all about the application and implication of how the two tools affect the host product. That was supposed to be my scorn but it was really a question still unanswered by the reviewer.
You can still move the HSL sliders to add further adjustments on top of those loaded by the SpyderCheckr.
Begging the question, what is the HSL preset built from the SpyderCheckr supposed to be doing, why would you build such a preset and then kind of invalidate what it just did? And if you want to really use the HSL tools as designed, why not build a camera calibration from a captured target using the tools Adobe built for both products, the DNG profile?
When I compared shots made with and without the corrections, the differences were rather subtle - less than I expected.
To be fair, one could say the same of some custom DNG profiles. But then I’ve seen significant difference not only in what a custom vs. “canned” (Adobe Standard as an example), DNG profile produce visually but also between DNG profiles built by the free Adobe product and with the Passport package. And least we forget, both DNG profiles can be edited in the free DNG profile editor. All while leaving the HSL controls to be used for other tasks.
Hopefully someone will produce a well researched and thought out review of not only how SpyderCheckr compare to the results using DNG profiles but further, its effect on the operation of the converters, the basis of my question below that started all the scorn!
So Keith, you have this SpyderCheckr which presumably has
industry standard layouts. Is it a 24 patch ColorChecker? Can you build a DNG profile with the free Passport software or DNG Profile Editor as anyone with an existing Macbeth can do?