headers
Bernard Lang | 1 May 2007 01:48

Re: stitching a photo with another image


* Bruno Postle <bruno <at> postle.net>, le 30-04-07, a écrit:
> 
> On Thu 26-Apr-2007 at 19:29 -0400, Bernard Lang wrote:
> >
> >Whatever ...  my problem is that, after changing the picture geometry,
> >I often have missing corners that force me to cut off a good part of
> >the picture if I want to make it rectangular.  Instead, since these
> >corner are often without real information, I choose to invent whatever
> >should have been there (apparently this is not too original), usually
> >by stealing texture in some other part of the picture with Gimp.
> 
> Recent development versions of the gimp have a 'perspective clone 
> tool' which you may find useful:
> 
> http://pedroalonso.es/blog/?p=88

Thanks for the pointer.

This is quite smart, and simple to use for someone who does not want
to get into the intricacies of Hugin.  However, it seems to me to be a
bit brutal, at least from what I understood of the tutorial.  I would
much prefer a drag-and-drop that changes shape as it is moved, if it
is to be done in Gimp.

But my real preference is as you suggest below.

> Otherwise, I suggest that you extract perspective corrected 
> fragments using hugin and retouch them by hand.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tom Brown | 1 May 2007 02:55

Re: Straight_line_control_points


Emmanuel Favre-Nicolin-2 wrote:
> 
> I've recently seen that Straight_line_control_points are avalaible since
> beta4 (after reading one of the last conversation). Is there a howto to
> use
> this (interesting) feature?
> 
> 
> 

If I understand your question, perhaps this bit of documentation I wrote for
PentaxWorld will be of help.  You can make vertical reference lines exactly
the same way.

"This is something I haven't been able to find on the Internet.  That is,
how to enter horizontal or vertical reference lines.  There are references
suggesting to add them, but not showing how.  I guess it's so easy they
didn't realize slower moving people, like myself, might ponder this sort of
thing for 10 minutes before figuring it out.

The key to adding a reference line is to go to the 'Control Points' tab,
selecting the same image in both frames, and then clicking on the image in
the left panel on one end of a horizontal reference, as well as clicking on
the right panel on the other end of the horizontal reference.  The program
will give you a warning if you have 'auto fine-tune' enabled.  Also, there
is no where to tell it you're entering a reference line, instead of a
control point pair.  Don't worry though, it will figure it out."

This doc was written quite some time ago for version 0.6.  There is now a
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lars Monsees | 1 May 2007 14:05
Picon

Problems with creating 360° panorama


Hello,

I have taken 14 images freehand with a Sony Cybershot DSC-S70 that I
can´t get a panorama of. Here is how I try to do it (hugin 0.7b3):

- load images, lens type rectilinear
- focal length is automatically set to 7, rest of the settings is
missing. Set focal length multiplier manually to 1
- autopano-sift starts, using default settings
- panorama preview looks bad
- assistant tab: "connected by 195 control points, mean error: 35.5, max
105.4", but control points look very good

- images tab: yaw values are not in right order
- 360° / 14 -> ~25° -> manually set yaw values

- camera and lens tab: degrees of view is set to 135
- change it to 75 -> focal length is set to ~22.5
- preview looks better now

- optimize positions y,p,r -> preview is totally twisted

I´ve uploaded the project and images to:
http://www.hansenet.de/~larsen/test.zip

I´ve read several tutorials but can´t figure out what I´m doing wrong
here. What makes me wonder is that the control points are perfect but
the ordering (yaw) of the images gets mixed up. Also, the values for
pitch and roll when optimized are totally mixed up.
(Continue reading)

Permalink | Reply | 22 comments |
headers
Serge Maandag | 1 May 2007 14:20

[hugin-ptx] Re: Problems with creating 360° panorama


> I have taken 14 images freehand with a Sony Cybershot DSC-S70 that I
> can´t get a panorama of. Here is how I try to do it (hugin 0.7b3):
>
> - camera and lens tab: degrees of view is set to 135
> - change it to 75 -> focal length is set to ~22.5
> - preview looks better now
>
> - optimize positions y,p,r -> preview is totally twisted

I haven't looked at your images, but I have made a lot of panoramas with
the similar Dsc-S75.

The Focal length when zoomed out is 34mm, when zoomed in it is 102mm.
So if you took the images zoomed out, set the focal length to 34mm and the
focal length multiplier to 1.

When optimizing, make sure you optimize FoV and horizontal/vertical shift
(d/e). If you're not rotating around you no parallax point, optimize for
individual d/e parameters per image.

That should give you nice results.

Serge.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx <at> googlegroups.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bruno Postle | 1 May 2007 14:23
X-Face

Re: Problems with creating 360° panorama


On Tue 01-May-2007 at 14:05 +0200, Lars Monsees wrote:
>
>- optimize positions y,p,r -> preview is totally twisted

Sorry I haven't had time to look at your project, but the problem 
sounds familiar.  Basically you always have to optimise Field of 
View for a 360 degree panorama, even if you think you know what it 
is already.

Probably you also want to optimise barrel distorion, there are some 
notes here:

http://wiki.panotools.org/Hugin_Optimizer_tab

--

-- 
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic
software" group.
To post to this group, send email to hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Michal | 1 May 2007 14:50
Picon
Favicon

Re: Problems with creating 360° panorama

Hi, I tried to load your project into hugin and I got quite good result 
in few seconds. See attached pto file. What I did was:

1) reset a,b,c,d,e to 0
2) optimize y,p,r,v,b
3) optimize exposure (LDR, variable with balance)
4) straighten the horizont in preview dialog

Michal

