On Nov 19, 2012 5:51 PM, alouest julien.schro...@gmail.com wrote:
I think I have a problem related to the interpolator, while using hugin
for remote sensing use, my result keep showing some crazy value in the
edges. Could that be the result of a bad interpolator?
Look at the intermediate
Am 19.11.2012 18:27, schrieb Carl von Einem:
btw here is some more information about interpolation and aliasing:
http://wiki.panotools.org/Interpolation
http://wiki.panotools.org/Aliasing
And here is Jim Watter's interpolator test page:
http://photocreations.ca/interpolator/index.html
As
There will be little difference between the best interpolators, but
here's a comparison of spline36 and nearest neighbour with nona (Hugin
V210.0.0):
http://www.johnhpanos.com/hugin-interps.jpg
John
On Apr 4, 4:39 pm, Lukáš Jirkovský l.jirkov...@gmail.com wrote:
On 2 April 2012 20:57,
On 6 April 2012 15:07, panostar j.hough...@ntlworld.com wrote:
There will be little difference between the best interpolators, but
here's a comparison of spline36 and nearest neighbour with nona (Hugin
V210.0.0):
http://www.johnhpanos.com/hugin-interps.jpg
John
That's what I would expect.
On 2 April 2012 20:57, swissgregi hag...@gmail.com wrote:
Thanks Lukas
Now i understand this.
But the problem is still the same.
I can change the interpolation of noa to whatever i want.
In the pto file the i parameter on the m line changes everstime (i0,
i6, i3 etc.)
But i never get any
Thanks Lukas
Now i understand this.
But the problem is still the same.
I can change the interpolation of noa to whatever i want.
In the pto file the i parameter on the m line changes everstime (i0,
i6, i3 etc.)
But i never get any differences between the output files.
Why? Is this a bug?
Gregor
