[Hugin-devs] [Bug 708294] Re: Random crashes and extreme memory use with overview mode
Are there messages shown in the console? Does the message createTexture(): GL Error when bulding mipmap levels: invalid value. still appear? Or an other message? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/708294 Title: Random crashes and extreme memory use with overview mode Status in Hugin - Panorama Tools GUI: New Bug description: Since the merge of the panorama overview branch into default hugin is suddenly very unstable and memory hungry. After using the FPW for a while and going forth and back between optimizing and looking at the FPW, hugin uses more than 1.5Gb memory, which is a lot more than before the merge. This is with a fairly small project of 6 Mpix images covering the full sphere and happens with the overview tab hidden as well. On the terminal hugin prints debug messages like this: ERROR: 21:20:02.993563 (/home/flixh/install/pano/hugin/src/hugin1/hugin/ProjectionGridTool.cpp:469) createTexture(): GL Error when bulding mipmap levels: invalid value. When crashing: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Looks like it's running out of memory? Should not happen on a machine with 2Gb RAM and 3Gb of swap, especially when I never saw that behaviour before. System: Hugin 2010.5.0.1fc6ad6e7c7a Linux system running Debian testing Regards Felix ___ 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 709428] [NEW] (2010.5 / Ubuntu 10.04) filenames badly sorted - destroys multirow technique
Public bug reported: Similar to another bug I just filed. But this one seems more strange On Ubuntu 10.04 / Hugin 2010.5 (the latest version) I drop four files onto Hugin, these are the filenames: IMG_0217_zero.JPG IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0220_zero.JPG but they get sorted like this: IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0217_zero.JPG IMG_0220_zero.JPG strange! I've tried it twice and it does it like this each time. on OS X it sorts them properly. I'm uploading the files so you can try it yourself if you like: www.vrlog.net/temp/badsort.zip (incidentally, feel free to use these files for testing, they are shaved nikkor 10.5 on canon 5d mk1, shot handheld with a string) cheers. ** 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/709428 Title: (2010.5 / Ubuntu 10.04) filenames badly sorted - destroys multirow technique Status in Hugin - Panorama Tools GUI: New Bug description: Similar to another bug I just filed. But this one seems more strange On Ubuntu 10.04 / Hugin 2010.5 (the latest version) I drop four files onto Hugin, these are the filenames: IMG_0217_zero.JPG IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0220_zero.JPG but they get sorted like this: IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0217_zero.JPG IMG_0220_zero.JPG strange! I've tried it twice and it does it like this each time. on OS X it sorts them properly. I'm uploading the files so you can try it yourself if you like: www.vrlog.net/temp/badsort.zip (incidentally, feel free to use these files for testing, they are shaved nikkor 10.5 on canon 5d mk1, shot handheld with a string) cheers. ___ 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 709428] Re: (2010.5 / Ubuntu 10.04) filenames badly sorted - destroys multirow technique
** Changed in: hugin Status: New = Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/709428 Title: (2010.5 / Ubuntu 10.04) filenames badly sorted - destroys multirow technique Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Similar to another bug I just filed. But this one seems more strange On Ubuntu 10.04 / Hugin 2010.5 (the latest version) I drop four files onto Hugin, these are the filenames: IMG_0217_zero.JPG IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0220_zero.JPG but they get sorted like this: IMG_0218_zero.JPG IMG_0219_zero.JPG IMG_0217_zero.JPG IMG_0220_zero.JPG strange! I've tried it twice and it does it like this each time. on OS X it sorts them properly. I'm uploading the files so you can try it yourself if you like: www.vrlog.net/temp/badsort.zip (incidentally, feel free to use these files for testing, they are shaved nikkor 10.5 on canon 5d mk1, shot handheld with a string) cheers. ___ 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 708294] Re: Random crashes and extreme memory use with overview mode
Yes, it's still the same message that appears (modulo the typo you fixed). Apart from that there are a lot of the usual CacheEntry: and Image: lines but nothing more. BTW: Couldn't we disable all the Cache messages by default? They just make it very hard to find real error/debug messages without any added benefit. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/708294 Title: Random crashes and extreme memory use with overview mode Status in Hugin - Panorama Tools GUI: New Bug description: Since the merge of the panorama overview branch into default hugin is suddenly very unstable and memory hungry. After using the FPW for a while and going forth and back between optimizing and looking at the FPW, hugin uses more than 1.5Gb memory, which is a lot more than before the merge. This is with a fairly small project of 6 Mpix images covering the full sphere and happens with the overview tab hidden as well. On the terminal hugin prints debug messages like this: ERROR: 21:20:02.993563 (/home/flixh/install/pano/hugin/src/hugin1/hugin/ProjectionGridTool.cpp:469) createTexture(): GL Error when bulding mipmap levels: invalid value. When crashing: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Looks like it's running out of memory? Should not happen on a machine with 2Gb RAM and 3Gb of swap, especially when I never saw that behaviour before. System: Hugin 2010.5.0.1fc6ad6e7c7a Linux system running Debian testing Regards Felix ___ 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 708363] Re: make: *** [info] Error 1
All is in the same path. c:\temp Nothing is in the user path. Please look at the last .ptp.mk. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/708363 Title: make: *** [info] Error 1 Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Der Befehl C:\Users\M ist entweder falsch geschrieben oder konnte nicht gefunden werden. Das System kann den angegebenen Pfad nicht finden. make: *** [info] Error 1 New installation on a win 7 64bit system. (HuginSetup_2010.4.0-64bit_Windows). ___ 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 709547] [NEW] Bracketed stack and exposure layer information isn't displayed
Public bug reported: [This is a long-standing issue, but there doesn't seem to be an item in the tracker.] When stitching, Hugin does an internal calculation to split the photos up into bracketed stacks and/or exposure layers (it looks at % overlap and EV numbers). However Hugin doesn't display this information to the user in any way without peering in the .pto.mk file. Possible ways of doing this in the GUI: In the Preview window Layout tab, stacks could be shown as a single item (maybe like a hand of cards), with only the middle exposure shown. Only the middle exposure of each stack should be shown in the 'normal' preview view. The button bar in the preview could group stacks together somehow, perhaps a stack could be shown as a vertical line of buttons and/or an exposure layer could be shown as a row of buttons. The Stitcher tab could have a text field that describes the stitching job, This project consists of bracketed stacks: [0,1,2],[3,4,5], [6,7,8], [9,10,11]. The Images tab could group photos stacks and exposure layers together somehow (don't have any ideas for this). ** Affects: hugin Importance: Wishlist Status: New ** 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/709547 Title: Bracketed stack and exposure layer information isn't displayed Status in Hugin - Panorama Tools GUI: New Bug description: [This is a long-standing issue, but there doesn't seem to be an item in the tracker.] When stitching, Hugin does an internal calculation to split the photos up into bracketed stacks and/or exposure layers (it looks at % overlap and EV numbers). However Hugin doesn't display this information to the user in any way without peering in the .pto.mk file. Possible ways of doing this in the GUI: In the Preview window Layout tab, stacks could be shown as a single item (maybe like a hand of cards), with only the middle exposure shown. Only the middle exposure of each stack should be shown in the 'normal' preview view. The button bar in the preview could group stacks together somehow, perhaps a stack could be shown as a vertical line of buttons and/or an exposure layer could be shown as a row of buttons. The Stitcher tab could have a text field that describes the stitching job, This project consists of bracketed stacks: [0,1,2],[3,4,5], [6,7,8], [9,10,11]. The Images tab could group photos stacks and exposure layers together somehow (don't have any ideas for this). ___ 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 709552] [NEW] EXIF display in Images tab doesn't show ISO
Public bug reported: This is a trivial bug, but it is maybe suitable as a summer of code student application patch, perhaps combined with formatting the display better at the same time (see Bug #679338 (sf-2877420)). The Images tab shows a list of EXIF attributes Including Aperture and Shutter Speed. However there are three numbers that are used to calculate the EV Exposure Value, so this display should also show ISO number for the photo. ** Affects: hugin Importance: Wishlist Status: New ** Tags: gsoc -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/709552 Title: EXIF display in Images tab doesn't show ISO Status in Hugin - Panorama Tools GUI: New Bug description: This is a trivial bug, but it is maybe suitable as a summer of code student application patch, perhaps combined with formatting the display better at the same time (see Bug #679338 (sf-2877420)). The Images tab shows a list of EXIF attributes Including Aperture and Shutter Speed. However there are three numbers that are used to calculate the EV Exposure Value, so this display should also show ISO number for the photo. ___ 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 709561] [NEW] Hugin doesn't copy icc colour profiles to output
Public bug reported: (reported by cels...@23degrees.com) Hugin copies lots of metadata from the first photo in the project to the final output, this is from src/hugin1/hugin/config_defaults: #define HUGIN_EXIFTOOL_COPY_ARGS -ImageDescription -Make -Model -Artist -WhitePoint -Copyright -GPS:all -DateTimeOriginal -CreateDate -UserComment -ColorSpace -OwnerName -SerialNumber It seems that it should also have these args: -icc_profile -xmp In particular, if there is no icc profile then the enblend -c option has no effect. ** Affects: hugin Importance: Undecided Status: New ** Tags: color -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/709561 Title: Hugin doesn't copy icc colour profiles to output Status in Hugin - Panorama Tools GUI: New Bug description: (reported by cels...@23degrees.com) Hugin copies lots of metadata from the first photo in the project to the final output, this is from src/hugin1/hugin/config_defaults: #define HUGIN_EXIFTOOL_COPY_ARGS -ImageDescription -Make -Model -Artist -WhitePoint -Copyright -GPS:all -DateTimeOriginal -CreateDate -UserComment -ColorSpace -OwnerName -SerialNumber It seems that it should also have these args: -icc_profile -xmp In particular, if there is no icc profile then the enblend -c option has no effect. ___ 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 700283] Re: enblend: error when first filename starts with -
This problem goes back to mid December 2009 and has affected every OSX issue since then including 2010.5.0-4886_a1cb4a2efa65. On OSX Intel Snow Leopard machines it manifests itself when using the Hugin stitcher when the pto file has already been saved as would be the case when re- stitching an existing project. Stitching on Leopard PPC machines fails also but without any shell residue to follow. Perhaps it is for the same reason. Note that in both cases the PTBatchGUI does not have the problem stitching. What appears to be happening is that when the pto already exists Hugin suggests a filename that includes the full path of the existing pto file where the hyphen character - is substituted for every instance of the normal path separator character in the full pto pathname and also as the first character. It looks like this name is subsequently passed not as a quoted string to enblend, which in turn thinks the first hyphen indicates an enblend parameter -U because all the described above substituted full pathnames would start with -User. It is interesting that this does not happen on Intel Leopard machines when the pto is not existing or when a different name is types in that does not start with -. However on Leopard PPC machines the stitch fails no matter what, even when on a totally fresh pto condition. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/700283 Title: enblend: error when first filename starts with - Status in Enblend: New Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I get the following error msg using hugin 2010.4.0 on Mac OS 10.6.5. Here's from the log: ... enblend: unknown option -U Try enblend --help for more information. gnumake: *** [-Users-Volker-Desktop-Hugin Test-DSC_0067-DSC_0074.jpg] Error 1 At this point, hugin has written the modified source pictures for the panaorama to the desiered directory, you can put them together manually using the gimp or something. I also tried successfully to start emblend out of the hugin package via terminal and make it do the job from there. Worked fine, too. to me it seems that the emblend gets a wrong input within hugin. I am not into the depth of any programming, so this is as far as I could get. HTH. ___ 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 709489] Re: Regression: Fine-tune all Points not usable anymore
** Changed in: hugin Status: New = Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/709489 Title: Regression: Fine-tune all Points not usable anymore Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Because of the relatively new immediate update of control point distances, the very useful function Fine-tune all Points is not usable anymore: After the fine-tune the control point distance is updated again and therefore not set to the correlation coefficient any more, so no way to delete all points with coefficient 0.8. ___ 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