Lars Monsees wrote:
> Hello,
> 
> I have taken 14 images freehand with a Sony Cybershot DSC-S70 that I
> can´t get a panorama of. Here is how I try to do it (hugin 0.7b3):
> 
> - load images, lens type rectilinear
> - focal length is automatically set to 7, rest of the settings is
> missing. Set focal length multiplier manually to 1
> - autopano-sift starts, using default settings
> - panorama preview looks bad
> - assistant tab: "connected by 195 control points, mean error: 35.5, max
> 105.4", but control points look very good
> 
> - images tab: yaw values are not in right order
> - 360° / 14 -> ~25° -> manually set yaw values
> 
> - camera and lens tab: degrees of view is set to 135
> - change it to 75 -> focal length is set to ~22.5
> - preview looks better now
(Continue reading)

Permalink | Reply | 1 comment |
headers
Frank Gevaerts | 1 May 2007 14:38
Picon

Re: Problems with creating 360° panorama

On Tue, May 01, 2007 at 02:05:38PM +0200, Lars Monsees wrote:
> 
> Hello,
> 
> I´ve uploaded the project and images to:
> http://www.hansenet.de/~larsen/test.zip
> 
> 
> I´ve read several tutorials but can´t figure out what I´m doing wrong
> here. What makes me wonder is that the control points are perfect but
> the ordering (yaw) of the images gets mixed up. Also, the values for
> pitch and roll when optimized are totally mixed up.
> 
> Is the scenery too complex? What am I doing wrong?

Hi,

I had a quick look, and I managed to get a reasonable panorama out of
it. Here's what I did:

- Since you said it was handheld, I didn't trust the control points near
  the bottom (because of potential parallax problems), so I removed
  those. After seeing the end result this was probably not necessary
- I added some horizontal lines
- I set the fov to 75 like you suggested, and then optimized for
  position only, then for position and view, and finally for position,
  view and barrel.

In the end I got the attached result.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bernard Lang | 1 May 2007 16:36

Re: Perspective correction of photos of flat surfaces


* Daniel M. German <dmg <at> uvic.ca>, le 30-04-07, a écrit:

>  Bernard> Sorry if my knowledge is spotty.  I understand that
>  Bernard> rectilinear is one type of azimuthal projection. Now all
>  Bernard> azimuthal projections are onto a tangential plane, and the
>  Bernard> idea of perspective correction applies to all since it
>  Bernard> means making a given plane of the picture parallel to this
>  Bernard> tangential plane (or the converse, whatever :-).  This is
>  Bernard> indeed independant of the way the actual projection is
>  Bernard> actually performed ... so you are right : it applies to
>  Bernard> all azimuthal projections [sorry for going into so many
>  Bernard> details ; these details are mainly to check my own
>  Bernard> understanding of your statement].

> The way I see it an oblique line will pass through the center of
> projection. So if you define 2 of them, their intersection will
> precisely define the center of projection. 

I am lost  ... are we talking about the same thing ?

I mean by "oblique line" a line that is neither horizontal nor
vertical.  Is it the wrong word (I am not a native English speaker) ?
What is your meaning ?

and I am referring to straight lines in the 3d world (which are also
straight lines in the projection plane in the rectilinear case). There
is no reason why they should be constrained to pass through any point.

If another azimuthal projection is used (other than rectilinear),
(Continue reading)

Permalink | Reply | 2 comments |
headers
dmg | 1 May 2007 17:22
Picon
Picon
Favicon

Re: Perspective correction of photos of flat surfaces


 Bernard Lang twisted the bytes to say:

 Bernard> I am lost  ... are we talking about the same thing ?

I guess not :)

 Bernard> I mean by "oblique line" a line that is neither horizontal nor
 Bernard> vertical.  Is it the wrong word (I am not a native English speaker) ?
 Bernard> What is your meaning ?

A straight line that crosses the center of projection.

Now I see your point. An "oblique line" is only defined in perspective
projection. It is meaningless in any other one. I think there is
already a "straight line" control point in hugin, but I might be
wrong. 

 Bernard> What do you mean by "center of projection" ?  (sorry for my ignorance)
 Bernard> Is it the point where the projection plane touches the sphere,
 Bernard> i.e. the orthogonal projection of the aperture point on the projection
 Bernard> plane ?

If the projection is azimuthal, it is the point where the projection
plane touches the sphere. It can be roughtly defined as the center of
the projected image. It is the point where you expect the viewer to be
in front.

In the cylindricals the center of projection is a line, usually
matchin the horizon.
(Continue reading)

Permalink | Reply | 1 comment |
headers
immauss@gmail.com | 1 May 2007 22:00
Picon

Re: Can Hugin be automated?


I'm not sure if its what you are looking for, but take a look at this;

http://wiki.osphoto.org/index.php/Multi-threading_with_autopano-sift

Its a simple bash script that I wrote mainly to fully utilize my dual
processor rig with autopano-sift. However, it also generates the PTO
file, and starts hugin at the end, so I don't go through the
repetitive process of loading in all the files as you describe, I only
enter the lens parameters once when hugin first loads the pto.
However, now that you mention it, it should be possible to use
exiftool to transfer the lens parameters from the raw files to the
tiff files and eliminate that problem.

exiftool -TagsFromFile p1070208.raw p1070208.tif  seems to work
great.

Scott

On Apr 30, 10:16 pm, Bruno Postle <b... <at> postle.net> wrote:
> On Sat 28-Apr-2007 at 13:28 -0700, Tom Brown wrote:
>
>
>
> > Since my Hugin input is so repetitive, it would be wonderful if it
> > could be automated.  Is there a mechanism that will allow this?
>
> Not really, there was a summer of code proposal to add batch
> processing to hugin, but it wasn't one of the ones selected:
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane