[hugin-ptx] Re: Looking for help fixing distortion in panoramic photos

On 29 jul, 22:29, "sani...@ymail.com" wrote: > Could you guys clarify for me what is causing the curving? What could > I do differently without adding seams to my image? As far as I can see from the tinypic image, the horizon isn't level. You can tell because the far ends of the building do not p

[hugin-ptx] Re: Hugin Mercurial Repo - Please Test and Help

Hey Yuv, Thanks for all your effort! I must say to me the HG web viewer looks a lot cleaner than the SVN web viewer. One interesting thing I noticed: the latest entry in the "changes" table shows "in the future convert-repo update tags default tip" Didn't know HG has supernatural powers :)

[hugin-ptx] Re: Using phone cameras and Hugin

On 24 apr, 11:14, aws357 wrote: > Google docs link to pictures I've taken. > > When I use a value of 37mm, hugins return me some funky results... I tried using Panomatic as the control point finder, and the result isn't that bad. I optimized Position, Translation, View, Barrel at once, and then s

[hugin-ptx] Re: (Patch-plugin practice) Enfuse and Enblend Gimp Plugins - Gsoc

Hi, I'm sorry, this is just for the crop/blur example. I missed your other file, which is definitely more impressive. Again, sorry. Best, Bart On 20 apr, 13:21, Bart van Andel wrote: > Hi, > > I don't want to sound rude, -- You received this message because you are subsc

[hugin-ptx] Re: (Patch-plugin practice) Enfuse and Enblend Gimp Plugins - Gsoc

Hi, I don't want to sound rude, but how exactly can we see your coding skills from these source files? From what I see: - You have successfully set up a build environment to build plugins for GIMP. - You can make a "hello world" plugin for GIMP, which is basically taken literally from [0] with onl

[hugin-ptx] Re: SVN repository conversion - Important for past contributors

Hi Yuv, Since sourceforge mail allows forwarding email to your own specified email address (I think this is the default when an email address has been supplied) I'm perfectly fine with the sourceforge.net address. In fact I prefer it this way, since it allows me to change the forward address whene

[hugin-ptx] Re: Simplest panohead ever? (was: Pano Head)

> I always like to keep things as simple as possible. My minimalist solution > might look childish but works great for my setup. This is brilliant! Simple is good! I *have* to find myself some second hand Meccano to build a similar setup :) -- Bart -- You received this message because you are s

[hugin-ptx] Re: triple me

Most obvious way: mask out the area you don't want from the images. With the most recent builds, you can do this very easily using the "Mask" tab. You can create "positive" masks (areas you want to see in the output, will automatically mask out the same area in other images) and "negative" masks (

[hugin-ptx] Re: GLpreview and projections

On 11 mrt, 16:45, Simon Oosthoek wrote: > Simon Oosthoek wrote: > > Bruno Postle wrote: > >> On Wed 10-Mar-2010 at 12:50 +0100, Simon Oosthoek wrote: > > >>> When I changed the projection, some projections altered the FoV in > >>> such a way that the output got totally distorted. Switching back to

