I did the following changes on Hugin++:
* When stitching the panorama, a temporary file with the image filenames is
created if the command line would be longer than about
7000 characters (to be exact: 8191 - 1024, older versions of Windows
support only 8191 chars in a command line,
and for other arguments I reserved generously 1024 chars). So Hugin++ works
both with enblend and with my modified Multiblend if the command line would
be too long.
In the control point list the following is changed:
* Added the buttons "next new image pair" and "previous new image pair". A
click on
"next new image pair" causes the next image pair (down) in the current
ordering to
be selected that is not used by the current or any of the above control
points.
I find it useful because I order the list by descending errors. I begin
with image
pairs with control points with high errors and delete bad CPs or increase
weights of good CPs.
Then I go down in the list, but often there are CPs from the same image
pair that I have
already checked. So by clicking on "next new image pair" I don't loose
time by looking at
the same image pair several times.
* "Stable ordering": You know that the list is sorted when clicking on the
list header in one column.
It is sorted by the "sort keys" in that column.
Stable ordering means that - if there are CPs with equal sort keys - they
are sorted by the (subordinated) sort key
of the column on whose header was previously clicked. If there are CPs
whose subordinated sort keys are also
equal, they are sorted by a sub-subordinated sort key (in the 2nd
previously clicked column).
* Added "average yaw" and "average pitch" in respective new columns of the
list. These are the
average yaw or pitch of the two images of the CP. The yaw and pitch can
be used just for information or for
sorting. Since yaw and pitch are real (not integer) values, CPs with
equal "average" yaw or pitch are typically
only those belonging to the same pair of images.
However you may want to view e.g. all control points with yaw between 20
and 40 and pitch between 0 and 20 and
sort them by descending error.
This is possible by not using the average yaw or pitch directly as sort
key. Instead the average yaw and pitch can be
projected into one interval inside a "stack" of equally-sized intervals.
Then the number of the intervals can
be used as sorting key.
The sorting from the above example can be achieved as follows: First, click
on the "error" column header once
or twice, so that sorting is done by descending errors.
Then click on the header of the "average pitch" column. A dialog appears in
that you can specify the pitch interval
from 0 to 20. Chose OK. Now sorting is done by the average pitch interval
number, followed by the error as subordinated
sort key. Now click on the "average yaw" column header. In the appearing
dialog choose the interval from 20 to 40.
Now sorting is done by the average yaw interval number, followed by the
average pitch interval number as subordinated
sort key and by the error as sub-subordinated sort key. All CPs that have
an image pair with average yaw and pitch in
the respective interval have yaw and pitch interval numbers 0. Scroll the
list to where these CPs are. They are
sorted by descending errors.
Florian Königstein schrieb am Donnerstag, 1. Juli 2021 um 22:01:19 UTC+2:
> There's a bug both in Hugin++ and in the latest official Hugin release
> (Hugin-2020.0.0):
> To reproduce it, start Hugin, and open a PTO file that is large enough so
> that the loading takes some seconds.
> Before the loading has finished, press the grayed out button for
> geometrical optimization in the "images" tab TWO times.
> After loading has finished, two windows with title "Panorama Tools" will
> appear. In one the text 012345678901234567890123456789... appears
> and nothing changes over time.
> The other "Panorama Tools" window behaves normally. When finished
> optimization, accept the results.
> Then Hugin / Hugin++ will crash.
>
> I didn't have the time to fix the bug. Maybe later.
>
> Florian Königstein schrieb am Donnerstag, 1. Juli 2021 um 21:46:47 UTC+2:
>
>> I have an update for fastPTOptimizer and also for the Windows installer
>> for Hugin++ that also installs the binaries for fastPTOptimizer.
>> When there are weights for CPs other than 1, say a weight 'w', it should
>> be exactly as if you had 'w' CPs with weight 1 at the same position. In the
>> old version of fastPTOptimizer the reported error during the optimization
>> wasn't correct. If e.g. all weights are 1000, the reported error should be
>> the same as if all weights were 1 since the error is an average over all
>> CP's errors. In the old version the error was too high if weights > 1 were
>> used. I have corrected it.
>>
>> bruno...@gmail.com schrieb am Donnerstag, 1. Juli 2021 um 12:14:54 UTC+2:
>>
>>> Apologies, I was wrong about this. Sourceforge does support the usual
>>>
