Hugin 2017.0 beta 1 release

[T. Modes]

Hi all,

today we are releasing a first beta of Hugin 2017.0.

Source tarball can be downloaded
at sourceforge: https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/hugin-2017.0beta1.tar.bz2/download
or at launchpad: https://launchpad.net/hugin/2017.0/2017.0beta1/+download/hugin-2017.0beta1.tar.bz2

Verify its checksums:
md5: bdcbdb63a7066bc889a46c595e4cd0a7  hugin-2017.0beta1.tar.bz2
sha1: 5ecff02eace752dbe3938fe06d7bcfeabaae3bd5  hugin-2017.0beta1.tar.bz2

This is a source code release.
Users communities produce executables for their respective platforms. Please announce them here.

(The beta 1 correspond to changeset 4fe670950b16 in our repository, which is also tagged as 2017.0 beta1).

Changes since 2016.2.0

The version 2017.0 is mainly a bug fix release. The biggest fixes regard:
* Several fixes for working with HDR images (display in GUI, photometric optimizer, handling of under/over exposured pixels in merging code).
* Fixes handling of masks in cpfind when images needs remapping for cp finding.
* Sometimes unsaved changes were disregarded without asking the user (e.g. when loading a project via the recently used projects list). Unsaved changes should now always require user confirmation.

Besides the bug fixes some smaller improvements have been implemented.
* Optimizer tabs uses now checkboxes instead of bold underlined font for marking of variables to be optimized.
* Use wxWidgets help windows instead of default browser (Linux&Mac only, this provides table of content, index and full text search in help files).
* Added special assistant variant for single image projects.
* Display of final panorama dimensions on stitcher tab.
* Extended the user defined output sequences:
   ** The shipped user defined output sequences are exposed in the GUI as own sub-menu.
   ** Added some more user defined output sequences (layered TIFF, cube faces).
   ** Added new placeholder %sourceimage% to user defined output sequence.

Upgrading from previous versions of Hugin should be seamless. If you do have problems with old settings, these can be reset in the Preferences window by clicking 'Load defaults'.

A first draft of release notes can be found at http://hugin.sourceforge.net/releases/2017.0.0/en.shtml

IMPORTANT
This is also a call for translators. Please update your translation files. Some new strings have been added.

[T. Modes]

An installer for Windows, 64 bit (Windows Vista/7/8/10) can be downloaded from sourceforge:
https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0beta1-win64.msi/download

MD5 Checksum
9b6899998be644053dc3292313589537 Hugin-2017.0beta1-win64.msi

[Niklas Mischkulnig]

Here is a mac build: (for macOS 10.9 and newer)

https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1.dmg/download

sha1: be9b6c7e4aa125d5c058d6e79af40499255f2871

[Andreas Metzler]

T. Modes <Thomas...@gmx.de> wrote:
> Hi all,

> today we are releasing a first beta of Hugin 2017.0.

> Source tarball can be downloaded

Hello,

binary packages are available in Debian/experimental.

cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

[Bruno Postle]

On 6 May 2017 14:07:44 BST, "T. Modes" wrote:
>
>today we are releasing a first beta of Hugin 2017.0.

I get a segfault on startup. This is with GTK3, I'll try again with GTK2 later when I get a chance.

--
Bruno

[T. Modes]

Hi Bruno,

Am Sonntag, 7. Mai 2017 10:31:43 UTC+2 schrieb Bruno Postle:

I get a segfault on startup. This is with GTK3, I'll try again with GTK2 later when I get a chance.

I can't reproduce the issue here. It works fine here with wxWidgets 3.0.2 with GTK 3.18 and also with 3.20.

Thomas

[Bruno Postle]

OK, Hugin no longer supports GTK2 with this release anyway.

I'm using fedora 25, wxGTK3-3.0.2 and gtk3-3.22.12

The stack suggests it is an OpenGL problem:

