[Hugin-devs] [Bug 1402613] [NEW] TIFFReadDirectory: Incorrect count for BitsPerSample.
Public bug reported: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 ** 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/1402613 Title: TIFFReadDirectory: Incorrect count for BitsPerSample. Status in Hugin - Panorama Tools GUI: New Bug description: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1402613/+subscriptions ___ 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 1402613] Re: TIFFReadDirectory: Incorrect count for BitsPerSample.
Opens without an error message in Photoshop CS6 (Mac) and GraphicConverter. Hugin however isn't able to decode that file. EXIF information of the image reveals that a software called Daminion (from daminion.net ) touched your image at some point. Have you seen that problem before using Hugin? Did you recently change your workflow? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1402613 Title: TIFFReadDirectory: Incorrect count for BitsPerSample. Status in Hugin - Panorama Tools GUI: New Bug description: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1402613/+subscriptions ___ 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 1402613] Re: TIFFReadDirectory: Incorrect count for BitsPerSample.
Any software that uses libtiff fails when try to render this image. It seems that the Photoshop CS6 (Mac) and GraphicConverter use the proprietary tiff processing libraries. I've played with both Hugin and Daminion, but can't reproduced this issue with the latest program versions. I'm waiting for an additional info from the user who's own this file. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1402613 Title: TIFFReadDirectory: Incorrect count for BitsPerSample. Status in Hugin - Panorama Tools GUI: New Bug description: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1402613/+subscriptions ___ 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 1402613] Re: TIFFReadDirectory: Incorrect count for BitsPerSample.
I sometimes feed panoramas back into Hugin directly after stitching (e.g. to level a wavy horizon) but never had issues like the one described here. Can the person who has that problem be pointed to this discussion so the developers here can get more details? The image contains some information about a landscape in Austria, so if the photographer feels more comfortable contributing in German, I'm fine with that. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1402613 Title: TIFFReadDirectory: Incorrect count for BitsPerSample. Status in Hugin - Panorama Tools GUI: New Bug description: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1402613/+subscriptions ___ 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 1402613] Re: TIFFReadDirectory: Incorrect count for BitsPerSample.
Hugin and enblend are using libtiff (via vigra) to write the images. And they write tiff files always with an alpha channel. So the shown image was not touched by Hugin at the end. Another software has removed the alpha channel without correctly updating the header. This is nothing which can be fixed at Hugins end. ** 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/1402613 Title: TIFFReadDirectory: Incorrect count for BitsPerSample. Status in Hugin - Panorama Tools GUI: Invalid Bug description: Can't render the below tiff file created by hugin using any program that uses the official libtiff: https://www.dropbox.com/s/4ieoef5nn1rfsaz/IMG_2322-2324.tif?dl=0 = $ tiffinfo broken.tif TIFFReadDirectory: Incorrect count for BitsPerSample. = Discussion on the VIPS tracker: https://github.com/jcupitt/libvips/issues/209#issuecomment-66978787 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1402613/+subscriptions ___ 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 1402347] Re: Segmentation autooptimiser
There are several issues with this pto file: 1.) First it contains 1266 images, but the control points refers up to image 1670, which does not exists. 2.) Not all images are connected by control points. checkpto reports 410 image groups. 3.) Each image has it own lens: so there are 1266 lenses, each with its own fov and its own distortion parameters. This is too much for the optimizer. So before further searching for the segmentation fault a valid pto file should be created; and not a file with there serious issues. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1402347 Title: Segmentation autooptimiser Status in Hugin - Panorama Tools GUI: Incomplete Bug description: Segfault using command line OSX 10.9.5 Very large set of control points (10k+) - could this be it? How come it segfaults late after a lot of steps and not early? Any way to get it to output after each iteration so I don't lose a day of CPU time? autooptimiser version 2014.0.0 built by Matthieu DESILE Thanks! /Applications/CIOTW/Hugin/Hugin.app/Contents/MacOS/autooptimiser -a -s -m -o project1.pto unopt.pto *** Adaptive geometric optimisation Optimizing Variables Strategy 1 Average (rms) distance between Controlpoints after 0 iteration(s): 21.3412455531342 units Strategy 1 Average (rms) distance between Controlpoints after 1 iteration(s): 20.782719988699 units Strategy 1 Average (rms) distance between Controlpoints after 2 iteration(s): 19.7306247970753 units Strategy 1 Average (rms) distance between Controlpoints after 3 iteration(s): 17.6435844732556 units Strategy 1 Average (rms) distance between Controlpoints after 4 iteration(s): 13.5340788487278 units Strategy 1 Average (rms) distance between Controlpoints after 5 iteration(s): 5.65389441304538 units Strategy 1 Average (rms) distance between Controlpoints after 6 iteration(s): 3.07970340905523 units Strategy 1 Average (rms) distance between Controlpoints after 7 iteration(s): 2.73728694462394 units Strategy 1 Average (rms) distance between Controlpoints after 8 iteration(s): 2.34698686018928 units Strategy 1 Average (rms) distance between Controlpoints after 9 iteration(s): 2.11046162527549 units Strategy 1 Average (rms) distance between Controlpoints after 10 iteration(s): 2.07022086098916 units Strategy 1 Average (rms) distance between Controlpoints after 11 iteration(s): 2.07022086098916 units Optimizing Variables Strategy 2 Average (rms) distance between Controlpoints after 0 iteration(s): 1.92672078393405 units Strategy 2 Average (rms) distance between Controlpoints after 1 iteration(s): 1.88786069412307 units Strategy 2 Average (rms) distance between Controlpoints after 2 iteration(s): 1.87438550339538 units Strategy 2 Average (rms) distance between Controlpoints after 3 iteration(s): 1.85729101654478 units Strategy 2 Average (rms) distance between Controlpoints after 4 iteration(s): 1.85106831230553 units Strategy 2 Average (rms) distance between Controlpoints after 5 iteration(s): 1.84714255659054 units Strategy 2 Average (rms) distance between Controlpoints after 6 iteration(s): 1.84596023689701 units Strategy 2 Average (rms) distance between Controlpoints after 7 iteration(s): 1.84548453420456 units Strategy 2 Average (rms) distance between Controlpoints after 8 iteration(s): 1.84531574757642 units Strategy 2 Average (rms) distance between Controlpoints after 9 iteration(s): 1.84525847815409 units Strategy 2 Average (rms) distance between Controlpoints after 10 iteration(s): 1.84523932666178 units Strategy 2 Average (rms) distance between Controlpoints after 11 iteration(s): 1.84522703991422 units Strategy 2 Average (rms) distance between Controlpoints after 12 iteration(s): 1.84522589794342 units Strategy 2 Average (rms) distance between Controlpoints after 13 iteration(s): 1.84522580718591 units Strategy 2 Average (rms) distance between Controlpoints after 14 iteration(s): 1.8452255766334 units Strategy 2 Average (rms) distance between Controlpoints after 15 iteration(s): 1.84522335069066 units Strategy 2 Average (rms) distance between Controlpoints after 16 iteration(s): 1.84522208887578 units Strategy 2 Average (rms) distance between Controlpoints after 17 iteration(s): 1.84522208726154 units Strategy 2 Average (rms) distance between Controlpoints after 18 iteration(s): 1.84522207229919 units Segmentation fault: 11 To manage
