by the 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
n 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 because
d vignetting 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
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
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 frequently asked q
ines?
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 unsubscribe fro
estion 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
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 questio
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
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 questions is available
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 asked questions
gin 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.)
Tschö,
Torsten.
--
Tor
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_mode
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 you are subscrib
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 not been necessary so far.
LOL, from
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.
*You* marked the fov api as deprecated on 13.04.2014
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.de
or http://bronger-jmp.appspot.com
-- 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.rwth-aachen.de
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
or http://bronger
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.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
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.com
--
A list of frequently asked questions is available
, 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...@jabber.rwth-aachen.de
or http://bronger
Hallöchen!
Terry Duell writes:
On Tue, 29 Apr 2014 04:21:16 +1000, Torsten Bronger
bron...@physik.rwth-aachen.de 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?
I suspect that's
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 control
points
Hallöchen!
Terry Duell writes:
On Tue, 29 Apr 2014 04:21:16 +1000, Torsten Bronger
bron...@physik.rwth-aachen.de 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?
I suspect that's
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ö,
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
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 is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because
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 list of frequently asked
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 define, that's all.
Optics textbook
= 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: torsten.bron...@jabber.rwth-aachen.de
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 Lensfun project, we need the exact focal
. 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 (*).
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
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 frequently asked questions is available
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
or http://bronger
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 * (a*r^3 + b*r^2 +c*r + 1
Hallöchen!
Torsten Bronger writes:
Bruno Postle writes:
On 3 March 2014 10:25, Torsten Bronger torsten.bron...@gmail.com wrote:
How is the FOV lens parameter in Hugin defined? Always the
horizontal axis, always the longer axis, always the shorter
axis?
Always horizontal
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
Hallöchen!
Bruno Postle writes:
On 3 March 2014 10:25, Torsten Bronger torsten.bron...@gmail.com 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 panotools lens
Hallöchen!
Torsten Bronger writes:
Hallöchen!
Bruno Postle writes:
On 3 March 2014 10:25, Torsten Bronger torsten.bron...@gmail.com wrote:
How is the FOV lens parameter in Hugin defined? Always the
horizontal axis, always the longer axis, always the shorter
axis?
Always horizontal
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
cite
The algorithm will look for a lens with crop factor not less than of given
camera, since the mathematical models of the lens
.
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
Hallöchen!
Terry Duell writes:
On Mon, 18 Nov 2013 19:22:30 +1100, Torsten Bronger
torsten.bron...@gmail.com
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
[snip]
I haven't seen
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 to the Google Groups
Hugin and other
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 BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
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 BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
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
--
--
You received this message
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.rwth-aachen.de
* more accurate, the
moving around works now, too. I think this is a powerful tool for
the general nadir problem. Thank you!
Could you provide the pto file for testing?
I'll do so in a private mail as I don't have non-private pictures
available right now.
Tschö,
Torsten.
--
Torsten Bronger
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
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
surface.
In Hugin, I added control points (on the plane only) and included
X, Y, and Z of this last photograph
://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.rwth-aachen.de
or http://bronger
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 and
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
Hallöchen!
I fiddled around with Hugin to generate vignetting calibration information,
according to
http://lensfun.berlios.de/lens-calibration/lens-vignetting.html. It
worked, but it was very tedious and difficult to check. Now, I know that
it was inaccurate, too.
I found a much better way
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 end. This seems to work.
Great, I hope you
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 end. This seems to work.
Great, I hope you
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
or http://bronger-jmp.appspot.com
--
You received
58 matches
Mail list logo