<frame level="0" function="GenerateReport(wxDebugReport::Context)" offset="000000cb"/>
<frame level="1"/>
<frame level="2"/>
<frame level="3" function="_XSend" offset="000000c7"/>
<frame level="4" function="XQueryExtension" offset="00000084"/>
<frame level="5"/>
<frame level="6" function="glXQueryVersion" offset="00000035"/>
<frame level="7" function="wxGLCanvasX11::GetGLXVersion()" offset="00000057"/>
<frame level="8" function="wxGLCanvasX11::ConvertWXAttrsToGL(int const*, int*, unsigned long)" offset="000003b5"/>
<frame level="9" function="wxGLCanvasX11::InitXVisualInfo(int const*, __GLXFBConfigRec***, XVisualInfo**)" offset="00000038"/>
<frame level="10" function="wxGLCanvas::Create(wxWindow*, int, wxPoint const&amp;, wxSize const&amp;, long, wxString const&amp;, int const*, wxPalette const&amp;)" offset="000000d0"/>
<frame level="11" function="wxGLCanvas::wxGLCanvas(wxWindow*, int, int const*, wxPoint const&amp;, wxSize const&amp;, long, wxString const&amp;, wxPalette const&amp;)" offset="00000063"/>
<frame level="12" function="GLViewer::GLViewer(wxWindow*, HuginBase::Panorama&amp;, int*, GLPreviewFrame*, wxGLContext*)" offset="000000b2"/>
<frame level="13" function="GLPreviewFrame::GLPreviewFrame(wxFrame*, HuginBase::Panorama&amp;)" offset="00001a69"/>
<frame level="14" function="MainFrame::MainFrame(wxWindow*, HuginBase::Panorama&amp;)" offset="00002579"/>
<frame level="15" function="huginApp::OnInit()" offset="00000b35"/>
<frame level="16" function="wxEntry(int&amp;, wchar_t**)" offset="00000092"/>
<frame level="17" function="main" offset="00000028"/>
<frame level="18" function="__libc_start_main" offset="000000f1"/>
<frame level="19" function="_start" offset="0000002a"/>

Fedora now uses Wayland by default instead of X11 (wayland-1.12.0), if I
switch back to X11 then Hugin seems to be fine. Not sure how to debug
this, is anyone else using Hugin on Wayland?

--
Bruno

[Terry Duell]

I built 2017.1.0 (at that time I couldn't see any differences) on Fedora
25, with GTK3, and it seems to be working OK thus far.

Cheers,
--
Regards,
Terry Duell

[Terry Duell]

Hello Bruno,

On Mon, 08 May 2017 07:26:12 +1000, Bruno Postle <br...@postle.net> wrote:

>
> Fedora now uses Wayland by default instead of X11 (wayland-1.12.0), if I
> switch back to X11 then Hugin seems to be fine. Not sure how to debug
> this, is anyone else using Hugin on Wayland?

A quick check shows I'm using X11, which would explain why I don't have
the problem.

[Wirz]

I'm also getting a segfault when I add pictures (since two or three
weeks ago).

My machine runs debian/testing (kernel 4.4), the used libraries are

wxWidgets: wxWidgets 3.0.2
wxWidgets Library (wxGTK port)
Version 3.0.2 (Unicode: wchar_t, debug level: 1),
Runtime version of toolkit used is 2.24.
Compile-time GTK+ version is 2.24.31.

libpano13: 2.9.19
Boost: 1.62.0
Exiv2: 0.25
SQLite3: 3.16.2
Vigra: 1.11.0
LittleCMS2: 2.8


However, in my stack trace there is nothing about GL. Do you reckon
that's a vigra-problem? I'm also using the tip there ... cheers, lukas

<frame level="0" function="GenerateReport(wxDebugReport::Context)"

offset="000000cc"/>

<frame level="1"/>
<frame level="2"/>

<frame level="3" function="jpeg_CreateDecompress" offset="0000001c"/>
<frame level="4"
function="vigra::JPEGDecoderImpl::JPEGDecoderImpl(std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;)" offset="0000003e"/>
<frame level="5"
function="vigra::JPEGDecoder::init(std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;)" offset="00000028"/>
<frame level="6"
function="vigra::CodecManager::getDecoder(std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;, std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;, unsigned int) const" offset="0000015a"/>
<frame level="7"
function="vigra::getDecoder(std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;, std::__cxx11::basic_string&lt;char,
std::char_traits&lt;char&gt;, std::allocator&lt;char&gt; &gt;
const&amp;, unsigned int)" offset="0000002f"/>
<frame level="8" function="vigra::ImageImportInfo::readHeader_()"
offset="0000004d"/>
<frame level="9"
function="vigra::ImageImportInfo::ImageImportInfo(char const*, unsigned
int)" offset="000000eb"/>
<frame level="10"
function="PanoCommand::wxAddImagesCmd::processPanorama(HuginBase::Panorama&amp;)"
offset="00000237"/>
<frame level="11"
function="PanoCommand::CombinedPanoCommand::processPanorama(HuginBase::Panorama&amp;)"
offset="00000030"/>
<frame level="12" function="PanoCommand::PanoCommand::execute()"
offset="000000e1"/>
<frame level="13"
function="PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*,
bool)" offset="00000067"/>
<frame level="14" function="huginApp::OnInit()" offset="0000232a"/>
<frame level="15" function="wxEntry(int&amp;, wchar_t**)"
offset="00000092"/>
<frame level="16" function="main" offset="00000028"/>
<frame level="17" function="__libc_start_main" offset="000000f1"/>
<frame level="18" function="_start" offset="0000002a"/>