[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01

On 7 mrt, 05:53, irv wrote: > Bart, this solved one problem with the wrapper.  Using zorin's svn > 5046 the tif opened 'up is up' but the PNG and jpg opened 'up is dn' > and the ruler in PSE7 only showed 0 for x-y. Opening and closing Image > & Resize (doing nothing else) recovered the full ruler.

[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01

to work. > > Can live with it and compress it later. > > The only strange thing is that a JPEG output is upside down. > > Have other people that experience too? > > > Kind regards > > Henk Tijdink > > > On 24 feb, 00:11, Bart van Andel wrote: > > >

[hugin-ptx] Re: Towards a non-patented control point detector

The name of Hugin itself comes from Norse mythology [0] (Huginn and Muninn [1], which stand for thought and memory respectively, are the ravens who tell Odin how the earth is doing). I think it may be a nice idea to steal another name there. So... what about Loki? According to its Wikipedia articl

[hugin-ptx] Re: Towards a non-patented control point detector

On 3 mrt, 00:03, Daniel Reetz wrote: > On Tue, Mar 2, 2010 at 6:04 AM, Bruno Postle > wrote: > > On 1 March 2010 18:36, Aron H wrote: > > >> perhaps 'daisy_geoblur' might be better. What do you think, Pablo? > > > 'daisy' is good, I like 'daisychain', 'daisypicker' or 'upsydaisy' > > (hmm, I'

[hugin-ptx] Re: hugin not compiling on Ubuntu 9.10

My guess: you haven't compiled or correctly installed a recent snapshot of libpano13 (you need a fairly recent one for current Hugin trunk, getting trunk probably won't hurt). The search function in this discussion group points to similar issues, just search for 'queryFOVLimits'. -- Bart On 1 mrt

[hugin-ptx] Re: Hugin 2010.1 svn5031 for download

> Please use 2.5.1 instead, which > I've uploaded to [0] for convenience [0] = http://www.sendspace.com/file/0mgb8o -- Bart -- 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 avai

[hugin-ptx] Re: Hugin 2010.1 svn5031 for download

I understand you include Autopano-SIFT-C version 2.5.2 23July2009 with your installer. This version is however known to be broken and should be discarded (or fixed of course). Please use 2.5.1 instead, which I've uploaded to [0] for convenience some time ago (I was never able to find it online myse

[hugin-ptx] Re: Hugin 2010.1 svn5031: autopano-sift-c finds VERY few keypoints

Autopano-SIFT-C 2.5.2 23July2009 is known to be broken and should not be used or included in the installer. You need to use 2.5.1 instead, which I've recently uploaded for convenience [0]. In the output you included in your message it says "hfov 180", but this can't be correct if I examine your exa

[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01

Whoops, I had mixed up two versions of the batch file on my harddrive and uploaded the wrong one (which was still an update, but incomplete), fixed that. Sorry Bruno, you'll need to merge again I guess... -- Bart On 23 feb, 23:30, Bart van Andel wrote: > I just committed a new versio

[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01

I just committed a new version, which can be found at [0]. Tested with Hugin 2009.04 official build, but it should be version independent. It will work with Hugin as long as Hugin does not the command line arguments currently supplied to enblend/smartblend. The wrapper currently strips -f and --com

[hugin-ptx] Re: Smartblend wrapper and Hugin 0.8 and upward till Hugin 2010.01

No you're not doing anything wrong. The Smartblend wrapper actually throws away most command line options (like compression) since Smartblend does not understand these options. The output does not contain EXIF information because this needs to be copied from one of the source images into the blende

[hugin-ptx] Re: Masking inside hugin

On 16 feb, 09:35, Bruno Postle wrote: > http://www.flickr.com/photos/36383...@n00/4359863335/ This will save a lot of work: instead of first outputting all the remapped images, editing masks by hand using a photo editor like GIMP or Photoshop, and then blending, everything can now be done from in

[hugin-ptx] Re: Hugin 2009.4.0 Win XP autopano-sift-c 2.5.2 bug

rote: > Thanks I get version 2.5.1 for hugin 0.7. > Now how do I tell which version of hugin I have? > Nathan > > > > Bart van Andel wrote: > > By opening a command prompt, and executing autopano using its full > > path, e.g. > > >   C:\apps\graphics\pano\

[hugin-ptx] Re: Hugin 2009.4.0 Win XP autopano-sift-c 2.5.2 bug

on my computer? > Nathan > > > > Bart van Andel wrote: > > For convenience, I've uploaded a Windows binary of Autopano-SIFT-C > > version 2.5.1 to Sendspace [0], because I had trouble finding it > > anywhere but on my computer. I know some (older) installers

[hugin-ptx] Re: Hugin 2009.4.0 Win XP autopano-sift-c 2.5.2 bug

Bart On 3 feb, 16:31, Bart van Andel wrote: > Autopano-SIFT-C 2.5.2 23July2009 is known to be broken. Please try > again with 2.5.1. There have been numerous reports on this list > already, but I admit, the search function *within* groups.google.com > seems to search only a limit

[hugin-ptx] Re: Hugin 2009.4.0 Win XP autopano-sift-c 2.5.2 bug

Autopano-SIFT-C 2.5.2 23July2009 is known to be broken. Please try again with 2.5.1. There have been numerous reports on this list already, but I admit, the search function *within* groups.google.com seems to search only a limited history of messages. Furthermore, I hope you didn't copy&paste that

[hugin-ptx] Re: enblend 4.0 vs. smartblend 1.25?

Yes, I wrote that script a while ago, while facing the same problems as you are now. Make sure you disabled "Save cropped images" under Nona options, either in the preferences or in the stitcher tab for every project where you want to use Smartblend. If you don't, you'll get the "terrible overlap"

[hugin-ptx] Re: APSC gives array out of bounds?

On 28 jan, 17:36, Zoran Zorkic wrote: > The problematic one is here:http://pastebin.com/f21e22535 > I get that one when I load an already optimized project, add more > images and try to create new CPs. To be clear it's a temp pto. Just wondering: does the temp pto only contain the newly added i

[hugin-ptx] Re: APSC gives array out of bounds?

What does the original .pto look like? The '=' signs are used to refer to images loaded earlier, e.g. 'v=0' means: 'take the v-value from image 0'. The PTO file specification (which I never seem to be able to find) allows for 'dummy' images which aren't really images, but contain various settings w

[hugin-ptx] Re: Windows Executables for Hugin's Panotools-Script

OK in case anyone else wants to build the executables: what were the steps you had to take in order to get it to work? Does the wiki page need an update, or did you just miss a step somehow? -- Bart -- You received this message because you are subscribed to the Google Groups "hugin and other fr

[hugin-ptx] Re: Hugin control point generator

Generally, you don't need all of them. Usually (at least for me) Autopano-SIFT-C does the trick, as well as Pan-o-matic. Both Autopano- SIFT and Autopano are superseded by Autopano-SIFT-C, kind of, so you won't need those. Anyway: panomatic: http://aorlinsk2.free.fr/panomatic/ regarding match-n-sh

[hugin-ptx] Re: Moral questions

Upon reading a bit further in the same OpenCV thread, I found a mention of different, possibly less patent-restricted algorithms [5]. Could be interesting! Further investigation needed... [5] http://n2.nabble.com/SURF-protected-by-patent-tp3458734p3463927.html -- Bart On 23 dec, 13:59, Bart van

[hugin-ptx] Re: Moral questions

On 23 dec, 04:46, DaveN wrote: > From the SURF page (interesting that the SURF page says it is > copyrighted but there is no mention of a patent) I checked the files they provide, and those contain a LICENSE file, which I'll quote below. Indeed nothing is mentioned about patents anywhere. I've

[hugin-ptx] Re: CP Detector vs. Generator

On 21 dec, 14:49, Kornel Benko wrote: > Detect corresponding points? Nice find! -- 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_F

[hugin-ptx] Re: CP Detector vs. Generator

OK, now we have: - control point - link point - connection point - anchor point I couldn't think of many more, except for: - key point - feature point I think the latter two define best what the points actually *are* in their own image. Both autopano-sift-c and panomatic actually combine finding

[hugin-ptx] Re: Announce: Enblend/Enfuse version 4.0 - Final Release

On 21 dec, 03:41, Yuv wrote: > OK, got the message. Usability is important. Will move to a single > long page, no frame. I have a working proof of concept stretching the > SVG on Firefox. Not ready to be pushed on the site yet. Will try to > get it done before the end of the year. In the past I'v

[hugin-ptx] Re: CP Detector vs. Generator

On 20 dec, 16:43, Carl von Einem wrote: > Thoughts? Another way to look at it: "autopano-sift-c and friends" detect points (or regions) which can be used as control points. In that respect, they are really detectors. Well, in fact they are feature detectors which generate/define control points.

[hugin-ptx] Re: Announce: Enblend/Enfuse version 4.0 - Final Release

Hey Yuv, Welcome back! Do you have a screenshot of what it's supposed to look like? I'm using Chrome on WinVista but I've got the feeling what I see is not exactly what you intended. Or it's just the beta thing, of course. * When resizing to an internal width (width of the background, as reported

[hugin-ptx] Re: Moral questions

On 18 dec, 16:33, DaveN wrote: > Regardless, I seem to be beating a dead horse here.  It is clear the > feeling here, IMHO, is 'I follow the rules I see fit, ignore the ones > I don't see as fit, and have no issue in expecting that my work will > not be infringed upon.' Luckily, that's just your

[hugin-ptx] 26 Gigapixel image

I just ran into an article about an interesting project: a 26 gigapixel image of Dresden, Germany (in German [0] / English translation [1]). The photo itself can be viewed interactively here [2]. Not stitched using Hugin it appears, but nevertheless I thought some of you might find it interesting :

[hugin-ptx] Re: ldconfig missing in 'make install'

> Try this with any other source package, you don't need to be root to > run: > >   make install DESTDIR=/tmp/foo > > This isn't just academic, every package on your Linux system was built > exactly like this with non-root user accounts. Ah! Interesting, thanks! Summarizing, we now have three appr

[hugin-ptx] Re: ldconfig missing in 'make install'

> The problem is that `make install` needs to work for non-root users, > this is why ldconfig is usually run after installation. Really? I could only run the command using 'sudo make install', and I haven't seen many packages for which 'make install' works without the 'sudo'. At least in my Ubuntu

[hugin-ptx] Re: ldconfig missing in 'make install'

On 18 dec, 13:16, Kornel Benko wrote: > Am Friday 18 December 2009 schrieb Bart van Andel: > > > On 18 dec, 12:22, Kornel Benko wrote: > > > You may want to consider this: > > >         cmake .. -DCPACK_BINARY_DEB:BOOL=on > > >         make package >

[hugin-ptx] Re: ldconfig missing in 'make install'

On 18 dec, 12:22, Kornel Benko wrote: > You may want to consider this: >         cmake .. -DCPACK_BINARY_DEB:BOOL=on >         make package > > and install the created .deb package instead. Okay, just did that (5 archives get created, I'm sure this can be suppressed using additional options), and

[hugin-ptx] ldconfig missing in 'make install'

Hi, I just compiled hugin from trunk ("Pre-Release 2009.5.0.4819", libpano also from trunk) on an up-to-date Hugin Jaunty system where it hadn't been installed before. b...@ubuntu-bart:~/src/hugin$ mkdir build-linux && cd build-linux b...@ubuntu-bart:~/src/hugin$ cmake .. b...@ubuntu-bart:~

[hugin-ptx] Re: Something like fog on stitched pano

Could you post an example to show what you mean by "fog"? From your report it's impossible to pinpoint the problem... -- Bart On 16 nov, 15:52, Can-C. Dörtbudak wrote: > Hi Guys, > > i've taken pictures for an cubic panorama. They fit very well but in > the output file i get on some areas someth

[hugin-ptx] Re: binary distribution policy

> Easiest thing to do: pull directly out of mingw-cross-env repository > (assuming you want install it in /opt/mingw-cross-env): > $ cd /opt > $ hg clone http://hg.savannah.nongnu.org/hgweb/mingw-cross-envmingw- > cross-env Forgot to mention: there are some dependencies... More on this here: http

[hugin-ptx] Re: Package manager for windows

I'm not exactly a professor on this subject either, but from my understanding (and experience), package managers are mostly for binary releases, in other words: the runtime dependencies. I'm not aware of a package manager for build time dependencies. These are generally different from runtime depe

[hugin-ptx] Re: binary distribution policy

Built glut (actually, freeglut) as well, just now. Mail is underway to Volker. So far he's been rather quick in replying, so I suspect it won't take long before both lcms and freeglut will be integrated. -- Bart On 11 nov, 17:34, Bart van Andel wrote: > > - Choose a dependen

[hugin-ptx] Re: binary distribution policy

> - Choose a dependency to work on (I assume "lcms" for this example). Note: I've just built lcms myself, so no need to work this one out anymore. I've just emailed it to Volker, so I expect it will be added to mingw-cross-env soon. --~--~-~--~~~---~--~~ You receiv

[hugin-ptx] Re: binary distribution policy

> > If anybody else wants to contribute by helping build the > > dependencies, for example, please do! > > I would like to participate here. Is there a homepage or a repository > where your current work is accessible? Easiest thing to do: pull directly out of mingw-cross-env repository (assuming

[hugin-ptx] Re: binary distribution policy

> You might take a peek at the build files I uploaded [0], because they > include the patches and configuration options used to compile hugin > and its assorted dependencies (what is libplot, btw?). I will. As far as I can see, most patches are for libraries which are already part of mingw-cross-

[hugin-ptx] Re: binary distribution policy

On 11 nov, 13:05, Ryan wrote: > 2. Anybody can install cygwin, for free. I hear it's even possible to > set up a mingw32 cross-compiler on linux I'm actually trying to get this working. Currently I have an Ubuntu 9.04 installation inside VirtualBox (on Windows host), and I'm using mingw-cross-en

[hugin-ptx] Re: Some hugin related scalable graphic

On 20 okt, 20:12, Yuval Levy wrote: > http://hugin-ptx.googlegroups.com/web/hug_icon+%282%29.svg > > displays right away in the browser (at least in Firefox 3.5 on Ubuntu). Displays right away in Chrome 4.0 as well (and with earlier versions too I believe), > my preference so far is A4 for Hu

[hugin-ptx] Re: Next GUI - take 2

On 15 okt, 18:43, Tom Sharpless wrote: > I think "a new Hugin" should provide only two direct stitching > targets: cube faces and equirectangular, and let you convert either of > those to other projections later. When this is done internally (e.g., as an intermediate kind of file), I don't see a

[hugin-ptx] Re: what is hugin doing to the exposure?

Thanks for your rather elaborate answer, Yuv. Of course you're completely right (and I'm dead serious too, sorry that I misunderstood). You can never really trust anything you download, or rely blindly on what a program says to be. > > What about a new command line argument "--version" which giv

[hugin-ptx] Re: Next GUI - take 2

On 13 okt, 19:18, Yuval Levy wrote: >   Also: wxPython has the same widgets as wxWidgets in C++ and one of the > things to consider, since this is becoming a complete rewrite, is to > start from scratch a wxPython GUI to replace the current C++ GUI. I haven't programmed either wx*, so I really d

[hugin-ptx] Re: Next GUI - take 2

I like your ideas, Yuv. One aspect which you are pointing out is that different users with different understanding of the way Hugin works (or: the way you can use Hugin) may need different GUI layouts. Expert users like yourself may find it useful to have as much controls as possible on a single p

[hugin-ptx] Re: what is hugin doing to the exposure?

On 12 okt, 19:00, Yuval Levy wrote: > Thank you, Bart, for going through this well done analysis. > If a binary says it is 2.5.2... caveat emptor. Point taken. It sounded really convincing though... ;) You're being sarcastic, which is okay, but this might indicate that the version information o

[hugin-ptx] Re: what is hugin doing to the exposure?

Just saved both files and ran the following steps: - Open Hugin 2009.2.4450 (by Ad), on my Windows Vista SP3 setup. - Clicked "Align..." on the assistant tab, which started APSCpp 2.5.2. As you can see in the output which I pasted below, something is going wrong: APSCpp is reporting FOV of 180 de

[hugin-ptx] Re: what is hugin doing to the exposure?

(I prefer to stay on-list except when not appropriate, so here's your answer and my new reply) On Fri, Oct 9, 2009 at 3:37 PM, don wrote: > I'm on Windows XP SP3. Not sure which version I can download, the > latest ones seem to be for Windows Vista only, so i tried "hugin- > SVN3943-setup.exe" -

[hugin-ptx] Re: what is hugin doing to the exposure?

On 9 okt, 10:22, don wrote: [...] > any tips? thank you. Tip: you're still using a fairly old version. Version 0.8.0 has come out not so long ago, and we are over 1000 svn commits further than your current version. Newer versions might solve your issue, so please try this first. You haven't supp

[hugin-ptx] Re: unsubscribe failure

On 8 okt, 22:14, Bruno Postle wrote: > The unsubscribe address is hugin-ptx+unsubscr...@googlegroups.com Looks like a sum to me. What is the outcome? ^_^ Sorry, couldn't let this one go :) --~--~-~--~~~---~--~~ You received this message because you are subscribe

Re: usability (was Re: [hugin-ptx] Re: Oups, I've added two strings!)

rectly) that there is not universal truth about usability, except maybe when you define it as usable to the average user. Always watch out when applying statistics. I dare to say that there are relatively a lot of "expert users" among the Hugin user base, so this group should not be denied. O

[hugin-ptx] Re: Oups, I've added two strings!

On 7 okt, 23:26, Yuval Levy wrote: > Bart van Andel wrote: > >> It is like letting people tilt beyond nadir/zenith when navigating a > >> 360x180 - fine for the expert who knows what he is doing, but not > >> helpful for the occasional user. > > > I d

[hugin-ptx] Re: Oups, I've added two strings!

On 6 okt, 01:00, Yuval Levy wrote: > Bruno Postle wrote: > > Surely just dragging the box to the point that it > > inverts could just silently flip the coordinates > > please don't. > > It is like letting people tilt beyond nadir/zenith when navigating a > 360x180 - fine for the expert who know

[hugin-ptx] Re: Oooh, it smarts

About a year and a half ago, this was also the topic of a thread here [1]. Both Yuv and myself have emailed Michael Norel (the author) about releasing the source code of SmartBlend, and he replied back then that he'd "At least i'll find time to publicsh sources." So far he hasn't, unfortunately, b

[hugin-ptx] Re: Mailing List(s)

> [...] I rather think that we will > have one separated list for notifications (tracker and commits), and one > separated list for talk (which can very well be hugin-ptx if the users > tolerate more dev talk). As a user with an interest in coding and algorithms, I'm pretty happy with the way the

[hugin-ptx] Re: strangely calling antipano-sift-c

If a previous version of Hugin (on Windows) was installed with and setup for autopano-sift-c (0.7.0 included this optionally if I remember correctly), these settings are saved in the registry. Since all Hugin versions use the same registry keys, newer versions may use old settings if those aren't

[hugin-ptx] Re: Control point generator incantations

On 7 sep, 05:26, Yuv wrote: > the more the merrier! I would suggest giving more meaningful names > (first column) indicating the purpose of the settings. Some works > better with fisheye lenses than others. I haven't even checked out this new preset thing (which I deem a very good idea!), so I d

[hugin-ptx] Re: MatchPoint naming

On 3 sep, 13:17, Yuval Levy wrote: > bottom line: don't worry about the name and keep calling our work in > progress CP generator MatchPoint. I was hoping it works the way you just explained, but you confirmed my guess. Bottom line: there is no problem :) -- Bart --~--~-~--~~---

[hugin-ptx] Re: Flipping Photos !

On 2 sep, 00:37, Greg wrote: > (2) After creating control points, and before any optimization, check > the distance values of all points in the control point table; problem > images have large (in the thousands) distance values for one or more > control point pairs, for whatever reason. Delete an

[hugin-ptx] Re: Flipping Photos !

On 1 sep, 20:42, Dale Beams wrote: > The problem is that it worked on the first pano, errors on the second and > then progressively got worse for each succeeding pano. What happens if you have Hugin make a pano, and then have it make the exact same pano *again* (without using a saved version I

[hugin-ptx] Re: Flipping Photos !

Could this be a problem with a 360 degree pano where the initial FOV guess is completely wrong? If so, you might circumvent this issue by resetting all parameters and entering a more appropriate FOV guess manually. I've also had this problem on occasion, usually with photos lacking EXIF or having

[hugin-ptx] MatchPoint naming

Hi Klaus, Please use English in this group. I've translated your message (freeform) for convenience here: "To find unused names is truly hard. I just found out on the German Wikipedia that Microsoft is also using MatchPoint for something." What should we do with this? Should we act and rename M

[hugin-ptx] Re: portable hugin 0.8

On 13 aug, 12:56, Emad ud din Butt wrote: > hugin is portable :) According to the portable apps site [0], a portable app should leave no traces after quitting. Of course this is just one definition, but in my opinion it is a preferable one. Hugin (I'm talking about the Windows version) *does* wo

[hugin-ptx] Re: Speed reference...

> Then there is something I probably don't understand... > > I thought that once nona was run, enblend and enfuse had no impact to > alignment, everything had already been calculated\preprocessed. enblend and > enfuse would only use this information. I think you understand that part correctly. H

[hugin-ptx] Re: Speed reference...

On 3 aug, 02:04, Nicolas Pelletier wrote: > What I expected: > Take the 36 images (12 per exposure). > Enblend the first exposure > Enblend the second exposure > Enblend the third exposure > Enfuse the 3 exposures By taking the following approach, you allow for the bracketed images to be aligned

[hugin-ptx] Re: portable hugin 0.8

> I guess it is to register .pto files with Hugin system-wide and not just > for the user performing the installation. That does explain using either hkcr or hklm, but not both, as far as I'm aware only one of those is needed for system-wide registration. For per-user registration, registration i

[hugin-ptx] Re: portable hugin 0.8

Upon installation, Hugin registers its file type (.pto). I found references in 3 places: - hkey_classes_root - hkey_local_machine\software\classes - hkey_current_user\software\classes The first and the second are system-wide and thus require elevation or administrative rights to add/modify. The l

[hugin-ptx] Re: Lens calibration gsoc project -- photos needed

Recently I ran into this web page: http://www.bobatkins.com/photography/technical/field_of_view.html It describes the formulas used for both rectangular and 4 types of fisheye lenses: equisolid, equidistant, stereographic and orthogonal. It also contains a graph plotting the associated functions

[hugin-ptx] Re: Lens calibration gsoc project -- photos needed

On 27 jul, 14:09, Bart van Andel wrote: > You haven't mentioned how long you want the > straight lines to be Oh well, I spoke too soon (should've refreshed before sending)... I know the quality of the images I sent aren't all that good, but these were the images I have

[hugin-ptx] Re: Lens calibration gsoc project -- photos needed

Hi Tom, I'm uploading 10 pictures right now. All but one contain a fair amount of straight lines. You haven't mentioned how long you want the straight lines to be, so I included both images with straight lines all through the image and images with straight lines which only partially cover the ima

[hugin-ptx] Re: Some hugin related scalable graphic - crayon is nice!

On 24 jul, 14:37, Yuval Levy wrote: > It seems to be a marketing-habit to change / evolve the logo / icon from > time to time, like it is to change the website (Bart, any news? I still > don't have your SourceForge user id). Actually I "replied to author" on the google group, which went to your

[hugin-ptx] Re: Release notes link on website wrong

On 22 jul, 03:05, Yuval Levy wrote: > Bart van Andel wrote: > > - PHP will be used to display most content > > please don't. I hate to be the one to damp your enthusiasm, but you have > to understand the limits of the current hosting environment. > > you can use

[hugin-ptx] Re: Release notes link on website wrong

Distilled and summarized from various posts: - The new design will be fresh and clear. - PHP will be used to display most content, including news and the header. I'll see what I can do about the sf news feed being garbage. If only I could talk with the db directly, this might be solved easily, bu

[hugin-ptx] Re: hugin crashes when adding photos on windows vista

Well, a new version has just been released (0.8.0) so I'd suggest that you try this new version first. The new version fixes lots of bugs and also introduce a bunch of new features. Release notes: http://hugin.sourceforge.net/releases/0.8.0/en.shtml Download (Windows): http://allardkatan.net/mis

[hugin-ptx] Re: hfov considered dangerous

Maybe FOV should be treated differently based on the lens type. This does make sense, as for circular fisheye the given (or guessed) fov of the lens is only the fov of the circle, not of the full frame. The image loading screen could be adapted to show a small helpful picture to denote how the fov

[hugin-ptx] Re: hfov considered dangerous

Perhaps the easiest (to understand) solution, at least for the landscape vs portrait mode problem, is to take max(HFOV, VFOV), in other words, the FOV of the greatest dimension. This is pretty easy to guess from a user perspective in case of missing EXIF information. I've thought about a DFOV as w

[hugin-ptx] Re: Hugin needs possibly different builds for Windows XP and VISTA

I'm running Vista and Ad's Hugin build crashes as well every now and then. Sometimes even directly after starting up, but I haven't really investigated the cause yet. Wrong paths in the registry seem to be able to cause crashes, which I found out after installing SVN4012 and removing all my previo

[hugin-ptx] Re: Release notes link on website wrong

On 20 jul, 03:03, Yuval Levy wrote: > Bruno Postle wrote: > > (we could use lots more of these banners, they need to be 165 pixels > > high, tile horizontally and be done with hugin) > > Like I said above, 165 pixels is for t

[hugin-ptx] Re: Release notes link on website wrong

On 20 jul, 01:28, Bruno Postle wrote: > Yes the design is tired and this looks like a nice change, the only > thing I would prefer not to fade the panorama at the top, as it is a > showcase of hugin itself. I'm aware that it's a showcase of Hugin, but it takes up a good deal of space, moving the

[hugin-ptx] Re: Release notes link on website wrong

On 20 jul, 00:49, Yuval Levy wrote: > Gerry Patterson wrote: > > This is very pretty although I am guess it it is a matter of available   > > time that Bruno? has.  How does one go about making changes to the   > > website? > > http://hugin.svn.sourceforge.net/viewvc/hugin/htdocs/ > > all you nee

[hugin-ptx] Re: some GUI ideas: multilayer tiff?

On 20 jul, 01:28, Bruno Postle wrote: > If you want a lower quality JPEG version as well as a full quality > TIFF, then running the stitch twice doesn't make sense.  The JPEG > should be derived from the high quality stitch just as the > multilayer file should be derived from the intermediate rem

[hugin-ptx] Re: Release notes link on website wrong

Sans Bold - headings: DejaVu Serif - texts: Georgia - screenshot caption: Georgia Italic -- Bart On 19 jul, 20:57, Bart van Andel wrote: > I think the website needs a little polish for other things too. The > screenshots are all pretty outdated, and maybe a cleaner design would > be nice

[hugin-ptx] Re: Release notes link on website wrong

I think the website needs a little polish for other things too. The screenshots are all pretty outdated, and maybe a cleaner design would be nice too. I played with GIMP a bit and this is what I came up with: http://hugin-ptx.googlegroups.com/web/2009.07.19+Hugin+website+mockup.jpg?gda=AAyq31UAAA

[hugin-ptx] Re: What's in a Version Number?

I have no objection against this approach. When installing I was already putting files in a folder named Hugin-x.y.z.SVN (latest one on disk: Hugin-0.8.0.4012), but I like the date-like versioning probably even better. -- Bart --~--~-~--~~~---~--~~ You received thi

[hugin-ptx] Re: some GUI ideas: multilayer tiff?

> By the way my (even more dream-like) suggestion I made some time ago > (http://groups.google.com/group/hugin-ptx/browse_thread/thread/1cfa0f4...http://www.joachimschneider.info/hugin_workflow_assembly.gif) > would make > all combinations of simultaneous output possible. I do like your alternat

[hugin-ptx] Re: some GUI ideas: multilayer tiff?

On 19 jul, 02:35, Bruno Postle wrote: > On Sat 18-Jul-2009 at 04:51 -0700, Bart van Andel wrote: > > >I'd suggest simply as a "Normal Output" option, which is now populated > >with TIFF/JPG/PNG. > >Or do you mean you want both TIFF/JPG/PNG output *and* a

[hugin-ptx] Re: some GUI ideas: multilayer tiff?

> The only problem is the already convoluted GUI in the hugin Stitcher > tab, how do we make this an option that users will be able to find? I'd suggest simply as a "Normal Output" option, which is now populated with TIFF/JPG/PNG. Or do you mean you want both TIFF/JPG/PNG output *and* a multi-lay

[hugin-ptx] Re: Autopano-sift-c memory leaks

Just a small note: 1. APSCpp version still displays 2.5.0 without SVN number, shouldn't this be added? It makes distinguishing between different builds (e.g. erroneous or not) a lot easier, for one. 2. At the end of the info screen (seen when APSCpp is called from the command line without any pa

<    1   2   3   >