[hugin-ptx] Re: Hugin 2010.0.0
I've been making some of the windows installers in the past. However, my computer with my hugin build environment on it died and I have not had this high enough on my personal priority list get everything together again and continue building installers. So I did not make the installer for the latest version, and apparently nobody else did. However, it is quite simple to do so for anyone who has a build environment that can build hugin and has a current version of each of its dependencies. One or two adjustments in a text file, and a button press, that's all. If anyone wants to give it a shot and the instructions in the SDK are not sufficient, just contact me off-list, with perhaps a cc to the group, as I don't check back here regularly at the moment. Allard On Apr 17, 6:46 am, Bruno Postle br...@postle.net wrote: On Sat 17-Apr-2010 at 09:26 -0400, Brian Sullivan wrote: On Sat, Apr 17, 2010 at 9:20 AM, Dezen ilja.mode...@googlemail.com wrote: Here are unofficial builds: http://lemur.dreamhosters.com/hugin/ These are all 2010.1.0 snapshots of the current development trunk (probably very usable, even though you should consider them 'testers' releases). Ok thanks -- I assume at some point this will make it to the Sourceforge download site? I don't think there are any Windows installers for the 2010.0.0 release, it would be nice to have one for the sourceforge download. -- 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 athttp://groups.google.com/group/hugin-ptx -- 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: 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 whenever I like. Thanks for asking and (as always) all your efforts! -- 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: Any way to reuse control points on a different set of images?
I don't think it's in the official releases yet, but there is the new stack feature. Basically, all the images that are different exposures of the same image, you assign them the same stack number. Then, whatever the optimization you do, all of them will end up at exactly the same place. Output your panorama with all exposure layers, and you get all your pano for HDR. IMHO, it's the best option (and the one I currently use). nick On Fri, Apr 16, 2010 at 6:16 PM, RickyRicky meles...@gmail.com wrote: cri, I had originally renamed all my different exposure files to match up with the original exposure... That's not too bad but I think your legit method of just applying a different exposure's .pto file as a template is a bit better and more convenient. I'll let you know how it works out! BTW - Yes... Using a great tripod is a must when your panorama is 240 photos.. =) Ricky On Apr 16, 2:33 pm, cri cri.pe...@gmail.com wrote: Have you tried to use a template? Just load all the photo at the same exposure level and go through all the needed passages to get the final panorama. Then save the project as pto file. Now start a new poject, load all the images at a different exposure level and select File-Apply template. In the dialog select the previously saved pto file and you will get all the parameters loaded on the new exposure level images. In this way you could save a panorama for every exposure level. To get the best out of this procedure you need to take all the images from a tripod. Regards Cristian On 16 Apr, 20:52, RickyRicky meles...@gmail.com wrote: Gents, I have shot a few high resolution night time 180 degree panorama but I think I've been doing it wrong. My typical workflow is to shoot from three to six images of each frame, then to HDR or exposure blend these photos together and THEN to HDR the resulting images. That workflow works but if you want to make any changes to how the image is HDR'ed or exposure blended, it means you have to start all over again from the beginning. I've been thinking, why don't I create panoramas from each bracketed exposure using hugin, and then HDR and/or exposure blend the resulting panoramas? The problem is.. Hugin will most likely not select the same control points for the various different panoramas since at varying exposures, some control points will be more visible, and others will not. Is there any way to force hugin to use the same control points for a different set of images? Thanks for any help! I'm happy to show my work if y'all are interested in seeing what I've been working on so far... http://www.rickyricky.net/Photography/Panoramas/My-Panoramas Thanks, Ricardo Meleschi -- 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.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group athttp:// groups.google.com/group/hugin-ptx -- 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.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group athttp:// groups.google.com/group/hugin-ptx -- 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.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- 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] Problem with German Special characte rs (Ü etc.)
ym12de wrote: The problem definitively disappeared when I changed the path name .. When I copied the command that failed from the error window and pasted it to a console , it worked there .. Hans Am 16.04.2010 00:25, schrieb Bruno Postle: On Thu 15-Apr-2010 at 06:35 -0700, hans wrote: just found out that I get an error 255 when I try to generate control points if there is a German special character (Ü in my case) in the name of file paths. After replacing Ü by UE it worked. I am working with the latest trunk version on opensuse 11.2 I'm suprised you see this on Linux, this is a known problem with some (not all) Windows codepages. Testing with the Hugin trunk and autopano-sift-C-2.5.1, I don't see any problem on Linux, I can match photos with filenames like this: /home/bruno/photos/test-BrÜno/BrÜno-1.jpg It *might* be that the directory had been created longer ago on a system that uses iso-latin or alike, and now it's running on UTF-8. I had similar problems with old filenames that I'm carrying along for some 10 years already... Pit -- 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] SVN repository conversion - Important for past contributors
Lukáš Jirkovský wrote: if it means extra work for you I don't have any bigger problem with sourceforge user name. editing a text file with a few entries is no extra work, really. my current limitation is that all my office, including the server on which I have the mirrored SVN repository, is in boxes. If everything works as planned, I'll be unpacking it on Friday. Don't know yet how long it will take to reconnect to the internet, though. If the cold joint on my frankenbook does not get worse, I'll find a hotspot somewhere for the basics. have a good week 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: GSoC - Regression tests for pano13
Hi Daniel, According to your comments I rewrite again schedule. Time I can spend on the project: May 1 - June 28 – 20h, June 29 - end of GSoC – 40h (a full time worker). Smaller amount of hours in May and June is connected with my university duties. Schedule: Week 1 (May 1st - May 9th). Preparations (20h/week) - read documentation - write simple tests cases - construct a preliminary design of the tests/framework - getting ready - other? Week 2 - 7 (May 10th - June 20th). Creation of tests cases that stress the most important parts of the system (20h/week, 120h total) Week 2: PTmender tests cases - selection of images - creation of scripts - creation of reference output images - I had some experience with PTmender while I was doing vetting exercise, so I put this tool at the beginning Week 3: PTroller and PTtiff2psd tests cases - selection of images - creation of scripts - creation of reference output images - PTroller and PTtiff2psd seem to be a good start to learn more about the tools (May 24 - Students begin coding for their GSoC projects) Week 4: PTmasker, PTcrop and PTuncrop tests cases - selection of images - creation of scripts - creation of reference output images Week 5: PToptimizer tests cases - selection of images - creation of scripts - creation of reference output images - PToptimizer is one of the main tool in the library, so I put it in the ending of the list - at that moment I will have much more experience with the tools than at the beginning Week 6: PTBatcher tests cases - selection of *.pro files - creation of scripts - creation of reference - PTBatcher is almost at the end, because it combines tools listed above Week 7: Tests cases improvements - improving of tests cases - creation of documentation - creation of new test cases if necessary After each week of this phase I will deliver a new or improved set of tests and scripts I made for running those tests. At the end of week 7 I will deliver also a documentation. I'm not sure if this time order is right. Week 8 - 10 (June 21 - July 11). Creation of the framework (20h/week till June 28, 40h/week after June 29; 100h total). Week 8: Creation of the tool for the automatic testing based on the tests created, integrate with scripts created during last phase (creation of tests cases) - additionally still improving of tests cases - at the end of this week I will deliver a new tool for the framework Week 9: Adding new functionality for the framework - tool that simplifies the creation of new tests - improving of tests cases, again - at the end of this week I will deliver a new tool for the framework Week 10: Finalization of this sub-project - creation of documentation - improving of the framework code - checking, improving and adding test cases - submit mid-term evaluation (July 12 - Mentors and students can begin submitting mid-term evaluations) Function level testing framework - not ready, planning still in progress Week 12 (July 12 - July 18). Determine what functionality (what functions) need to be tested in function level testing framework (40h/ week). (July 16 - Mid-term evaluations deadline) Week 13 - Week 15 (July 19th - August 8th). Make framework for testing the main functionality of libpano as used by hugin (function level) (August 9 - Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc) Week 16 (August 9th - August 15th). Code improvements, tests, documentation,... (August 16 - Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google) (August 20 - Final evaluation deadline) Best regards, 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
Re: [hugin-ptx] [OSX] Hugin 2010.1.0 svn5031 bundle
Just realized that I still use the 5093 build... BTW I later succeeded somehow, so just for fun here are two panoramic sights from the restaurant right above the mountain station of the Lagazuoi cable car in the Dolomites: http://einem.net/berge/2010/100303-dolomiti/lagazuoi-1.html http://einem.net/berge/2010/100303-dolomiti/lagazuoi-2.html Let's see, first of all 5102 doesn't have the build number in the startup screen, one could think that this is already the 2010.1.0 release ;-) (On OS X 10.4) I Load Defaults in Preferences - CP Detectors tab. My default is now Pablo's patent free Panomatic using patfree-panomatic with args --sieve1size 20 --sieve2size 2 -o %o %i On my first attempt the images by accident had a -90 deg. roll in the pto file. Align didn't crash but finished without generating a single CP pair. After that I reset the roll values to 0, saved the project and pressed the Align button again. This time I got a wxExecute Error (Could not execute command: path/to/patfree-panomatic arguments) Also, no crash on the second run, but also no control points... Carl Harry van der Wolf schrieb am 19.04.10 21:00: Hi Carl, Sorry, I missed this mail completely. I don't know why. Is this still occuring in the 5102 build? Harry 2010/3/9 Carl von Einem c...@einem.net mailto:c...@einem.net Hoi Harry, patfree-panomatic crashed on my G5 / 10.4, see description below. I will try now the same in 10.5 on the same machine... I downloaded svn 5031, reset the CP detector settings as suggested below, made sure that Pablo's patent free Panomatic is set as default, and tried the Assistant tab with a handheld panorama from a Canon PowerShot G7. 21 images in portrait mode (2816 x 2112 pixels). Clicking button '2. Align...' leads to an error wxExecute Error: Could not execute command:... after showing the following lines in a progress window (I hope I was able to copy enough since the window was suddenly replaced with the error message in another window) Pan-o-matic 0.9.4 by Anael Orlinski - nao...@naouel.org mailto:nao...@naouel.org Output file : /private/var/tmp/folders.502/TemporaryItems/ap_resIv185G Number of CPU : 2 Input image options Downscale to half-size : yes Gradient based description Score threshold : 1000 Sieve 1 Options Width : 10 Height : 10 Size : 20 == Maximum keypoints per image : 2000 KDTree Options Search steps : 40 Second match distance : 0.15 Matching Options Mode : All pairs Distance threshold : 25 RANSAC Options Iterations : 1000 Distance threshold : 25 Sieve 2 Options Width : 5 Height : 5 Size : 2 == Maximum matches per image pair : 50 Input Files : - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120656_100-4029.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120704_100-4030.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120712_100-4031.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120720_100-4032.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120737_100-4033.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120744_100-4034.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120750_100-4035.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120757_100-4036.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120804_100-4037.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120811_100-4038.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120820_100-4039.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120845_100-4040.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120851_100-4041.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120922_100-4042.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120927_100-4043.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120934_100-4044.JPG - /Users/carl/Pictures/20100227-0306_Ski_ValBadia_Corvara/antje/img_4029-4049/aw_20100303-120952_100-4045.JPG -
[hugin-ptx] TIF compression
Does anyone know how the file compression works in hugin. TIFs are limited to 4GB, but there are compression options in hugin -- LZW, deflate, packbits. They yield pretty good compressions around 50 to 75% reduction. Does this reduction happen prior of the final image TIF assembly, or after. In other words if I'm generating a a 3gb tiff uncompressed and it ends up as 1GB, can I safely triple the size of the panorama or will that cause problems because the final output tif is generated first and then compressed. In this example that would be a 9GB uncompressed over double the limit before compression. And in a related question if I switched to PNG or JPG ouput, when are those files generated and does this get me past the 4GB TIF file size limit? Thanks Battle -- 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] Problem with German Special characte rs (Ü etc.)
On Mon 19-Apr-2010 at 14:54 +0200, ym12de wrote: Hi Pit, the directory is only a few months old and the filesystem itself also only some months older .. What is your default character set, i.e. what do you get from the `locale` command? (I would expect you to see de_DE.UTF-8 on a recent Linux system in a German locale). -- 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] (Patch-plugin practice) Enfuse and Enblend Gimp Plugins - Gsoc
Hi, Sorry for the late reply. I just got a chance to organize some source code files. I will have plenty of time in the summer (from May). Thank you very much for all suggestions of getting involved in open source development. It is really helpful. I am excited to contribute to Hugin and open source community. I learned quite a lot about open source before, but think taking some good actions from now is good. This Gsoc project will be a wonderful opportunity for me to start. I have uploaded some source code in Hugin Google Groups: http://groups.google.com/group/hugin-ptx/web/Sample%20source%20code.zip or, the Sample source code.zip file at: http://groups.google.com/group/hugin-ptx/files?upload=1 I also uploaded another zip file, Hugin patch-screenshots.zip, in the same directory. That is my patch work to support the application of Hugin Gsoc project, Enfuse and Enblend Gimp Plugins. I have write a description for those files in the first email. I have shared source code before, and I agree that it is really great to give back. Thank you. Elle. On Thu, Apr 15, 2010 at 9:12 AM, Yuval Levy goo...@levy.ch wrote: I should be packing boxes and the computer should be already in one of them. so concise and to the point: On April 15, 2010 01:24:13 am Elle Yan wrote: I should have asked how to send a patch. or read the messages on this mailing list. I think it was Antoine that asked. Learning from other peoples questions and answers is an important skill in Open Source. Since everyone in the mailing list can see the email addresses of the senders, why are they private information? everybody can see my phone number in the phone book but it is still private information and an unsolicited call on it without permission is not a good thing. ... maybe you can explain why I didn't notice you in this community before? I just started to communicate in the community recently. Before, when I reviewed the code base, and found very useful sources, I made use of them, e.g. spline.cpp. OpenSource 101: FEEDBACK. Saying Thank You when making use of the code. can you share some links to code you committed in the repository of the mentioned projects? I am happy to share some. I did not often commit to the repository of large software though. I don't expect you to have commit right to the repository of large software. OpenSource 102: Contribution starts with communication. Usually forwarding the changes to a maintainer (somebody with access to the repository); or publishing a patch somewhere. Subsequently the maintainer may or may not accept the patch. If the patch is accepted, it leaves a trace in a commit and most maintainers will credit the contributor in the commit log. For an example, see [0]. Usually, I code for the software out of my own interest or goal. For example, I code within the code base, to make and change some features as I needed. Or, I use their routines or libraries. It is not the formal commit. OpenSource 103: it is common for people to code out of their own interest. It's called scratch your itches. The spirit of Open Source is that when you make changes you publish them for the next person in your same situation. Sometimes this spirit is enshrined, to different extent, in the more or less permissive licenses. For smaller software, I did have many commits. It is open source projects locally in two universities. They do not currently have commit info on line publicly. Do they have the source code published in other form, e.g. a tarball? OpenSource 104: Giving back to the general public is key to be a good Open Source citizen. In the days prior to the internet, these were off line tools such as CDs, books, or other media. However, I have many written source code for projects mentioned. Please let me know if you need code samples. I have many of them for image processing purposes. Yes, please. Put them online somewhere and post links here. This GoogleGroup has a facility for uploading files, in case you want to use that as the online somewhere I mention above. Learning to use the communication tools is the very basic skills that you need to participate successfully in Open Source development. I appreciate your comments and correction. We all started from the same point where you are now. I am not sure if you have enough time to acquire the necessary skills to succeed in a GSoC project now. You definitely have enough time to acquire them and become an Open Source contributor in general. I recommend you learn about how Open Source works and start participating *publicly* on a smaller scale. There will be other opportunities (maybe GSoC 2011) for you to harness when you're ready. To finish on a positive note: in Open Source it is good to re-use what already exist and to credit those who have created it. You are already doing this quite well in your communication.
[hugin-ptx] Re: enblend out of memory error
HI Harry, I was able to download from source forge the enblend 4.0 version which contains both enblend-openmp and enfuse-opnemp which run in openmp and as 64bit. In you svn 5102 which is 32 bit kernal in the preferences area of Hugin I was able to specify that an alternate version of enblend (or enfuse) be used. It worked great. I was able to run an almost 100 image 12 mp/image pano. Activity monitor said real memory and virtual memory both peaked at about 12GB. So clearly there were no out of memory problems. The output was an a nice uncompressed 3GB TIF. Thanks for the pointers toward 64 bit enblend. Battle On Apr 17, 4:54 am, Harry van der Wolf hvdw...@gmail.com wrote: Hi, Somewhat delayed response as I have been on a business trip. This is already an error going way back due to memory allocation in a 32bit address space and fragmentation occurring in this 32bit memory address space, preventing programs from using it correctly/entirely. The first thing to mention though is that the mentioned enblend (and enfuse) is not 64bit openmp. It's a 32bit openmp build and that's also what I mentioned in the first 2 sentences of my mail (This time for the first time a Hugin bundle with an OpenMP enabled version of enblend and enfuse. It's a 32bit version of svn 5102.). Unless you use/build a 64bit enblend/enfuse, this problem will remain with large image sets. And even then you have to run Snow Leopard in 64bit mode. Leopard is always running in 32bit mode. Please be aware that even a 64bit SnowLeopard on fully 64bit Intel Macs ALWAYS run in 32bit mode, unless you tell the system otherwise on boot!! I will start a post about 32 bit/64bit for OSX, explaining some things as most users are not aware. And more important: I'm not sure yet what to do with the next builds. Hoi, Harry 2010/4/15 Battle battlebr...@gmail.com I'm gettitng an enblend out of memory error on a MacPro with Harry's 64bit openmp build svn 5102 This is a 66 image by 12MP pano running on a Mac Pro quad with 24GB memory and over a TB of disks space for swap. don't know what error code 12 is I think this is the final unconnected group being processed... any thoughts... enblend: info: combining non-overlapping images: col123merged_deryp0001.tif 1/1 col123merged_deryp0003.tif col123merged_deryp0006.tif col123merged_deryp0010.tif col123merged_deryp0015.tif col123merged_deryp0017.tif col123merged_deryp0021.tif col123merged_deryp0024.tif col123merged_deryp0049.tif col123merged_deryp0050.tif col123merged_deryp0051.tif col123merged_deryp0059.tif col123merged_deryp0063.tif enblend(2967,0xa0a2e4e0) malloc: *** mmap(size=553238528) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug enblend: out of memory enblend: std::bad_alloc enblend: info: remove invalid output image col123merged_deryp.tif gnumake: *** [col123merged_deryp.tif] Error 1 Thanks, Battle -- 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.comhugin-ptx%2bunsubscr...@googlegroups .com For more options, visit this group at http://groups.google.com/group/hugin-ptx To unsubscribe, reply using remove me as the subject. -- 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 athttp://groups.google.com/group/hugin-ptx -- 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