Do not believe the naysayers who say it cannot be done.

[Luís Henrique Camargo Quiroz]

   Hi,

   Next week I will update the portuguese translations, if needed.

   Thomas, when do you plan to release the beta?

    regards,

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/e7c89a9d-9d23-48ec-a513-be3b2ff2beb0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--
Luis Henrique Camargo Quiroz
http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
http://panoramaslh.net/

[Stefan Peter]

Hi Thomas
Hi all

Am 06.05.2017 um 15:07 schrieb T. Modes:
> Hi all,
>
> today we are releasing a first beta of Hugin 2017.0.

Thank you very much for this new release.

Binary packages for Ubuntu trusty, vivid, xenial, yakkety and zesty are
available from the Hugin PPA Packagers "next Hugin builds" repository at
https://launchpad.net/~hugin/+archive/ubuntu/next

Please test these packages and send error report, success stories and
praises to this mailing list (hugi...@googlegroups.com).

Enjoy!

With kind regards
Stefan Peter

[T. Modes]

Hi Bruno,

Am Sonntag, 7. Mai 2017 23:26:21 UTC+2 schrieb Bruno Postle:

Fedora now uses Wayland by default instead of X11 (wayland-1.12.0), if I
switch back to X11 then Hugin seems to be fine.  Not sure how to debug
this, is anyone else using Hugin on Wayland?

This is probably a wxWidgets problem. Also the OpenGL sample of wxwidgets crashes with Wayland.
See ticket http://trac.wxwidgets.org/ticket/17702 , it contains a very similar backtrace.
So this crash needs to be fixed upstreams.
Not sure how to handle this. (What was different in the last version? Did this one work with Wayland?)
Maybe you could add a notice to the release notes.

Thomas

[T. Modes]

 Hi Lukas,

Am Montag, 8. Mai 2017 14:23:05 UTC+2 schrieb lukas:

I'm also getting a segfault when I add pictures (since two or three
weeks ago).

However, in my stack trace there is nothing about GL.  Do you reckon
that's a vigra-problem?  I'm also using the tip there ... cheers, lukas

This is not very helpful. When using the tip it would be nice if you could name the offending changeset. So it become a wild guess.

The load code in Hugin was not changed in the last time. Also in vigra the jpeg load code was changed the last time at Oct 25, 2012, so a long time ago.
So maybe there was a change in libjpeg? Which version of libjeg or jpeg-turbo are you using?
Does other image formats (tiff/png) work?

Thomas

[T. Modes]

Hi Luis,

Am Montag, 8. Mai 2017 14:30:15 UTC+2 schrieb Luís Henrique Camargo Quiroz:

   Next week I will update the portuguese translations, if needed.

This would be nice.
 

   Thomas, when do you plan to release the beta?

I don't understand. I have released beta 1 the day before yesterday.
Or do you mean release candidate 1? I have planned 2-4 weeks for beta 1.

Thomas

[Wirz]

Hi Thomas,

sorry for the noise. Everything is in order now. (Apparently, during
my last system update, libpng had been kept in the old version. Fixing
that and rebuilding vigra/libpano/hugin resolved that issue. Possibly,
the actual problem was that the update of some other library hadn't been
picked up by make.)

cheers, lukas

[Luís Henrique Camargo Quiroz]

Oh, I made a silly confusion here, my question was nonsense ;)

[Bruno Postle]

