jmac698
Clearly if you're at the point of waiting for photons to hit, you need a long exposure.
You need a longer total exposure, but the photons don't care how many times you read out the sensor in between their respective arrival times. Astronomy routinely gets deeper by adding images collected over many separate exposures (e.g.
http://xdf.ucolick.org/)
On the subject of stacking with low end sensors, this may be of interest
https://research.googleblog.com/2017/04/experimental-nighttime-photography-with.html (also the SeeInTheDark presentation linked from there)
I'm still confused as to why the amp glow is reduced in the mask area; maybe, being an electric field, it's shielded by the metal mask.
It may be that the area outside the mask is artificially brightened by the camera (related to
https://chdk.setepontos.com/d/12926/7)
Anyhow, my point was to not artificially limit programs, as you never know what your users will do.
I agree completely. All else being equal, CHDK should let user push things as far as they want.
If extending my limit requires extra programming, I don't expect anyone to do that
I'm not averse to extra programming, but I'm more likely to be motivated if I see a clear real-world use case.
In the case of cameras that natively support 1000 seconds vs implementing exp_drive (up to 2000) there's a trade of effort to implement, maintenance and RAM that would otherwise be available for other things. If someone shows me a real case where using a single 30 minute exposure makes the difference compared to a few shorter exposures, I'd support implementing it on those cameras.
Do you know the exposure limits with the SX50 or SX60?
Both have code to support up to 2000 seconds. Whether something else fails before that as on your
sd1200 I don't know.
