Hugin 2025.0 rc1 released

[T. Modes]

Hi all,

today we are releasing release candidate 1 of Hugin 2025.0.0

Source tarball can be downloaded

https://sourceforge.net/projects/hugin/files/hugin/hugin-2025.0/hugin-2025.0rc1.tar.bz2/download

Verify its checksums:
md5:
2097412a824a2d2dc5333a9f8033ccb3  hugin-2025.0rc1.tar.bz2
sha1:
2eb5fe179723c379ab274da1b8dc65e9ee428978  hugin-2025.0rc1.tar.bz2


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

(The release candidate 1 correspond to changeset cf857c87875cour repository, which is also tagged as 2025.0rc1).

Canges since 2025.0 beta 1

* Updated translations

* Fix top handling issue when optimizing

* hugin_toolbox stores its internal settings in a internal subfolder for better extension

* Fixes an assert when switching between mask and crop editor

* Fixes drawing of line cp in fast preview. Also draw for these cp now a straight line instead of a great arc.

* Fast preview: ignore line cp in layout mode.

Changes since 2024.0

The most changes are under the hood and affect mainly the builders.

Now a C++17 compiler is needed. Therefore the boost library is not needed anymore. 

You may need newer version of some dependencies depending on the used compiler.

Also libjpeg and libpng are not needed when building the shared version (which is the default).

wxWidgets 3.2 or later is now required. The code has be refactored to follow the modern wxWidgets code style. With this change Hugin is now using vector SVG files instead of raster PNG files for the toolboor and buttons. This should improve the appearance on hdpi displays.

A new GUI has be added: hugin_toolbox. It provides a GUI for enfuse and for simple perspective correction.

Beside there are many small bugfixes.

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'.

Windows binaries (64 bit) can be found at sourceforge: 

https://sourceforge.net/projects/hugin/files/hugin/hugin-2025.0/Hugin-2025.0rc1-win64.msi/download

MD5 checksum
dd4d0ea7c4ee9318424018bc4fb74217  Hugin-2025.0rc1-win64.msi

[Cristian Marchi]

Hi Thomas, while working with hugin toolbox, I've found some string not translatable:

[T. Modes]

Hi Cristian,

cri....@gmail.com schrieb am Sonntag, 9. November 2025 um 20:20:04 UTC+1:

Hi Thomas, while working with hugin toolbox, I've found some string not translatable:

this page of hugin_toolbox is not part of version 2025.0. 

It was added after the release of beta 1, so the strings will be added in the next version.

So in version 2025.0 you will not see this page (and therefore these string are not shown).

Thomas

[T. Modes]

T. Modes schrieb am Freitag, 31. Oktober 2025 um 13:40:36 UTC+1:

today we are releasing release candidate 1 of Hugin 2025.0.0

mmh, nearly no feedback after more than a week. 

I wanted to release 2025.0 at the next weekend, but without feedback that it at least compiles and works this will delay...

Nobody has tested it? There were at least 50 downloads from sourceforge of the source package.

Thomas

[Robert Clausecker]

Hi Thomas,

Code builds fine for me on FreeBSD.
The LAPACK option is new, I didn't notice that in the Beta.
Perhaps you could point this out more clearly in the release notes.

Yours,
Robert Clausecker

Am Montag, dem 10.11.2025 um 09:53 -0800 schrieb 'T. Modes' via hugin
and other free panoramic software:

> --
> 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+...@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/hugin-ptx/bcda1bdb-51b7-4e68-9568-ff35f58c28c4n%40googlegroups.com
> .

[T. Modes]

Hi Robert,

fuz...@gmail.com schrieb am Montag, 10. November 2025 um 19:14:17 UTC+1:

Code builds fine for me on FreeBSD.

thanks for confirmation.

 

The LAPACK option is new, I didn't notice that in the Beta.
Perhaps you could point this out more clearly in the release notes.

Do you mean the option "ENABLE_LAPACK"? This is not new, it is availabe since 2009.

Thomas

[Robert Clausecker]

Hello Thomas,

Am Montag, dem 10.11.2025 um 10:34 -0800 schrieb 'T. Modes' via hugin

and other free panoramic software:

Yes, that's the one I mean. Seems like the original author of the port
didn't add this option back when the port was added to our ports
collection.

