[hugin-ptx] Re: Celeste missing in SVN 4450 (Windows)
I mean the latest from Ad. Until I'm 100% up and running with the compile, that install kit is still what is generating panos on my machine. On Sun, Oct 25, 2009 at 4:34 PM, Yuval Levy wrote: > > you mean you built yourself, from SVN? is there a celeste.model > somewhere in the INSTALL\FILES\ folder? > > Yuv > > Nicolas Pelletier wrote: > > I can confirm I have the problem with the latest alpha build. > > > > On Sun, Oct 25, 2009 at 12:05 PM, Yuval Levy wrote: > > > >> J. Schneider wrote: > and indeed it is likely an installer issue. > >>> OK, so it's not worth filing an "official" bug. Hope Ad has read this > >>> thread. > >> I'm looking at the files in my Windows partition (from Linux) and I see > >> that the build process put celeste.model where I would expect it, in > >> hugin/data/celeste.model. > >> > >> Then I look at the most recent installer source file that Allard > >> committed a few weeks ago and as far as I can read (I can not test > >> because I am not in Windows) it looks correct to me. > >> > >> From your comment I infer that you are using one of Ad's unofficial > >> snapshots? > >> > >> 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste missing in SVN 4450 (Windows)
> From your comment I infer that you are using one of Ad's unofficial > snapshots? Ad's 2009.2.4450, his latest. 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: 2009.4.0 RC2 'clean control points' produces crook (bad) result
On Sat 24-Oct-2009 at 22:44 -0400, Roger Goodman wrote: > > If the 'clean control points' button _always_ causes problems if > two (or more) lenses are selected, how about a small chunk of code > that disables the button if two or more lenses are > selected/entered? Just to clarify things, the multiple lens case seems to be fine, or at least is handled properly by cpclean. It is still possible that cpclean deletes too many or too few points and needs more tuning, but it does seem to behave as expected. -- 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste missing in SVN 4450 (Windows)
you mean you built yourself, from SVN? is there a celeste.model somewhere in the INSTALL\FILES\ folder? Yuv Nicolas Pelletier wrote: > I can confirm I have the problem with the latest alpha build. > > On Sun, Oct 25, 2009 at 12:05 PM, Yuval Levy wrote: > >> J. Schneider wrote: and indeed it is likely an installer issue. >>> OK, so it's not worth filing an "official" bug. Hope Ad has read this >>> thread. >> I'm looking at the files in my Windows partition (from Linux) and I see >> that the build process put celeste.model where I would expect it, in >> hugin/data/celeste.model. >> >> Then I look at the most recent installer source file that Allard >> committed a few weeks ago and as far as I can read (I can not test >> because I am not in Windows) it looks correct to me. >> >> From your comment I infer that you are using one of Ad's unofficial >> snapshots? >> >> 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Hugin 2009.4.0 (and earlier) CP gen. interface question
2009/10/25 Nicolas Pelletier
> I don't know exactly the difference, but would expect that it is related to
> the way the output is done.
>
> This being said, here is what is configured in the latest builds for what
> you mentioned
>
> Panomatic: autopano-sift
> match n shift: autopano-sift
> align image stack: autopano-sift
>
autopano-sift-c: autopano-sift
>
> hope this helps
>
>
>
Nicolas is right.
To explain my probable cryptic addition. The original and still existing
autopano-sift is a mono (.net in windows) "executable" which was a
cross-platform "semi-compiled" program. autopano-sift-c is a complete
C/C++-remake of the relatively slow autopano-sift.
> On Sun, Oct 25, 2009 at 3:37 AM, Andreas Metzler <
> ametz...@downhill.at.eu.org> wrote:
>
>>
>> [Edit] allows to customize to specific program invokations. That is
>> were the magic switch is: What does the "Autopano-SIFT / Autopano by A
>> Jenny" choice do? How should it be set for the non-obvious choices
>> (panoramic, match-n-shift, align image stack)?
>>
>>
And next to that: the mentioned autopano is a (by now) somewhat older
program and only available for/on windows. You can use it on on Linux and
OSX if your run a windows version of hugin and autopano via wine.
It has already been suggested several times to remove the option from hugin
to reduce confusion, but there is still a number of devoted windows users
that use autopano.
A better suggestion might be to make it a "conditional compilation" step
like: If Windows { display autopano as option} else {don't display}
This shouldn't be too difficult for a programmer.
Harry
--~--~-~--~~~---~--~~
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
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---
[hugin-ptx] Re: Hugin 2009.4.0 (and earlier) CP gen. interface question
I don't know exactly the difference, but would expect that it is related to the way the output is done. This being said, here is what is configured in the latest builds for what you mentioned Panomatic: autopano-sift match n shift: autopano-sift align image stack: autopano-sift hope this helps On Sun, Oct 25, 2009 at 3:37 AM, Andreas Metzler < ametz...@downhill.at.eu.org> wrote: > > Hello, > > the cp-detector preferences are strangly structured: There is the main > dialogue, offering a choice of cp detectors. > > [Edit] allows to customize to specific program invokations. That is > were the magic switch is: What does the "Autopano-SIFT / Autopano by A > Jenny" choice do? How should it be set for the non-obvious choices > (panoramic, match-n-shift, align image stack)? > > I have been wondering about this since at last 0.8 but have never > bothered to ask. ;-) > > cu andreas > -- > `What a good friend you are to him, Dr. Maturin. His other friends are > so grateful to you.' > `I sew his ears on from time to time, sure' > > > > > --~--~-~--~~~---~--~~ 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Exif Information. Automatic Computing
If the information is not in the EXIF, then it is not provided to the software, and it has to "guess" or optimize to what seems the best value. Typical algorithms are very good at finding those values (both Hugin and Autopano according to your results). I've not played with autopano, but I can tell that hugin can figure out what lens you used (Field of View and focal length). The way it will do so is by starting with a value that may not be exact, and converge to the best value it can. With hugin, you must give it a starting value (even quite imprecise) and it will figure out the values. I remember one time I shot a pano and gave hugin the information from the wrong lens. After optimization, it had changed everything back to what it should. My recommendation, put what you think and let hugin figure out the details! When you optimize, FOV may not be checked as something that can be changed, so if it does not work, go on the optimizer tab to see if FOV is indeed checked. nick On Sun, Oct 25, 2009 at 4:47 AM, villa wrote: > > Hi all > > I've been evaluating several programs for mosaic generation, one of > them is free (hugin) while the other is commercial (Autopano Pro). > Both are very good but the Autopano Pro has a feature that I find very > interesting but I don't really know how it works. > > When you upload photos to "hugin" if the photos don't have EXIF > information you need to include the hfov and the focal length to > continue the process, but the Autopano Pro if the photos don't have > EXIF information it seems that somehow calculates the hfov and the > focal length. > > This information autopano computes is provided subsequently to hugin > and this program works perfectly, therefore the values are correct. > > My question is if there a technique or algorithm that allows to obtain > this information if not included in the EXIF > > Best regards. > > > > --~--~-~--~~~---~--~~ 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste missing in SVN 4450 (Windows)
I can confirm I have the problem with the latest alpha build. On Sun, Oct 25, 2009 at 12:05 PM, Yuval Levy wrote: > > J. Schneider wrote: > >> and indeed it is likely an installer issue. > > OK, so it's not worth filing an "official" bug. Hope Ad has read this > > thread. > > I'm looking at the files in my Windows partition (from Linux) and I see > that the build process put celeste.model where I would expect it, in > hugin/data/celeste.model. > > Then I look at the most recent installer source file that Allard > committed a few weeks ago and as far as I can read (I can not test > because I am not in Windows) it looks correct to me. > > From your comment I infer that you are using one of Ad's unofficial > snapshots? > > 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Celeste missing in SVN 4450 (Windows)
J. Schneider wrote: >> and indeed it is likely an installer issue. > OK, so it's not worth filing an "official" bug. Hope Ad has read this > thread. I'm looking at the files in my Windows partition (from Linux) and I see that the build process put celeste.model where I would expect it, in hugin/data/celeste.model. Then I look at the most recent installer source file that Allard committed a few weeks ago and as far as I can read (I can not test because I am not in Windows) it looks correct to me. From your comment I infer that you are using one of Ad's unofficial snapshots? 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: 2009.4.0 RC2 'clean control points' produces crook (bad) result
Yuval, If the 'clean control points' button _always_ causes problems if two (or more) lenses are selected, how about a small chunk of code that disables the button if two or more lenses are selected/entered? I'm not a coder, so I can't help with that, but it seems like it would be a simple change. Roger Goodman Yuval Levy wrote: > Hi Terry, > > Tduell wrote: > >> I did provide files showing the problem as I saw it >> > > I had to look for the files. It was not immediately obvious to me that > they are in the GoogleGroup's files area. And when I opened them I saw > what you saw, but I did not see what is needed to reproduce and > understand the error. > > > >> I really didn't know >> what info it was best to provide, and in those cases I try to report >> it as best I can and then respond to specific requests for files/data. >> > > When in doubt always post at least the PTO file. It's small and gives > plenty of useful info. > > From my perspective there are a lot of things that need to be done on > Hugin. More than anybody here has time to spare. When I engage in > something Hugin, I have my list of priorities. To request extra > information/files/data is usually very low on my priority list. Either > it is something important to more than one users, and somebody at some > point will provide them; or it is important enough for the only user > concerned and he will provide them. For me it is extra work. I much > rather get to the bug tracker, fetch a bug with all the required > information and elements from there, and fix it. > > > >> I am reluctant to post bug reports until I'm sure that it isn't really >> the result of the way I have done things or due to my system >> > > It's a tradeoff. I appreciate your consideration. On the other hand, if > you want to be heard you need to come forward. > > > >> [snip] >> >> >>> even if it was, I would not call it a step backward but rather a step on >>> the place. It would be a step backward if 'clean control points' was >>> mandated. It is not. You can safely ignore the button and ont press it. >>> To me it is helpful. I don't have cases at hand with different lenses. >>> It may very well be that it is not helpful in cases where different >>> lenses are used. >>> >> But the button is there, and if the ordinary user selects it and the >> project goes haywire, I isn't very helpful. >> > > I disagree. An ordinary user can send the project haywire by pushing all > sorts of buttons - e.g. by clicking randomly left and right on the CP > tab (and creating wrong CPs). That's no reason to judge the button or to > remove it. > > Turn it around: it isn't very helpful if a user hit a buttons without > understanding the consequences; and it isn't very helpful to withhold a > functionality from all users because of a few cases. > > > >> I would think that it a definite backward step if an option that >> wasn't previously available causes a problem. >> > > *IF* the option was *always* causing a problem, I'd agree with you. This > is not the case here. > > If the option is beneficial to some cases and detrimental to others > (like it may be in this case where it is beneficial to single lens > projects and detrimental to multiple lenses projects), we'd have to > ponder. What is the relative importance of each use case? And what are > the workarounds / alternatives? > > I dare to say that the vast majority of use cases are single lens > project that do benefit from cpclean. > > And since cpclean is not hard coded in the workflow, it can be disabled > for multiple lenses project with no consequences and with little effort > (it's a preference, in case you use the assistant; and it's no extra > effort at all in case you use the "normal" workflow). > > So I am pondering between: a material improvement for the vast majority > of use cases and a minimum effort workaround to keep the current level > of quality for the exceptional multi-lens case vs. no improvement for > anybody. > > My decision here is clear: it can be released as-is with a release note > stating that cpclean may be detrimental for a few use cases, notably > multiple-lens projects. > > If the proportion of users and projects affected would be > 10%, I would > consider changing the default for cpclean after automatic alignment from > ON to OFF. > > If the proportion of users and projects affected would be > 50% I would > start thinking about other things; but even then, just changing the > default preferences would be enough IMO. > > At > 75% I'd take the feature out from the release and wait for a bug fix. > > 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 t
[hugin-ptx] Exif Information. Automatic Computing
Hi all I've been evaluating several programs for mosaic generation, one of them is free (hugin) while the other is commercial (Autopano Pro). Both are very good but the Autopano Pro has a feature that I find very interesting but I don't really know how it works. When you upload photos to "hugin" if the photos don't have EXIF information you need to include the hfov and the focal length to continue the process, but the Autopano Pro if the photos don't have EXIF information it seems that somehow calculates the hfov and the focal length. This information autopano computes is provided subsequently to hugin and this program works perfectly, therefore the values are correct. My question is if there a technique or algorithm that allows to obtain this information if not included in the EXIF Best regards. --~--~-~--~~~---~--~~ 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Celeste missing in SVN 4450 (Windows)
> actually it is the celeste model that is expected there, (That's what I meant.) > and indeed it is likely an installer issue. OK, so it's not worth filing an "official" bug. Hope Ad has read this thread. 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Hugin 2009.4.0 (and earlier) CP gen. interface question
Hello, the cp-detector preferences are strangly structured: There is the main dialogue, offering a choice of cp detectors. [Edit] allows to customize to specific program invokations. That is were the magic switch is: What does the "Autopano-SIFT / Autopano by A Jenny" choice do? How should it be set for the non-obvious choices (panoramic, match-n-shift, align image stack)? I have been wondering about this since at last 0.8 but have never bothered to ask. ;-) cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --~--~-~--~~~---~--~~ 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 hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
