As I say, if CHDK could over some of this functionality it would greatly add to its raw based capability. Note I say raw based based, ie not jpegs.
In CHDK, you have to shoot an image to have access to full dynamic range raw pixel values.
Is get_live_histo RAW based?
the relationship between viewport YUV pixels and raw values isn't specified AFAIK.
Peace: I’ll say no more ;-)
BTW my use case is ‘just’ stills photography, not even timelapses.
I’m content with the current histogram, with a calibration step, although I wish the overexposure warning was clearer, ie I can hardly see it on my G7X.
Hmm, looking at mine I think the histogram over/under warnings are broken on digic 6. There is a smaller red dot that that shows when a peak overflows the vertical range, but for me the actual warning dots don't usually show up even with wildly incorrect exposure set in M mode.For zebra, the limits are configurable and need to be moved significantly from the defaults, but the live view values used for histo over/under appear to be hard coded to use the 3 lowest and highest bins (weighted to the extremes) which basically never show up in the digic 6 live view.I'll look into fixing / improving this.
I think we'll need configurable black level and white level for live view. One of my D6 cameras uses approximately a 16...240 range (luma), the other one is approximately full range. This is when using the LCD, other output devices can potentially use different levels, I guess. I don't know whether pre-D6 cameras are affected.
Started by mkmenuts
Started by larrycafe
Started by pigeonhill
General Help and Assistance on using CHDK stable releases
Started by pauledney
General Discussion and Assistance