In any case, looking forwards to the release!

> Thomas

Yours,
Robert Clausecker

[Bruno Postle]

On Mon, 10 Nov 2025, 17:53 'T. Modes' wrote:

I wanted to release 2025.0 at the next weekend, but without feedback that it at least compiles and works this will delay...

Nobody has tested it? There were at least 50 downloads from sourceforge of the source package.

The fedora build is ok, and Hugin seems to run as usual, though I didn't do a lot of testing: 

https://copr.fedorainfracloud.org/coprs/bpostle/panorama/build/9764728/

-- 

Bruno

Bruno

[T. Modes]

Hi Bruno,

bruno...@gmail.com schrieb am Montag, 10. November 2025 um 20:30:03 UTC+1:

The fedora build is ok, and Hugin seems to run as usual, though I didn't do a lot of testing: 

thanks for the feedback.

Thomas

[Lajos Höss]

Hi Thomas,

I am working on the Hungarian translation. I cannot test the result because the windows installer is questionable (2025.0 RC1). See attached image. Why does hugin depend on NI programs (National Instruments LabVIEW)?

The Hungarian beta translation is finished. I don't know where to put the "&" sign for the remaining two translations. I'm afraid to install Hugin, will it conflict with Labview? I'm attaching the beta hu.po file.

Lajos

--

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+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/701916d7-459d-4e58-b3a7-7680fa2716can%40googlegroups.com.

[T. Modes]

Hi Lajos,

cqh...@gmail.com schrieb am Dienstag, 11. November 2025 um 21:35:46 UTC+1:

I cannot test the result because the windows installer is questionable (2025.0 RC1). See attached image. Why does hugin depend on NI programs (National Instruments LabVIEW)?

Hugin does not depend on NI programs. Hugin does need the  Microsoft Visual C++ Redistributable   https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 to run and the installer does install these files. The NI program are probably compiled with the same compiler and therefore needs the the same Visual C++ Redistributables.

The installer contains these files since 2016, until now nobody complained.

I could remove these files from the installer but then the user had to install these files by hand otherwise Hugin does not run and it will show a cryptic errror message - which would not be so nice user experience for casual users.

You can inspect the msi installer by yourself and check/extract the files in it.

Thomas

[Lajos Höss]

Hi Thomas,

Thanks for the help. I extracted the msi file. I tried the program and it's good. I uploaded the translations to the launchpad. Other programs, it usually offers the full Visual C++ Redistributables installer as an option during installation. NI programs are problematic, dll versions, etc.

Lajos

--

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+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/7fefd507-96c3-4514-850d-b8db253bb2a9n%40googlegroups.com.

[Abrimaal]

Thanks for building the new version.

The first impression: Wow, dark background > finally I can stitch night panoramas that waited for years.

and this is the only noticeable improvement visible to an experienced photographer.

In Batch processor, I noticed that when I check "Shutdown computer", 
Starting a new work next day, we simply don't remember (being humans) that the checkbox was selected. 
(Human memory is not a hard drive storing binary data.)
The computer shuts down after stitching a panorama.
Please take the checkbox as One Time option. 
At the next start the "Shutdown" gets automatically unchecked.

Hugin was dedicated for photographers, but written by programmers (there is no other way and this is the correct way).
Photographers (using many drivers, thousands of folders and organized workflow), are not exactly interested in numeric parameters. 
The simple interface is the default tool for creating panoramas.
Even when Hugin detects advanced features, and switches to advanced mode, 
when Opening a new file, please return to the Simple interface.

In Batch processor, this button is long awaited:
[ Open containing folder ] and point to that file in Explorer.
with thousands of folders it will significantly speed up the work.
If there is "Open in Hugin", the project may be also opened in Explorer.

Also an option to Delete a selected project (.pto file) from the drive, from the level of the Batch processor.
Anyway when Open Containing Folder is introduced, the project may be easily deleted in Explorer.

Clean up (Remove finished projects from the Processor).
It asks to remove Failed projects, but "File missing" stay on the list (are not removed from Batch).