On Mon 08-May-2017 at 08:12 -0700, Thomas Modes wrote:
>Am Sonntag, 7. Mai 2017 23:26:21 UTC+2 schrieb Bruno Postle:
>>
>> Fedora now uses Wayland by default instead of X11 (wayland-1.12.0), if I
>> switch back to X11 then Hugin seems to be fine. Not sure how to debug
>> this, is anyone else using Hugin on Wayland?
>
>This is probably a wxWidgets problem. Also the OpenGL sample of wxwidgets
>crashes with Wayland.
>See ticket http://trac.wxwidgets.org/ticket/17702 , it contains a very
>similar backtrace.
>So this crash needs to be fixed upstreams.

Yes looks like it isn't going to get fixed soon.

>Not sure how to handle this. (What was different in the last version? Did
>this one work with Wayland?)

The existing hugin-2016.2.0 package is linked to wxGTK-2.8.12 and
gtk2-2.24.31 and continues to work fine on Wayland. I haven't tried
rebuilding this for wxGTK3 to see if it has the same problem.

A page linked from the ticket above offers a workaround, I can get
the beta1 Hugin to work with wxGTK3 and Wayland like this:

GDK_BACKEND=x11 hugin

Further, I can put this hack in the hugin.desktop file:

Exec=env GDK_BACKEND=x11 hugin %f

This even allows launching the Batch Processor from Hugin and
vice-versa, but it doesn't feel like a great solution.

--
Bruno

[Bruno Postle]

On Mon 08-May-2017 at 08:53 +1000, Terry Duell wrote:

>On Mon, 08 May 2017 07:26:12 +1000, Bruno Postle wrote:
>
>>Fedora now uses Wayland by default instead of X11 (wayland-1.12.0),
>>if I switch back to X11 then Hugin seems to be fine. Not sure how
>>to debug this, is anyone else using Hugin on Wayland?
>
>A quick check shows I'm using X11, which would explain why I don't
>have the problem.

Hi Terry, can you try and reproduce the crash by enabling Wayland?
This would rule out a hardware problem with my system.

When you log in to Fedora 25 there is a little cogwheel shown below
the password field, click this, the 'GNOME' option gives you a
Wayland session, the 'GNOME on Xorg' option gives you X11.

--
Bruno

[Bruno Postle]

On Mon 08-May-2017 at 19:13 +0100, Bruno Postle wrote:

[snip wxWidgets bug with Wayland on Fedora]

>A page linked from the ticket above offers a workaround, I can get the
>beta1 Hugin to work with wxGTK3 and Wayland like this:

> GDK_BACKEND=x11 hugin

>This even allows launching the Batch Processor from Hugin and
>vice-versa, but it doesn't feel like a great solution.

I've built packages of Hugin 2017.0.0 beta1 for current Fedora
releases using this workaround:
https://copr.fedorainfracloud.org/coprs/bpostle/panorama/

I'm still not sure this is a good enough solution to push into
Fedora itself.

--
Bruno

[Terry Duell]

Hello Bruno,

On Mon, 08 May 2017 18:58:59 +1000, Bruno Postle <br...@postle.net> wrote:

[snip]

> Hi Terry, can you try and reproduce the crash by enabling Wayland? This
> would rule out a hardware problem with my system.
>
> When you log in to Fedora 25 there is a little cogwheel shown below the
> password field, click this, the 'GNOME' option gives you a Wayland
> session, the 'GNOME on Xorg' option gives you X11.
>

I'm running with Cinnamon, and thus far finding how to switch to gnome and
wayland is proving elusive.
I'll persist but suspect domestic blindness amongst other things isn't
helping.

[Terry Duell]

On Tue, 09 May 2017 08:23:10 +1000, Terry Duell <tdu...@iinet.net.au>
wrote:

I'm not having any luck here.
No cogwheel below password field here.
I see two options to start in gnome (upper right corner of login screen),
neither specify x11 or wayland and both end up running x11.
Unless anyone has any good ideas as to how I can log into a gnome/wayland
session, I'm not going to be able to help.

[Carl von Einem]

Hi!

On 06.05.17 20:28, Niklas Mischkulnig wrote:
> Here is a mac build: (for macOS 10.9 and newer)
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1.dmg/download
>
> sha1: be9b6c7e4aa125d5c058d6e79af40499255f2871
>

All my attempts to stitch a panorama with this beta version fail at some
point during the enblend stage.

Carl

Mac OS X 10.11
Version: 2017.0.0.4fe670950b16 built by Niklas Mischkulnig
enblend 4.2.1-f0304648cc0f

Here are the last lines of the log:

