Few control points on HDR images with CPFind

59 views
Skip to first unread message

Torsten Stremlau

unread,
Jun 7, 2016, 6:15:55 PM6/7/16
to hugin and other free panoramic software
I recently started using Hugin to create 360° panoramas of HDR images.
The images I am trying to stitch together are in OpenEXR format.

I noticed that cpfind hardly finds any control points on these HDR images.
If I convert the images to LDR first, then cpfind actually finds quite a few control points.

I poked around in cpfind and found out that this is probably because the HDR images are first mapped
to [0,255] before any features are detected. As this is done using a linear mapping the images end up being
mostly black with only the brightest parts in the image visible. (Usually the sun...)

When I switched the mapping in cpfind to logarithmic in the source code, the results became much better and
more control points were found.

Is this a known issue, or am I doing something wrong?

I am using hugin on ubuntu 16.04 64bit.
I built hugin myself from hg revision:674a88cfacb6468ac185c8e12392ba9c206a7113

-- Torsten

T. Modes

unread,
Jun 8, 2016, 11:34:53 AM6/8/16
to hugin and other free panoramic software
Hi Torsten,


Am Mittwoch, 8. Juni 2016 00:15:55 UTC+2 schrieb Torsten Stremlau:
When I switched the mapping in cpfind to logarithmic in the source code, the results became much better and
more control points were found.

Is this a known issue, or am I doing something wrong?

The hdr capabilities of cpfind has not been extensively tested. So it may be that there are some bugs.
Can you provide a patch of your changes?

Thomas

Torsten Stremlau

unread,
Jun 8, 2016, 1:02:14 PM6/8/16
to hugin and other free panoramic software
Hi Thomas,

here is the patch of the changes I made.

-- Torsten


Am Mittwoch, 8. Juni 2016 00:15:55 UTC+2 schrieb Torsten Stremlau:
logarithmic_mapping.patch

T. Modes

unread,
Jun 8, 2016, 2:28:17 PM6/8/16
to hugin and other free panoramic software
Hi Torsten,


Am Mittwoch, 8. Juni 2016 19:02:14 UTC+2 schrieb Torsten Stremlau:
here is the patch of the changes I made.

I think it is reasonable to activate the logarithm mapping for all hdr images (currently filetype double/float and linear response type) automatically instead of an additional switch.
So I committed this modification. I hope this works for you also.

Thomas

Torsten Stremlau

unread,
Jun 8, 2016, 3:30:41 PM6/8/16
to hugin and other free panoramic software
Hi Thomas,


Am Mittwoch, 8. Juni 2016 20:28:17 UTC+2 schrieb T. Modes:
I think it is reasonable to activate the logarithm mapping for all hdr images (currently filetype double/float and linear response type) automatically instead of an additional switch.
So I committed this modification. I hope this works for you also.

Works nicely, thank you very much :)


-- Torsten

David W. Jones

unread,
Jun 9, 2016, 3:10:32 AM6/9/16
to hugi...@googlegroups.com
Do 16-bit TIFF files count as HDR for this? Or is it just EXR? I use
TIFF, not EXR.

Thanks.

--
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com

T. Modes

unread,
Jun 9, 2016, 12:19:00 PM6/9/16
to hugin and other free panoramic software


Am Donnerstag, 9. Juni 2016 09:10:32 UTC+2 schrieb GnomeNomad:
> images (currently filetype double/float and linear response type)
Do 16-bit TIFF files count as HDR for this? Or is it just EXR? I use
TIFF, not EXR.

It pays to be able to read.
Again for you "currently filetype double/float and linear response type"

Second, are there problems with less or no control points in your images?

Gnome Nomad

unread,
Jun 10, 2016, 1:24:00 AM6/10/16
to hugin and other free panoramic software
Sorry, I did read it, then had to translate from programmerese. ;)
I have no problems getting control points in 16-bit TIFFs. I've never tried an EXR as input to Hugin. I sometimes use them as output for use in Luminance HDR, but that's not dealing with control points.



Reply all
Reply to author
Forward
0 new messages