[hugin-ptx] Re: The math is perfect ...

Abrimaal is the difficulty to set control points if the GUI is bright and the image is dark.] @Abrimaal: Can Hugin’s GUI style be influenced by your operating system’s settings? Tschö, Torsten. -- Torsten Bronger -- A list of frequently asked questions is available at: http://wiki.panotool

[hugin-ptx] Re: incomplete lens correction model - it bites

rve in the Lensfun lens database that a and c are strongly damped. b (the only odd coefficient) mostly has the biggest absolute value. Tschö, Torsten. -- Torsten Bronger -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message becaus

[hugin-ptx] Re: incomplete lens correction model - it bites

ignetting in the lens, the reasoning > should work. How does the vignetting affect distortion? Tschö, Torsten. -- Torsten Bronger -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to th

[hugin-ptx] Re: incomplete lens correction model - it bites

Hallöchen! Gunter Königsmann writes: > Would that help with cellphone lenses that tend to have a > different scale in the top left corner than in the lower right > one? No. It is all about centrosymmetric aberrations here. Tschö, Torsten. -- Torsten Bronger -- A list of frequen

[hugin-ptx] Re: incomplete lens correction model - it bites

ters. FWIW, I once patched the Pano library to use the exponents 3, 5, and 7 for a, b, c. It did not help for the (albeit single) pano that I used for testing. This is not a proof, it was only discouragement for me to follow this path further. Tschö, Torsten. -- Torsten Bronger -- A list of freque

[hugin-ptx] Re: Lens correction with Hugin

had vertical lines? Tschö, Torsten. -- Torsten Bronger -- 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

[hugin-ptx] Re: Lens correction with Hugin

ion is whether your coefficients lead to a good-looking correction. Tschö, Torsten. -- Torsten Bronger -- 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

[hugin-ptx] Re: Lens correction with Hugin

Hallöchen! Torsten Bronger writes: > [...] > > To switch off the lines, see <https://www.screencast.com/t/HSWzBkoPB>. Sorry, http://permalink.gmane.org/gmane.comp.misc.ptx/35067 is the correct link. Tschö, Torsten. -- Torsten Bronger -- A list of frequently asked questions

[hugin-ptx] Re: Lens correction with Hugin

image on both sides as seen here - > https://www.screencast.com/t/RVRV1srhI2 To switch off the lines, see <https://www.screencast.com/t/HSWzBkoPB>. And, "horiz. Line" in this screenshot indicates that you are doing something wrong. It must be a "new line" instead (like &q

[hugin-ptx] Re: Printed image for stitch calibration

it itself. Thus, I don't think you get more accuracy than with far away structures, or with a least-parallax adapter. Moreover, you should know the stars quite well, otherwise, it is a tedious search. Tschö, Torsten. -- Torsten Bronger -- A list of frequently asked question

[hugin-ptx] Re: Distortion parameters "a, b, c" to "k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]]" (OpenCV)

exactly because you have scaling as one degree of freedom. This way, one coefficient (no matter which!) can be set to an arbitrary non-zero value. The conversion is not easy, though. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de -- A list of frequently

[hugin-ptx] Re: Distortion parameters "a, b, c" to "k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]]" (OpenCV)

