Hmmm, just to add a bit of personal experience with Hugin, memory and
image sizes.
I shoot 6MP, 48-bit files. I decided one time, a few years ago, to run
cpfind on some of my full-rez images (no downscaling). I wasn't aligning
stacks, just my usual handheld panorama. On my old laptop with 2GB of
RAM, running Linux. I started it from my GUI (XFCE). It seemingly
stalled. After about 12 hours, I stopped it and long minutes afterwards,
the machine began responding again. So I decided to try it again, only I
used no GUI and ran it from the command line on one image. With another
login terminal monitoring memory usage.
It used up just about 2GB of RAM to process 1 6MP 48-bit TIFF. I can't
project from there to how much memory running cpfind (or other image
feature recognition sw) on an 18MP image would use ... but I bet it's a
lot more than a mere 2GB. So just how much memory DO you have on your
machine?
I think the 30-60 second response time (when manually creating control
points) sounds like an issue someone mentioned a good while ago when he
put forth his idea of replacing Hugin's present text-based PTO format
with a database format - figuring it would speed up the process of
handling really big image sets. I don't remember what happened with that
discussion, although I think the idea of changing the PTO format didn't
go anywhere?
BTW, I like image stabilization. My camera has it built into the body,
makes quite a difference.
On 04/13/2014 08:15 PM, Hansjörg Temperli wrote:
Yes, image stabilisation is what i need.
These tutorials surely work fine for a few small images - but my current
heap consists of 800 18MP tiffs. Downscaling is not really an option
because i plan to do some panning.
I started hand-tuning the results from the align procedure, but this is
very tedious because it takes some 30-60seconds for one operation, be it
deleting or adding a controll point.
I use the 2014.0.0 x64 release for windows and there is still plenty of
empty RAM ;)
Am Sonntag, 13. April 2014 00:04:44 UTC+2 schrieb Thomas Pryds:
It sounds like what you need is image stabilization. This is possible
with Hugin. I successfully accomplished this, following the guide at
http://imgur.com/a/3qfWQ . Also, the Panotools wiki has something on
the subject at http://wiki.panotools.org/Time_lapse_stabilization
<http://wiki.panotools.org/Time_lapse_stabilization>
Thomas P.
2014-04-12 23:38 GMT+02:00 Hansjörg Temperli <[email protected]>:
> Hi Folks
> I recently started with timelapse photography, and the main
problem is, due
> to the lack of a very sturdy tripod, that i need to align the images
> afterwards.
> My current projects have at least 800 images, so i have to call
> align_image_stack on the command line. During the last night, i
ran a 800
> image batch that ultimatively failed because in some images,
ships move
> through the imageand the program somehow tried to align these
moving objects
> instead of the horizon.
>
> Now i have this idea to make it work:
>
> Select some 10-15 points on a reference frame, then the program
tries to
> find each point in one of the images, aligns this image and then
goes on to
> the next image. And if it cant find a point in the vicinity
(because this
> point is hidden by an object that moves by), it just goes on and
tries the
> other points.
>
> Now if only someone could program such an algorithm... or has
another idea
> how to align huge stacks?
>
> Thanks!
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
--
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/534B932C.8020105%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
