You're right - if DRC is enabled, it will run a stats pass. The reason it isn't documented is that I wasn't aware of it! That algorithm was developed by a different team who often did quirky things, and this seems to be one of them. I haven't checked, but I'm guessing that it is using the hardware block to implement at least part of the dynamic range manipulation, and so needs the stats to work out the ranges. I'm not going into that code to make mods - it's just too scary!shusheer wrote:It appears that the dynamic range compression option (-drc high) triggers a recalculation of white-balance in the same way as adding a stats pass (-st or --stats) - i.e. this prevents the setting of fixed white balance gains.
I have not found any documentation anywhere saying that setting DRC will clobber your fixed AWB settings, so it may be helpful if this is added (in much the same way --stats has this mentioned somewhere, but I can't seem to find that reference now).
I've just looked back at your original command:shusheer wrote:However this doesn't actually fix the reported problem, other than giving me a work-around (awb off and removing -drc and -st) - what this does do is home in on where the white-balance algorithm may have an error, in that it's something to do with AWB, DRC and/or stats (in fact it appears to happen without AWB=off or stats or DRC, which implies that it's an issue with the basic AWB algorithm having some kind of instability).
Not quite accurate.so I have tried setting this to off, and also using --stats which is supposed to calculate white balance from the captured image rather than heuristics
Users browsing this forum: No registered users and 11 guests