Pages: [1]   Go Down

Author Topic: A question about Hugin  (Read 1544 times)

Chairman Bill

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 2113
    • flickr page
A question about Hugin
« on: January 27, 2013, 06:08:56 PM »

I've been trying to do panoramas with Hugin. All is fairly straightforward, except for one thing - a stitch of say three D700 files (12.1 MP each), even with a significant (30%) overlap, should give me more than a 7.3 MP image!

Why are the panoramas less big in terms of pixel count, than a single original image? Further, how do I get it to output full-size images?

Any help gratefully received.

BartvanderWolf

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 5282
Re: A question about Hugin
« Reply #1 on: January 27, 2013, 06:53:42 PM »

I've been trying to do panoramas with Hugin. All is fairly straightforward, except for one thing - a stitch of say three D700 files (12.1 MP each), even with a significant (30%) overlap, should give me more than a 7.3 MP image!

Why are the panoramas less big in terms of pixel count, than a single original image? Further, how do I get it to output full-size images?

Hi,

Depending on the Field of View and the projection method you choose, there may be a fair amount of cropping needed if you want to avoid having to clone in areas that were not covered.

On the Stitcher tab you can click the "Calculate optimal size" button, and then the "Fit crop to images" button to see if it is the cropping that causes the loss of pixels. You can always override the calculated canvas size by typing in your assumption, and Hugin will interpolate with the method chosen with the remapper options (at the bottom of that Stitcher tab), and you can also switch off the final cropping there.

Cheers,
Bart
Logged
== If you do what you did, you'll get what you got. ==

EduPerez

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 701
    • Edu Pérez
Re: A question about Hugin
« Reply #2 on: January 29, 2013, 09:03:58 AM »

In addition to the post above, and if I recall correctly, Hugin also does some resizing to the final output; looks like perhaps it is resizing too much.
Logged
Pages: [1]   Go Up