to use only b in Hugin for calibration, take the different coordinate system into account (i.e. scaling factor to the power of 3), and take d!=1 into account by dividing the resulting k1 by (1-b)^3. (Beware that I haven't checked the calculation, and one can easily make mistakes in these things.)

[hugin-ptx] Re: Change distortion formula

Hallöchen! Bruno Postle writes: > On Mon 07-Dec-2015 at 11:14 +0100, Torsten Bronger wrote: >> >> I would like to model distortion with an alternative formula. >> Hugin's formula is described on >> <http://hugin.sourceforge.net/docs/manual/Lens_correction

[hugin-ptx] Change distortion formula

ere I need to change that. Can anybody help me with that? Thank you! Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because

[hugin-ptx] Re: fun with lensfun

Hallöchen! T. Modes writes: > Am Freitag, 20. Februar 2015 18:03:37 UTC+1 schrieb Torsten Bronger: > >> ... which was initiated after your removal of Lensfun from Hugin. >> So, the only "issue" you present is one you was not even affected >> by. > > *

[hugin-ptx] Re: fun with lensfun

Hallöchen! T. Modes writes: > Am Donnerstag, 19. Februar 2015 21:18:10 UTC+1 schrieb Torsten Bronger: > >> The lensfun library has a stable and well-documented API. If we >> make changes, we follow the established procedures of >> obsolescence. And even that has n

[hugin-ptx] Re: fun with lensfun

ssfully, and never have complained about lensfun being a moving target. So, for the sake of fairness to a fellow open source project, please do not post such discrediting and vague statements without evidence. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.

[hugin-ptx] Re: Lens database

rate own values -- they are a by-product of the first good pano that you do anyway. And then, you store them for later use. Besides, there are typically only few lenses and few focal lengths that you use for panos. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber

[hugin-ptx] Re: Lens database

n's database and can say that even for high-quality lenses, there is significant series deviation. Panorama stitching needs *much* more accuracy than single-image correction. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de

[hugin-ptx] Re: Hugin is purely and simply unusable for panorama stiching

one's responses to their post, which just furthers my belief > that they weren't looking for help at all. They were just > trolling. Maybe. But the rest of the thread contained so much well-disposed and constructive critisism that this doesn't matter anymore. Tschö, Torsten.

[hugin-ptx] Re: Hugin is purely and simply unusable for panorama stiching

"implement it yourself, it's open source". This leads to nowhere. A proper answer is disputing the argument per se, or pointing to lack of manpower. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de

[hugin-ptx] Re: How to switch off lines in control point editor

tand that my use case is exotic. Still, Hugin's settings dialog is not crowded, so maybe there's room for another checkbox ... ;-) Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot

[hugin-ptx] Re: How to switch of lines in crontrol point editor

> and I don't know of any way of switching off these lines. Well, the problem is that if you mark an edge in the image with control points, you quickly don't see the edge anymore because it is buried under these lines. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron.

[hugin-ptx] Re: More fit parameters worsen fit?

Hallöchen! Torsten Bronger writes: > Currently, I make the (for me) confusing observation that the > residual errors increase if I include the FOV into the fit. > Shouldn't more parameters *never* make the fit worse? I must correct this statement. The average distance between

[hugin-ptx] Re: How to switch of lines in crontrol point editor

Hallöchen! Terry Duell writes: > On Tue, 29 Apr 2014 04:21:16 +1000, Torsten Bronger > wrote: > >> Recent versions of Hugin draw thin black lines between the >> control point and its counterpart in the control point editor. >> How can I switch that off? > &

[hugin-ptx] More fit parameters worsen fit?

Hallöchen! Currently, I make the (for me) confusing observation that the residual errors increase if I include the FOV into the fit. Shouldn't more parameters *never* make the fit worse? After all, Hugin could just leave the FOV as it is, and the fit quality would be preserved. Tschö, Torste

Re: [hugin-ptx] How to switch of lines in crontrol point editor

Hallöchen! Terry Duell writes: > On Tue, 29 Apr 2014 04:21:16 +1000, Torsten Bronger > wrote: > >> Recent versions of Hugin draw thin black lines between the >> control point and its counterpart in the control point editor. >> How can I switch that off? > &

[hugin-ptx] How to switch of lines in crontrol point editor

Hallöchen! Recent versions of Hugin draw thin black lines between the control point and its counterpart in the control point editor. How can I switch that off? Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http

[hugin-ptx] Re: Wanted: Your distortion parameters

apparent focal length of the lens." Exactly about this we've had a discussion on this list this week. ;-) -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- A list of frequently asked questions

[hugin-ptx] Wanted: Your distortion parameters

you to load your old pto file again and re-do the optimisation with all these parameters fixed to zero. Thank you very much! Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- A lis

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

Hallöchen! Erik Krause writes: > Am 08.04.2014 20:32, schrieb Torsten Bronger: > >> I think this supports my view that Hugin's focal length, >> multiplied by (1-a-b-c), results in the real one. > > Why do you want to know the focal length that precise? In the Lensf

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

trol points yield focal length = 8.65 a = 0.02142 b = -0.0194 c = 0.02785 ==> real focal length = 8.39 I think this supports my view that Hugin's focal length, multiplied by (1-a-b-c), results in the real one. Tschö, Torsten. -- Torsten BrongerJabber ID: torst

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

