[hugin-ptx] Re: custom install package
On Jun 6, 5:24 pm, Yuv wrote: > There has not been a user-contributed 2010.0.0 build for Windows so far. as an aside note on this important and unresolved subject - the Luminance HDR project has taken the approach of charging a nominal charge of 15 EUR for a Windows binary - see http://qtpfsgui.sourceforge.net/ I think that Hugin should consider a similar approach and support a Windows builder with a "ransom" approach, which is not uncommon for GPL software: the builder quantifies in terms of $ the effort and resources. Then he builds the binary and makes it first available only to paying users. The money that the users pay is accounted toward the ransom. Once enough money has been collected to pay all the ransom, the binary is set free and made available through the usual download channel. Example: the builder states that it is a 2500$ effort to build and quality-test a Hugin 2010.0.0 Windows installer. We put up a link to his Paypal account on Hugin's home page, offering the Windows binary for 10$. The first 250 users who pay this way get their latest Hugin faster. Once there have been 250 paid downloads, we put his binary in the normal, free, download section of SourceForge. What do you, Windows users and builders, think? 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
Re: [hugin-ptx] Re: Why not ask for directions?
On Sun 06-Jun-2010 at 14:29 -0700, Yuv wrote: yes, the optimizer should look into the template and try to generate CPs only for images that are overlapping. If I am not mistaken Bruno has a perl tool for this in his PanoTools? Also in the current Hugin trunk, but better because Thomas Modes has added genuine overlap detection that calculates area of overlap. You can match a roughly prealigned project, either by starting with a template or by dragging the photos around in the preview first. Hugin will then only compare pairs of photos that overlap. -- 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
Re: [hugin-ptx] Why not ask for directions?
On Sun 06-Jun-2010 at 10:32 -0700, Tom Sharpless wrote: Would it really be so hard to add a 'shooting grid' that lets the photographer specify roughly the directions of the views? That would surely help avoid false control points on highly symmetric scenes, and more important, would save much of the CPU time now spent uselessly looking for control points in wrong places. Have you tried the 'multi-row panorama' option in the current Hugin trunk? This should do what you want (only match pairs of photos that are very likely to overlap), but with a real advantage that it doesn't require any hints about the number of rows or columns. -- 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] Implications of APSC args (crashes and more)
[Been away in some hard "Real Life" for quite a while... it's nice to be back!] Zoran's latest Windows build is looking really nice. However, the default APSC parameters really do cause some trouble. The following two issues are fixed by changing args to --maxdim 1600 --maxmatches %p %o %s 1) Wrong hfov causes non-spherical lens to be treated as spherical 2) If more than 122 images are loaded, the "Align" step immediately crashes FWIW, Pete -- 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: Why not ask for directions?
Hi Tom, On Jun 6, 1:32 pm, Tom Sharpless wrote: > Our stitchers still stubbornly refuse to ask for directions. actually it is our optimizers and that's not entirely true. I've had consistently better results by starting with a template that includes lens parameters and "standardized" image positions for my workflow. > Would it really be so hard to add a 'shooting grid' that lets the > photographer specify roughly the directions of the views? IMHO this could make sense as a help to create the template, but I think starting with a template can yield better results. > That would surely help avoid false control points on highly symmetric > scenes, and more important, would save much of the CPU time now spent > uselessly looking for control points in wrong places. yes, the optimizer should look into the template and try to generate CPs only for images that are overlapping. If I am not mistaken Bruno has a perl tool for this in his PanoTools? 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: custom install package
Hi Bill, good to see you in this group. Many people here use Nodal Ninja products. I hope you will keep us posted about your new products here in the future. On Jun 4, 8:22 pm, Nodal Ninja wrote: > As many of you know it was our pleasure to support the last two Google > Summer of Code events. Thank you very much - you've always had an open ear when I approached you for support. Very much appreciated. > We were given a Special Edition package for > distribution to those purchasing our product. I remember. I created that package about three years ago. > It was actually very > cool - had our logo and said "Special Edition - for distribution with > a Nodal Ninja only. customizing the logo is quite easy with any image editor. I don't recall exactly which image I customized - the Windows installer images and other files are in the source tree in /platforms/windows/installer and the application's splash screen image is in /src/hugin1/hugin/xrc/ data Just edit the image before running the installer compilation and it will work. the "Special Edition" text is also easy to add, both in the installer and in the application. I don't remember where I added it, but just running the old installer and looking at the old app should give a hint. > The old package (v 0.7.0.3242SVN-Yuv) no > longer installs because it's out of date. that's indeed a very old installer and it is better not to distribute it, but it should install without problems? As fas as I can recall, the specifics of that package were: 1. no control point detectors (because all CP detectors available back then were tainted by U.S. patent and you're U.S. based) 2. at that time there was a lot of instability in upstream dependencies, particularly Enblend and libpano. I recall building very specific versions of them, with patches that have since been applied, and testing them thoroughly for functionality and stability. the "Special Edition" notice is a nice way to brandmark those two things. The stability of the sources of both Enblend and libpano have improved in the meantime. And Hugin has made leap advancement since 0.7.0. We still don't have a patent-free control point detector, but work is in progress on that. In the meantime, in /platforms/windows/installer there is also the source to make an installer without autopano, derived from my original installer. I think the last person who improved it was Allard. As a U.S. based distributor you don't want to touch autopano. > Can anyone help in developing a new install package for us? Unfortunately I can't help you this time: I've been without a usable Windows box for about a year now and a Windows box is required to build that package. There is a user-contributed 2009.4.0 build for download at https://sourceforge.net/projects/hugin/files/hugin/hugin-2009.4/Hugin_2009-4-0_win32_setup.exe/download According to the release notes, it has no control point generator and could be OK for you to distribute. It will lack the cool-factor, and you will have to do some quality testing on it before including it in your CD - all things I did for you back then. Any user with a Windows box can do this. There has not been a user-contributed 2010.0.0 build for Windows so far. Theoretically any user a Windows box could follow the instructions in the panotools wiki at http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK but the instructions and the SDK are outdated. There have been repeated attempts at updating this, but so far they have all stucked at the discussion stage. Also, while following blindly instruction may yield an executable, this does not guarantee the quality of the resulting executable. It is preferable if an experienced and knowledgeable Windows user does this step. Unfortunately that user either does not exist or does not want to share his work. Good luck 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
RE: [hugin-ptx] Why not ask for directions?
A good point, something that we've all been yearning. Perhaps a bounty to help the process along? In regards to the joke, the problem really was, they failed to follow directions, rather than ask. Look it up. On a side note, I consider the joke a bit inappropriate. > Date: Sun, 6 Jun 2010 10:32:12 -0700 > Subject: [hugin-ptx] Why not ask for directions? > From: tksharpl...@gmail.com > To: hugin-ptx@googlegroups.com > > [Bible joke. Q: Why did the Jews wander in the desert for 40 years? A: > The men wouldn't ask for directions.] > > Our stitchers still stubbornly refuse to ask for directions. > > Would it really be so hard to add a 'shooting grid' that lets the > photographer specify roughly the directions of the views? > > That would surely help avoid false control points on highly symmetric > scenes, and more important, would save much of the CPU time now spent > uselessly looking for control points in wrong places. > When the number of views is large, that can be a very great deal of > CPU time indeed, as there is > a combinatorial explosion of possible image pairs. I suspect the > GigaPan stitcher already uses its knowledge of the shooting grid to > good avantage. > > But you certainly don't need a robot head to create a predictable > shooting pattern. The majority of panographers shoot systematically. > Don't they deserve to be rewarded with faster and more-often-correct > automatic alignments? > > Best, Tom > > -- > 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 _ Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2 -- 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 & parallelization
Hi Markku, Am 05.06.2010 13:40, schrieb markku.kol...@iki.fi: On 5 kesä, 09:33, Lukáš Jirkovský wrote: OpenMP isn't supported in the Express edition of VisualC++, you need at least the Professional version to use it: http://msdn.microsoft.com/en-us/library/hs24szh9%28VS.100%29.aspx This will cause problems for Windows users that want/need to compile Hugin. Not really, if OpenMP is not mandatory (Which should be easily possible). Users of the Express edition won't get parallel support though. As parallelizing with OpenMP is really so much easier than with explicit threads, I think the missing support in the free Microsoft compiler should not stop Linux or OSX users from using all their processor cores. ciao Pablo -- 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] Why not ask for directions?
[Bible joke. Q: Why did the Jews wander in the desert for 40 years? A: The men wouldn't ask for directions.] Our stitchers still stubbornly refuse to ask for directions. Would it really be so hard to add a 'shooting grid' that lets the photographer specify roughly the directions of the views? That would surely help avoid false control points on highly symmetric scenes, and more important, would save much of the CPU time now spent uselessly looking for control points in wrong places. When the number of views is large, that can be a very great deal of CPU time indeed, as there is a combinatorial explosion of possible image pairs. I suspect the GigaPan stitcher already uses its knowledge of the shooting grid to good avantage. But you certainly don't need a robot head to create a predictable shooting pattern. The majority of panographers shoot systematically. Don't they deserve to be rewarded with faster and more-often-correct automatic alignments? Best, Tom -- 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
