News for hackers. Stuff that matters.

A comment on The Limits of Computational Photography. Parent comment

Re:The Limits of Computational Photography by godsfshrmn on Tuesday January 31, 2023 @05:27AM (#34593481)
My mirror less Olympus does this as well. Set number of f stops, exposures etc all in-camera
[ Parent | on HN ]
Re:The Limits of Computational Photography by fsloth on Tuesday January 31, 2023 @07:49AM (#34594419)
It composes the hdr as well?
[ Parent | on HN ]
Re:The Limits of Computational Photography by leviathant on Tuesday January 31, 2023 @08:33AM (#34594800)
The Canon T2i that I bought in 2010 sure did.
[ Parent | on HN ]
Re:The Limits of Computational Photography by fsloth on Wednesday February 01, 2023 @05:44AM (#34608832)
All the references I found just referred the auto-bracketing (I.e. shooting the the images with different exposure) but I can't find any mention of in-camera composition of the final hdr - all sources just tell you to use an external software for the HDR composition. I'm not doubting you but this sounds like an undermarketed obscure feature - can you find any references for this feature?
[ Parent | on HN ]
Re:The Limits of Computational Photography by CWuestefeld on Tuesday January 31, 2023 @02:00PM (#34600006)
Yup. I was recently doing some night sky shooting with my E-M1.3. Not only does it do what you say, but when using its "super exposure" it'll take multiple shots moving its sensor (using its in-body stabilization) by sub-pixel amounts. This produces from a 15Mp sensor, a 50Mp or 80Mp result - and as a side-effect, the stack of images results in weighted averaging of the pixels, thus doing a fantastic job of noise suppression. And yes, it auto-aligns, at least in the 50Mp mode.
[ Parent | on HN ]