[hugin-ptx] Re: Lens Distrortion Params in EXIF

[icysubdweller]

> Because Olympus hasn't released any public documentation on how
> to use those parameters. Without that knowledge the "parameters"
> are just a bunch of useless random numbers, there's no way to
> convert them to Hugin-style correction coefficients.

This is the main point, I believe... no-one knows what Olympus uses
those numbers for.  They call it lens distortion, but it's actually
*unlikely* to be even related to the a, b, c, d, e parameters that
hugin uses.  These values could be sub-pixel shifts for correcting
chromatic distortion, or they could be one side of the coefficients
for a sharpness filter, or who knows?  It's just some set of numbers
that some young engineer at Olympus called "lens distortion."  It's
even possible that "lens distortion" is a mistranslation from another
language of something that wasn't originally called lens distortion at
all.

I have a different model Olympus camera, and the EXIF tags that get
stored are extensive, but they do not include a single field with the
word distortion in them.  So it would seem that these lens distortion
parameters are something specific to that model of camera... or more
likely, to the image processing hardware in that family of cameras.

-Rodnney



On Oct 30, 9:57 am, Markku Kolkka <[EMAIL PROTECTED]> wrote:
> 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 parameters. Without that knowledge the "parameters"
> are just a bunch of useless random numbers, there's no way to
> convert them to Hugin-style correction coefficients.
>
> > And - much more important question - wouldn't be nice, if
> > Hugin could use them?
>
> Yes, but it requires co-operation from camera manufacturers.
>
> --
>  Markku Kolkka
> [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Panorama in flash, which tool?

[Tim Nugent]

found a closed source flash player, it's about 40 euros. seems to be XML 
based too

http://flashpanoramas.com/player/

here it is in action, looks good:

http://www.gillesvidal.com/blogpano/cockpit1.htm


Alfredo Lingoist Jr. wrote:
> 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 
> *rev_128_example\images* folder
>  
> 4 • Edit "PanoSalado.xml" (in *rev_128_example* folder)
>  You  may found some tips in "XML Schema.txt" (in *rev_128 *folder)
>  * It's a pity PanoSalado does not have user interface...
>  
> 5 • Ready to be used! *NO NEW COMPILATION IS NEEDED*
> Alfredo
> Brasília - Brazil
> 
> 
> 2008/10/30 Bruno Postle <[EMAIL PROTECTED] >
> 
> 
> 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 hugin users want to do flash panoramas with
> panosalado - Could you post some notes to the list?  Just saying:
> what to download, which files to copy, bits you need to edit etc...
> 
> --
> Bruno
> 
> 
> 
> > 

--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Lens Distrortion Params in EXIF

[paul womack]

Jaroslav.Beran wrote:
> Hi, Klaus,
> 
> as you can see from my post, lens distortion parameters vary with
> focal length. There is a high possibility, that they also vary with
> each camera of the same model. But - if they vary with focal length,
> it seems to me, that they are calculated by the camera during the
> shoot.
> 
> But that was not the point of my questions/suggestions. I'm just
> curious, why these parameters are not used directly by Hugin. Why do I
> have to difficultly determine lens distortion parameters myself, when
> camera does it for me?
> 
> I'm not questioning, how much control points do we have to use - the
> more control points, the better...
> 
> Anyway - how about other cameras? Do they also save lens distortion
> parameters in EXIF?
> And - much more important question - wouldn't be nice, if Hugin could
> use them?

If Hugin can evaluate them more accurately than EXIF can supply
them, why on earth would I want Hugin to use the EXIF values?

   BugBear

--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: mac build: not yet, still having problems

[Harry van der Wolf]

Hi Steve,

Thanks for replying. You can get the up-to-date code from the hugin svn:
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk hugin>.

My modified XCode project is not in SVN yet as that svn XCode project is
working for 0.7. I might overwrite it as that 0.7 doesn't work anyway
anymore. I could also mail you the XCode project.
I have the issue as mentioned in my previous post, that is with celeste and
new "stuff" from gsoc 2008, but without PTBatcher and PTBatcherGui.
PTBatcher and PTBatcherGui really want to run wx-config which is undesired
behaviour in an Xcode project (but can be implemented).
I made PTBatcher and PTBatcherGui my "second goal in life", but wanted to
get the Xcode project running with celeste to start with.

So, do you want me to mail the XCode project?

Harry

2008/10/31 stwf <[EMAIL PROTECTED]>

>
> 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 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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Lens Distrortion Params in EXIF

[stativ]

> I have found that lens parameters vary within the same camera model…
I had the same camera and I've exactly same numbers here, so I don't
think that lens distortion parameters vary. IMHO it only can only look
like they vary because this camera has as Jaroslav said connected zoom
and It shouldn't be possible to determine focal length with great
accuracy (then it would be possible to use some tables), so camera
possibly changes (and saves) lens distortion according to it's
internal and possibly more accurate data than it could be possible to
do on computer using only EXIF data.

Anyway, now I have Cannon EOS 400D which doesn't save this data (but
some other which can be used for some calculations like crop factor
etc.)

One more thing, I've found out that I can achieve best results with
Olympus using values from hugin ptlens database (http://
hugin.svn.sourceforge.net/viewvc/hugin/lensdb/trunk/db/ptlens.xml?
revision=77&view=markup). Look for olympus750 (It's exactly the same
as 765 only with different electronics). Just copy appropriate values
to hugin. But there is one major culprit: It only works for exact
focal length (and thus you'll probably use it only with lowest and
highest zoom). This process allowed me to create many panoramas which
can't be done with auto generation of lens parameters within hugin.

--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---