enblend: info: loading next image: 170514-test-hugin2017beta0000.tif 1/1
enblend: info: assembled images bounding box: [(140, 347) to (5153,
4872) = (5013x4525)]
enblend: info: loading next image: 170514-test-hugin2017beta0001.tif 1/1

[Niklas Mischkulnig]

Hello,

Here are the last lines of the log:

enblend: info: loading next image: 170514-test-hugin2017beta0000.tif 1/1
enblend: info: assembled images bounding box: [(140, 347) to (5153,
4872) = (5013x4525)]
enblend: info: loading next image: 170514-test-hugin2017beta0001.tif 1/1

These lines don't contain any error message, could you please post the full log of PTBatcher.

If this is indeed everything, then I would say that enblend ran successfully.

Niklas

[Carl von Einem]

Sorry, somehow I cut off the important part. Here come the last lines of
the log file.

Carl

[Niklas Mischkulnig]

Am Montag, 15. Mai 2017 16:07:48 UTC+2 schrieb zarl:

Sorry, somehow I cut off the important part. Here come the last lines of
the log file.

Carl

enblend: info: loading next image: 170514-test-hugin2017beta0000.tif 1/1
enblend: info: assembled images bounding box: [(140, 347) to (5153,
4872) = (5013x4525)]
enblend: info: loading next image: 170514-test-hugin2017beta0001.tif 1/1

Could you please post the whole PTBatcher log as an attachment?

Niklas

[Carl von Einem]

Sure, here it is.

Carl

[Niklas Mischkulnig]

It should be fixed, please try out this new version:

https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1-r1.dmg/download

Niklas

[Kornel Benko]

Am Dienstag, 16. Mai 2017 um 08:38:17, schrieb Niklas Mischkulnig <nik...@mischkulnig.de>

> It should be fixed, please try out this new version:
>
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1-r1.dmg/download
>
>
> Niklas

It is not compilable because of
cd /BUILD/BUILDMint17/BuildHugin_hg/src/translations && /usr/bin/msgfmt -o /BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.gmo /BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.po
/BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.po:7476: 'msgid' and 'msgstr' entries do not both end with '\n'
/usr/bin/msgfmt: found 1 fatal error
make[2]: *** [src/translations/pt_BR.gmo] Error 1
make[2]: *** Deleting file `src/translations/pt_BR.gmo'
make[2]: Leaving directory `/BUILD/BUILDMint17/BuildHugin_hg'
make[1]: *** [src/translations/CMakeFiles/translations.dir/all] Error 2
make[1]: Leaving directory `/BUILD/BUILDMint17/BuildHugin_hg'
make: *** [all] Error 2

The patch is easy though.

#diff -r 462085503da3 src/translations/pt_BR.po
--- a/src/translations/pt_BR.po Tue May 16 10:12:02 2017 -0300
+++ b/src/translations/pt_BR.po Tue May 16 18:12:27 2017 +0200
@@ -7162,7 +7162,7 @@
"intermediate images."
msgstr ""
"O seguinte arquivo de argumentos será usado para copiar etiquetas da "
-"primeira imagem para todas as imagens intermediárias.\n"
+"primeira imagem para todas as imagens intermediárias."

#: hugin1/hugin/xrc/pref_dialog.xrc:971
msgid "Intermediate ExifTool argfile:"

Kornel

[T. Modes]

Am Dienstag, 16. Mai 2017 18:19:13 UTC+2 schrieb kornel:

It is not compilable because of

Should be fixed.

Thomas

[Kornel Benko]

Am Dienstag, 16. Mai 2017 um 09:27:29, schrieb T. Modes <Thomas...@gmx.de>

It is.

Kornel

[Carl von Einem]

Hi Niklas,

that version is for 10.12 only, it doesn't start on my 10.11 system. I'll need a more universial build, please.

Thanks,
Carl

Am 16.05.17 um 17:38 schrieb Niklas Mischkulnig

[Niklas Mischkulnig]

Something was messed up that time, this should support 10.9 and newer:

https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1-r2.dmg/download

Niklas

[Carl von Einem]

Thank you, the new build now works on my OS X 10.11 and also the stitching process using enblend works (at first glance even better than with the last release). Now let's see if I can find some other problems...

I really like the checkboxes in the Optimizing tab.

Thank you all for your work!

Carl

Am 18.05.17 um 15:53 schrieb Niklas Mischkulnig