a question to the developers: what is FDiff2D? I found it in plenty of
places in the code, googling for it does not bring anything and I don't
understand it.
Specifically: line 506 of hugin_base/panodata/SrcPanoImage.cpp
FDiff2D sensorSize;
what does this line do?
Yuv
On Wed 29-Oct-2008 at 13:08 -0700, Can-C. Dörtbudak wrote:
oh this was very easy. I've used the example. The only thing you
need is six cubic images and the PanoSalado.xml. In this file you
can adapt all paths to the pictures and remove or change the tour
points. That's all.
I'm sure lots of
Jaroslav.Beran kirjoitti viestissään (lähetysaika torstai, 30.
lokakuuta 2008):
But that was not the point of my questions/suggestions. I'm
just curious, why these parameters are not used directly by
Hugin.
Because Olympus hasn't released any public documentation on how
to use those
Klaus schrieb:
On 30 Oct, 14:52, Jaroslav.Beran [EMAIL PROTECTED] wrote:
At least with my cameras, there is only a finite number of zoom
positions. So I suspect a rather small lookup table.
PTLens works with lookup tables as well and it works fine.
Why do I have to difficultly determine lens
Here it is what I did:
1 • Download PanoSalado and its example
http://panosalado.googlecode.com/files/rev_128_example.zip
http://panosalado.googlecode.com/files/rev_128.zip
2 • Unzip rev_128_example.zip and rev_123.zip
3 • Copy panoramic pictures that you created in HUGIN in *
I've recently built a new PC and I'm having trouble creating control
points with Hugin on it (I'm using Version 0.7.0 (SVN 3465), on
Windows XP with a default installation (both Hugin XP)).
When autopano-sift-c uses more than 2GB of memory it instantly
crashes. When I create control points
Hi
I'd like to take a look. Is the hugin project checked in now? Is there
anywhere I can get the up to date code and try and recreate the
problem?
steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
hugin and
Hi, Klaus,
my camera has infinite number of zoom positions, as it has seamless
zoom from 6.3 to 63 mm (38 to 380 mm if we speak in terms of 35 mm
camera). So it seems to me, that there is no lookup table, but lens
distortion parameters are calculated.
Regards
Jaroslav
On 30 Říj, 16:27, Klaus