Hallöchen! Erik Krause writes: > Am 03.04.2014 14:33, schrieb Torsten Bronger: > >> AFAIKS, everything is fine. Hugin's calculations are precise. >> The only issue is that Hugin defines a focal length different >> from the one that an optics textbook would d

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

that Hugin defines a focal length different from the one that an optics textbook would define, that's all. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- A list of frequ

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

n't see the advantage of the fixed point on the long image edge. In Lensfun, it often makes autoscaling (to get rid of black corners) unnecessary. But even this fails often enough. That said, I'm aware this all this cannot be changed anymore. So actually, I only need to know (*). T

[hugin-ptx] Re: Focal length and FOV badly defined in Hugin?

Hallöchen! Torsten Bronger writes: > If I understand the Hugin projection model correctly, the distance > of a pixel from the image centre r (in real-world coordinates), > depending of the angle of the incoming light ray with respect to > the optical axis, is > > r(alpha) = f *

[hugin-ptx] Focal length and FOV badly defined in Hugin?

think this is not written to the files anyway. I ask this because I care for the Lensfun project at the moment, and it inherits all the formulae from Hugin. With all their quirks. ;-) Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de

[hugin-ptx] Re: FOV and orientation

Hallöchen! Torsten Bronger writes: > Bruno Postle writes: > >> On 3 March 2014 10:25, Torsten Bronger wrote: >> >>> How is the FOV lens parameter in Hugin defined? Always the >>> horizontal axis, always the longer axis, always the shorter >>> axi

[hugin-ptx] Re: FOV and orientation

Hallöchen! Torsten Bronger writes: > Hallöchen! > > Bruno Postle writes: > >> On 3 March 2014 10:25, Torsten Bronger wrote: >> >>> How is the FOV lens parameter in Hugin defined? Always the >>> horizontal axis, always the longer axis, always the short

[hugin-ptx] Re: FOV and orientation

Hallöchen! Bruno Postle writes: > On 3 March 2014 10:25, Torsten Bronger wrote: > >> How is the FOV lens parameter in Hugin defined? Always the >> horizontal axis, always the longer axis, always the shorter axis? > > Always horizontal, this is inherited from the pan

[hugin-ptx] FOV and orientation

Hallöchen! How is the FOV lens parameter in Hugin defined? Always the horizontal axis, always the longer axis, always the shorter axis? Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com

[hugin-ptx] Re: Aspect ratio and coordinate system

Hallöchen! T. Modes writes: > Am Montag, 18. November 2013 09:22:30 UTC+1 schrieb Torsten Bronger: > > [...] > > [...] > In the documentation to both function it states > > The algorithm will look for a lens with crop factor not less than of given > camera, since the

[hugin-ptx] Re: Ordering of geometry transformation and anti-destortion

Hallöchen! Erik Krause writes: > Am 28.11.2013 16:00, schrieb Torsten Bronger: > >> This means that the anti-distortion polynomial does not apply to the >> original sensor image but the remapped one. > > Yes. The polynomial describes the deviation from the ideal fi

[hugin-ptx] Ordering of geometry transformation and anti-destortion

. This also means that if I want to have a *perfect* stereographic picture, Hugin needs to map to rectilinear, apply a, b, c, and map back to stereographic. This would be rather wasteful. Can anybody confirm or dispute this? Thank you! Bye, Torsten. -- Torsten BrongerJabber ID: torsten.bron

[hugin-ptx] Re: Aspect ratio and coordinate system

Hallöchen! Terry Duell writes: > On Mon, 18 Nov 2013 19:22:30 +1100, Torsten Bronger > > wrote: > >> We have a problem in the LensFun project that also affects Hugin. >> The coordinate system used for distortion and TCA correction is >> poorly designed >

[hugin-ptx] Aspect ratio and coordinate system

We have a problem in the LensFun project that also affects Hugin. The coordinate system used for distortion and TCA correction is poorly designed, namely, r=1 is half-height. By contrast for vignetting, r=1 is half-diagonal. This is much better. Why? Because the crop factor also refers to th

[hugin-ptx] Re: How to contribute lens file to lensfun?

