[hugin-ptx] Re: Olympus and EXIF
Yuval Levy twisted the bytes to say:
Yuval> Bruno Postle wrote:
>> If you add wx code to src/hugin_base then everything, even the
>> command-line tools, will get linked to wxwidgets.
Yuval> fear not - it would be *temporary* for verbose debugging only and would
Yuval> never make it even into SVN - or if it will it will be commented out
Yuval> with a notice for developers how to activate it when they need
verbosity
Yuval> for debug.
Yuval> the problem is that unlike Linux and OS X, Wincrap kills the console
Yuval> when a GUI app is started, so stderr output goes to the equivalent of
Yuval> /dev/nul. Tom directed us to a flag in MSVC when Tim started
introducing
Yuval> verbosity to debug the issue with Celeste in the Wincrap version of
Yuval> Hugin. I tried toying with that flag but it messed up compiling big
Yuval> time. Right now I am writing to a log file, with a method introduced by
Yuval> Tim to debug Celeste. Unfortunately, if Hugin hangs, the buffer does
not
Yuval> get flushed into the file and so the last bits of verbosity, which are
Yuval> the critical ones, are missing. Popping up alert windows gives
real-time
Yuval> immediate feedback and enable quick identification of the source of the
Yuval> problem.
How about flushing after each printf?
Panotools has a Print_Error function that can be reused in hugin. This
function can take any number of parameters. Its beauty is that it uses
a pointer to a function that can be used instead of writing to the
standard output.
static void (*g_printErrorFcn)(char* , va_list va) = NULL;
void PrintError(char*fmt, ...)
{
va_list ap;
va_start(ap, fmt);
if (g_printErrorFcn == NULL) {
PrintErrorIntern(fmt, ap);
} else {
(*g_printErrorFcn)(fmt, ap);
}
va_end(ap);
}
void PrintErrorIntern( char* fmt, va_list ap)
{
vprintf(fmt, ap);
fflush(stdout);
}
>> All this GUI stuff needs to be confined to src/hugin1. Currently
>> it is possible to build and install the command-line tools on a
>> system with no GUI libraries whatsoever (and I do this).
Yuval> Absolutely agreed. We should document these architectural choices
Yuval> somewhere. As these are my first steps into the depth of the code base,
Yuval> I find it an unintuitive nightmare just to locate where things are and
Yuval> understand why there were placed there.
Use the code above, and, at run time, define a function that uses
WX. Then assign it to g_printErrorFcn.
--
Daniel M. German "I still have to see a problem,
however complicated, which, when
you looked at it in the right way
Poul Anderson ->did not become still more complicated."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
--~--~-~--~~~---~--~~
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: hugin creating random panoramas
Date: Sat, 08 Nov 2008 23:56:49 +0100 From: "J. Schneider" <[EMAIL PROTECTED]> Bart.van.Andel schrieb: >> most of the time hugin forms the panoramas >> totally wrong and on the preview i get all kinds of shapes and circles >> and diagonals > ... > I've had a problem recently which kind of sounds like what you're > trying to explain, I think. In my case, there were very nice control > points between the right images, but also some between images which > aren't adjacent at all. This caused Hugin to screw up the alignment > completely. After removing these wrong matches, the problem was > solved. It took quite a lot of effort to remove all these CPs by hand > though. This is one possibility. Another one is that the hfov is not exact enough. If you entered 38mm this might be just rounded. So let hugin optimize for hfov, maybe it works then. I've had this case several times. My experience has been that using automatic control point generation for typical outdoor panoramas is all but useless -- it picks a fair number of seemingly random control points in the sky and clouds that at best aren't very well aligned and at worst are completely incorrect (from the wrong images). So I wind up having to go through the table and remove a significant fraction of the control points. I don't know what features it's seeing -- maybe sensor noise or something that just happens to match up in a few places? I'd rather see an assistant (or at least an option) with an interface more like Fotoxx -- drag and drop the images into rough alignment. This might speed up control point generation, since it would have to search much smaller regions of the images. Fotoxx itself has a lot of limitations; you have to place the images left to right (so it can really only do strip panoramas), and it doesn't offer nearly as much control as Hugin. But the interface makes it a lot easier to get started. -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gutenprint --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton --~--~-~--~~~---~--~~ 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: hugin creating random panoramas
Am Saturday, November 08, 2008 um 14:10 schrieb Bart.van.Andel: > After removing these wrong matches, the problem was > solved. It took quite a lot of effort to remove all these CPs by hand > though. The place to do that is the global control point table (F3). First sort by right image, then sort by left image. Now scroll down and compare image numbers. If it is a one row panorama any image n should have control points to n-1 and n+1 only. If it is a 360° one the last image should have points with the first one of course. Ususally there are few wrong points only, hence you might spot them in the "P CP" (private control point number) column, too. best regards -- Erik Krause Offenburger Str. 33 79108 Freiburg --~--~-~--~~~---~--~~ 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: hugin creating random panoramas
Bart.van.Andel schrieb: >> most of the time hugin forms the panoramas >> totally wrong and on the preview i get all kinds of shapes and circles >> and diagonals > ... > I've had a problem recently which kind of sounds like what you're > trying to explain, I think. In my case, there were very nice control > points between the right images, but also some between images which > aren't adjacent at all. This caused Hugin to screw up the alignment > completely. After removing these wrong matches, the problem was > solved. It took quite a lot of effort to remove all these CPs by hand > though. This is one possibility. Another one is that the hfov is not exact enough. If you entered 38mm this might be just rounded. So let hugin optimize for hfov, maybe it works then. I've had this case several times. 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: hugin creating random panoramas
> most of the time hugin forms the panoramas > totally wrong and on the preview i get all kinds of shapes and circles > and diagonals Could you explain this a bit more, by showing a screenshot for example? I've had a problem recently which kind of sounds like what you're trying to explain, I think. In my case, there were very nice control points between the right images, but also some between images which aren't adjacent at all. This caused Hugin to screw up the alignment completely. After removing these wrong matches, the problem was solved. It took quite a lot of effort to remove all these CPs by hand though. Feature idea: a graph showing which images are matched to which could be a nice idea, with an option to remove "edges" in the graph, to speed up the process of removing such wrong image match CPs quite a bit. --~--~-~--~~~---~--~~ 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] hugin creating random panoramas
hi guys, so need a little help with circular panoramas with hugin. i use a tripod with a pano head to make 18 shots that stitch together nicely with a few different pieces of software but hugin does blends them better and the colours are better. problem is it only occasionally works, when it does it works first time and perfectly, but most of the time hugin forms the panoramas totally wrong and on the preview i get all kinds of shapes and circles and diagonals even though i use the same technique each time and hugin finds all the control points automatically and very well. i use a pretty old digital camera and it doesnt auto feed lens data to the software but it should be 38mm equiv, regardless, sometimes it works sometimes not... any ideas? thanks in advance mark --~--~-~--~~~---~--~~ 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: perspective correction?
Am Saturday, November 08, 2008 um 11:08 schrieb Tom Sharpless: > It is probably easier to do this kind of correction with tools other > than hugin. Why that? There is an excellent tutorial doing this using hugin: http://hugin.sourceforge.net/tutorials/perspective/en.shtml Doesn't this work anymore with 0.7.0? If this really would be the case the tutorial should be removed... best regards -- Erik Krause Offenburger Str. 33 79108 Freiburg --~--~-~--~~~---~--~~ 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: perspective correction?
Hello Paul It is probably easier to do this kind of correction with tools other than hugin. Photoshop has 2D perspective correction as an option on its cropping tool. As you are on Linux, you don't use Photoshop, but I expect the Gimp has something similar. Basically you draw a stretched rectangle on the image and the program gives you a real rectangle containing that part of the image. Very easy when you have a picture of something rectangular. You can also correct perspective with PanoTools. This is a little more abstract as you have to specify angles of rotation of the original picture plane around its horizontal and vertical axes, but works just as well. I have only used the photoshop plugins (which I believe also work with the Gimp) for this, but one of the command line tools does it too. Regards, Tom On Nov 4, 5:23 am, paul womack <[EMAIL PROTECTED]> wrote: > I've tried to correct a photograph I took in a antique shop of > a pencil sketch. In order to avoid light flare, I had to take > the photo from an angle, and (hence) would now like > to correct the perspective. > > I've read and understood this page: > > http://wiki.panotools.org/Perspective_correction#Camera_panned.2C_til... > > but I can't make it work; when I go to preview, the image is centred, > but still perspective distorted. > > I have set two horizontal controls and two vertical controls, > (one control on each edge). > > I am optimising for (y,p,r). > > Once clue may be that one of the control points (a vertical one) > shows a major control point distance. I'd have thought that with so few > control point, optimisation should be perfect. > > I'm working in Hugin 0.7.0 of Fedora > > 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: Olympus and EXIF
Bruno Postle wrote: > If you add wx code to src/hugin_base then everything, even the > command-line tools, will get linked to wxwidgets. fear not - it would be *temporary* for verbose debugging only and would never make it even into SVN - or if it will it will be commented out with a notice for developers how to activate it when they need verbosity for debug. the problem is that unlike Linux and OS X, Wincrap kills the console when a GUI app is started, so stderr output goes to the equivalent of /dev/nul. Tom directed us to a flag in MSVC when Tim started introducing verbosity to debug the issue with Celeste in the Wincrap version of Hugin. I tried toying with that flag but it messed up compiling big time. Right now I am writing to a log file, with a method introduced by Tim to debug Celeste. Unfortunately, if Hugin hangs, the buffer does not get flushed into the file and so the last bits of verbosity, which are the critical ones, are missing. Popping up alert windows gives real-time immediate feedback and enable quick identification of the source of the problem. > All this GUI stuff needs to be confined to src/hugin1. Currently it > is possible to build and install the command-line tools on a system > with no GUI libraries whatsoever (and I do this). Absolutely agreed. We should document these architectural choices somewhere. As these are my first steps into the depth of the code base, I find it an unintuitive nightmare just to locate where things are and understand why there were placed there. 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: Olympus and EXIF
On Sat 08-Nov-2008 at 00:06 -0500, Yuval Levy wrote: > >I am still at loss why wx functions are available to code inside >src/hugin1/hugin and not to src/hugin_base/panodata - Daniel said that >it would require the WX flags to add wx functions to code inside >hugin_base and compile. If you add wx code to src/hugin_base then everything, even the command-line tools, will get linked to wxwidgets. All this GUI stuff needs to be confined to src/hugin1. Currently it is possible to build and install the command-line tools on a system with no GUI libraries whatsoever (and I do this). -- 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: Olympus and EXIF
Yuv,
To add WX functions follow what I did at the top of the celeste
CMakeList.txt file that I just committed.
Add link libraries too
TARGET_LINK_LIBRARIES(celeste huginbasewx ${wxWidgets_LIBRARIES})
Then some includes in the source
#include "panoinc_WX.h"
#include "base_wx/platform.h"
Managed to get exmessage boxes working from inside the celeste library by
doing this, so should work for you too.
And good work with the c++ :-)
Tim
2008/11/8 Yuval Levy <[EMAIL PROTECTED]>
>
> Hi all,
>
> just a notice to say that I am proud of my first feature contribution
> (or bugfix, depends how you see it).
>
> It has recently been discussed on this list that images from Olympus
> cameras are not recognized automatically and that the user is required
> to enter manually focal distance and crop factor.
>
> I investigated the issue. The problem is that Olympus camera don't
> provide Exif.Image.ImageWidth and Exif.Image.ImageLength values, so the
> sensor's diagonal can't be calculated, and the calculation of the crop
> factor depends on the sensor's diagonal.
>
> But Olympus has a proprietary tag to do the trick:
> Exif.Olympus.FocalPlaneDiagonal
>
> Finding this was relatively easy - thanks to Andreas Huggel, author of
> the Exiv2 library. Implementing this would have been a two minutes piece
> of cake for a seasoned developers, but I wanted to do it myself. Thank
> you Daniel M. German for coaching me through the process. I have learned
> a little bit of C++ and fixed the bug.
>
> I am still at loss why wx functions are available to code inside
> src/hugin1/hugin and not to src/hugin_base/panodata - Daniel said that
> it would require the WX flags to add wx functions to code inside
> hugin_base and compile.
>
> Any CMake/wxWidgets expert out there willing to help me understand?
>
> In the meantime, my fix for Olympus users is committed to trunk (SVN
> rev. 3533).
>
> 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: Olympus and EXIF
Harry van der Wolf wrote: > Two major achievements in less than 3 months: > - first becoming a full-time father. > - Now becoming a part-time C++ programmer. no offense intended, I would not put them on the same level ;-) but I am still a newbie at both, and trying to do my best. 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: Olympus and EXIF
Congratulations, Two major achievements in less than 3 months: - first becoming a full-time father. - Now becoming a part-time C++ programmer. :-) Hoi, Harry 2008/11/8 Yuval Levy <[EMAIL PROTECTED]> > > Hi all, > > just a notice to say that I am proud of my first feature contribution > (or bugfix, depends how you see it). > > It has recently been discussed on this list that images from Olympus > cameras are not recognized automatically and that the user is required > to enter manually focal distance and crop factor. > > I investigated the issue. The problem is that Olympus camera don't > provide Exif.Image.ImageWidth and Exif.Image.ImageLength values, so the > sensor's diagonal can't be calculated, and the calculation of the crop > factor depends on the sensor's diagonal. > > But Olympus has a proprietary tag to do the trick: > Exif.Olympus.FocalPlaneDiagonal > > Finding this was relatively easy - thanks to Andreas Huggel, author of > the Exiv2 library. Implementing this would have been a two minutes piece > of cake for a seasoned developers, but I wanted to do it myself. Thank > you Daniel M. German for coaching me through the process. I have learned > a little bit of C++ and fixed the bug. > > I am still at loss why wx functions are available to code inside > src/hugin1/hugin and not to src/hugin_base/panodata - Daniel said that > it would require the WX flags to add wx functions to code inside > hugin_base and compile. > > Any CMake/wxWidgets expert out there willing to help me understand? > > In the meantime, my fix for Olympus users is committed to trunk (SVN > rev. 3533). > > 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 -~--~~~~--~~--~--~---
