[Hugin-devs] [Bug 679346] Re: nona: malloc: error: can't allocate region
*** This bug is a duplicate of bug 678946 *** https://bugs.launchpad.net/bugs/678946 ** This bug has been marked a duplicate of bug 678946 nona: bad allocation with high-resolution panorama * You can subscribe to bug 678946 by following this link: https://bugs.launchpad.net/hugin/+bug/678946/+subscribe -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679346 Title: nona: malloc: error: can't allocate region Status in Hugin - Panorama Tools GUI: New Bug description: Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] /Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Stitch4 -i 0 /var/folders/fZ/fZBNn1QtFSKWgk9JA6q9HU+++TI/-Tmp-/huginpto_hrRrMa nona(2443) malloc: *** mmap(size=2839310336) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug caught exception: St9bad_alloc gnumake: *** [Stitch4.tif] Error 1 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679347] Re: OS X: nona: malloc: mmap failed
*** This bug is a duplicate of bug 678946 *** https://bugs.launchpad.net/bugs/678946 ** This bug has been marked a duplicate of bug 678946 nona: bad allocation with high-resolution panorama * You can subscribe to bug 678946 by following this link: https://bugs.launchpad.net/hugin/+bug/678946/+subscribe -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679347 Title: OS X: nona: malloc: mmap failed Status in Hugin - Panorama Tools GUI: Incomplete Bug description: Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] /Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Stitch4 -i 0 /var/folders/fZ/fZBNn1QtFSKWgk9JA6q9HU+++TI/-Tmp-/huginpto_hrRrMa nona(2443) malloc: *** mmap(size=2839310336) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug caught exception: St9bad_alloc gnumake: *** [Stitch4.tif] Error 1 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678848] Re: matchpoint fails on images with alpha channels
Someone should check if this is still valid. But it sounds like a valid request to me. ** Changed in: hugin Importance: Undecided = Wishlist ** Changed in: hugin Status: New = Triaged ** Tags added: alpha channel matchpoint -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678848 Title: matchpoint fails on images with alpha channels Status in Hugin - Panorama Tools GUI: Triaged Bug description: match-n-shift uses PTmender to create conformal input for generatekeys/matchpoint, this data has an alpha channel, which causes matchpoint to fail: ContractViolation: Precondition violation! importImage(): number of bands (color channels) in file and destination image differ. (/BUILD/hugin-0.7.0/src/foreign/vigra/vigra/impex.hxx:118) Error! Image can not be opened matchpoint should ignore alpha data, or even better it could use the alpha channel to define areas where it shouldn't find features. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678821] Re: hugin hangs when autopano returns and --maxmatches is set
I have tested this, and this set of images comes out just fine when I run it through hugin. Apparently fix released in the last two years. ** Changed in: hugin Importance: Undecided = Medium ** Changed in: hugin Status: New = Fix Released ** Tags added: autopano-sift-c hang -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678821 Title: hugin hangs when autopano returns and --maxmatches is set Status in Hugin - Panorama Tools GUI: Fix Released Bug description: When I run a specific set of images through autopano-sift-c from hugin and autopano paramters are--maxmatches %p %o %i, hugin hangs when the dialog determining placement of images is shown (on my machine at around 6 minutes, the time varies). The hang is permanent, hugin is no longer responding to mouse events. The set of images can be downloaded at http://margo.student.utwente.nl/simon/temp/wall.zip The problem goes away when I change the autopano parameters to just %o %i. Cheers Simon PS, see also discussion at: http://groups.google.com/group/hugin-ptx/browse_thread/thread/9ac67e3dfc288c53/53bbfb0ed20ee3a7#53bbfb0ed20ee3a7 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678935] Re: Blended Panorama (enfuse) - invalid parameters
Careful examination shows that you're enblend-ing a stack that should be enfused. Could this be a user-error? The stitcher tab has been changed, and will change even more. ** Changed in: hugin Status: New = Invalid ** Changed in: hugin Importance: Undecided = Low ** Tags added: enblend stitcher-tab -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678935 Title: Blended Panorama (enfuse) - invalid parameters Status in Hugin - Panorama Tools GUI: Invalid Bug description: SVN3245 Windows XP * 18 images, 3 exposures, HDR * in the stitcher tab, output is set to Blended panorama (enfuse) * processing is left to default and it shows remapper: nona, image fusion: enfuse, blender:enblend (do I need a blender for exposure blending?) * file formats set to EXR for both Normal Output and HDR Output. * the resulting error is below (but is not really relevant). * leftover files were all 8bit TIFF: 18 LDR images and six enfusions of the stacks * i suspect the next stage would have been to blend the enfusions together - and my suspicion was confirmed when I set the file formats for both Normal Output and HDR Output to TIFF and run the process again. to say the least, the user interface to the process is confusing. For the current release, I suggest to write some clear manual pages about the stitcher tab and try to explain it to the user as it stands now. For after release, we need to redesign the stitcher tab. ERROR REPORT C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 0 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 1 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 2 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\enfuse -w -o exr-enblend__stack_ldr_.tif exr-enblend__exposure_layers_.tif exr-enblend__exposure_layers_0001.tif exr-enblend__exposure_layers_0002.tif Loading next image: exr-enblend__exposure_layers_.tif Loading next image: exr-enblend__exposure_layers_0001.tif Loading next image: exr-enblend__exposure_layers_0002.tif Using 10 blending levels enblend: image geometry precludes using more than 10 levels. Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Collapsing Laplacian pyramid: l9 l8 l7 l6 l5 l4 l3 l2 l1 l0 C:\Program\ Files\Hugin\bin\exiftool -overwrite_original_in_place -TagsFromFile I:\080601arnd\02\02a_MG_2100.tif -ImageDescription -Make -Model -Artist -WhitePoint -Copyright -GPS:all -DateTimeOriginal -CreateDate -UserComment -ColorSpace -OwnerName -SerialNumber exr-enblend__stack_ldr_.tif 1 image files updated C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 3 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 4 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\nona -r ldr -e 0 -m TIFF_m -o exr-enblend__exposure_layers_ -i 5 C:\DOCUME~1\coolblu\LOCALS~1\Temp\hug8F.tmp C:\Program\ Files\Hugin\bin\enfuse -w -o exr-enblend__stack_ldr_0001.tif exr-enblend__exposure_layers_0003.tif exr-enblend__exposure_layers_0004.tif exr-enblend__exposure_layers_0005.tif Loading next image: exr-enblend__exposure_layers_0003.tif Loading next image: exr-enblend__exposure_layers_0004.tif Loading next image: exr-enblend__exposure_layers_0005.tif Using 10 blending levels enblend: image geometry precludes using more than 10 levels. Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7 l8 l9 Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 Collapsing Laplacian pyramid: l9 l8 l7 l6 l5 l4 l3 l2 l1 l0 C:\Program\ Files\Hugin\bin\exiftool -overwrite_original_in_place -TagsFromFile I:\080601arnd\02\02a_MG_2100.tif -ImageDescription -Make -Model -Artist -WhitePoint
[Hugin-devs] [Bug 678960] Re: Error during stitching
Probably user error: Nona couldn't find the source image. ** Tags added: nona precondition ** Changed in: hugin Importance: Undecided = Low ** Changed in: hugin Status: New = Invalid -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678960 Title: Error during stitching Status in Hugin - Panorama Tools GUI: Invalid Bug description: C:\Programmi\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o yyy -i 0 C:\DOCUME~1\VALENT~1\IMPOST~1\Temp\hug26.tmp ContractViolation: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. caught exception: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. make: *** [yyy.tif] Error 1 i follow all the tutorial steps, save the fila in jpg. what can be happened? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679402] Re: Display corruption in CP tab drop down menu
There is a workaround, (hover over the menu items). Does this still happen? Can anybody reproduce this with 2010.4 ? ** Changed in: hugin Status: New = Incomplete ** Changed in: hugin Importance: Undecided = Low ** Tags added: controlpoint-tab corruption display -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679402 Title: Display corruption in CP tab drop down menu Status in Hugin - Panorama Tools GUI: Incomplete Bug description: Display corruption in CP tab drop down menu. It however disappears once user hovers over the menu items. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679418] Re: wrong crop factor after reduce size
This is probably due to the other scaling program doing something wrong / unexpected. ** Changed in: hugin Importance: Undecided = Low ** Changed in: hugin Importance: Low = Wishlist ** Changed in: hugin Status: New = Triaged ** Tags added: crop factor fov -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679418 Title: wrong crop factor after reduce size Status in Hugin - Panorama Tools GUI: Triaged Bug description: Hi, I am accustomed to reducing the images size before stitching with Hugin. With the version 0.7 beta 3, it did not have there a problem. Since, all the other versions give an erroneous crop Factor. Whereas it is of 1.6 on the image, it becomes 7.6 and wrong after reduction of the image. So the FOV is wrong too. I use Photosop CS4 or the Freeware Xnview to reduce size and the problem is the same with this two softawre. Sorry for my bad english. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679398] Re: autopano-sift-c crashes with very wide photos
** Tags added: autopano-sift-c fisheye projection ** Changed in: hugin Importance: Undecided = Medium ** Changed in: hugin Status: New = Triaged -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679398 Title: autopano-sift-c crashes with very wide photos Status in Hugin - Panorama Tools GUI: Triaged Bug description: With autopano-sift-C 2.5.1 An 8mm fisheye on a full size sensor produces a landscape orientation photo with an angle of view of 260 degrees, calling apsc like this results in no features identified and a segfault: autopano-sift-c --projection 2,260 output.pto *.JPG The transition is sudden: 223, 224, 225 degrees are fine and hundreds of features are detected. 226 degrees and above and 0 features are detected and matching produces a segfault. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679424] Re: BUG: less than three neighbours! (autopano-sift-c)
Oh. If it crashes, can you post the images so that we can check if it happens cross-platform, and that someone with coding skills can run with your images inside the debugger. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679424 Title: BUG: less than three neighbours! (autopano-sift-c) Status in Hugin - Panorama Tools GUI: Incomplete Bug description: I have tried autopano-sift-c on two different sets of images with the command autopano-sift-c --maxdim 4800 --refine --keep-unrefinable 0 --ransac 0 --maxmatches 25 with_control_points.pto images_only.pto, and both resulted in autopano-sift-c terminating with the message BUG: less than three neighbours! I am using version 2.5.1 Let me know if you need any additional information. I do have a debugger installed, you need me to try anything. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679421] Re: enblend default arguments are not (allways) written to *pto
save / load should not lead to different results ** Changed in: hugin Importance: Undecided = Medium ** Changed in: hugin Status: New = Triaged ** Tags added: preference pto save -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679421 Title: enblend default arguments are not (allways) written to *pto Status in Hugin - Panorama Tools GUI: Triaged Bug description: Enblend default arguments that are added in the hugin preferences menu are kept globally. This may be a bug or a feature. As one normally doesn't need any refinements and if any supplementary arguments are added these will be rather special I tend to call it a bug. The main problem is: These arguments are only written to the *pto and *pto.mk the time you add them. For any other project opened later the arguments are still present in the preference menu but are not written to *pto or *pto.mk when the protect is saved. This is certainly a bug. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679451] Re: enblend.exe error -1073741795
Build problem? The program enblend fails to start, giving an immediate error. This is so basic, someone will show up with a bug report if this still happens. ** Tags added: build enblend ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679451 Title: enblend.exe error -1073741795 Status in Hugin - Panorama Tools GUI: Fix Released Bug description: When stitching the panorama the enblend.exe crashes and the following text is shown: D:\Archivos\ de\ programa\Hugin\bin\nona -r ldr -m TIFF_m -o casa -i 0 C:\WINDOWS\TEMP\hug13A9.tmp D:\Archivos\ de\ programa\Hugin\bin\nona -r ldr -m TIFF_m -o casa -i 1 C:\WINDOWS\TEMP\hug13A9.tmp D:\Archivos\ de\ programa\Hugin\bin\nona -r ldr -m TIFF_m -o casa -i 2 C:\WINDOWS\TEMP\hug13A9.tmp D:\Archivos\ de\ programa\Hugin\bin\nona -r ldr -m TIFF_m -o casa -i 3 C:\WINDOWS\TEMP\hug13A9.tmp D:\Archivos\ de\ programa\Hugin\bin\enblend -f4090x3473 -o casa.png casa.tif casa0001.tif casa0002.tif casa0003.tif make: *** [casa.png] Error -1073741795 I updated the Visual C runtime but it did not work. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679461] Re: error during panorama creation
It should be using enfuse. I think modern Hugin now detects this situation and calls the right programs. ** Changed in: hugin Importance: Undecided = Medium ** Changed in: hugin Status: New = Fix Released ** Tags added: enblend enfuse hdr -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679461 Title: error during panorama creation Status in Hugin - Panorama Tools GUI: Fix Released Bug description: Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 0 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 1 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 2 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 3 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 4 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 7 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 12 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 13 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 14 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 15 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 16 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 17 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 18 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 19 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/nona -z PACKBITS -r ldr -m TIFF_m -o Kilbane\ HeadTest -i 20 /var/folders/BS/BSCOSY7SE2amNNknI3lXeE+++TI/-Tmp-/huginpto_SOdc8G /Applications/media/pics/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/enblend --compression NONE -f5145x677+130+405 -o Kilbane\ HeadTest.tif Kilbane\ HeadTest.tif Kilbane\ HeadTest0001.tif Kilbane\ HeadTest0002.tif Kilbane\ HeadTest0003.tif Kilbane\ HeadTest0004.tif Kilbane\ HeadTest0007.tif Kilbane\ HeadTest0012.tif Kilbane\ HeadTest0013.tif Kilbane\ HeadTest0014.tif Kilbane\ HeadTest0015.tif Kilbane\ HeadTest0016.tif Kilbane\ HeadTest0017.tif Kilbane\ HeadTest0018.tif Kilbane\ HeadTest0019.tif Kilbane\ HeadTest0020.tif enblend: info: loading next image: Kilbane HeadTest.tif 1/1 enblend: info: loading next image: Kilbane HeadTest0001.tif 1/1 enblend: excessive overlap detected; remove one of the images enblend: info: remove invalid output image Kilbane HeadTest.tif gnumake: *** [Kilbane HeadTest.tif] Error 1 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe :
[Hugin-devs] [Bug 679854] Re: Multiple Images, same control point
** Tags added: controlpoint controlpoint-tab gui ** Changed in: hugin Importance: Undecided = Wishlist ** Changed in: hugin Status: New = Triaged -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679854 Title: Multiple Images, same control point Status in Hugin - Panorama Tools GUI: Triaged Bug description: When shooting a large panorama, it's good practice to have fairly large overlap. This means that a given point can appear in 3 or more frames. It would be helpful to be able to be able to a control point that can span all relevant frames, instead of just two of them. This might also be very helpful in figuring out the 3d relationships between points in a panorama, and dealing with camera shift resulting from differing distance from the lens. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
enblend got the composition of the TMPDIR variable wrong. IIRC this has been fixed or is being fixed. Please check that it still happens on 2010.4. It fails to make the tmp file NAME. Not that the disk fills after writing a little bit to the temp file ** Tags added: enblend tmpdir ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679858] Re: nona should scale non-float HDR output files
I think the concept should be that the 065535 range and 0..255 range are considered to be 0..1 ranges. That's the only way to get consistent results. (otherwise a float file that started out as bytes might have a 0...255 range. (this is so stupid we already don't do it). ) ** Changed in: hugin Importance: Undecided = Wishlist ** Changed in: hugin Status: New = Triaged ** Tags added: hdr nona -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679858 Title: nona should scale non-float HDR output files Status in Hugin - Panorama Tools GUI: Triaged Bug description: If nona is used with the HDR option (-r hdr) and a pixel type other than FLOAT (e.g. UINT16), the output is still in the range 0..1 rather than 0..65535.This particular combination of options is useful in aligning 16-bit linear files without converting to EXR or HDR. Note that this can be worked around by setting the EV of the input images to 16. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 684859] Re: Nona phase should use all CPUs on big stitch
Someone wrote to tell me this is purely user-error: nona has a -t 1 option to restrict it to one thread. and hugin has a make options entry where I can set -j 2 to use two CPUs. ** Changed in: hugin Status: Triaged = Fix Released -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/684859 Title: Nona phase should use all CPUs on big stitch Status in Hugin - Panorama Tools GUI: Fix Released Bug description: Although nona is said to use all available CPUs, my CPU graph shows otherwise. The issue is that when i'm working on a big project (where i'd expect the multi-cpu to be extra useful), the images are downscaled significantly. Thus the phase that nona executes multi-cpu is short. The single-threaded pre and post processing take up about half the time. As I have plenty of memory I'd gladly tell make to start two or three concurrent nona processes to keep my CPU busy. Suggestion: preference setting: how many nona processes should run concurrently ? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679974] Re: Allow assignment of image priorities
** Tags added: image priority -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679974 Title: Allow assignment of image priorities Status in Hugin - Panorama Tools GUI: Triaged Bug description: Dear Hugin Developers, I would love to see a feature in Hugin that allows to prioritize the usage of certain images when stitching a panorama over others. Rationale: When I use hugin to stitch panoramas of landscapes that have significant details/features only in part of the whole panorama (like e.g. the image of desert with a tower visible, that has interesting ornaments) I use different focal lengths - short ones for the parts where little detail is to see, and zoomed images of the parts where lots of details are to see. I guess this is a common approach used by many users. The problem is that while Hugin even detects and reports automatically there is redundant coverage of certain image areas, there seems to be no way to tell Hugin Yes, I know, please prefer the long-focal-length pictures whereever available. I can try to workaround by using the crop feature to crop all the wide angle pictures such that they do not overlap the zoomed in ones anymore, but that is an extremely tedious task especially if there are lots of pictures to stitch and when the difference in focal lengths is big. I hope I haven't missed to spot an already existing feature like that, but searching for it didn't reveal any. Regards, Peter Niemayer ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679974] Re: Allow assignment of image priorities
Ah the commentbox has proportional font while the comment finally shows in fixed-width font. Anyway it still comes out reasonably. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679974 Title: Allow assignment of image priorities Status in Hugin - Panorama Tools GUI: Triaged Bug description: Dear Hugin Developers, I would love to see a feature in Hugin that allows to prioritize the usage of certain images when stitching a panorama over others. Rationale: When I use hugin to stitch panoramas of landscapes that have significant details/features only in part of the whole panorama (like e.g. the image of desert with a tower visible, that has interesting ornaments) I use different focal lengths - short ones for the parts where little detail is to see, and zoomed images of the parts where lots of details are to see. I guess this is a common approach used by many users. The problem is that while Hugin even detects and reports automatically there is redundant coverage of certain image areas, there seems to be no way to tell Hugin Yes, I know, please prefer the long-focal-length pictures whereever available. I can try to workaround by using the crop feature to crop all the wide angle pictures such that they do not overlap the zoomed in ones anymore, but that is an extremely tedious task especially if there are lots of pictures to stitch and when the difference in focal lengths is big. I hope I haven't missed to spot an already existing feature like that, but searching for it didn't reveal any. Regards, Peter Niemayer ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679974] Re: Allow assignment of image priorities
Could we use the alpha channel to indicate an image priority? alpha=0 - no image data. alpha=1.0 - normal: use this image. alpha1 alpha2 - prefer using image 2. this would lead to special case of alpha 1.0. It should be considered medium priority where images can come above and below. It would be most consistent, but have a painful transition period if we'd set the alpha to 0.5 by default. Suppose I have two images. 111 ...222... Of course 2 was taken with longer focal length, so it has more details. So I'd prefer image 2 to image 1. Currently enblend would say something like excessive overlap, and forget all about image 2. In fact it should cut everything on image 1 that is far from the edge of image 2 away and then do a normal blend. Of course this requires some interesting coding in enblend.. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679974 Title: Allow assignment of image priorities Status in Hugin - Panorama Tools GUI: Triaged Bug description: Dear Hugin Developers, I would love to see a feature in Hugin that allows to prioritize the usage of certain images when stitching a panorama over others. Rationale: When I use hugin to stitch panoramas of landscapes that have significant details/features only in part of the whole panorama (like e.g. the image of desert with a tower visible, that has interesting ornaments) I use different focal lengths - short ones for the parts where little detail is to see, and zoomed images of the parts where lots of details are to see. I guess this is a common approach used by many users. The problem is that while Hugin even detects and reports automatically there is redundant coverage of certain image areas, there seems to be no way to tell Hugin Yes, I know, please prefer the long-focal-length pictures whereever available. I can try to workaround by using the crop feature to crop all the wide angle pictures such that they do not overlap the zoomed in ones anymore, but that is an extremely tedious task especially if there are lots of pictures to stitch and when the difference in focal lengths is big. I hope I haven't missed to spot an already existing feature like that, but searching for it didn't reveal any. Regards, Peter Niemayer ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685703] Re: Selecting New project leaves old project image displayed
haha! yes it does. Confirmed in 2010.4.beta ** Tags added: imagestab newproject ** Changed in: hugin Status: New = Confirmed ** Changed in: hugin Importance: Undecided = Medium ** Changed in: hugin Importance: Medium = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685703 Title: Selecting New project leaves old project image displayed Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I am running a build of hugin-2010.5.0 (rev f2522064a8f3). Having worked through a project, I select File new to start a new project. The images tab continues to display the last selected image from the previous project. Probably not a serious issue, but indicates that all is not being cleaned up. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685703] Re: Selecting New project leaves old project image displayed
This bug doesn't make the program unusable, so confirmed/low prio for now. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685703 Title: Selecting New project leaves old project image displayed Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I am running a build of hugin-2010.5.0 (rev f2522064a8f3). Having worked through a project, I select File new to start a new project. The images tab continues to display the last selected image from the previous project. Probably not a serious issue, but indicates that all is not being cleaned up. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679777] Re: image format selection fails
Ooops. Seems to have been fixed somewhere in the last six years. ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = High -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679777 Title: image format selection fails Status in Hugin - Panorama Tools GUI: Fix Released Bug description: When choosing 'image format' In Sticher tab, Output File Options, the selection is changed to an other one (two apart before the wanted one). This appears only if a change has been made. For example, selecting 'Layered PSD with masks' reverts immediately to 'PSD' (diplayed in combobox and visible in script). Stiching with layered 'PSD with mask' can be achieved by selecting 'IVR' in the list ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679591] Re: unhandled exception manually setting cp more than 12 pics
Tom, we're working on 2010.4 right now. 2009.4 has at least been superseded by 2010.2. Can you reproduce this on a recent version? I can definitely scroll beyond 13 images on my system 2010.4beta and Linux ** Changed in: hugin Status: New = Incomplete ** Changed in: hugin Importance: Undecided = Medium -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679591 Title: unhandled exception manually setting cp more than 12 pics Status in Hugin - Panorama Tools GUI: Incomplete Bug description: In projects with more than 12 pics I always get an unhandled exception while setting control points manually and changing in the control point editor from the picture pair 11/12 to 12/13. It seems not due to setting the cp but simply by reaching the 13th picture in the control point editor. And it's not project or picture specific as I got it also with other projects with different pics. There is no problem when I use autopano-sift-c an let the cp set automatically. I work with 16bit TIFFs, Hugin Version 2009.4.0 and Win XP 32bit. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679545] Re: Error during stitching
Too little context. Not a bug but an installation problem. ** Changed in: hugin Status: New = Invalid ** Changed in: hugin Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679545 Title: Error during stitching Status in Hugin - Panorama Tools GUI: Invalid Bug description: C:\Users\rex\AppData\Local\Temp\hugF02A.tmp:199: Malformed per-target variable definition make: Interrupt/Exception caught (code = 0xc005, addr = 0x40e480) --- This error appears with all projects (i've just installed hugin) I will try to play with options, but all tips are welcome ;] ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678936] Re: enblend fails on EXR (hdr) blending
Seems similar to bug #679520 . (black areas. ). I'm starting to suspect enblend has an uninitialized memory access somewhere. This leads to ugly stripes in some cases, and black areas in others. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678936 Title: enblend fails on EXR (hdr) blending Status in Hugin - Panorama Tools GUI: New Bug description: I think I came across a bug in enblend (CVS20080718), but since there is no bug tracker in enblend, I document it here. I was testing thoroughly hugin SVN3251 in both Windows XP and Ubuntu Linux 8.04. The box is an AMD 2x 6000+ with 6GB RAM and I made sure I had plenty of HDD space. The project: A full spherical panorama, six shots around, three exposures each, output resolution 7000x3500. enfuse went through it no problems (although I identified some cosmetic issues in the user interface to it through hugin http://sourceforge.net/tracker/index.php?func=detailaid=2032140group_id=77506atid=550441) then I went for the fully fledged HDR. The process seemed to run well through hugin (although it was taking a lot more time than PTGui 8beta6 or Autopano Pro 1.4.2). I let hugin retain all byproducts (individual non merged images and stacked HDR images) which all looked good. But the blend was just mostly black with some areas from the panorama. This happened in both Windows and Linux, with two different outputs. Then I run the process from the command line in Windows and the output was once again different but not correct. When I blend only the first two stacks from the CLI, the output is OK. The first three stacks, I get a bit of black areas again. The second pair of stacks blended well. The last pair of stack had a large black area. Trying to add an additional stack to one of the first two blendings also results in black areas. At http://www.photopla.net/hugin/hdr/enblend-hdr-errors.7z you will find the first three test blends (from hugin in windows and linux, and from the CLI). ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679520] Re: hdrmerge fails due to differing image sizes
Zach, Amidee, PLEASE upload the images somewhere so that we can try to reproduce it on a developer's machine. If all else fails, Email me the images. You might have to split things because your mail system doesn't handle large files. But I can handle up to 100Mb just fine. ** Changed in: hugin Status: New = Triaged ** Changed in: hugin Importance: Undecided = Medium -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679520 Title: hdrmerge fails due to differing image sizes Status in Hugin - Panorama Tools GUI: Triaged Bug description: I get this message (and another telling me to post it here) while stitching an HDR panorama: hugin_hdrmerge -m khan -i 4 -s 30.00 -o _MG_7820-_MG_7855_stack_hdr_.exr _MG_7820-_MG_7855_hdr_.exr _MG_7820-_MG_7855_hdr_0001.exr _MG_7820-_MG_7855_hdr_0002.exr caught exception: Input images must have the same dimensions make: *** [_MG_7820-_MG_7855_stack_hdr_.exr] aborted There are two stacks with 3 images each. I get the individual TIFFs, I can build 3 panoramas for the different exposures, but merging the first stack fails because the first of the three TIFFs from the first stack (and in consequence the EXRs) is just slightly wider than the others, for no apparent reason. I tried to make a series of these panoramas in batch mode, and some failed this way, others worked. I can't seem to find out what makes the difference. I could post the project, but the files have 13 MB combined, so I'd better ask before uploading. I'm on Linux, using version 2010.0.0-12.6 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679397] Re: Error during stitching
What version? What OS? How large are your images? We have plenty of these bugs in the datbase, I'm retiring this one, with so little info, it isn't worth the trouble to find the others, and mark as duplicate. ** Tags added: malloc nona ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679397 Title: Error during stitching Status in Hugin - Panorama Tools GUI: Fix Released Bug description: I receive the following error during stitching of stereographic image no problems with equirectangular image C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o island -i 0 C:\DOCUME~1\me\LOCALS~1\Temp\hug12.tmp caught exception: bad allocation make: *** [island.tif] Error 1 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679396] Re: Unknown exception on Albers Equal Area Conic
It is stitching my 0.5gigapixel albers-equal-area pano just fine right now. cannot reproduce. Probably fixed. shabeker, please reopen if you still have this in 2010.4beta ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = Medium -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679396 Title: Unknown exception on Albers Equal Area Conic Status in Hugin - Panorama Tools GUI: Fix Released Bug description: I tried to create a 360 degree circle view using the Albers Equal Area Conic projection with phi1 90 and phi2 90, but this leads to the following error when creating the panorama. The error message asked me to post this in the bug tracker: C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o Panorama -i 0 C:\Users\myUser\AppData\Local\Temp\hugC630.tmp caught exception: Unknown exception make: *** [Panorama.tif] Error 1 ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679383] Re: HDR export failure (improper stacking?)
** Tags added: identification stack ** Tags added: enblend hugin -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679383 Title: HDR export failure (improper stacking?) Status in Hugin - Panorama Tools GUI: New Bug description: hugin 2009.2 on OS X 10.6.2 Failure to generate HDR output (TIF or EXR). Input was three bracketed sets of 6 fisheye images (total of 18) defining a 5 around/1 zenith, 360 degree panorama. Blended exposure output is fine, but HDR output failed with gnumake: *** [ptoHDR_hdr.tif] Error 1. Full trace is attached. It appears that the stacks are not being properly identified. Images (0, 6, 12), (1,7,13) etc. should be stacked. However stacks (3,9,15), the image crossing the 360 boundary, and (5,11,17), the zenith, are not properly stacked. I do have another 360 project with bracketed exposures (just two) that works properly, so my installation appears to be good. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678763] Re: Pano13: struct Image initialization error
If this is the one can you move this to fix comitted? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678763 Title: Pano13: struct Image initialization error Status in Hugin - Panorama Tools GUI: Confirmed Bug description: The Pano13 source in the hugin SDK has a typo in line 849 of filter.c, in function SetImageDefaults(). It reads bzero(im-formatParam, sizeof(im-precomputedValue)); but should be bzero(im-precomputedValue, sizeof(im-precomputedValue)); This leaves 4 of the precomputed values uninitialized since formatParam starts 4 words before precomputedValue and overwrites precomputedCount with (another) zero. Unlikely to cause malfunction. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679917] Re: Backup copy of project.
I have a better patch that fixes most of the problems. I can't decide on a proper autosave place such that running multiple hugin instances works. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679917 Title: Backup copy of project. Status in Hugin - Panorama Tools GUI: Confirmed Bug description: Hugin just crashed on me. Pre 0.7.0 this happened so often that I knew I had to save often, or risk losing my work. So far this is the first since I went to 0.7.0. Now 0.8.0 crashed on me However I'm most pissed that a pto file got saved to run nona, but this gets (I think) cleaned up after running nona. So now I'm left with a project file with hours of work missing. PLEASE write a backup pto file where I can find it, or mention this project had unsaved changes when hugin crashed, load the backup file? when I start it. (then I don't need to know where the backup is stored...). ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679199] Re: hugin-0.8.0_rc1 creates artifacts
A friend found a workaround to reduce/remove the stripes in the images: Increase the imagecache size. This reduces the amount of artifacts. In his case to none. this is usable for those blends where RAM is sufficent to hold everything (but not the default 1Gb). This is a hint that the problem lies in the imagecache code. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679199 Title: hugin-0.8.0_rc1 creates artifacts Status in Hugin - Panorama Tools GUI: New Bug description: Hi I'm using hugin-0.8.0_rc1 with libpano13-2.9.14_rc1 And it creates a lot of artifacts on huge panoramas. http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP.png http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-3.png And a line in the middle http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-1.png The image: http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-2.png I had to create screenshots since gimp didn't allow me to save the image (not enough ram). Here's the file hugin created: http://downloads.mop.com/panoramabug/pano5.png (402mb -- needs at least 6.6gb ram to display). It has a size of 61638x10876 pixels ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685962] Re: setting for temporary directory/files.
*** This bug is a duplicate of bug 678632 *** https://bugs.launchpad.net/bugs/678632 ** This bug has been marked a duplicate of bug 678632 Windows uses current directory for temporary files * You can subscribe to bug 678632 by following this link: https://bugs.launchpad.net/hugin/+bug/678632/+subscribe -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685962 Title: setting for temporary directory/files. Status in Hugin - Panorama Tools GUI: Triaged Bug description: In hugin you can set the directory for temporary files. It seems this is not correctly passed on to Makefiles and/or enblend. To make sure we don't forget about checking this I'm submitting this as a wishlist item: Please make the temporary files setting work across the line ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685959] Re: create source images from PTO file.
ptodummy is a perl cript that does exactly this:http://search.cpan.org/dist/Panotools-Script/bin/ptodummy. It is a part of the Panotools::Script collection of useful perl scripts. I don't think such a specialized bug analysis tools needs to be implemented within hugin itself, therefore setting to Fix released. ** Changed in: hugin Status: Triaged = Fix Released -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685959 Title: create source images from PTO file. Status in Hugin - Panorama Tools GUI: Fix Released Bug description: For bughunting it would be very useful if I can easily create a sample set of images that for most purposes would be useful as test-case images if a reporter only submits a PTO file. for each image in the PTO file, generate an image (with the name of the image in the pixels) of the specified size and type ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685582] Re: enblend wrong lib extension
This looks a lot like a packaging problem. Where did you get your hugin from? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685582 Title: enblend wrong lib extension Status in Hugin - Panorama Tools GUI: Confirmed Bug description: When trying to stitch some photos, I kept getting errors similar to the following: enblend --compression=LZW -f3000x1500 -o PICT0828-PICT0832.tif PICT0828-PICT0832.tif PICT0828-PICT08320001.tif PICT0828-PICT08320002.tif PICT0828-PICT08320003.tif PICT0828-PICT08320004.tif enblend: error while loading shared libraries: libImath.so.2: cannot open shared object file: No such file or directory make: *** [PICT0828-PICT0832.tif] Error 127 To fix the issue I made a symbolic link to the lib as follows: sudo ln -s /usr/lib/libIlmImf.so.6.0.0 /usr/lib/libIlmImf.so.2 sudo ln -s /usr/lib/libImath.so.6.0.0 /usr/lib/libImath.so.2 sudo ln -s /usr/lib/libHalf.so.6.0.0 /usr/lib/libHalf.so.2 sudo ln -s /usr/lib/libIex.so.6.0.0 /usr/lib/libIex.so.2 Machine is running Lucid. Also attached one of the Hugin logs. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679398] Re: autopano-sift-c crashes with very wide photos
With a current snapshot this happens as well. Occurs with portait images of 2920x4386 when going from 199 degrees to 200 degrees fov. I have spend a bit of time trying to hunt this bug down. Preliminary result: 1. During image remapping in saRemap.c, saRemap_new(...) x[i] in this line y[i] = CamLens_RofA( pd, CamLens_AofR( ps, x[i] ) ) becomes Pi. 2. Therefore the calls to CamLens_RofA( pd, CamLens_AofR( ps, x[i] ) ) (itself calling a2r_ster which calculates tan(0.5 * x[i] ) returns a negative value for y[i]. 3. The negative value for y[i] makes the monoticity test of the following spline evaluation fail, making the whole saRemap_new return 0 and autopano-sift-c segfault when saRemap_inv tries to dereference the null pointer. Questions: A comment in CamLens.c indicates that A (or x[i] in the above) should be Pi for stereographic projection. Does this make sense? How did we end up with it being greater? Why does this trigger at fov 199 in portrait and 225 in landscape? Should we just remap all x pi to x = pi to get rid of the problem? Sorry for the chaotic braindump above, I need to go to sleep now and need to write the stuff down, otherwise a start from scratch is needed when I'm looking at the problem again. Regards Felix -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679398 Title: autopano-sift-c crashes with very wide photos Status in Hugin - Panorama Tools GUI: Triaged Bug description: With autopano-sift-C 2.5.1 An 8mm fisheye on a full size sensor produces a landscape orientation photo with an angle of view of 260 degrees, calling apsc like this results in no features identified and a segfault: autopano-sift-c --projection 2,260 output.pto *.JPG The transition is sudden: 223, 224, 225 degrees are fine and hundreds of features are detected. 226 degrees and above and 0 features are detected and matching produces a segfault. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679398] Re: autopano-sift-c crashes with very wide photos
** Changed in: hugin Status: Triaged = Confirmed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679398 Title: autopano-sift-c crashes with very wide photos Status in Hugin - Panorama Tools GUI: Confirmed Bug description: With autopano-sift-C 2.5.1 An 8mm fisheye on a full size sensor produces a landscape orientation photo with an angle of view of 260 degrees, calling apsc like this results in no features identified and a segfault: autopano-sift-c --projection 2,260 output.pto *.JPG The transition is sudden: 223, 224, 225 degrees are fine and hundreds of features are detected. 226 degrees and above and 0 features are detected and matching produces a segfault. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678809] Re: CP area selection square disapears
Yes, the behavior of the magnifier glass could be more consistent and the small rectangle should be visible in both images when one cp is selected. ** Changed in: hugin Status: Triaged = Confirmed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678809 Title: CP area selection square disapears Status in Hugin - Panorama Tools GUI: Confirmed Bug description: When manually selecting control points, with auto add _deselected_, I select a cp in the one image, then hugin gives a very convenient white square to select the area in the other image for the matching point. If you want to select the next point in the same image pair, the white square disappears, it only comes back if you move to the next image pair. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 684749] Re: makefile generation problems
Now, on a real project it happened to me again. hugin (no pto, so a clean project) assistant tab: add one image. assistant tab: add second image. somehow, cpfind fails images tab: Try all options for automatic control point finding none work controlpoints tab: Add a few control points. (about 10) optimizer tab: optimize now open gl-preview remove two control points, add one... optimize now stitcher tab click remapped images: exposure corected LDR. stitch now Erorr. Log attached. ** Attachment added: This is the logfile of the stitch failure. https://bugs.launchpad.net/hugin/+bug/684749/+attachment/1757918/+files/stitch_failure.log -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/684749 Title: makefile generation problems Status in Hugin - Panorama Tools GUI: Triaged Bug description: I started a new project, and then went through the assistant up to align. Next I switch to the stitcher tab, and click stitch now. This results in: no way to make target dest.tif needed for target all . Ticking and unticking exposure corrected LDR as remapped output to keep results in the makefile being updated apparently, because restarting the stitch now works This seems to be quite common: I've seen this two or three times while testing 2010.4 beta. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 686256] [NEW] Error enblending temp images
Public bug reported: enblend: input image test0002.tif has pixel type UINT16, enblend: but previous images have pixel type UINT8 make: *** [test.png] Error 1 Current version 2010.2.0.d8ce0ba947cc (downloaded today) no previous versions installed. (HelpAbout System is not a valid menu option) Windows 7 Pro 32 Bit stitching of two images worked OK, but when the third was added get the error. ** Affects: hugin Importance: Undecided Status: New -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/686256 Title: Error enblending temp images Status in Hugin - Panorama Tools GUI: New Bug description: enblend: input image test0002.tif has pixel type UINT16, enblend: but previous images have pixel type UINT8 make: *** [test.png] Error 1 Current version 2010.2.0.d8ce0ba947cc (downloaded today) no previous versions installed. (HelpAbout System is not a valid menu option) Windows 7 Pro 32 Bit stitching of two images worked OK, but when the third was added get the error. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685582] Re: enblend wrong lib extension
** Project changed: hugin = enblend ** Changed in: enblend Assignee: Yuv (yuv) = (unassigned) ** Changed in: enblend Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/685582 Title: enblend wrong lib extension Status in Enblend: Incomplete Bug description: When trying to stitch some photos, I kept getting errors similar to the following: enblend --compression=LZW -f3000x1500 -o PICT0828-PICT0832.tif PICT0828-PICT0832.tif PICT0828-PICT08320001.tif PICT0828-PICT08320002.tif PICT0828-PICT08320003.tif PICT0828-PICT08320004.tif enblend: error while loading shared libraries: libImath.so.2: cannot open shared object file: No such file or directory make: *** [PICT0828-PICT0832.tif] Error 127 To fix the issue I made a symbolic link to the lib as follows: sudo ln -s /usr/lib/libIlmImf.so.6.0.0 /usr/lib/libIlmImf.so.2 sudo ln -s /usr/lib/libImath.so.6.0.0 /usr/lib/libImath.so.2 sudo ln -s /usr/lib/libHalf.so.6.0.0 /usr/lib/libHalf.so.2 sudo ln -s /usr/lib/libIex.so.6.0.0 /usr/lib/libIex.so.2 Machine is running Lucid. Also attached one of the Hugin logs. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685959] Re: create source images from PTO file.
** Changed in: hugin Status: Fix Released = Invalid ** Converted to question: https://answers.launchpad.net/hugin/+question/136883 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/685959 Title: create source images from PTO file. Status in Hugin - Panorama Tools GUI: Invalid Bug description: For bughunting it would be very useful if I can easily create a sample set of images that for most purposes would be useful as test-case images if a reporter only submits a PTO file. for each image in the PTO file, generate an image (with the name of the image in the pixels) of the specified size and type ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679592] Re: Broken link on Tutorials page
Temporary fix: commented out the faulty link from the website. If you get a new link, or the html to host, feel free to add to website again. ** Changed in: hugin Assignee: Yuv (yuv) = (unassigned) ** Tags added: website ** Tags removed: documentation wiki ** Changed in: hugin Importance: Wishlist = Critical ** Changed in: hugin Status: Triaged = Confirmed ** Changed in: hugin Status: Confirmed = Triaged ** Changed in: hugin Status: Triaged = Fix Committed ** Changed in: hugin Importance: Critical = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679592 Title: Broken link on Tutorials page Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Just to let you know that the link to Rectilinear/cylindric/equirectangular projection selection made easy tutorial is broken. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 686256] Re: Error enblending temp images
Thank you for reporting the error. From the error message it seems that your previous images are 8bits and the one you're trying to add is 16bits. The solution for you is to either upsample the 8bits pitures to 16bits or to downsample the 16bits picture to 8bit. I'm converting this to a feature request for enblend to blend images of different color depths. ** Project changed: hugin = enblend ** Changed in: enblend Status: New = Triaged ** Changed in: enblend Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/686256 Title: Error enblending temp images Status in Enblend: Triaged Bug description: enblend: input image test0002.tif has pixel type UINT16, enblend: but previous images have pixel type UINT8 make: *** [test.png] Error 1 Current version 2010.2.0.d8ce0ba947cc (downloaded today) no previous versions installed. (HelpAbout System is not a valid menu option) Windows 7 Pro 32 Bit stitching of two images worked OK, but when the third was added get the error. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679199] Re: hugin-0.8.0_rc1 creates artifacts
** Project changed: hugin = enblend ** Summary changed: - hugin-0.8.0_rc1 creates artifacts + enblend 3.2 creates artifacts ** Changed in: enblend Status: New = Confirmed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/679199 Title: enblend 3.2 creates artifacts Status in Enblend: Confirmed Bug description: Hi I'm using hugin-0.8.0_rc1 with libpano13-2.9.14_rc1 And it creates a lot of artifacts on huge panoramas. http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP.png http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-3.png And a line in the middle http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-1.png The image: http://downloads.mop.com/panoramabug/Bildschirmfoto-pano5.png-1.0%20(RGB,%201%20Ebene)%2061638x10876%20%E2%80%93%20GIMP-2.png I had to create screenshots since gimp didn't allow me to save the image (not enough ram). Here's the file hugin created: http://downloads.mop.com/panoramabug/pano5.png (402mb -- needs at least 6.6gb ram to display). It has a size of 61638x10876 pixels ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685933] Re: Process only selected layer in multi-layer TIFF
*** This bug is a duplicate of bug 685891 *** https://bugs.launchpad.net/bugs/685891 ** This bug has been marked a duplicate of bug 685891 16bit Tiff's containing preview imgs stop enfuse/enblend * You can subscribe to bug 685891 by following this link: https://bugs.launchpad.net/enblend/+bug/685891/+subscribe ** Changed in: enblend Status: New = Fix Released -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/685933 Title: Process only selected layer in multi-layer TIFF Status in Enblend: Fix Released Bug description: Canon's DPP creates TIFF files with 2 layers. Layer 1 contains the processed image, and layer 2 contains a small thumbnail. Several other RAW converters do the same. When feeding these images to Enfuse, both layers are attempted to be processed, causing incorrect results. And as far as I know there is no way to turn this feature off in the RAW converters. The only way to correct the problem now is to open these images in an image editor, and re-save them to get rid of the thumbnail. It would be great if it was possible introduce a syntax in Enfuse to specify layer(s) to process. Something like this: IMAGE.TIFF would process all layers, IMAGE.TIFF[1] would only process layer 1, etc... ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678763] Re: Pano13: struct Image initialization error
P.S.: SVN1305 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678763 Title: Pano13: struct Image initialization error Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: The Pano13 source in the hugin SDK has a typo in line 849 of filter.c, in function SetImageDefaults(). It reads bzero(im-formatParam, sizeof(im-precomputedValue)); but should be bzero(im-precomputedValue, sizeof(im-precomputedValue)); This leaves 4 of the precomputed values uninitialized since formatParam starts 4 words before precomputedValue and overwrites precomputedCount with (another) zero. Unlikely to cause malfunction. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679974] Re: Allow assignment of image priorities
actually for what the reporter want to achieve the mask functionality is the way to go. Other than that, the priority is determined by the order of the images in the images tab. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679974 Title: Allow assignment of image priorities Status in Hugin - Panorama Tools GUI: Triaged Bug description: Dear Hugin Developers, I would love to see a feature in Hugin that allows to prioritize the usage of certain images when stitching a panorama over others. Rationale: When I use hugin to stitch panoramas of landscapes that have significant details/features only in part of the whole panorama (like e.g. the image of desert with a tower visible, that has interesting ornaments) I use different focal lengths - short ones for the parts where little detail is to see, and zoomed images of the parts where lots of details are to see. I guess this is a common approach used by many users. The problem is that while Hugin even detects and reports automatically there is redundant coverage of certain image areas, there seems to be no way to tell Hugin Yes, I know, please prefer the long-focal-length pictures whereever available. I can try to workaround by using the crop feature to crop all the wide angle pictures such that they do not overlap the zoomed in ones anymore, but that is an extremely tedious task especially if there are lots of pictures to stitch and when the difference in focal lengths is big. I hope I haven't missed to spot an already existing feature like that, but searching for it didn't reveal any. Regards, Peter Niemayer ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679513] Re: delayed propagation of options to makefile
See also bug 679421 when fixing this behavior -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679513 Title: delayed propagation of options to makefile Status in Hugin - Panorama Tools GUI: Triaged Bug description: Hello, this is http://bugs.debian.org/586607 submitted against 2010.0.0. The enblend options set in hugin GUI do not immediately propagate to to pto.mk. How to reproduce: Start hugin. OpenFile-Preferences Stitching and change enblend's options. Exit the dialogue with Ok. Load two images in the images tab, generate control points. Optimizer [Optimize now] exposure [Optimize now] stitching: Set projection, Calculate FOV and Optimal size. Save project file exit hugin make -f foo.pt.mk all The changed option is not present. Closing hugin and restarting hugin before starting to work on the project (by loading the images) makes the option setting propagate to the pto.mk. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679421] Re: enblend default arguments are not (allways) written to *pto
see also bug 679513 there are two issues here: one is per-project settings (which would be an added feature, on the Stitcher Tab). The other one are global preferences not being propagated right. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679421 Title: enblend default arguments are not (allways) written to *pto Status in Hugin - Panorama Tools GUI: Triaged Bug description: Enblend default arguments that are added in the hugin preferences menu are kept globally. This may be a bug or a feature. As one normally doesn't need any refinements and if any supplementary arguments are added these will be rather special I tend to call it a bug. The main problem is: These arguments are only written to the *pto and *pto.mk the time you add them. For any other project opened later the arguments are still present in the preference menu but are not written to *pto or *pto.mk when the protect is saved. This is certainly a bug. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 685582] Re: enblend wrong lib extension
I got Hugin from the ppa as per the instructions on the Hugin site: http://wiki.panotools.org/Hugin_Compiling_ubuntu sudo add-apt-repository ppa:hugin/hugin-builds sudo apt-get update sudo apt-get install hugin enblend autopano-sift-c panini -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/685582 Title: enblend wrong lib extension Status in Enblend: Incomplete Bug description: When trying to stitch some photos, I kept getting errors similar to the following: enblend --compression=LZW -f3000x1500 -o PICT0828-PICT0832.tif PICT0828-PICT0832.tif PICT0828-PICT08320001.tif PICT0828-PICT08320002.tif PICT0828-PICT08320003.tif PICT0828-PICT08320004.tif enblend: error while loading shared libraries: libImath.so.2: cannot open shared object file: No such file or directory make: *** [PICT0828-PICT0832.tif] Error 127 To fix the issue I made a symbolic link to the lib as follows: sudo ln -s /usr/lib/libIlmImf.so.6.0.0 /usr/lib/libIlmImf.so.2 sudo ln -s /usr/lib/libImath.so.6.0.0 /usr/lib/libImath.so.2 sudo ln -s /usr/lib/libHalf.so.6.0.0 /usr/lib/libHalf.so.2 sudo ln -s /usr/lib/libIex.so.6.0.0 /usr/lib/libIex.so.2 Machine is running Lucid. Also attached one of the Hugin logs. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