unny enough, even this email address is only visible if you are logged-in. :-( Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- -- You received this message because you are subscribed

[hugin-ptx] Re: Small errors, Projection formula and Preview

enough that the enblend process cannot make them invisible, I can also see in fast preview. But as I already pointed out, I would never align this way. CP are the proper way to go. Correct CPs have unbeatable accuracy. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rw

[hugin-ptx] Re: Small errors, Projection formula and Preview

tter preview. I must admit that I did not understand this paragraph in your first post. Probably somebody else can help you with this. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com --

[hugin-ptx] Re: Small errors, Projection formula and Preview

t's why simply aligning in GIMP is not ok > for me :( I'm afraid I don't fully understand what you need. You can manually move single images relatively to others with the mouse or by entering values. Is this what you are looking for? Tschö, Torsten. -- Torsten Bronger

[hugin-ptx] Re: Small errors, Projection formula and Preview

point (2) gets worse when doing interiors. It can be a couple of mm, especially with large overlaps, so noticable mismatches in straight lines. Maybe one could try a rectilinear lens, but I'm not willing to do that. I just live with the mismatches. Tschö, Torsten. -- Torsten Bronger

[hugin-ptx] Re: Viewpoint correction (aka translation)

in a private mail as I don't have non-private pictures available right now. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- -- You received this message because you are subscr

[hugin-ptx] Re: Viewpoint correction (aka translation)

rs > > Translation is needed for something like this: > http://www.flickr.com/photos/36383814@N00/5830006193 I don't see any difference to my nadir method. The front of Bruno's buildings is my room floor. Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.

[hugin-ptx] Re: Viewpoint correction (aka translation)

Hallöchen! Torsten Bronger writes: > For the nadir image, my plan was to move the tripod 1 metre to the > side and take another picture downwards. The ground is a flat > surfac > In Hugin, I added control points (on the plane only) and included > X, Y, and Z of this last phot

[hugin-ptx] Viewpoint correction (aka translation)

age relatively to the other depending on the viewing direction of the panorama centre? Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- -- You received this message because you are subscribed

[hugin-ptx] "degrees of view" always for equidistant fisheye?

Why do the "degrees of view" in Hugin's "Camera and Lens" tab always refer to rectilinear or equidistant? I can choose stereographic, equisolid, orthographic ... I only see the FOV for the equidistant case. -- You received this message because you are subscribed to the Google Groups "Hugin an

[hugin-ptx] ANN: lens calibration tutorial

Hallöchen! At http://wilson.homeunix.com/lens_calibration_tutorial/ you find my new lens calibration tutorial. I release it together with a script program that simplifies the process heavily. Just copy the calibration shots in the proper directories and start the script. (Well, almost.) The

[hugin-ptx] Lens calibration GUI -- line detection

Hallöchen! I tested the "Hugin lens calibration GUI" for distortion calibration purposes. However, at least for my images, line detection hasn't worked well enough. I think the most valuable line is the one running from one end to the other (i.e. length 1.0) but it's almost impossible for the

[hugin-ptx] Calibrating lens vignetting

Hallöchen! I fiddled around with Hugin to generate vignetting calibration information, according to . It worked, but it was very tedious and difficult to check. Now, I know that it was inaccurate, too. I found a much better wa

Re: [hugin-ptx] lensfun vignetting correction using Hugin

Hallöchen! Bruno Postle writes: > On Wed 15-Aug-2012 at 20:40 +0200, Torsten Bronger wrote: > >> [...] >> >> I wrote a Python script that generates the makefiles and calls >> make for each picture triplett, and generates the XML code for >> lensfun in the en

Re: [hugin-ptx] lensfun vignetting correction using Hugin

Hallöchen! Bruno Postle writes: > On Wed 15-Aug-2012 at 20:40 +0200, Torsten Bronger wrote: > >> [...] >> >> I wrote a Python script that generates the makefiles and calls >> make for each picture triplett, and generates the XML code for >> lensfun in the en

[hugin-ptx] lensfun vignetting correction using Hugin

d. I suspect the --levels option of enblend can help me. If it does, which value do you recommend? I didn't quite understand the manpage. Thanks in advance! Tschö, Torsten. -- Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de o