Re: [hugin-ptx] Re: CP Detector vs. Generator
On Mon, 21 Dec 2009 05:52:50 -0800 (PST), Bart van Andel wrote: > On 21 dec, 14:49, Kornel Benko wrote: >> Detect corresponding points? > > Nice find! Feature match? 100 feature matches found... Match features manually? Etc... -- 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] "Bad Allocation" error during stitching
On Mon 21-Dec-2009 at 08:19 -0800, Scott K wrote: >I have tried to create an HDR panorama from 118 pictures. It has found >the cp easily, but when i try to view the pano, i get an error stating >"Bad allocation" with the title being "error during stitching". There are a few reports of this in the tracker, but no solution. It only seems to effect Windows, and is related to large projects consuming a lot of memory. If it is nona that is crashing, can you make sure that 'saved cropped images' is set in the Stitcher tab -> Nona -> Options, and that the 'canvas size' is a reasonable pixel dimension for the panorama you expect to create? -- 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: CP Detector vs. Generator
On Mon 21-Dec-2009 at 17:14 +0100, Pablo d'Angelo wrote: > > In photogrammetry, what we call control points is called tie > points. I like that term it more than control points, but > panotools has used control point, and for the sake of consistency, > I think we should keep it. I'm not sure any of the options are good enough to change from 'control points', but in general it would be nice to use a more limited vocabulary of technical words. e.g. We still have stuff like 'Field of View', 'View', 'hfov', 'degrees of view' and 'horizontal field of view' all referring to the same thing, similarly we use 'photo', 'image' and 'picture' interchangeably. All these things make it difficult for casual users, translators, and for users with English as a second language. To reduce this vocabulary, we'd need a list of existing technical words, and reduce it down, this list is a good start: http://wiki.panotools.org/Hugin_translation_guide#Translation_guide_for_specific_terms -- 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: hugin not passing --compression to enfuse
Ok, I determined I had one setting wrong and that's why the stack_ldr files were so big. I had the 'Save cropped images' setting turned off in the nona options. Not sure why, but that makes much much smaller stack_ldr files! However, the two improvements would still be nice to see, passing the --compression setting to enfuse and only running exiftool on the final output file. -- 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 not passing --compression to enfuse
I'm working on a rather large stitch that is taking some time to complete and noticed that hugin doesn't pass the --compression setting to enfuse - at least when using the .mk file to do the stitching. In the preferences screen it says not to set the --compression arguments for both enblend or enfuse as these are set by hugin. If you look in the .mk file it's set for enblend but not enfuse. Setting this does make a large difference in stitching speed - along with turning off exiftool so it's not run after every enblend/enfuse running. For a smaller test stitch that's 50MP in size by setting --compression for enfuse and turning off exiftool I've decreased the stitching time from 95 mins to 64 mins. This is on a quad-core Core2 machine with 8GB of memory running Slackware64. For even larger stitches it should make an even bigger difference. The stitch I was working on when I noticed this is 250MP in size. There are 151 stack_ldr files, each almost 1G in size (1001M). If you stop to think about the data to/from the drive, that's a lot of data. 151 of these files at 1G in size, that's 151G right there. That's 151G written to the drive when they are first created by enfuse. Then exiftool reads in 151G of data to attach the exif data and then writes out that 151G of data. Then later enblend will read in all 151G of data to blend those stack_ldr files together. So that's 604G of data moving back and forth to the drive. By setting --compression to PACKBITS for enfuse the stack_ldr files shrink down to around 100M, about 1/10 of the non-compressed stack_ldr files. If we also set EXIFTOOL to 'false' in the .mk file then exiftool doesn't have to read and write out the data. So making these changes enfuse will write out roughly 15G of data that enblend then later reads in. We've gone from moving 604G of data to/from the drive down to 30G of data. Pretty big improvment. A couple improvements for hugin would be nice to see: 1) hugin should set the --compression argument for enfuse also like it does enblend 2) should exiftool be set so it's only run on the final output file instead of after every run of enblend/enfuse? As a further optimization, this would require more work, if enfuse output a stack_ldr file that was cropped to only contain the important data that would save space too. Could put an exif tag in the file to tell enfuse or enblend later on where that portion actually belongs in the full-size version. -- 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] "Bad Allocation" error during stitching
I have tried to create an HDR panorama from 118 pictures. It has found the cp easily, but when i try to view the pano, i get an error stating "Bad allocation" with the title being "error during stitching". I don't know where to go to fix this, I have tried to find a solution, but can't figure it out. I have tried to increase the Image Cache, but it won't let me raise it higher than 2000. Any help would be appreciated. I don't have any programming experience, but I can find my way through a computer. I am using 2009.2 for windows on Windows 7 (in compatibility mode for vista SP2) on a computer with 8 gigs of ram and a core i7 2.67. -- 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: CP Detector vs. Generator
bruno.postle wrote: > On Dec 21, 2:51 pm, Mick Crane wrote: >> Common point > > 'shared features' is another one I like. In photogrammetry, what we call control points is called tie points. I like that term it more than control points, but panotools has used control point, and for the sake of consistency, I think we should keep it. 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
Re: [hugin-ptx] Re: CP Detector vs. Generator
On Mon, Dec 21, 2009 at 7:52 AM, Bart van Andel wrote: > On 21 dec, 14:49, Kornel Benko wrote: >> Detect corresponding points? I think this suggestion gets to the heart of the matter. Do we want this part of the interface to describe accurately the underlying technology or the relevant part of the Hugin process? Tricky, indeed. "Detect corresponding points" gets my vote, but if it goes some other way, I like Carl's suggestion a lot.. Daniel Reetz -- 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: CP Detector vs. Generator
On Dec 21, 2:51 pm, Mick Crane wrote: > > Common point 'shared features' is another one I like. -- 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: CP Detector vs. Generator
... On 21 Dec 2009, at 13:51, Bart van Andel wrote: > 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 > > Common point -- 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: 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_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: 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 the points of interest, and matching them between images. Before matching, the points are essentially key points / feature points, but after matching, they control how the images are (found to be) related to one another, so I think they *do* become control points in the process. Hmm, tricky... -- 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] CP Detector vs. Generator
Am Monday 21 December 2009 schrieb Pit Suetterlin: > Bruno Postle wrote: > > > 'Generator' or 'creator' makes a bit more sense than 'detector' but > > the phrase 'control point' is confusing already. It would be nice > > to see an alternative, somebody suggested 'anchor' or 'link', 'tie' > > or 'connection' would all be more comprehensible than 'control > > point'. > > Anchor imho sounds too fixed. Might be mixed up with the anchor image? > Link or connection are better, I'd say. > As for the detector: In principle correct, as nothing is created in the > image, it's just finding good points that are there already... > > Link Point Extractor? Detect corresponding points? >Pit > > -- > Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit > Institute for Solar Physics > Tel.: +34 922 405 590 (Spain) p.suetter...@royac.iac.es > +46 8 5537 8507 (Sweden)peter.suetter...@astro.su.se > Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] CP Detector vs. Generator
Bruno Postle wrote: > 'Generator' or 'creator' makes a bit more sense than 'detector' but > the phrase 'control point' is confusing already. It would be nice > to see an alternative, somebody suggested 'anchor' or 'link', 'tie' > or 'connection' would all be more comprehensible than 'control > point'. Anchor imho sounds too fixed. Might be mixed up with the anchor image? Link or connection are better, I'd say. As for the detector: In principle correct, as nothing is created in the image, it's just finding good points that are there already... Link Point Extractor? Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) p.suetter...@royac.iac.es +46 8 5537 8507 (Sweden)peter.suetter...@astro.su.se -- 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: Announce: Enblend/Enfuse version 4.0 - Final Release
Yuv wrote: > The website is up [0] - beta quality. The content is mostly unchanged > (with the exception of the new and excellent 4.0 documentation > implemented by Chris) and the next step is an overhaul of the content. Opera (10.10, on openSUSE 11.0): The scrollbar for the central content box doesn't work. I cannot click-and-drag, neither does clicking in the empty slider area work. At least most of the time not: On trying several pages (clicking links does work), sometimes I got a reaction/scroll of the content. However, it was delayed and not clear what action had triggered the scroll. CPU load is low during this. Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) p.suetter...@royac.iac.es +46 8 5537 8507 (Sweden)peter.suetter...@astro.su.se -- 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: 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've seen ways to use Javascript to determine the content height, Google is your friend here, for example [0]. Can't you use that to instruct the SVN to stretch? I haven't played around with it myself but from my quick look at your code it seems Javascript already drives the page quite intensively. [0] http://codylindley.com/webdev/295/javascript-get-page-height-with-scroll -- 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
[hugin-ptx] Re: 26 Gigapixel image
I somehow think it's cheating, I wouldn't call it 26 gigapixel, when 50% of the image are just blue sky with no content, it is more a publicity stunt... joergen On Dec 18, 8:47 am, Bart van Andel wrote: > 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 :) > > [0]http://www.sz-online.de/nachrichten/artikel.asp?id=2341875 > [1]http://translate.google.com/translate?hl=nl&sl=auto&tl=en&u=http://ww... > [2]http://www.gigapixel-dresden.de/dresden26GP -- 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
