Memory is an issue, particularly after having upsampled 16-MP images to 
200%. ImageJ is another program that can do different types of averaging of 
a stack of images, but indeed, memory usage is the limiting factor.

Regarding upsampling: as a first step, I'd be happy to end up with an image 
with the same pixel number, i.e., no upsampling. The idea is to record 
images such that an image element that first fell on a red pixel will also 
fall on a green and a blue pixel in subsequent images. That is, all three 
colors will be recorded for every image element, as in mimicking a Foveon 
sensor. That should result in the same image dimensions but significantly 
higher effective resolution and color accuracy. I believe technologies that 
shift the sensor by one pixel at a time attempt exactly that.

Shifts by 1/2 of a pixel could then increase the resolution even further, 
but it's computationally much more expensive compared to shifting by one 
pixel. In any case, it seems to me that super-resolution imaging (as well 
as other multi-shot stacking techniques) has a lot of untapped potential, 
and I hope software manufacturers will provide tools now that probably 
every new camera at some point in the future will get the requisite 
hardware capabilities (sensor shift).


On Thursday, March 5, 2015 at 5:58:49 AM UTC-5, bugbear wrote:
>
> Bruno Postle wrote: 
> > On 5 March 2015 at 09:15, bugbear <[email protected] <javascript:>> 
> wrote: 
> >> 
> >> If you just want to average, a simple script using something like 
> >> netpbm could do it simply and efficiently. 
> > 
> > ImageMagick works well for averaging images, see this post from Pat 
> > David: 
> http://blog.patdavid.net/2012/08/imagemagick-average-blending-files.html 
>
> Yes, probably OK for super-resolution work, 
> which has a small number (say 5-15) of source images. 
>
> But, in a world of HDR panoramas, even well equipped 
> computers *sometimes* need to worry about memory 
> efficiency,  and ImageMagick, like enblend and enfuse, holds all the 
> images 
> in memory, and ImageMagick uses quite a lot of memory per image. 
>
>   BugBear 
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/559312b1-fdfd-4be4-85b8-84aac6571865%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to