Artefacts after verdandi

Bug #1595169 reported by Alex Fliker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
Fix Released
Undecided
Unassigned

Bug Description

OS: Kubuntu 16.04 x86_64
Verdandi version: 2016.2.0

With --seam=hard I get this:
http://i.imgur.com/ETA3rPo.jpg

With --seam=blend I get this:
http://i.imgur.com/nLG6Z7t.jpg

Hard looks good if not considering seam lines. But what happened with Blend? Is there any clue?
If more information is needed just ask!

Revision history for this message
tmodes (tmodes) wrote :

This code is new. So there can be some bugs which occur only in special circumstances.
Can you provide the image files and the pto file to I can have a look, what goes wrong?

Changed in hugin:
status: New → Incomplete
Revision history for this message
Alex Fliker (fliker09) wrote :

I uploaded files created by nona:
https://files.fm/u/4dxx8e9b

Revision history for this message
tmodes (tmodes) wrote :

First thanks. But such big files are bad for debugging. Can you reproduce the issue also with much smaller output images?
Also the pto file would be nice. For verdandi the blending order matters, the blending order can be calculated from the pto file.

Revision history for this message
Alex Fliker (fliker09) wrote :

I will try to reproduce the bug with down-scaled images. Regarding PTO... I don't work in GUI, only in terminal, so there is no sense in giving the PTO. Last actions in my pipeline is like this:
nona -m TIFF_m -z NONE --ignore-exposure -o panorama panorama.pto
verdandi --output=panorama.tif --wrap --seam=blend panorama0*.tif

Revision history for this message
Alex Fliker (fliker09) wrote :

I tried with a lot of different resolutions... Very inconsistent results. The image size has quite an effect on final result. One trend can be clearly observed - with lower resolution, seam line quality drops down. In the end I found working resolution (but on of the seam lines is not that good), but just by pure luck and random. Take a look at the links below:
https://filebin.net/e2wekguzhasuabwe/8192x4096.jpg
https://filebin.net/e2wekguzhasuabwe/12288x6144.jpg
https://filebin.net/e2wekguzhasuabwe/12728x6364.jpg

Revision history for this message
tmodes (tmodes) wrote :

Thanks for testing. But this does not help any further. Debugging with such big files does not work effectively.

PS: The 2 lines
nona -m TIFF_m -z NONE --ignore-exposure -o panorama panorama.pto
verdandi --output=panorama.tif --wrap --seam=blend panorama0*.tif
can be wrapped into one call to nona. As a side effect the big temporary files are not created (and beside the space you save the time to save and load these big files).

Changed in hugin:
status: Incomplete → Confirmed
Revision history for this message
Alex Fliker (fliker09) wrote :

Ok, files are big, but the thing is - only they can reproduce the bug.

How to make the magic call to nona you mentioned?

Revision history for this message
Alex Fliker (fliker09) wrote :

An update on the bug - there is a dependency on geometry. I found this out while working on another sphere. Adjusting the control points in it helped me to fight off the artifact. So, it seems there is something to do with image features...

Revision history for this message
tmodes (tmodes) wrote :

I fixed some issues in the blending code in default branch. This should also fix the issue reported here.

Changed in hugin:
milestone: none → 2019.2beta1
status: Confirmed → Fix Committed
tmodes (tmodes)
Changed in hugin:
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.