[hugin-ptx] FDiff2D
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 --~--~-~--~~~---~--~~ 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: FDiff2D
Yuv, It's a VIGRA class - a 2 dimensional difference vector. I presume the preceding F means it stores float values. http://kogs-www.informatik.uni-hamburg.de/~koethe/vigra/doc/vigra/classvigra_1_1Diff2D.html Tim Yuval Levy wrote: > 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 > > > > --~--~-~--~~~---~--~~ 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
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? Regards Jaroslav On 26 Říj, 13:50, Klaus <[EMAIL PROTECTED]> wrote: > Hello Jaroslav, > > While it is nice to have these values saved, I have found that lense > parameters vary within the same camera model. Hence I usually have > them optimised from the image data itself, which overall requires a > few more control points. > > Do you have an idea what mathematical model corresponds to these > coefficients? > > Regards > > Klaus --~--~-~--~~~---~--~~ 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
Hi Jaroslav, On 30 Oct, 14:52, "Jaroslav.Beran" <[EMAIL PROTECTED]> wrote: > as you can see from my post, lens distortion parameters vary with > focal length. Yepp. > There is a high possibility, that they also vary with each camera of the same > model. There I wonder, whether eaach camera is measured indeed and provided with its individual parameter set. Given the needs of mass production, I somewhat doubt it. > But - if they vary with focal length, it seems to me, that they are > calculated by the camera during the shoot. At least with my cameras, there is only a finite number of zoom positions. So I suspect a rather small lookup table. > But that was not the point of my questions/suggestions. I'm just > curious, why these parameters are not used directly by Hugin. Honestly, I cannot say why not. But I suspect reasons among the following: model for coefficients not documented, several different models, different model to the panotools framework, need to actually code and implement it. And most importantly: no big problem to determine the actual parameters from image data. Without the need to decode different EXIF entries with different models from different manufacturers. And it describes your individual lense. > Why do I have to difficultly determine lens distortion parameters myself, > when camera does it for me? I challenge the perception of "difficulty". Hugin does it for you, at the expense of marginally more control points. > 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? There is a research project for someone - and do they use the same mathematical framework? > And - much more important question - wouldn't be nice, if Hugin could use > them? My opinion is: while the hugin lense model has a mathematical shortcoming, it is still good enough to describe your lense distortions to subpixel accuracy. I doubt the additional benefit is worth the effort, but anyone who wants to tackle this particular aspect is free to write some code. Regards Klaus --~--~-~--~~~---~--~~ 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?
I've done this in the past just like you say. Here is an example (be patient, it's at home dsl connection) http://www.fotospanoramicas.org/esfericas/mirepoix/ Sergi On Oct 29, 9:08 pm, Can-C. Dörtbudak <[EMAIL PROTECTED]> wrote: > Hi Alfredo, > > 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. > > Can > > On 29 Okt., 13:39, "Alfredo Lingoist Jr." <[EMAIL PROTECTED]> > wrote: > > > Hi Can, > > > What haeve you done? Have you just changed the original pano-photo? > > > Thanks, > > Alfredo > > > 2008/10/29 Can-C. Dörtbudak <[EMAIL PROTECTED]> > > > > Hi Alfredo, > > > > same for me. That's why i've adapted the example. But i will ask for > > > help on their message board. > > > > Can > > > > On 29 Okt., 13:20, "Alfredo Lingoist Jr." <[EMAIL PROTECTED]> > > > wrote: > > > > I've been trying to compile PanoSalado for 2 days, but it does not work > > > at > > > > all. Does it have any user interface? > > > > > Thanks again, > > > > Alfredo Lingoist > > > > > 2008/10/28 Can-C. Dörtbudak <[EMAIL PROTECTED]> > > > > > > Hi Sergi, > > > > > > that's really cool! Thanks a lot. I could not figure out how to > > > > > compile it myself, but the example works very well. > > > > > > If you want to have a look: doertbudak.de/blog/ > > > > > > Thanks, Can > > > > > > On 28 Okt., 09:47, sergi34 <[EMAIL PROTECTED]> wrote: > > > > > > try this: panosalado. It's an open source solution for flash panos. > > > > > > > It accepts as input cubic panos in 6 cube faces, but I think it's > > > also > > > > > > implemented quicktime qtvr input, too. > > > > > > >http://flashpanos.com/blog/79 > > > > > > > Sergi > > > > > > > On Oct 27, 11:18 pm, Can-C. Dörtbudak <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > Hi Guys, > > > > > > > > is there a chance of building panoramas in flash with a tool like > > > the > > > > > > > very good Panotools-Script to get a qtvr? i'm running linux and > > > that's > > > > > > > why i would like to use flash. > > > > > > > > Cheers, Can --~--~-~--~~~---~--~~ 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?
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
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: Lens Distrortion Params in EXIF
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 distortion parameters myself, >> when camera does it for me? > I challenge the perception of "difficulty". Hugin does it for you, at > the expense of marginally more control points. It depends on the situation. If you have a set of images shot with a precise setup it is easy. If you shoot freehand (as I usually do) or you have a single image that you want to correct yo rely on given parameters. Or you have to have straight lines in that single image. So I think in an ideal case the result of hugins calculation will be superior to that of a lookup table that is not specific to this single camera - but the latter will be a lot better than nothing. So I would say it would be worth implementing - if you needn't do it with a different mathematical model for each vendor. I just wonder where the parameters stored in the exif data are used if they are not documented. Does some raw converter by Olympus feature automatic distortion correction? regards Joachim --~--~-~--~~~---~--~~ 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?
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] autopano-sift-c crashes when it uses more than 2GB of memory
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 using Hugin (same version) on another of my computers it has no problems whatsoever. Does anyone know how to fix this problem? p.s. If you need to know any system information, just say. --~--~-~--~~~---~--~~ 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
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
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 <[EMAIL PROTECTED]> wrote: > Hi Jaroslav, > > On 30 Oct, 14:52, "Jaroslav.Beran" <[EMAIL PROTECTED]> wrote:> as you can see > from my post, lens distortion parameters vary with > > focal length. > Yepp. > > There is a high possibility, that they also vary with each camera of the > > same model. > > There I wonder, whether eaach camera is measured indeed and provided > with its individual parameter set. Given the needs of mass production, > I somewhat doubt it.> But - if they vary with focal length, it seems to me, > that they are calculated by the camera during the shoot. > > At least with my cameras, there is only a finite number of zoom > positions. So I suspect a rather small lookup table. > > > But that was not the point of my questions/suggestions. I'm just > > curious, why these parameters are not used directly by Hugin. > > Honestly, I cannot say why not. But I suspect reasons among the > following: model for coefficients not documented, several different > models, different model to the panotools framework, need to actually > code and implement it. And most importantly: no big problem to > determine the actual parameters from image data. Without the need to > decode different EXIF entries with different models from different > manufacturers. And it describes your individual lense. > > > Why do I have to difficultly determine lens distortion parameters myself, > > when camera does it for me? > > I challenge the perception of "difficulty". Hugin does it for you, at > the expense of marginally more control points. > > > 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? > > There is a research project for someone - and do they use the same > mathematical framework? > > > And - much more important question - wouldn't be nice, if Hugin could use > > them? > > My opinion is: while the hugin lense model has a mathematical > shortcoming, it is still good enough to describe your lense > distortions to subpixel accuracy. I doubt the additional benefit is > worth the effort, but anyone who wants to tackle this particular > aspect is free to write some code. > > Regards > Klaus --~--~-~--~~~---~--~~ 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
Hi, Markku, so I'll try to get some info from Olympus - perhaps nobody tried before, so that's why we don't have any documentation or info on that. In the meantime I will try to find some corellation between those numbers in exif and Hugin. Regards Jaroslav On 30 Říj, 17:57, 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 -~--~~~~--~~--~--~---
