Panorama render artifacts in some SW with Hugin 2013

Bug #1267806 reported by Andrew Travneff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
Fix Released
Undecided
Unassigned

Bug Description

Duplicating from questions section (#241262)

I've used Hugin 2012 for several months and it was just great.
After update to version 2013 there is some corruption in the final panorama and it isn't visible in all viewers (may be related to some other part, not Hugin).

Example is attached. Cropped and converted from PNG to JPEG, just to show the pattern.
TIFF output has the same issue.

I use Fedora x64 and such a broken images are displayed fine (no stripes, no problems at all) in KolourPaint or Feh, for example.
On the other hand, Viewnior and ImageMagick show the stripes and Firefox just refuses to load the image with error like "the image cannot be displayed because it contains errors".

The interesting thing is that image scaled down with ImageMagick doesn't have stripes if scaling coefficient is below ~0.95-0.96.

Versions of the related packages:
hugin-2013.0.0-5.fc20.x86_64
enblend-4.1.2-1.fc20.x86_64

Revision history for this message
Andrew Travneff (travneff) wrote :
Revision history for this message
Bruno Postle (brunopostle) wrote : Re: [Bug 1267806] [NEW] Panorama render artifacts in some SW with Hugin 2013

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri 10-Jan-2014 at 11:39 -0000, Andrew Travneff wrote:
>
> I use Fedora x64 and such a broken images are displayed fine (no
> stripes, no problems at all) in KolourPaint or Feh, for example.
>
> On the other hand, Viewnior and ImageMagick show the stripes and
> Firefox just refuses to load the image with error like "the image
> cannot be displayed because it contains errors".

I don't think anything like this has been reported before, can you
upload one of the corrupted TIFF/PNG files somewhere?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFS0b58FqOhwCjyCLoRAj1mAJ9dRwtUAYQWb2CMUiQPcq1+5i8YigCff7Mq
iqqS36Qr5kz7oJLque1AOJk=
=tqmA
-----END PGP SIGNATURE-----

Revision history for this message
Andrew Travneff (travneff) wrote :

Sure, it's here (280MB), unmodified: http://www.ex.ua/538083568271
MD5: 0695ec5818c21c1b819462b3a913df4c
Sorry for the hosting.

I have to add that the mentioned update (v2012->v2013) was a part of the distro rebase (Fedora 19 -> 20), so a lot of another stuff was updated too.

Tried to reproduce it with kubuntu 13.10 x64 live, but got "std::bad_alloc" exception in the middle, log attached. Version here: hugin_2013.0.0~rc1+dfsg-1ubuntu1_amd64.deb

Also attaching .mk and .pto files for Fedora.

Revision history for this message
Andrew Travneff (travneff) wrote :
Revision history for this message
Andrew Travneff (travneff) wrote :
Revision history for this message
Bruno Postle (brunopostle) wrote : Re: [Bug 1267806] Re: Panorama render artifacts in some SW with Hugin 2013

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon 13-Jan-2014 at 13:09 -0000, Andrew Travneff wrote:
>Sure, it's here (280MB), unmodified: http://www.ex.ua/538083568271

I'm still downloading the PNG file, but I noticed that it is
33352x4696 pixels. This is big but it should be fine with PNG. The
Vigra library used by Hugin/enblend has a hard limit of 2
gigapixels, and different TIFF libraries have a 2 or 4 gigabyte
filesize limit, but you are nowhere near this.

Is it possible that your image viewers only support a 32768 (2^15)
pixel maximum dimension? This would explain the artefacts in the
right hand side of the image.

- --
Bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFS1AE9FqOhwCjyCLoRArFhAJ9szehSX7qgJtsJlZ50O9UxwAXTQQCfVCP0
2t4s/v3QSewODVzU5w7KTfA=
=2+hd
-----END PGP SIGNATURE-----

Revision history for this message
Bruno Postle (brunopostle) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Testing on fedora f20: I can create a 33000 pixel wide PNG image in
GIMP, but it won't display in 'eog':

Gdk:ERROR:gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion
   failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24
   || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32)

A 32000 wide image displays fine, so I assume this is a limitation
of gnome3/cairo/gtk3/xorg, not a Hugin/enblend bug.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFS1A0xFqOhwCjyCLoRAma8AJ9kNrq6VcCZuOrnH/sarhsQBE0WeACgpL5U
suBdYjuokf/ZVO6MR7Yeo9E=
=WeC5
-----END PGP SIGNATURE-----

Revision history for this message
Andrew Travneff (travneff) wrote :

Bruno, you are just right. Thank you.
I've started to check other viewers but then realized that there is much better way:

Fine: convert -size 32500x200 xc: +noise Random noise.png && viewnior noise.png
Broken: convert -size 32800x200 xc: +noise Random noise.png && viewnior noise.png

It's not 100% clear for me why some SW is OK, but Hugin is obviously unrelated to the example above.
Also not sure why I caught it just now. I got a new camera recently, but it has the same 16 MP.
I'll leave more description here just in case.

* Windows 7 x64:
** IE11, Paint, built-in viewer: OK
** FF26: fail. Same problem with Linux ("image cannot be displayed ...")
** Qupzilla: fail. Recognizes image size but shows the blank page.

* Fedora 20 x64:
** Feh, Kolourpaint: OK
** Viewnior: fail (stripes at right)
** Qupzilla: fail. Stripes over all the image. Picture becames visible just while window resizing.
** Gwenview: fail with image fit to window (just cropped the extra part), OK with zoom.
** Okular: fail. Stripes over all the image.

Feh, Kolourpaint and Viewnior are linked with the same libpng16.so.16, the problem seems more common. TIFF isn't tested much, but seems similar.

Summarizing, I would add some notification about possible issues to Hugin if some resulting dimension exceeds 32768 px.

Revision history for this message
tmodes (tmodes) wrote :

Warning message implemented in changeset d45f4334bebb1919f0892c24c380ad88848d677d

Changed in hugin:
status: New → Fix Committed
tmodes (tmodes)
Changed in hugin:
milestone: none → 2015.0beta1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.