2013/7/6 edmund ronald <edmundronald@xxxxxxxxx>: > At random, I'd say that wb is not so important; especially if you want to > process for the exact illumination in which you imaged the chart -a > "situation profile' in which case you just choose a white balance and lock > it down for ulterior uses of the profile. The problem is that I'd like to make general use camera profile for use in different daylight condition so wb IS important. I have 2 problems: 1) Setting correct WB, but I hope that shifting wb and tint gives me linear shift of a* and b*, so it'll be possible to create wb,tint -> a*,b* matrix. (I can have as many data as I want to :) ). I had a hope that somebody did it before me. I miss option from ProfileMaker to use Camera wb and make profile not change wb. 2) As I said I manualy changed wb and tint to the moment when dE on gray patches is lower than 1. Unfortunately there is a visible difference between profiles from Argyll and ProfileMaker and I think that ProfileMaker made better job. I see color cast on deep blue and magenta patches of IT8.7/2 (KL17-19) (comparision between calibrated wide gamut monitor and target) Argyll results (profcheck) [0.607386] K19: 0.095811 0.189180 0.455330 -> 19.066371 32.121577 -63.826558 should be 19.013502 33.141103 -63.779567 [1.004242] L19: 0.048637 0.135180 0.387260 -> 12.695499 37.168763 -64.801893 should be 12.608060 39.190741 -65.031424 ProfileMaker (profcheck) [1.054828] K19: 0.095811 0.189180 0.455330 -> 19.571349 30.159904 -60.372242 should be 19.013502 33.141103 -63.779567 [0.982863] L19: 0.048637 0.135180 0.387260 -> 11.731159 37.078710 -62.004068 should be 12.608060 39.190741 -65.031424 Maybe I'm wrong. -- Maciek Bryński