A720 IS and its overexposure-behaviour

[viewpix]

[LjL]

Well, this should be the relevant thread, but I'm not sure there is a binary build for the A720.

You can compile from source, with some patience, by following the instructions about compiling and applying the patches provided in the thread.

But maybe if you wait a little it'll end up in truck, in AllBest, in the collaborative build or somewhere... or for that matter, I could try making an AllBest build for the A720 myself (I have an A720 and I have the compiling environment set up), but don't hold your breath on this, because I always plan on doing things and then don't

By the way, I've found this thread that's very much relevant to what we're talking about here.

[Jucifer]

Or... you could try the collaborative CHDK build. Be warned though, you may not want to go back... ;)

[LjL]

Ah, right, I should have known it's in there already... but when I opened the thread again, I searched for "curve" and didn't find that keyword, so assumed it was somewhere else 

Information about the builds is still a bit scattered out... perhaps I'll play with the wiki.

[viewpix]

[LjL]

Yes, basically. Given it does contain the JPEG curves feature, I'd definitely suggest you try it out first. It worked fine on my A720, although I didn't use it for very long (since I'm testing DataGhost's build right now).

[viewpix]

[LjL]

I think it's the same thing described in the Custom processing for JPEG thread...

[viewpix]

[LjL]

I'm new myself (camera has about one week now...) and experimenting. The funny thing is I'm not really so interested in photography, but rather in the tricks you can do with software...

[Jucifer]

viewpix: the collaborative CHDK build has everything the trunk ("allbest build") has, and a lot of tweaks & additions.

[LjL]

Anyway, the feature is likely possible to implement.

The zebra code already looks for 100% white pixels; it'd be a matter of telling it to step down if it sees (m)any.

I've tried shooting_set_user_tv96(shooting_get_user_tv96()+32) and shooting_set_tv96_direct(shooting_get_tv96()+32, SET_NOW) (guess-copied from the bracketing code in shooting.c), but got awkward results - most importantly, the viewport's brightness doesn't change in real time.

But it's more than likely that some more clever functions can be employed instead, and/or a viewport update with the requested exposure forced.

[PhyrePhoX]

here is a whole thread about the EV correction: S3IS: Add shortcut for EV adjustments (Allbest build) maybe there is some useful information in there for you. basically manual ev correction is implemented in the jucifer build, you can set ev by a shortcut. the problem that the screen isnt updated persists though, thats why this feature isnt in main trunk yet. on my cam (s3is and possibly s5is as well) the screen updates when you enable the on screen CANON histogram. i think we need to tap into that code somewhere.

[viewpix]

[Hacki]

I honestly see nothing wrong with this pic. Human eyes cover a much bigger dynamic range than a crappy little P&S-sensor. Even though it looks ok to you, there is a huge difference between a roof which is directly illuminated by the sun, or a wall which is in the shadow..