Re: [hugin-ptx] Re: how should hugin interact with plugins?
kfj wrote: On 18 Mrz., 09:55, Gnome Nomad wrote: No, definitely not a focus stack. I'm sure doing things with focus stacks would use much more memory. I was just talking about producing a 750MB panorama. I've done a couple of HDR images, I don't know if they consume memory at the rate of a focus stack. Propably less, since with exposure stacks you can look at every pixel in isolation. But don't take my word for it. At any rate, stacks with enfuse seem to be memory-intensive. Maybe enfuse is memory intensive? Haven't noticed it on ordinary stuff. Question: were you running the enfuse stage from command line? I don't remember if you said so. I had to do that once before I doubled the memory in the laptop. I did it from the command line. Maybe I could have somehow coaxed hugin into issuing the enfuse command for me, but the command line is a good friend of mine anyway, so that's the path I took ;-) I decided one time to use command-line autopano with 6MPX images at full size (no reduction). Just processing a single image used 1.9GB of memory! -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god http://www.cafepress.com/otherend/ -- 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] Fwd: Congratulations!
Yeah! We've been accepted for GSoC! (See forwarded email below). Habi Begin forwarded message: > From: socghop.nore...@gmail.com > Date: 18. März 2011 20:00:30 MEZ > To: david.haberth...@gmail.com > Subject: Congratulations! > > Hi David Haberthür, > > Congratulations, your application for Hugin - Panorama photo stitcher as a > mentoring organization for Google Summer of Code 2011 has been accepted! Over > the next few days, you should plan to register your mentors and complete some > housekeeping tasks to make sure your pages on the GSoC 2010 site are up to > date. Please read this email very carefully, as it contains important > instructions for you and your organization. > > The most important thing to do right now is to check your email for an > invitation to become an organization administrator. If you do not do this, it > will *not* be possible for anyone to apply to become a mentor (as there is no > adminstrator to approve them)! You should have received a notification (the > same as an email too) about this. If you cannot find the notification, you > can find the invitation under your requests. Again, please do this *now*. > > For more information on registering your mentors and other/alternate > administrators, please see the site User Guide. > > You should immediately plan to update your accepted organization profile and > to create your organization's home page at socghop.appspot.com. You can find > instructions for this in the User Guide: Organization Administrators section. > Please do this *now*, as it ensure that would-be student applicants have the > best access to your organization's information. > > We will periodically subscribe mentors who sign up with your organization to > the program's private mentors mailing list. Please let your mentors know to > expect this. Please also let them know that they may be resubscribed a few > times if they choose to unsubscribe and we apologize in advance if this > occurs. It may be worth setting the mailing list preferences to digest only > for the few days of the program. > > Once again, congratulations for your acceptance into Google Summer of Code > 2011! > > Kind regards, > The Google Summer of Code Program Administration Team -- 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] panosphere overview disappears when an image has a mask beyond its boundaries
On Wed 16-Mar-2011 at 14:43 -0700, Jeff wrote: If you have a mask on an image beyond the boundaries of the image, the panosphere doesn't appear correctly in the overview in the fast preview window. The panosphere acts correctly when you toggle off the image with the mask. The odd behavior goes away if the mask is completely contained within the image. Confirmed, I created a bug report in the tracker: https://bugs.launchpad.net/hugin/+bug/737852 -- 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] Re: Toward RC1: show stoppers
On Fri 18-Mar-2011 at 10:29 +0100, Peter Suetterlin wrote: I am using a shellscript to compile, at some point I had added -DENABLE_LAPACK=ON there after some recommendation from the list here. So my question is: Is this still needed/recommended, or should I just switch it off (I verified that it does not crash when compiled without lapack) There doesn't seem to be any difference if you leave it on or off, I leave it off. You are the first to report negative results from switching it on. -- 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] Re: Hugin stitching problem
On 18/03/11 06:03, kfj wrote: > > > On 17 Mrz., 00:13, Guillermo Movia wrote: > >> I change tem folder to a non standard one. I don't know if this could be >> the problem > > Look into the pto file with a text editor and make sure that the image > files given in the pto are accessible by the paths used in the pto > file. The filename is the last entry in the i-line. It looks like > DSC_9049.JPG etc. are looked for in the folder /tmp/Mexico/JPG - so > you should also check if the images are really there or somehwere > else. > > Kay > Thanks for your reply. All photos are at /mnt/datos/Mexico/JPG folder, where pto file is too. temp/working folder is set to /mnt/datos and in the pto file, images are referenced like Mexico/JPG/DSC So, for some reason, still use /tmp/ n some way and I couldn't change it. I will try to return to default values and start again. -- Guillermo Movia @deimidis http://unojoenelcielo.com.ar signature.asc Description: OpenPGP digital signature
Re: [hugin-ptx] GSoC 2011 is on!
On 18 March 2011 21:19, Yuval Levy wrote: > Congratulation Habi and everybody else for the good job on the application. > > http://www.google-melange.com/gsoc/program/accepted_orgs/google/gsoc2011 > > A good news to start the weekend. > > Yuv > Thats a great news! Lukas -- 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] GSoC 2011 is on!
Congratulation Habi and everybody else for the good job on the application. http://www.google-melange.com/gsoc/program/accepted_orgs/google/gsoc2011 A good news to start the weekend. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Bug
Probably related: out of curiosity I've played around a bit with a test makefile to try different special characters in target names. I've added the resulting test.mk as an attachment to bug "Stitching fails with '&' character in path" [0]. [0] https://bugs.launchpad.net/hugin/+bug/679353 -- 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 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: Hugin stitching problem
kfj schrieb am 18.03.11 10:03: On 17 Mrz., 00:13, Guillermo Movia wrote: I change tem folder to a non standard one. I don't know if this could be the problem Look into the pto file with a text editor and make sure that the image files given in the pto are accessible by the paths used in the pto file. The filename is the last entry in the i-line. It looks like DSC_9049.JPG etc. are looked for in the folder /tmp/Mexico/JPG - so you should also check if the images are really there or somehwere else. As long as all the source images are in the same folder as the .pto project file Hugin should be able to locate them. Otherwise Hugin asks for missing images when the project is opened. I wouldn't use 'tmp' as a name for a new folder though, since that's already used by my system (Mac OS X, in Finder -> Shift-cmd-G -> type '/tmp/' without the ' -> click 'start') Carl -- 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: Toward RC1: show stoppers
Hi all, I had a (sort of) closer look, running hugin in dd. This tells me Program received signal SIGSEGV, Segmentation fault. 0x752ed742 in dscal_ () from /usr/lib64/libblas.so.3 so it seems to be in the lapack part.. I am using a shellscript to compile, at some point I had added -DENABLE_LAPACK=ON there after some recommendation from the list here. So my question is: Is this still needed/recommended, or should I just switch it off (I verified that it does not crash when compiled without lapack) Cheers, Pit Andreas Metzler wrote: > Peter Suetterlin wrote: > > didn't have much time for panos lately, but remembered I had some > > trouble with exposure optimization some time ago. So I had a look > > at the respective project, and it still crashes. > > It's a 3-image partial pano, manual control points. It stitches > > fine, but when I open the project, go to the 'Exposure' Tab and > > press optimize hugin crashes with a segfault. > [...] > > pto file and images here: http://www.astro.su.se/~pit/hugin_example.tgz > > (9.1MB) > > > Version is hg f3a428981466, opensuse 11.2 64bit > [...] > > Hello, > it does not seem to be reproducible on all systems. It does not crash > for me. -- 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: how should hugin interact with plugins?
On 18 Mrz., 09:55, Gnome Nomad wrote: > No, definitely not a focus stack. I'm sure doing things with focus > stacks would use much more memory. I was just talking about producing a > 750MB panorama. > > I've done a couple of HDR images, I don't know if they consume memory at > the rate of a focus stack. Propably less, since with exposure stacks you can look at every pixel in isolation. But don't take my word for it. At any rate, stacks with enfuse seem to be memory-intensive. > Question: were you running the enfuse stage from command line? I don't > remember if you said so. I had to do that once before I doubled the > memory in the laptop. I did it from the command line. Maybe I could have somehow coaxed hugin into issuing the enfuse command for me, but the command line is a good friend of mine anyway, so that's the path I took ;-) Kay -- 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 stitching problem
On 17 Mrz., 00:13, Guillermo Movia wrote: > I change tem folder to a non standard one. I don't know if this could be > the problem Look into the pto file with a text editor and make sure that the image files given in the pto are accessible by the paths used in the pto file. The filename is the last entry in the i-line. It looks like DSC_9049.JPG etc. are looked for in the folder /tmp/Mexico/JPG - so you should also check if the images are really there or somehwere else. Kay -- 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: how should hugin interact with plugins?
kfj wrote: On 18 Mrz., 08:11, Gnome Nomad wrote: A great amount of patience? Running it under FluxBox, which consumes only about 128MB of memory vs a couple meg for KDE. And not using 16-bit images. And letting the little laptop grind away on it for 10 hours ... ;-) I made mine from a series of frames I shot covering our trip into the harbor at Victoria, Canada, (on a ferry). They covered 3-5 miles of shoreline. This doesn't really sound like a focus stack to me. Are we talking about the same thing? I'm not talking about exposure blending with enblend, but focus stacking with enfuse. I think focus stacks may need more memory, because they have to look at the neighbourhood of all pixels to determine the local contrast, which is used as a weighting criterion. I know that I could have gone 8-bit but chose not to. And of course I could have chopped the thing up into several smaller partial images - there's always a way. Currently, it takes a lot of finessing to do stuff like that, and that's one reason why I'm developing the scripting interface. When I did the image I was talking about, it didn't rerally take long, but it took massive amounts of memory, and when I used larger source images, enfuse simply failed with a bad alloc. I have an idea what I could have done on top of what I did to manage with consuming less memory - alas, right now I can't try it out because the AC adapter of my laptop gave up yesterday... No, definitely not a focus stack. I'm sure doing things with focus stacks would use much more memory. I was just talking about producing a 750MB panorama. I've done a couple of HDR images, I don't know if they consume memory at the rate of a focus stack. Question: were you running the enfuse stage from command line? I don't remember if you said so. I had to do that once before I doubled the memory in the laptop. -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god http://www.cafepress.com/otherend/ -- 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: upcoming GSOC 2011
On 17 Mrz., 10:58, David Haberthür wrote: > The applications for the OpenUsability Season is open until the end of > march. No others got back to this thread with suggestions and support. > This leaves me wondering if we should apply for a project there. As I > mentioned before, the OpenUsabilty application seems to be "easier" > than for GSoC. Did you look through the application and could you > suggest someone as a mentor? I can't propose anyone as mentor, and I can't offer to do it myself - I'm too busy trying to get the Python interface off the ground, and summer is approaching, so I'll be off(line) for extended periods. In fact I could use a mentor - how about an experienced wxWidgets programmer who can help sort out the current troubles with plugins wanting do GUI stuff on Windows - or an experienced Mac programmer who can compile a working Python module on the zoo of feline predators... I'm quite new to the project as well and don't know any of the other contributors personally, so I have no idea what they might be able or willing to do. > I guess we could just > usehttps://blueprints.launchpad.net/hugin/+spec/ui-overhaulas an idea > for the student project. If you feel it states what needs to be done I can't see why not. But don't count on me to do more than writing the blueprint. Let me add a word of caution. I feel that a lot of everyone's time is consumed by intergrating new features into hugin and hammering out frequent releases. Are we sure we can make good use of yet another source of material? What would the result of the process be and how expensive would it be to integrate it? If noone else comes forward and you can't think of anyone, we might be better off shelving the idea, rather than potentially getting another fat lump of data to swallow that noone's willing to digest. Kay -- 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: how should hugin interact with plugins?
On 18 Mrz., 08:11, Gnome Nomad wrote: > A great amount of patience? Running it under FluxBox, which consumes > only about 128MB of memory vs a couple meg for KDE. And not using 16-bit > images. And letting the little laptop grind away on it for 10 hours ... ;-) > > I made mine from a series of frames I shot covering our trip into the > harbor at Victoria, Canada, (on a ferry). They covered 3-5 miles of > shoreline. This doesn't really sound like a focus stack to me. Are we talking about the same thing? I'm not talking about exposure blending with enblend, but focus stacking with enfuse. I think focus stacks may need more memory, because they have to look at the neighbourhood of all pixels to determine the local contrast, which is used as a weighting criterion. I know that I could have gone 8-bit but chose not to. And of course I could have chopped the thing up into several smaller partial images - there's always a way. Currently, it takes a lot of finessing to do stuff like that, and that's one reason why I'm developing the scripting interface. When I did the image I was talking about, it didn't rerally take long, but it took massive amounts of memory, and when I used larger source images, enfuse simply failed with a bad alloc. I have an idea what I could have done on top of what I did to manage with consuming less memory - alas, right now I can't try it out because the AC adapter of my laptop gave up yesterday... Kay -- 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: how should hugin interact with plugins?
kfj wrote: On 17 Mrz., 11:33, Gnome Nomad wrote: Hmm, I've created 750MB TIFFs on a 32-bit Linux system that has only 2GB of memory ... I guess Windows is different. What makes you think I'm on Windows? Im runnung Kububtu 10.10 Somebody - I guess not you! - in the thread mentioned using 32-bit Windows 7. But I did a focus stack with enfuse from three 30 megapixel 16 bit images. Well near the limit. When I used about 40 megapixels per source image it became impossible. I doubt you'd manage that with 2GB, but if you do please tell me how you did it ;-) A great amount of patience? Running it under FluxBox, which consumes only about 128MB of memory vs a couple meg for KDE. And not using 16-bit images. And letting the little laptop grind away on it for 10 hours ... ;-) I made mine from a series of frames I shot covering our trip into the harbor at Victoria, Canada, (on a ferry). They covered 3-5 miles of shoreline. By far the biggest I've ever done. -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god http://www.cafepress.com/otherend/ -- 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