Logs:
They are a  inconvenience is smooth workflow. In fact, nobody except the developers needs them.
Anyway they are saved every time when a project fails.
Photographers have different minds than programmers (not %0101#DF5, we see images, that's why we are photographers).
Humanists have also different minds - they see words. Musicians hear sounds.
It too difficult for us to write a command script, that goes through all folders and subfolders and deletes all *.log files.
In Batch processor there are options: Verbose Output and Always Save Log - they are useful for developers.
But what about users? 
[Never save Logs] or [Delete all Logs in current folder]

Skipping unaligned images.
When Batch processor fails to find control points in a single image, the whole project fails and is not processed.
When opening the .pto file in Hugin, the projection is not changed, exposures are not corrected (the Steps in .assistant files).
It could be done simpler and logically - all unaligned images are not processed (excluded), but the rest of images are processed (aligned, straightened, exposure corrected - depending on the assistant steps)
and the panorama becomes stitched without the excluded image(s).

[David W. Jones]

On November 26, 2025 7:59:38 AM HST, Abrimaal <abri...@wp.pl> wrote:
> Thanks for building the new version.
>

> The first impression: Wow, *dark background *> finally I can stitch night

> panoramas that waited for years.

> and this is the only *noticeable improvement* visible to an experienced
> photographer.
>
> In Batch processor, I noticed that when I check "*Shutdown computer*",

> Starting a new work next day, we simply don't remember (being humans) that
> the checkbox was selected.

> *(Human memory is not a hard drive storing binary data.)*

> The computer shuts down after stitching a panorama.

> Please take the checkbox as* One Time option*.
> At the next start the "*Shutdown*" gets *automatically unchecked.*

Makes sense to me.

> Hugin was dedicated for photographers, but written by programmers (there is
> no other way and this is the correct way).
> Photographers (using many drivers, thousands of folders and organized
> workflow), are not exactly interested in numeric parameters.
> The simple interface is the default tool for creating panoramas.

My default tool is the Advanced interface.

> Even when Hugin detects advanced features, and switches to *advanced mode*,
> when Opening a new file, please* return to the Simple interface*.

NO NO NO.

> In Batch processor, this button is long awaited:

> [ *Open containing folder* ] and point to that file in* Explorer.*

> with thousands of folders it will significantly speed up the work.
> If there is "Open in Hugin", the project may be also opened in Explorer.
>

> Also an option to *Delete* a selected* project* (.pto file) from the drive,

> from the level of the Batch processor.

> Anyway when *Open Containing Folder* is introduced, the project may be
> easily deleted in *Explorer*.

>
> Clean up (Remove finished projects from the Processor).

> It asks to remove Failed projects, but *"File missing*" stay on the list

> (are not removed from Batch).
>

> *Logs:*

> They are a inconvenience is smooth workflow. In fact, nobody except the
> developers needs them.
> Anyway they are saved every time when a project fails.
> Photographers have different minds than programmers (not %0101#DF5, we see
> images, that's why we are photographers).
> Humanists have also different minds - they see words. Musicians hear sounds.

As a writer, a musician, and a photographer, I have no problems dealing with numbers. Stops, field of view, exposure values, shutter speeds, ISO - all numbers. Photography, in particular, has long been connected with science, technology, and numbers.

Am I your idea of a humanist? I have B.A. and M.A. degrees in Creative Writing. I don't think coming from the humanities excludes understanding and use of numbers.

> It too difficult for us to write a command script, that goes through all

> folders and subfolders and deletes *all *.log files*.
> In Batch processor there are options: *Verbose Output* and *Always Save Log*

> - they are useful for developers.
> But what about users?

Useful to me when a stitch fails. And I'm not a developer.

> [*Never save Logs*] or [*Delete all Logs in current folder*]
>
> *Skipping unaligned images*.

> When Batch processor fails to find control points in a single image, the
> whole project fails and is not processed.
> When opening the .pto file in Hugin, the projection is not changed,

> exposures are not corrected (the *Steps in .assistant files)*.

> It could be done simpler and logically - all unaligned images are not

> processed (*excluded*), but the rest of images are processed (aligned,

> straightened, exposure corrected - depending on the assistant steps)

A feature I rarely use, and then only if all else fails.

> and the panorama becomes stitched without the excluded image(s).

Maybe an option, but in my experience the reason for "unaligned images" is usually that no control points were found *when they should have been*. So it tells me I need to add manual control points.

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

Sent from my Android device with F/LOSS K-9 Mail.