Re: [hugin-ptx] Mac builds of Hugin

['T. Modes' via hugin and other free panoramic software]

There are often reports about crashes in the Mac build in the bug tracker: 
https://bugs.launchpad.net/hugin/+bug/2045446
But nobody seems to take care of them?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/93870376-c091-4bf2-8b29-326c335d2e18n%40googlegroups.com.

[hugin-ptx] Re: so i extracted the OnFineTuneAll function from MainFrame into it's own binary...

['T. Modes' via hugin and other free panoramic software]

jak schrieb am Mittwoch, 15. Mai 2024 um 19:49:57 UTC+2:

my experience has been that cpfind creates a fair number of outright bad 
points and a few that are just a bit off and fine-tune tends to fix all of 
that fairly cleanly (where cpclean tends to miss many of these)


then this should be fixed in cpfind, don't it? This should be tried first 
before introducing a new tool. Maybe you could try this first?
So only if this does not help, the patch could be taken into consideration. 
But then the patch needs a lot of reworking:
* Don't duplicate code of base algorithms. That makes the maintenance more 
difficult than necessary. So both places should use the same code.
* When using wx functions in a program you need to initialize the wx 
library before. Command line tools should use wxWidgets only if absolute 
necessary (some single program need it, but most cli are not depended on 
wxWidgets).
* Also the image cache needs some more initialization before using it.
* You are using nearly the whole alphabet for switches. Not all switches 
are really necessary to tweak by the user (e.g. reproject, alternate, maybe 
other also). Some are totally unnecessary: the correlation is always 
between 0 and 1. No need to clean cp with correlation >1.0 - this does not 
happen. Also is really the tweaking of the curvature necessary? This adds a 
lot of complexity to the command line, documentation but also to the code, 
which is not necessary. 
There are many options technical possible, but it makes no sense to expose 
all finer details to the user. For some it is better to use sensible fixed 
default values.
* There may be other issues I have miss at a first scan of the code.

And then there are more formal issues
* Please provide an unified diff file with all changes in a single file. 
And not several files with the comment "feel free to put it wherever" (your 
words)
* Unnecessary code should be removed and not commented out only with the 
comment "not sure what these do but everything seems to work fine without 
it?". This helps nobody and adds only garbage.
* Please use our indentation/brace style (most new code is Allman style 
based) and don't mix in the same file.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/240af542-57fd-454e-9e17-2591257dbd03n%40googlegroups.com.

[hugin-ptx] Re: so i extracted the OnFineTuneAll function from MainFrame into it's own binary...

['T. Modes' via hugin and other free panoramic software]

jak schrieb am Mittwoch, 15. Mai 2024 um 07:45:23 UTC+2:

i wanted to script it in an assistant so here it is

the fine-tune function was written at a time without automatic control 
point detector in Hugin and was intended for fine-tuning manually set 
control points. Therefore scripting was not intending for this function.

For automatic found control points you should not call fine tune. Fine-tune 
works only at the 100 % scale. But the control points by cpfind are already 
optimized and contain information from several size scales. If you 
fine-tune these control points you destroy this information and so this 
should be avoided.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/778c643c-dd9a-439d-ae89-768a20777abcn%40googlegroups.com.

Re: [hugin-ptx] Re: cpfind manual not very clear

['T. Modes' via hugin and other free panoramic software]

chamele...@protonmail.com schrieb am Dienstag, 14. Mai 2024 um 15:25:00 
UTC+2:

I can't find documentation of what that sigma value really is. Can someone 
explain it ?


Under step 1in the manual:
calculates for each pair mean and standard deviation sigma  

The statistics the standard deviation is often labelled with sigma. So for 
more detail of standard deviation consult a maths book.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/200efc6f-71c7-485f-9032-d2655c595cedn%40googlegroups.com.

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

['T. Modes' via hugin and other free panoramic software]

lukas wirz schrieb am Dienstag, 7. Mai 2024 um 18:20:03 UTC+2:

That's slightly old, the version has been 4.3 for a bit. 


Just to make it more clear. The last released version is 4.2.
The current development in the default branch of the repository is using 
the version 4.3 to identify. This will be the next released version.
Lukas changes are currently only in the default branch of enblend 
repository http://hg.code.sf.net/p/enblend/code
but not in any official released version.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6b361cb9-c3d1-4d6f-970f-8d0ed354ee64n%40googlegroups.com.

[hugin-ptx] Re: Xpano

['T. Modes' via hugin and other free panoramic software]

Hi Bruno,
bruno...@gmail.com schrieb am Donnerstag, 2. Mai 2024 um 09:31:33 UTC+2:

Has anyone tried xpano?

"Automated photo stiching tool.
Import a directory of images and then export auto detected panoramas.


This is "only" a GUI for the panorama functions in the OpenCV. library It 
does not implement own panorama stitching algorithms.
In my simple tests the results were good for some projects, but for other 
projects it works not so good. 
There are no possibilities to manually improve/change the result. So it is 
a hit or miss. 
Also there were some memory issues for big projects.

In your feature list I don't see anything, which is not possible with Hugin.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f2ee79c5-50e8-4e83-b0f3-8f460c467efdn%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

['T. Modes' via hugin and other free panoramic software]

Chris schrieb am Montag, 15. April 2024 um 18:11:57 UTC+2:

...here. What is the third platform are you referring to?


Sorry, I did not check correctly. It was a mistake on my side. Take my 
excuse.

But you repeat often the same phrases: assumes options or implies options 
means in this context that the corresponding option automatically 
activated/set and does not need to set manually.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/76d3d605-587a-4163-8135-b91704390bbdn%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

['T. Modes' via hugin and other free panoramic software]

Hi Chris,

Chris schrieb am Montag, 15. April 2024 um 11:06:51 UTC+2:

The Panotools 3D page https://wiki.panotools.org/Talk:Align_image_stack gives 
a statement which is clearly wrong:

Please keep the discussion on one platform. This is now the third one you 
are using for the same questions. Most discussion are  done on this mailing 
list. The bug tracker and the wiki are not an ideal place for such 
discussion.

*align_image_stack -i -a AIS_ -S -A -P IMG_.*

   - 
   
   - 
   
   It only names one input file.
   
No, you can also use placeholder like ? or *. 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/580c2bc3-4c05-4c50-ba53-51c64c65c84fn%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

['T. Modes' via hugin and other free panoramic software]

Chris schrieb am Donnerstag, 11. April 2024 um 10:20:43 UTC+2:

*Great! The webpage is far more informative now, putting it into sections 
helps a lot. *

I’m only interested in 3D image processing, but I’ve had a look at all the 
options in case they might be relevant and I hope my further questions 
might help someone else. I'll look at the 3D ones later.


*--align-to-first*

*...This implies also the --use-given-order option. *

The -use-given-order is automatically activated. (But adding it manually 
makes no difference.)

*-f HFOV* *...use if EXIF info not complete* 


If neither is available what happens?

It will use a sensible default value - see output of the program.

*-l* *Assume linear input files are in linera colour space.* 

Is the default gamma colour space?

Yes.
 

*Optimisation phase* 

How do “(yaw, pitch and roll) “ relate to x, y,z?

They all together describe the position and direction of the camera in 
space. 
See coordinate system of panotools.

*-**m -d -i -x -y -z **Optimize field of view* 

I assume one might as well always set all of -m -d -i -x -y -z in order to 
optimise 
everything .

No, that' s totally wrong. The more parameter you try to optimize the more 
precise and better distributed control points you need. 
Especially optimization of x/y/z can often be fragile and should only be 
added when really needed. 
Instead of the command line the best would be to start with the pto file 
and optimize then in the GUI. First start with only the basic parameters 
and then add one parameter after the other and after each optimization run 
check the result in the preview window.
 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0393de32-4fff-4d74-a9ed-bd930ecd7fedn%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

['T. Modes' via hugin and other free panoramic software]

Chris schrieb am Dienstag, 9. April 2024 um 20:14:04 UTC+2:


*-v* Verbose, print progress messages. Repeat for higher verbosity
-
Does “Repeat…” mean that -v -v would output more details than -v?

yes,
 

*-l* Assume linear input files 
- 
Parameter-e states “(default: rectilinear)”. 
So isn’t this parameter redundant? Or does it mean something else? 

This refers to linear color space, this has nothing to do with rectilinear 
projection. So it is not redundant.
 

*--distortion* Try to load distortion information from lens database
 - 
Presumably if data is available, AIS uses it to try to compensate for the 
distortion. What happens if there is none or it’s invalid?

If no data is available, no distortion is corrected. 
 

*--use-given-order* Use the image order as given on the command line. (By 
default images will be sorted by exposure values.)
 - 
Does not affect 3D processing as images are identified as right and left by 
their order on the command line? 

Not sure what you mean with 3D processing.  
 

*--gpu* Use GPU for remapping 
-
 What happens if there’s no GPU or it’s unsuitable? 

Normally it should stop with an error message. But I have no test system 
without GPU. No sure if this is from any practical relevance.

*Group/Probable Relationship/Parameters/Function*

1x

Mutually exclusive

-p or -o

Output file(s)

No, they can be combined.
 

2x 

Mutually exclusive

-A or -P

-S?

Stereo image type

*It’s not clear whether -S must be used when -A or -P is, or whether it 
will be included automatically when -A or -P is.*

-A and -P add automatically switch -S internal.

*What is the difference between -A and -S?*

See the linked 
page 
http://vndlinuxphoto.blogspot.com/2011/01/stereo-image-alignment-in-hugin.html 


3x 

Mutually exclusive

-d -i -x -y -z

Which coordinate to optimise?

Can be combined in any combination. 

4x 

Mutually exclusive 

-e -l

Image geometry

*What’s the point of -l if the default is rectilinear?*

see above, both are unrelated. 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ac5a38ae-e958-4c9b-a39f-b5d9c17675e1n%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

['T. Modes' via hugin and other free panoramic software]

Chris schrieb am Dienstag, 9. April 2024 um 00:51:28 UTC+2:

I am using align_image_stack to align 2 images for processing into a 3D 
image.

There is documentation https://wiki.panotools.org/Align_image_stack but the 
page states that ““*This article is incomplete. You can help Panotools Wiki 
by expanding it 
.”*

The descriptions are brief and I’m not sure I completely understand them 
all. It is not clear which options are mutually exclusive.

I expanded the wiki page. Hopefully this make some more clear.
All (or most) of the switches are not mutually exclusive, they can be used 
together. 
By posting only PNG images you make it more difficult to answer to some of 
your points.

e.g. -l switch refer to linear color space. This has totally unrelated to 
rectilinear images, also fisheye images can be in linear color space. So 
this switch is not redundant.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0bf1f627-0578-4db5-9858-be6cf1170413n%40googlegroups.com.

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

['T. Modes' via hugin and other free panoramic software]

Venkat schrieb am Samstag, 30. März 2024 um 07:06:32 UTC+1:

Problems:
1) Attached Default.txt which captures the log output of the above steps.  
>From Line 112 to Line 143 we could see the match is made
among the combinations of the images ex: image 0.jpg  (its actually 1.jpg 
but zero indexed internally ) with all other images, likewise other images
are matched as well. 


No, it does not check all combinations.
e.g. image 0 is matched with image 1, 2, 3, 7, 8, 9, 10, 11; but not with 
images 4-6.
These matches are done because you have a lot of overlap between the images 
(see that most of the matches are done under the caption --- Find matches 
for overlapping images ---).

You see this also in the output of enblend: warning: some images are 
redundant and will not be blended.

So if speed is your main concern, reduce the number of images, because you 
have a lot of overlap and redundant images.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/add9e176-6f2d-4cda-bde3-5739314d4cefn%40googlegroups.com.

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

['T. Modes' via hugin and other free panoramic software]

Venkat schrieb am Freitag, 29. März 2024 um 02:09:38 UTC+1:

So when hugin_executor gets called with --assistant it calls 
"cpfind" with some defaults. This results in trying all matches ( 
regardless of sort or not  
during the "pto_gen" step). 


Either you have not set the multirow switch for the default cp generator or 
something else is going wrong.
But have been said already and I have the feeling we are going in circles. 
The best would be you provide a link to one image set and the log of 
commands. Then we can try ourself and compare with your output.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/732065dd-6ed6-4c55-9a4b-70fc6fe89e8en%40googlegroups.com.

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

['T. Modes' via hugin and other free panoramic software]

Hi Greg,
Groogle schrieb am Mittwoch, 27. März 2024 um 02:03:34 UTC+1:


Wouldn't it be a good idea to check what the current setting is first? 
But I can't find how to do that in the GUI, and I can't find a "reset 
to default" button, just "Load Defaults". 

I meant this button. I did not check the English string, I looked only on 
the localized version.
 

This is Hugin 
2023.0.0.d88dc56ded0e. But the information is all in the ~/.hugin 
file. Here an example entry that probably matches what Thomas is 
saying: 

That corresponds to two entries on the GUI preferences screen, Hugin's 
CPFind and Cpfind (multirow/stacked). 

So you did change these settings in the past! The default setting has 6 
entries.

It's not clear, though, that this is what you want. --multirow only 
makes sense when you have, well, multiple rows. 

That is a misunderstanding. The multirow algorithm works also fine for 
single row panoramas.
The help page for cpfind states under --multirow:
> This is an optimized matching strategy for single and multi-row panorama: 
 

> Then check the default control point setting, it should be cpfind 
> and it should contain the --multirow switch in the settings. 

Thomas: OK, where do I check this? How do I change it? 

I though the "edit" button directly beside the list is obviously enough.
 Mhh, maybe I should rename the button to "show the setting and 
let me change them to my personal preferences"

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/52203402-2a06-4a00-8122-184187a7c29bn%40googlegroups.com.

Re: [hugin-ptx] Re: Providing order of images in Hugin assistant

['T. Modes' via hugin and other free panoramic software]

Venkat schrieb am Dienstag, 26. März 2024 um 07:48:18 UTC+1:

>From reading the code 
https://github.com/ndevenish/Hugin/blob/master/src/hugin1/executor/hugin_executor.cpp
 
looks like there isn't much option to provide "use the predefined order of 
images''. 


This is not the official repository. And it is totally out of date.
Hopefully you are using a current version and not this very old one from 
the mentioned repo.

When the assistant checks all image pairs there is a wrong setting in the 
preferences.
Goto the menu File>Preferences, on tab control points detectors select 
reset to default.
Then check the default control point setting, it should be cpfind and it 
should contain the --multirow switch in the settings.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cb459f3b-226d-46da-89be-4b832e9475can%40googlegroups.com.

[hugin-ptx] Re: Providing order of images in Hugin assistant

['T. Modes' via hugin and other free panoramic software]

Please post only once. No need for duplicate posts.

Venkat schrieb am Montag, 25. März 2024 um 17:11:16 UTC+1:

Since we know the order to be stitched wonder is there a way to force the 
assistant to use the designated order as opposed to trying all the 
permutations.  Any pointers would be really appreciated.


The default assistant is using cpfind --multirow. This should prevent a 
check of all permutation and only test a sensible count if image pairs. (It 
falls back to all image pairs only if there are unconnected image pairs.)

Otherwise you would assign rough image positions and then run cpfind 
--prealigned. But this would require some more adjustment to the assistant.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2e8a9fbe-c67c-44bd-8096-828aca8591f7n%40googlegroups.com.

[hugin-ptx] Re: Optimization with few bad points

['T. Modes' via hugin and other free panoramic software]

Hi,
byfl...@gmail.com schrieb am Sonntag, 24. März 2024 um 15:56:48 UTC+1:

 Due to regular structure on microchips often there are quite a few 
(0.1-1%, sometimes even 5%) incorrect control points. It is clear that 
optimizing control point detector is first step to resolving the issue, but 
it is hard to prevent it completely. 

Does anyone know if optimization algorithm can be adjusted to behave 
differently? Are there different optimizers and did optimizer drastically 
changed over last few years?


There are no different optimizer in Hugin/panotools and it did not change 
drastically in the last years.

For this use case there is cpclean which should delete most of the wrong 
control points automatically.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7dab43ce-514d-4cda-92d9-be88b430d708n%40googlegroups.com.

[hugin-ptx] Re: OpenMP CMakeLists.txt patch

['T. Modes' via hugin and other free panoramic software]

Markus Meier schrieb am Sonntag, 24. März 2024 um 10:02:49 UTC+1:

would it be possible to include a fix to explicitly disable OpenMP if 
requested by the user? 


Sorry, but I don't understand what's your problem here.
This code is in place since 10 years without problems.
Second disabling the OpenMP multithreading does slow down many parts of 
Hugin. 

And the linked bug report does not help further.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/77f91364-c51a-4f12-9c58-f075c7e2aea8n%40googlegroups.com.

Re: [hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

['T. Modes' via hugin and other free panoramic software]

chamele...@protonmail.com schrieb am Donnerstag, 14. März 2024 um 01:41:13 
UTC+1:

Ok, so it's only documented in --help but not in man cpfind. To me the 
manual is usually supposed to be more complete than the help, so I use "man 
command" most often. 


Currently there are 3 possible places:
* program --help
* man program -> only on Linux, but not on Windows
* help pages in the GUI

When I add new switches I always add it to the program --help output. This 
should be the up to date place.
The other 2 places may be out of date.
In case of the help pages you can help and edit these pages on the 
wiki.panotools.org. They will then be update before a new release.

For the man pages, which are only available on Linux, updates from users 
are welcome. If you send a patch file with your proposed changes they can 
be easily incorporated.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d4e81266-e79e-4989-af74-e17cdbb58b74n%40googlegroups.com.

Re: [hugin-ptx] Re: Disappearing photo list in the Photos tab

['T. Modes' via hugin and other free panoramic software]

mkogoj...@gmail.com schrieb am Sonntag, 25. Februar 2024 um 16:25:59 UTC+1:

Hello.

Which repository would that be? I'm on Windows and repo sounds more like 
Linux, but from what I could tell OP was as well.


The official source code repository was meant: 
https://sourceforge.net/p/hugin/hugin/ci/default/tree/
This is contains the source for all platforms, not only Linux.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/26b24fcf-9f5c-4b4d-91fd-fe8d53a3545bn%40googlegroups.com.

Re: [hugin-ptx] creating panoramas directly from RAW images

['T. Modes' via hugin and other free panoramic software]

kfj schrieb am Freitag, 23. Februar 2024 um 17:38:09 UTC+1:


So it's not done with simply replacing the load image call with another 
library. 
The whole ecosystems needs to be adopted and you have to implement a lot of 
functions of a raw converter.

 
No, you don't. 


Sorry, but you are ignoring Hugin photometric optimizer and the photometric 
corrections done at stitching totally. It may not be import for you, but I 
see this an important feature of Hugin and this will not work with your 
proposed workflow..
 

They are already all there, and you simply pass the parameters you want. 
Again, here's the link to OIIO's libRAW plugin 

 
, you'll see it's pretty much all there. And in lux you can simply pass 
these args on e.g. on the command line, like --oiio_arg=raw:user_flip=0


Sorry, but this something for programmers or nerds. This is nothing a 
regular user does. 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/81c84892-37ff-4b2a-ae91-7a0494a8815cn%40googlegroups.com.

Re: [hugin-ptx] creating panoramas directly from RAW images

['T. Modes' via hugin and other free panoramic software]

kfj schrieb am Freitag, 23. Februar 2024 um 08:35:28 UTC+1:

My proposal is simply about reading image files into the program. it's to 
replace use of libvigraimpex for image import, that's all. Everything else 
remains just the same. This is why it was so easy to 'slot it in' to cpfind 
and pto_gen:


Sorry for kill the joy. But when taking the full Hugin workflow into 
account and take all advantage of the raw format it becomes fast more 
complicated.

It's not so easy to just replace the load routines, the whole ecosystem 
around have to be adopted.
Just to mention some things to considers:
* The colorspace of the image data has to controlled, ideally a linear 
colorspace with a wide gamut and not default gamma corrected sRGB of OIIO.
* Disable all automatic changes/adoption by libraw (auto brightness, …).
* Control the white balance, so that all images get the same wb.  (e.g. 
reading from the first one and apply this then to the other images)
* Take care of the cropping of the raw images (they often contain black 
borders).
* Take care of rotation of the images.
* Allow the user to change some parameters (debayer algorithm, noise, …). 
Then the user want a GUI to change them interactive and fast preview. These 
would mean to implement a crude raw converter GUI into Hugin.(Just out of 
curiosity, OIIOs raw import has at least 24! different user settings for 
the raw import.)

These are only the first issues came me into consideration - these are 
simply ignored by your proposal. 

(There may be some program parts which would also work without take all 
this considerations. But it needs to be taken into consideration the whole 
workflow.)

Taking all together would mean to extend the file format to save the new 
settings and the load routine would needs to update to take care of them.

Converting a raw image takes also some run time. How does this affect the 
responsivity of the GUI, especially when loading several images or when the 
caching of the images is needed?

So it's not done with simply replacing the load image call with another 
library. 
The whole ecosystems needs to be adopted and you have to implement a lot of 
functions of a raw converter.

IMHO there are dedicated raw converter better suited for these task. Hugin 
can already take care of some of them. This I consider a better solution, 
than to open Pandoras box and implement a lot of RAW converter features 
into Hugin.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/34049e94-853e-4c6c-9abc-8f3ef0a5be28n%40googlegroups.com.

Re: [hugin-ptx] Re: Compiling Hugin 2023.0.0 on Ubuntu 22.04

['T. Modes' via hugin and other free panoramic software]

gianni.c...@gmail.com schrieb am Freitag, 5. Januar 2024 um 18:19:02 UTC+1:

Hi Thomas,
I try the commend:
/opt/hugin$ cmake -DCMAKE_INSTALL_PREFIX=/usr/local 
-DCPACK_BINARY_DEB:BOOL=ON hugin-2023.0.0

the content of /opt/hugin id
/opt/hugin$ ll
totale 12
drwxr-xr-x  3 lorenzo root4096 gen  5 09:19 ./
drwxr-xr-x  9 rootroot4096 gen  5 09:17 ../
drwxrwxr-x 16 lorenzo lorenzo 4096 gen  5 18:12 hugin-2023.0.0/


That looks good.

-rw-rw-r--  1 lorenzo lorenzo 14511 gen  5 09:28 CMakeCache.txt

 I don't understand, I'm not in the source folder for cmake and pass the 
correct folder for hugin, but the error is the same.

What's wrong?

There are still temporary files from the first wrong call in the directory.
Delete the complete directory and extract newly from the tarball to be on 
the right side.

Do you have write access to the /opt folder?

If it happens again please attach the complete log.
What is your CMake version?

Just for the mentioned warnings/errors:

CMake Warning (dev) in CMakeLists.txt:
  No project() command is present.  The top-level CMakeLists.txt file must
  contain a literal, direct call to the project() command.  Add a line of
  code such as

project(ProjectName)

in ./CMakeLists.txt, line 61 is 
project(hugin)

CMake Error at translations/CMakeLists.txt:7 (find_package):
  By not providing "FindMSGFMT.cmake" in CMAKE_MODULE_PATH this project has 

in the source tarball there is a file CMakeModules/FindMSGFMT.cmake

CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

cmake_minimum_required(VERSION 3.22) 

line 3 in ./CMakeLists.txt is
cmake_minimum_required(VERSION 3.8 FATAL_ERROR )

So if you pass the correct root folder I have no idea why CMakes complains 
about these lines, because the necessary lines/file are there.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6e0ac391-8536-4639-a863-21e1cd3c3204n%40googlegroups.com.

[hugin-ptx] Re: Compiling Hugin 2023.0.0 on Ubuntu 22.04

['T. Modes' via hugin and other free panoramic software]

Hi,

gianni.c...@gmail.com schrieb am Freitag, 5. Januar 2024 um 10:06:50 UTC+1:

Hi I try compiling hugin on ubuntu 22.04 but I have problem.
I have download the package and extract in a folder, the run cmake as 
follow:

---


/opt/hugin/hugin-2023.0.0$ cmake -DCMAKE_INSTALL_PREFIX=/usr/local 
-DCPACK_BINARY_DEB:BOOL=ON /opt/hugin/hugin-2023.0.0
CMake Warning (dev) in CMakeLists.txt:
  No project() command is present.  The top-level CMakeLists.txt file must
  contain a literal, direct call to the project() command.  Add a line of
  code such as

project(ProjectName)

 

How can I resolve?


First you need to call CMake from a separate build directory and not try an 
in-tree build.

Second, you need to pass the root of the Hugin source to CMake and not the 
src sub-directory only.

Thomas 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3a90339a-263c-4a71-8715-c935fbd3cc1dn%40googlegroups.com.

Re: [hugin-ptx] Control points improvement proposal

['T. Modes' via hugin and other free panoramic software]

bruno...@gmail.com schrieb am Freitag, 5. Januar 2024 um 13:54:39 UTC+1:

I can't check the exact usage from here, but look for the 'multirow' option.

This does a linear match (matching consecutive images), then matches the 
ends of each resulting disconnected chain together, then finally does a 
'prearranged' match (with the hope that the previous steps have put 
everything in an approximate position).


Alternatively you can assign rough positions to the images (via template or 
pto_var) and then call cpfind with --prealigned option to only match now 
overlapping images.

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8508c501-af12-4c98-b5ba-0ca2bcc4a051n%40googlegroups.com.

Re: [hugin-ptx] Re: Disappearing photo list in the Photos tab

['T. Modes' via hugin and other free panoramic software]

Hi Frederic,

davi...@gmail.com schrieb am Samstag, 16. Dezember 2023 um 10:15:18 UTC+1:

One important piece of information : because I have a (close to) 4K 
display, I set the scaling to 200%. If I set it to 100%, all those issues 
disappear.


That's the culprit. wxWidgets does automatically scale the bitmap with this 
factor - so the preview size increases.
It should now be fixed in the repository.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/845a6b8f-2d34-404e-a3a6-c221beb3b60bn%40googlegroups.com.

Re: [hugin-ptx] Re: Simple UI improvement suggestion (correct exposures and colors)

['T. Modes' via hugin and other free panoramic software]

GnomeNomad schrieb am Freitag, 15. Dezember 2023 um 00:33:50 UTC+1:

I suppose it depends on your definition of HDR, but my understanding is 
that HDR is 16-bit or higher... My thought on it is "HDR" is anything 
higher than 8-bit per color channel, 


yes, a HDR image is 16 bit or higher. But the reversal is not valid: a 16 
bit image is not automatically a HDR image. There are also 16 bit LDR 
images.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7e921bd0-1874-4208-9d0c-651cdfd46466n%40googlegroups.com.

Re: [hugin-ptx] Re: Simple UI improvement suggestion (correct exposures and colors)

['T. Modes' via hugin and other free panoramic software]

GnomeNomad schrieb am Donnerstag, 14. Dezember 2023 um 00:59:13 UTC+1:

There's one situation where Abrimaal's idea makes sense for me: when using 
16-bit HDR source images. I don't do any exposure corrections in the source 
images, just take them as the camera produced them.

What (consumer) camera produces HDR images straight out of the cam?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9f9206f0-dfcb-4fad-8326-27c5945940f8n%40googlegroups.com.

Re: [hugin-ptx] Re: Inno setup - The .MSI installer version of Hugin is compatible with the "INSTALLDIR" option in the [RUN] section in Inno Setup?.

['T. Modes' via hugin and other free panoramic software]

samir@fenomatch.com schrieb am Donnerstag, 14. Dezember 2023 um 
11:14:02 UTC+1:

Good morning, thanks for responding. So maybe there is a 32-bit installer 
that will install me in "Program File (x86)"?

The effort for building an additional 32 bit installer is significant 
higher than the benefit.
A 32 bit program can use only 2 GB of memory and will therefore have more 
problems with bigger panoramas.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7e9836cf-2f4f-48aa-b29b-a689d44b7320n%40googlegroups.com.

Re: [hugin-ptx] 2023.08 Flatpak EGL 1.5 required

['T. Modes' via hugin and other free panoramic software]

GnomeNomad schrieb am Donnerstag, 14. Dezember 2023 um 00:58:15 UTC+1:

Oh. I always thought the benefit of the flatpak concept was that it was 
independent of the installed system.


Some basic stuff needs to be in the drivers. They can't be in the flatpack.
If you want a complete independent program you would need to use a live 
CD/system.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8278e73b-8acf-4a1e-b745-d0668ee39c46n%40googlegroups.com.

[hugin-ptx] Re: Disappearing photo list in the Photos tab

['T. Modes' via hugin and other free panoramic software]

davi...@gmail.com schrieb am Mittwoch, 29. November 2023 um 15:24:30 UTC+1:
 

My first idea was to install the latest version, which I did. Same results. 
Then I tried to reset the parameters, no improvement. I have found the 
workaround, but is there a way for me to fix this?

sorry for answering so late. But I have no idea what could cause these 
issue. The size of these panes is coded in the xrc file. There could be 
some dynamic adjustment to adapt to different window size / display 
resolution. 
So my initial idea would be to reinstall the version (but this you did 
already). 
So maybe deleting the stored window size in registry. Close Hugin, start 
regedit, navigate to HKEY_CURRENT_USER\Software\hugin and delete the folder 
MainFrame. The close regedit and restart Hugin.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f203f88c-9a38-4544-b993-360318eacbd1n%40googlegroups.com.

[hugin-ptx] Re: Simple UI improvement suggestion (correct exposures and colors)

['T. Modes' via hugin and other free panoramic software]

Abrimaal schrieb am Montag, 11. Dezember 2023 um 01:20:18 UTC+1:

After 10 years of making panoramas in Hugin, I see that the most of 
panoramas look better (more naturally) without exposure correction. 
Especially the sky and night scenes.

I suggest adding two *optional* steps in the Assistant preferences:
Correct exposures, correct colors,
without entering the Panorama editor to Reset.


I see the opposite. For me the panoramas become significant better with 
photometric corrections.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/83aebad0-deb1-41d5-a4ca-f1e3b5188769n%40googlegroups.com.

Re: [hugin-ptx] 2023.08 Flatpak EGL 1.5 required

['T. Modes' via hugin and other free panoramic software]

GnomeNomad schrieb am Montag, 11. Dezember 2023 um 10:30:40 UTC+1:

So, I'm confused. The *flatpak* version of Hugin requires EGL 1.5 but it's 
not included in the flatpak, or *all* versions of Hugin require EGL 1.5? 
Thanks. 


The underlying GUI library wxWidgets is using (by default) EGL 1.5 to 
support OpenGL (wxGLCanvas) under Wayland. So Hugin inherits this 
dependency.
I think it does not packed into the flatpak, instead the graphics driver 
has to support EGL 1.5 or later.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/74b37041-1bc1-46e3-ba68-14959b0e9a62n%40googlegroups.com.

[hugin-ptx] Re: Inno setup - The .MSI installer version of Hugin is compatible with the "INSTALLDIR" option in the [RUN] section in Inno Setup?.

['T. Modes' via hugin and other free panoramic software]

samir@fenomatch.com schrieb am Mittwoch, 13. Dezember 2023 um 14:39:10 
UTC+1:

But in the end Hugin installs "Program files" and it is not "Program Files 
(x86)" as I wish.


The installer is 64 bit and therefore the files belongs into "Program 
Files" and not into "Program Files (x86)". This folder is only for 32 bit 
programs.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ec4be347-ec29-4811-8d77-86d4c4f7cadan%40googlegroups.com.

[hugin-ptx] Hugin 2023.0.0 released

[T. Modes]

 Hi all,

today we are releasing Hugin 2023.0.0 

Source tarball can be downloaded
at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/hugin-2023.0.0.tar.bz2/download

Verify its checksums:
md5:
a0a14535cc5a06b75940c4d3a989b658 hugin-2023.0.0.tar.bz2
sha1:
78d3fb8732e50b37b4db4d3abe3e29b1f8e74653 hugin-2023.0.0.tar.bz2

This is a source code release. 
Users communities produce executables for their respective platforms. 
Please announce them here.
When building on Linux check that the configuration of all dependencies 
matches. This refers mainly to wxWidgets and GLEW. See the release notes 
for more details https://hugin.sourceforge.io/releases/2023.0.0/en.shtml

(The release correspond to changeset d88dc56ded0e our repository, which is 
also tagged as 2023.0.0).

Changes since 2022.0
* PTBatcherGUI can now also queue user defined assistant and user defined 
output sequences.
* PTBatcherGUI: Added option to generate panorama sequences from an 
existing pto template.
* Assistant: Added option to select different output options like 
projection, FOV or canvas size depending on different variables (e.g. image 
count, field of view, lens type).
* Allow building with epoxy instead of GLEW for OpenGL pointer management.
* Several improvements to crop tool (outside crop, aspect ratio, ...).
* Several bug fixes (e.g. for verdandi/internal blender)

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-2023.0/Hugin-2023.0.0-win64.msi/download

MD5 checksum
a78c2e9083424ba202d26e296f7c88cf Hugin-2023.0.0-win64.msi

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/bc9f1df6-ce0f-408b-bd9c-79292a0c01e0n%40googlegroups.com.

[hugin-ptx] Hugin 2023.0 rc1 released

[T. Modes]

 Hi all,

today we are releasing release candidate 1 of Hugin 2023.0.0 

Source tarball can be downloaded
at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/hugin-2023.0rc1.tar.bz2/download

Verify its checksums:
md5:
e15c4760d0199dd051915e480fd42c3f hugin-2023.0rc1.tar.bz2
sha1:
182c6272883389a1b8eda0c6238efefdd848d302 hugin-2023.0rc1.tar.bz2

This is a source code release. 
Users communities produce executables for their respective platforms. 
Please announce them here.
When building on Linux check that the configuration of all dependencies 
matches. This refers mainly to wxWidgets and GLEW. See the release notes 
for more details https://hugin.sourceforge.io/releases/2023.0.0/en.shtml

(The rc1 correspond to changeset 287ae9ecb029 our repository, which is also 
tagged as 2023.0rc1).

Changes since 2023.0 beta1
* Updated translations files.
* Fixed an assert when stitching.
* Fixes display of progress messages under wxGTK.
* Fixes a bug in stack detection.
* Fixed a bug in verdandi when blending about 360 deg border.
* Fixes retrieving color profile under Windows.

Changes since 2022.0
* PTBatcherGUI can now also queue user defined assistant and user defined 
output sequences.
* PTBatcherGUI: Added option to generate panorama sequences from an 
existing pto template.
* Assistant: Added option to select different output options like 
projection, FOV or canvas size depending on different variables (e.g. image 
count, field of view, lens type).
* Allow building with epoxy instead of GLEW for OpenGL pointer management.
* Several improvements to crop tool (outside crop, aspect ratio, ...).
* Several bug fixes (e.g. for verdandi/internal blender)

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

Please test and report bug/issues to mailing list or bug tracker 
https://bugs.launchpad.net/hugin (so issues can be fixed before the final 
release).

Windows binaries (64 bit) can be found at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/Hugin-2023.0rc1-win64.msi/download

MD5 checksum
4fda5d62e26ff71531f2843979c8ccf4 *Hugin-2023.0rc1-win64.msi

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/96f059ce-23c2-4712-be12-fbacc9ae6adfn%40googlegroups.com.

[hugin-ptx] Re: Cropping using hugin_executor

[T. Modes]

Hi Jon,

hugin and other free panoramic software schrieb am Donnerstag, 19. Oktober 
2023 um 11:32:06 UTC+2:

The problem is that I can't see how to achieve this same crop when using 
the executor.  Can someone tell me if this is possible please and if so how 
to do it?


It is possible. But the way depends on the exact workflow.
Hugin_executor itself does not calculate the crop. It delegates the 
function to other program.

The crop function itself can be called by pano_modify:
pano_modify --crop=autooutside ..

If you already calling pano_modify in your script simply adopt the call 
from pano_modify --crop=auto to the above.

If you are using the default assistant, you can create an user-defined 
assistant. You can use the example normal.assistant (under \Hugin\share\hugin\data\assistant under windows or 
/usr/local/share/hugin/data/assistant under Linux) file as starting point 
and modify the pano_modify call.

In the current 2023.0 beta 1 you could instead also using an user-defined 
output options (File/Preferences, Assistant tab) and use the outside crop 
from there.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e54bf114-e613-4b08-8fc3-7b6304a0d788n%40googlegroups.com.

[hugin-ptx] Re: Re: Hugin 2023.0 beta 1 released

[T. Modes]

Hi Jeff,

eljef...@gmail.com schrieb am Sonntag, 15. Oktober 2023 um 18:16:11 UTC+2:

I started hugin with an existing project, confirmed it was the beta with 
Help->About
I typically use the fast panorama preview window, and that window went 
completely blank -- only the "File,Edit,View,Interface,Help" menu items 
were visible, the tabs "Assistant ... Crop" were not displayed at all.

I can reproduce this behaviour by:

. Minimizing the fast preview window
. Removing an image from the project
. Restore the fast preview window

If I click the undo button (making the removed image part of the project 
again), the fast  preview window displays everything properly.

I don't know if this bug existed in the previous version of hugin.


 

Libraries
wxWidgets: wxWidgets 3.0.5
wxWidgets Library (wxGTK port)
Version 3.0.5 (Unicode: wchar_t, debug level: 1),
Runtime version of toolkit used is 3.24.
Compile-time GTK+ version is 3.24.33.


Nobody else has reported something similar. So I assume a build issue. The 
wxWidgets version is very old - it has some flaws with Wayland.
Read the "notes" section in the file INSTALL_cmake or in the release notes.
Either activate the workaround or - better - use wxWidgets 3.2.x.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/18579529-95d8-4058-8ae8-3a81c4147b1cn%40googlegroups.com.

Re: [hugin-ptx] Re: Hugin 2023.0 beta 1 released

[T. Modes]

Hi David,

David Benes schrieb am Sonntag, 15. Oktober 2023 um 19:34:50 UTC+2:

The only thing I wasn't able to find (and test) is the FOV output option in 
the assistant.

The setup is done in the preferences, tab  assistant. Tick option 
"User-defined output options", then configure and set the options for your 
use case.

Also please find the attached updated Czech translations.
(not sure whether complete updated file or diff is better to be shared, so 
attaching both)

Thanks, committed to repository. 

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a80cd36c-00a2-480e-8b96-8104811969een%40googlegroups.com.

[hugin-ptx] Re: Dwarf Gigapixel panoramas

[T. Modes]

Hi Tamas,

KissT schrieb am Mittwoch, 11. Oktober 2023 um 20:11:20 UTC+2:

Is this possible in Hugin, or will be anytime soon, as for now my 
panoramas are just sitting idle waiting to be assembled. 


This is already possible. First set the initial positions of the images 
either with a template or with pto_var (and the shooting pattern).
Then run cpfind --prealigned ... 

see e.g. https://groups.google.com/g/hugin-ptx/c/Af7TG2Bq-ko for a similar 
use case (pano from drone)

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/87b1aefa-0968-42f4-b68d-b7dd6ba46197n%40googlegroups.com.

Re: [hugin-ptx] Re: Aligning multiple image stacks in the same pano - any way to do this automatically?

[T. Modes]

Hi Jochiam,

j-sc...@gmx.de schrieb am Montag, 9. Oktober 2023 um 23:25:57 UTC+2:

Hi Thomas!
Wow! Now I know why the expert interface is called like that.
Thank you very much. I would never have found this!

Is my use case so unusual that such a function is so hidden?


Hugin is very flexible. But that means also many options. So we can't show 
all on one page.
So this option is only shown when you see the actual stacks. Otherwise you 
don't see direct the effect when linking/unlink the position.

Beside this there are 2 other options:
* when adding the images the user is asked if the stacks should be linked 
or not. (In the current version (also in 2023.0 beta 1) there is a bug in 
the stack detection code. This will be fixed in 2023.0 rc1.)
* when setting the stack size the user can also choose to link or not the 
position.

Thomas

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cf7db8c2-5e91-4e90-92ae-5e0b0be3f440n%40googlegroups.com.

Re: [hugin-ptx] Re: Hugin 2023.0 beta 1 released

[T. Modes]

Thanks Harry, committed to repository. 

hvd...@gmail.com schrieb am Freitag, 6. Oktober 2023 um 18:41:12 UTC+2:

Please find attached the updated Dutch translation.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2d0b5bf0-0b9e-416e-957f-e61034b1593an%40googlegroups.com.

[hugin-ptx] Re: Hugin 2023.0 beta 1 released

[T. Modes]

Hi all,

have anybody tested the new features? 
No response until now? Does this mean that all works fine?

Also a reminder to all translators. There are still some/many untranslated 
strings.
The current status:
complete
de.po 
1800 translated messages.

some missing translations:
ca_ES.po 
1673 translated messages, 79 fuzzy translations, 48 untranslated messages.
ca...@valencia.po 
1673 translated messages, 79 fuzzy translations, 48 untranslated messages.
pt_BR.po 
1710 translated messages, 53 fuzzy translations, 37 untranslated messages.
fr.po 
1674 translated messages, 75 fuzzy translations, 51 untranslated messages.
hu.po 
1687 translated messages, 70 fuzzy translations, 43 untranslated messages.
it.po 
1760 translated messages, 20 fuzzy translations, 20 untranslated messages.
sk.po 
1710 translated messages, 54 fuzzy translations, 36 untranslated messages.
nl.po 
1710 translated messages, 53 fuzzy translations, 37 untranslated messages.

and finally languages with many untranslated strings:
cs_CZ.po 
1417 translated messages, 271 fuzzy translations, 112 untranslated messages.
da.po 
1439 translated messages, 248 fuzzy translations, 113 untranslated messages.
es.po 
1282 translated messages, 407 fuzzy translations, 111 untranslated messages.
eu.po 
896 translated messages, 500 fuzzy translations, 404 untranslated messages.
fi.po 
709 translated messages, 598 fuzzy translations, 493 untranslated messages.
ja.po 
986 translated messages, 507 fuzzy translations, 307 untranslated messages.
pl.po 
1182 translated messages, 386 fuzzy translations, 232 untranslated messages.
ro.po 
582 translated messages, 682 fuzzy translations, 536 untranslated messages.
ru.po 
1383 translated messages, 254 fuzzy translations, 163 untranslated messages.
sv.po 
964 translated messages, 537 fuzzy translations, 299 untranslated messages.
zh_CN.po 
1216 translated messages, 375 fuzzy translations, 209 untranslated messages.
zh_TW.po 
1174 translated messages, 396 fuzzy translations, 230 untranslated messages.

en_GB.po 
69 translated messages, 32 fuzzy translations, 1699 untranslated messages.

So it would be good if you could update your translation file.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ca20f39d-1a35-46ea-b8ea-4e8eb80f77cbn%40googlegroups.com.

[hugin-ptx] Re: Hugin 2023.0 beta 1 released

[T. Modes]

Hi Andreas,
Andreas Metzler schrieb am Sonntag, 1. Oktober 2023 um 14:01:01 UTC+2:


FWIW I have also opened an upstream ticket on 
https://github.com/flann-lib/flann/issues/514


thanks for taking care of this. Much appreciated.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e3430b94-b9b8-4715-96fe-6a2f66158be7n%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Mittwoch, 27. September 2023 um 00:01:02 UTC+2:

Just want to put out this again but with a refined change.
In *ImageTransformsGPU.cpp *we have following
*:*
const int bytesPerDestPixel = 16 + 16 + 8
  + ((XGLMap[destGLTransferFormat] != 
GL_RGBA32F_ARB) ? BytesPerPixel[destGLTransferFormat] : 0)
  + ((destAlphaBuffer != NULL) ? 1 : 0);
const long long int maxDestPixels = gpuMemoryRemaining / 
bytesPerDestPixel;


*Change to below for mac M1 ARM 64-bit:*
const int bytesPerDestPixel = 16 + 16 + 8
  + ((XGLMap[destGLTransferFormat] != 
GL_RGBA32F_ARB) ? BytesPerPixel[destGLTransferFormat] : 0)
  + ((destAlphaBuffer != NULL) ? 1 : 0);
#ifdef __aarch64__  // Check for ARM 64-bit architecture
   * const long long int maxDestPixels = gpuMemoryRemaining / 
bytesPerDestPixel / 2;*
#else
const long long int maxDestPixels = gpuMemoryRemaining / 
bytesPerDestPixel;
#endif


I asked you already the last time to use a diff file and not to copy this 
into the mail. The mail program does often mangle the format. And the exact 
line in the code is unknown, I have to guess. (It may works in this simple 
case, but for more complicated one this becomes more complicated.)
 


By reducing bytesPerDestPixel by half I can process huge files on my M1. 
Tested 2 X  1 pixel files and they come out just fine. My first fix 
would segfault on these files.
Of course this could be tested more and maybe you want a version to try 
mikko? You are actually the first person I hear about selecting the GPU 
option working on M1.

If tested around some maybe it would be a legit fix? What´s your opinion 
T.Modes?


If you can explain why a factor of 2 is needed only for the Mac M1, yes. 
And why 2 and not any other random number?
And it works for me is not enough.  There are many more use case than your 
limited testing with only 2 pixel and only a limited format variation.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8c62eaf2-2b34-4af3-8242-14fdcee5bf5en%40googlegroups.com.

Re: [hugin-ptx] Re: Aligning multiple image stacks in the same pano - any way to do this automatically?

[T. Modes]

Hi Joachim,

j-sc...@gmx.de schrieb am Dienstag, 26. September 2023 um 19:22:50 UTC+2:

Hello Thomas,
did I understand correctly, the images can be members of a stack and their 
positions can be unlinked at the same time?

Yes, in this case the stack is an indicator for e.g. cpfind which images it 
should match with other images in the stack.
 


"Display the image position" - is this?:
Okay, done so.

Is this the place where I should do the unlinking? 
"... on the image position" - is there a particular spot where I have to 
click to get the according context menu entry? Or is it only that I don't 
recognize it?
In the screenshot I have selected the images that have already been 
assigned to stacks 0. 

I forgot to mentioned that you need to group by stack for this. Then open 
the context menu on yaw/pitch/roll/… (not on the filename or image number) 
because it affects the image position parameters but not the filename. 


On the Optimiser tab the context menu is the same. I tried checking the 
boxes also of the first stack, selecting the images and then optimize.. 


You can also unlink the images here. Open the context menu on the checkbox 
or the number beside and select unlink.
The checkboxes in the tree should present which position/parameters is 
optimized - only one parameter for all images of the stack or each image 
individually.

 Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b6682cc5-b893-474b-8964-8fcf6a428503n%40googlegroups.com.

Re: [hugin-ptx] Re: Aligning multiple image stacks in the same pano - any way to do this automatically?

[T. Modes]

j-sc...@gmx.de schrieb am Dienstag, 26. September 2023 um 00:10:20 UTC+2:

Okay, 
>  you need to assign the stacks and unlink the positions when shooting 
> handheld before running cpfind. Cpfind needs this information for the 
> decision which images belong to which stack. 
This sounds plausible. 
So I guess I have to set Optimise - Geometric (on the Photos tab) to 
"Custom Parameters" to get the Optimiser tab. But once the stacks are 
defined, I can't do anything to the positions any more. There are 
checkboxes only for the stack as a whole. Or what am I missing? 

As I already written, you need to unlink the position in the stack. This 
can be done on the photos tab or on the optimize tab.
Display the image position and open the context menu on the image position, 
there you can it unlink (or link) the image position.

And "cpfind --multirow" is not in the dropdown menu. I guess the whole 
approach has to be done on the command line, right? 

No, it can also be done in the GUI. The default cpfind settings includes 
already the multirow setting.
You can also create your own settings for the control point detectors in 
the GUI.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6bc7a110-9fe8-4307-b6d1-2233396dab10n%40googlegroups.com.

Re: [hugin-ptx] Re: Aligning multiple image stacks in the same pano - any way to do this automatically?

[T. Modes]

Hi Joachim,

j-sc...@gmx.de schrieb am Sonntag, 24. September 2023 um 21:23:40 UTC+2:

  But in the current version (2022 on Windows) doesn't have "Cpfind 
(multirow/stacked)" as a setting any more. 

This feature has been integrated into cpfind multirow strategy. So just use 
cpfind 
--multirow .
But you need to assign the stacks and unlink the positions when shooting 
handheld before running cpfind. Cpfind needs this information for the 
decision which images belong to which stack.

So the task is:
6 images, handheld!, consisting of 2 stacks of 3 images each, as a 
(vertical, in this case) panorama.
When adding the images, hugin doesn't yet recognise by itself that there 
might be stacks involved.
Ist there a way to
1) make hugin align the images inside the stacks first and
2) then align the 2 stacks as a panorama?

Just optimise all 6 images at once. This should work.

If you want to do it manually, it is just vice versa.
1.) Optimize only the single pano layer first. (disable all other images in 
the stacks)
2.) Then fix the position of the images of this pano layer and optimise 
only the other images of the stacks.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/541a1ab8-3ba0-4bc8-beb7-9a55db57185bn%40googlegroups.com.

Re: [hugin-ptx] Hugin 2023.0 beta 1 released

[T. Modes]

Hi Bruno and Andreas,

bruno...@gmail.com schrieb am Sonntag, 24. September 2023 um 19:37:10 UTC+2:

I see this on fedora, this look a bit messed-up:

$ pkg-config flann --libs
-L/usr/lib64\;-llz4 -lflann -lflann_cpp 

Is there something we can workaround in CMakeModules/FindFLANN.cmake? 
Replace the semicolon?
Or have we to wait for a fix upstreams?

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/09823901-335c-4b6e-9b2a-636e3f3735d0n%40googlegroups.com.

Re: [hugin-ptx] Hugin 2023.0 beta 1 released

[T. Modes]

Hi Bruno, 

it works here. lz4 is added to FLANN_LIBRARIES automatically by pgkconfig:

from the Cache:
FLANN_LIBRARIES:INTERNAL=lz4;flann;flann_cpp;lz4

Thomas

bruno...@gmail.com schrieb am Sonntag, 24. September 2023 um 13:23:16 UTC+2:

I'm not quite sure where to fix this, but flann-1.9.2 now has a dependency 
on lz4. So I needed to add "-llz4" to get hugin to build with this version 
of flann.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4570b037-50df-42c7-9104-d855d6d9bd5en%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

Thanks for building, but …

dud...@gmail.com schrieb am Samstag, 23. September 2023 um 10:08:41 UTC+2:

Releasing a mac arm64 build according to this source code relaease from 
T.Modes:


Please use the dedicated thread for the beta 1 release for such 
announcement and not your "private" mac thread.
So all reports concerning the beta 1 are in one thread and not scattered 
about several ones.
This was explicitly written in the announcement.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7a6e1cc7-2b96-4f8b-8dc7-472685a3fe98n%40googlegroups.com.

[hugin-ptx] Hugin 2023.0 beta 1 released

[T. Modes]

 Hi all,

today we are releasing beta 1 of Hugin 2023.0.0 

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

Verify its checksums:
md5:
b09a0fab8a78c684b0b90249926e3e82 hugin-2023.0beta1.tar.bz2
sha1:
f36124c380fea75ecc052a0ca2f69e734865deaf hugin-2023.0beta1.tar.bz2

This is a source code release. 
Users communities produce executables for their respective platforms. 
Please announce them here.
When building on Linux check that the configuration of all dependencies 
matches. This refers mainly to wxWidgets and GLEW. See the release notes 
for more details https://hugin.sourceforge.io/releases/2023.0.0/en.shtml

(The beta 1 correspond to changeset de090f232982in our repository, which is 
also tagged as 2023.0beta1).

Changes since 2022.0
* PTBatcherGUI can now also queue user defined assistant and user defined 
output sequences.
* PTBatcherGUI: Added option to generate panorama sequences from an 
existing pto template.
* Assistant: Added option to select different output options like 
projection, FOV or canvas size depending on different variables (e.g. image 
count, field of view, lens type).
* Allow building with epoxy instead of GLEW for OpenGL pointer management.
* Several improvements to crop tool (outside crop, aspect ratio, ...).
* Several bug fixes (e.g. for verdandi/internal blender)

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

Please test and report bug/issues to mailing list or bug tracker 
https://bugs.launchpad.net/hugin (so issues can be fixed before the final 
release).

Windows binaries (64 bit) can be found at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/Hugin-2023.0beta1-win64.msi/download

MD5 checksum
f1e9aa196c412f7734209dfcda0817d5 *Hugin-2023.0beta1-win64.msi

Request for translators
Please update the translation file of your language. Some new strings have 
been added.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5a6e388e-b7bb-4575-b190-5f0947479e9bn%40googlegroups.com.

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc2

[T. Modes]

I will look at the changes.
But that you put all changes into one big patch makes is difficult to test 
or comment on single issues.
But some comments:
* you are fixing the warning for a specific version of a specific compiler. 
Other compiles or even other versions the same compiler will throw warnings 
on different issues. So fixing all warnings for all compilers and all it 
version (especially for a platform independent way) is a lot of work with 
only little benefits.
* Your changes break the ABI again, this is something which we would 
prevent in this release.
* You did also white spaces changes and introduced a mixed indentation 
style.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7b149cca-a00a-49c4-aa1f-b139d4be7630n%40googlegroups.com.

[hugin-ptx] Re: SkyFill tutorials completed

[T. Modes]

PanoSeek schrieb am Dienstag, 5. September 2023 um 20:48:35 UTC+2:


Here is what I have done so far - 

   1. setup directories 
   2. git clone the repo to the local directory - git clone 
   https://github.com/weltyj/SkyFill
   3. Installed cmake 3.27.4
   4. Installed tiff-3.8.2-1.exe to the same directory as the clone of the 
   repo.

I don't know what this file is. But the libtiff library has to be compiled 
with the same compiler as the one you are using for skyfill.
Probably they don't match. (From the name libtiff could be from gcc and you 
are compiling skyfill with Visual Studio, just guessing.)
 
   
   1. added a few lines to the cmakelists.txt file as I could not get the 
   find package to work.

 

5. added a few lines to the makelists.txt file as I could not get the find 
package to work. 

6. ran cmake from the \build directory - cmake C:\Users\Rod\SkyFill\
7. Opened the solution in visual studio community 2022
8. tweaked the projects include locations because it was still not finding 
the TIFF files it needed.

CMake does not work this way. You should not modify the CMakeLists.txt 
file. Instead enter the correct path in the CMake-GUI.
 

9. Attempted Build and got 9 errors like this- Severity Code Description 
Project File Line Suppression State
Error LNK2019 unresolved external symbol __imp__TIFFmalloc referenced in 
function read_tif_image skyfill C:\Users\Rod\SkyFill\Build\skyfill_tif.obj 1 

At this time, I have no idea why I cannot get it to compile. 

So above.

Also Hugin has the fill edges option to fill missing edges. Not sure if 
this would also work in your usecase.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0fd605b3-c90e-402e-8ae0-5b4cdca32125n%40googlegroups.com.

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

[T. Modes]

bruno...@gmail.com schrieb am Sonntag, 30. Juli 2023 um 19:49:36 UTC+2:

The immediate need is to put out a bugfix release. If we bump the soname 
then it won't be a drop-in replacement, and Hugin will need to be rebuilt 
for all platforms etc..

These bugs are not relevant to Hugin users, but they are still security 
issues, so Linux distros will be looking to update their pano13 packages as 
soon as we do a release. It would be nice to have this be a minimal change 
without bumping the soname.

I'm not confident I can do this change that keeps the ABI intact, so 
looking for help here.


I found a possibility to keep the ABI constant. All public functions keep 
their signature and exist furthermore. But the critical functions have been 
replace with a stub which prints only a message to stdout and does nothing 
else.  So the security issue should be fixed.
The complete removal of these function will be postponed to the next 
version.

To keep the changes more cleanly I created a new branch in the mercurial 
repo. So the release should use this branch. All further work goes again to 
the default branch.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7d46af37-6153-4bd3-8512-8d1f0504bbcbn%40googlegroups.com.

[hugin-ptx] Re: Consolidate Mac build

[T. Modes]

dud...@gmail.com schrieb am Dienstag, 25. Juli 2023 um 23:09:10 UTC+2:

We should add an additional mac_intel folder as opposed to mac_arm64. I 
tested on both architectures and intel based scripts works pretty much as 
is right now  but arm64 is another ballpark.


This is the opposite I meant with consolidate. There are already a lot of 
scripts for mac alone. Duplicating them for different case is a no go (with 
only a minor differences). This becomes a maintenance nightmare. 

All necessary things should be in one set of scripts. The architecture 
and/or compiler can then be chosen by a command line switch or an 
environment variable and then evaluated in the scripts.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4ed654a9-050e-4360-adc2-ffd3dae69011n%40googlegroups.com.

[hugin-ptx] Consolidate Mac build

[T. Modes]

Hello Mac builder,

currently there are at least 3 different build scripts for Hugin I'm aware. 
https://bugs.launchpad.net/hugin/+bug/2028086 by p.w.wong
https://sourceforge.net/p/hugin/hugin/merge-requests/4/ by Erkan Ozgur 
Yilmaz 
https://bitbucket.org/Dannephoto/hugin/src/master/ by Dudeck

Two of them wants now be merged with our default repository.

But each of them is different:
e.g. all are using different paths to the compiler:
CC="/opt/local/bin/clang" 
CXX="/opt/local/bin/clang++"

CC="/opt/homebrew/Cellar/llvm/16.0.1/bin/clang" 
CXX="/opt/homebrew/Cellar/llvm/16.0.1/bin/clang++" 

CC="/opt/homebrew/Cellar/llvm/16.0.3/bin/clang"
CXX="/opt/homebrew/Cellar/llvm/16.0.3/bin/clang++" 

Just to name one of them. 

We can't have different flavours of the build scripts in the main 
repository.
So please synchronize your efforts and reach an agreement on one! way for 
the main repository.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8e3ab7ce-cb14-4d43-90c0-865817ddb935n%40googlegroups.com.

[hugin-ptx] Re: Batch process Move/drag

[T. Modes]

g...@arctan.se schrieb am Mittwoch, 5. Juli 2023 um 17:25:09 UTC+2:

I have a set of panoramas that are captured with the camera laying down, 
the top of the camera does not point upwards towards the sky. I managed to 
correct this on a single panorama with the tool Move/Drag, but is it 
possible to do in batch?


try pano_modify --rotate=yaw,pitch,roll --output=project.pto input.pto
 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4682571c-d8ce-413f-9479-4369c02496ecn%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Donnerstag, 15. Juni 2023 um 20:34:54 UTC+2:

Might have a fix for the button issue when in darkmode. Feel free to refine 
it.

In splitbutton.cpp:


*void SplitButton::OnPaint(wxPaintEvent& WXUNUSED(event))*


Please don't copy the full code into the mail. First the software/mail 
client can reformat the code lines - this can introduce a lot of 
unnecessary trouble. 
Second it is not so obviously what you changed exactly. 
Please attached instead a unified diff (from hg diff). This makes the 
handling of such changes more easily.

The changes affect only the caption (text) of the button, but not the 
drawing of the buttons itself. These are still wrongly drawn.

Second, I don't like the fixed coded colours. What if the users theme is 
using other colours? Then it looks wrong again.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3ae298e7-1f3a-429a-b395-3d6e2ea1abb3n%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

Attached is a patch which should try to set the background color to the 
correct color.
Please test if this fixes the issue in dark mode and if it works also in 
non-dark mode.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3d19b13a-6417-4055-9b08-146b08aafb17n%40googlegroups.com.
diff -r 79cd11a7a66f src/hugin1/hugin/SplitButton.cpp
--- a/src/hugin1/hugin/SplitButton.cpp	Wed May 24 19:13:20 2023 +0200
+++ b/src/hugin1/hugin/SplitButton.cpp	Thu Jun 01 17:24:09 2023 +0200
@@ -43,6 +43,11 @@
 {
 UpdateMinSize();
 }
+#ifdef __WXMAC__
+// explicitly set background color for Mac 
+// otherwise DrawPushButton does not draw button correctly when dark mode is enabled
+SetBackgroundColour(wxSystemSettings::GetColour(wxSYS_COLOUR_BTNFACE));
+#endif
 
 Bind(wxEVT_PAINT, ::OnPaint, this);
 Bind(wxEVT_LEFT_UP, ::OnLeftButtonUp, this);

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

Donald Johnston schrieb am Mittwoch, 31. Mai 2023 um 21:37:36 UTC+2:

Yes, same here. Under “Appearance” in the Mac System settings I changed 
between Light and Dark and the text is readable.

Now it’s just the big ugly 1, 2, and 3 … (smilie face) … seriously that’s 
not an issue.

What’s missing also is the “lens type” and “Focal length” etc. between the 
1 and 2 buttons. The drop down is connected to the “Load Images” button so 
it is not obvious.


No, it is not missing. The tab was simplified in version 2022.0 and 
unneeded functions for the assistant tab were removed. This is mentioned in 
the release notes.
There were some discussion about it some time ago: 
https://groups.google.com/g/hugin-ptx/c/Vzd1vq2eY9Y

Concerning the dark mode: here we are using directly the functions from 
wxWidgets to draw the button. Maybe this was fixed in a later version. 
There were some issues related to dark mode mentioned in the 
changelog/release notes.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2f7536db-5fe3-43c5-a291-5212acaeabc6n%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

Donald Johnston schrieb am Mittwoch, 31. Mai 2023 um 18:30:40 UTC+2:

Thanks dude53! I certainly appreciated the work you’ve put into getting 
this going for Mac silicon!
And Thomas any help you can provide is also appreciated. Here are the two 
images that I’d posted earlier.


Okay, we make progress.
Does this happen only in dark mode? When disabling dark mode does looks it 
better?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c6f0432a-6ced-47a1-8038-e9409aa477b8n%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

Hi Donald,
Donald Johnston schrieb am Mittwoch, 31. Mai 2023 um 18:30:40 UTC+2:

And Thomas any help you can provide is also appreciated. Here are the two 
images that I’d posted earlier.


thanks for the feedback. But these images don't appear in the web 
interface. Other attachment appear also in the mailing list. Not sure what 
the problem here is with these images.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/962ebb4c-f0c7-451f-b8dd-e8a656d7478dn%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Mittwoch, 31. Mai 2023 um 18:05:25 UTC+2:

Well I've seen the image. Maybe taken down. 

There is no attached image in the web interface. 

Maybe the author could repost it if that's the case. 

Interesting. You can reproduce the glitch but are not able to provide a 
screenshot on your own?
There are also some questions which the builder should able to answer (e.g. 
wxWidgets version). These are still unanswered.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/63cf19c1-750b-40b8-a0ff-1fe0eb3b3175n%40googlegroups.com.

Re: [hugin-ptx] Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Mittwoch, 31. Mai 2023 um 05:27:02 UTC+2:

I had a look a while ago but couldn´t find any issue here. Makes me wonder 
if the graphical change is suppose to be like this. Maybe T. Modes or some 
one else could verify this? 

It works fine on Windows and Linux, I don't see problems here.

There was an attached image mentioned, which should show the issue. But 
there is no image attached. So I don't know what you mean. It seems to be a 
Mac issue which only "insiders" knows and nobody else.

So a screenshot with the issue and some more information would be needed, 
e.g. wxWidgets version, is this a HiDPI display?, (if so scaling factor)
I can't read thoughts…

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/bcc65cdb-51dc-44a3-b0d7-1f8073f0d14bn%40googlegroups.com.

[hugin-ptx] Re: Verdandi segfault with 2022.0.0

[T. Modes]

kevin@gmail.com schrieb am Mittwoch, 31. Mai 2023 um 02:13:56 UTC+2:

And thanks also for the advice on the image ordering. I hadn't noticed that 
pto_gen 
is no longer sorting 
 the input images, 
and so I've updated my script to sort them itself. 

 there should be no need to sort them by itself. Simply add the switch 
--sort to the pto_gen command and let pto_gen sort the images.
There are use cases where a special order is important. So I made the 
sorting optional. (Because otherwise it is not possible to enforce an 
order.)
Sorry for the noise.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4949395a-3606-4e45-a076-da756334b867n%40googlegroups.com.

[hugin-ptx] Re: Verdandi segfault with 2022.0.0

[T. Modes]

kevin@gmail.com schrieb am Dienstag, 23. Mai 2023 um 22:08:39 UTC+2:

After upgrading Hugin from 2021.0.0 to 2022.0.0, I am seeing verdandi 
segfault when stitching 360x180° drone panoramas. One of the affected image 
sets is linked below. It stitches correctly when downgrading to 2021.0.0, 
and reproducibly fails with 2022.0.0 and latest from hg. 


Thanks for the detailed bug report and reproducer. It should be now fixed 
in repository.
 

unzip photos.zip
nona -v -z LZW -r ldr -m TIFF_m -o part project.pto
verdandi --wrap --seam=blend --compression=LZW -o equirectangular.tif -- 
part.tif part0001.tif part0002.tif part0003.tif part0004.tif 
part0005.tif part0006.tif part0007.tif part0008.tif part0009.tif 
part0010.tif part0011.tif part0012.tif part0013.tif part0014.tif 
part0015.tif part0016.tif part0017.tif part0018.tif part0019.tif 
part0020.tif part0021.tif part0022.tif part0023.tif part0024.tif 
part0025.tif part0026.tif part0027.tif part0028.tif part0029.tif 
part0030.tif part0031.tif part0032.tif part0033.tif part0034.tif
```

The main issue here is that you are supplying the images in a random order 
(already in the pto file).
But verdandi's blend algorithm works best when working on neighbouring 
images starting from an anchor. But when using a random order greater 
gradients can occurs. 
Imaging 3 images in a row: from left to right image 1/image 2/image 3. The 
best result is achieved when first blend image 1 and image 2 and then 
blending the result with image 3. 
Now imaging a random order e.g. first image 1 and image 3, both images will 
be only copied into the results because they don't overlap (and don't 
touch). When now blending image 2 in between it has to change to match to 
image 1 *and* image 3. This creates greater restriction on the blending and 
therefore can create a bigger gradient.
When stitching from the GUI or hugin_executor they take care of this and 
supply the images in a sensible order to verdandi. 
By using the command line utilities in combination with the random order in 
the pto file you are bypassing this restriction. 
It would also help when you would generate the pto file with ordered images 
instead of the random order. Then you would also have a sensible order for 
blending.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/104a8e48-3966-4406-afdb-7d8e461353cbn%40googlegroups.com.

[hugin-ptx] Re: image unexpectedly changed dimensions

[T. Modes]

j-sc...@gmx.de schrieb am Mittwoch, 17. Mai 2023 um 22:55:01 UTC+2:

Hello, 
I have just experienced an error I had never before: 


can you provide the pto file for debugging?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/edf7de51-5d46-46f0-89eb-7e5b49d4883an%40googlegroups.com.

[hugin-ptx] Re: .bat file to run hugin

[T. Modes]

patj...@gmail.com schrieb am Dienstag, 16. Mai 2023 um 21:08:05 UTC+2:

I've created a .bat file to run hugin. This is a windows command-tool file. 
To run this, hugin needs to be on the environmental path, and imagemagick 
should be as well

pano_modify --canvas=AUTO --crop=AUTO -o --center --straighten %1.pto 


This command is not doing what you think it does. The -o switch requires a 
filename - so the result of this command is written to a file --center and 
the --center command is not done.
Look at the output of the commands. You should be see something like:
Written output to --center

(Do not simply copy and paste. Try to understand to commands and look also 
at the output, it can contain a lot of additional information. Otherwise 
there are more high level functions available - see below.)

rem convert z%1.tif -resize 7000x z%1r.jpg

Not sure what you doing here. Instead of creating a pano and then resize it 
adjust the pano_modify command to get the final size in one go.
 

In my use, I set up a .bat file to call the bat file:

convert file0436.jpg afile01.jpg
convert file0439.jpg afile02.jpg
 . convert more files 

Why this? Converting a jpg file will require a new re-compression and this 
will degrade the image quality.
So rename the file only or copy it.
Or more easily Hugin can also handle non consecutive numbered image. So 
there is no need to rename the files.

But a final remark: I don't understand what you try to achieve. 
PTBatcherGUI has already a lot of functions for automatic running assistant 
and stitching.
Activate option stitch after assistant in PTBatcherGUI and then
pto_gen -o %1.pto %2
ptbatchergui --assistant %1.pto

Even if you don't want to use PTBatcherGUI the whole script can be 
simplified to a three liner
pto_gen  -o %1.pto %2
hugin_executor --assistant %1.pto
hugin_executor --stitching --prefix=z%1 %1.pto


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/75bbc455-35ce-4e22-a768-bd8606661f3bn%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Freitag, 5. Mai 2023 um 17:40:17 UTC+2:

Regarding the numbers that fixed my issue. Could you suggest a way to 
verify the validity of the fix? I tested it on 5-6 different workstations 
with different people having the same issue and the fix fully worked on all 
stations.


I thought I explained it already in my earlier replies.
Just 2 tests cases after applying your changes:
* Input gray scale images: works in official version, crashes with your 
numbers
* Large output image (e.g. 34000x27000): works in official version, with 
your numbers it stops with an error message

I think there could be more cases…

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a98489cd-496d-4b0d-805e-28e49852343en%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Freitag, 5. Mai 2023 um 11:38:20 UTC+2:

Added sources and diffed the arm64 hugin source against latest official 
sources here. Maybe helps to follow changes from Erkan and me:
https://bitbucket.org/Dannephoto/hugin/src/master/


sorry, but it does not help. This is hacking that it works for *you* only 
and not for any other.

Instead of cloning the existing repository you copied all files to a new 
git repo. Now the whole history is lost. Also it is unknown on which 
changeset it is based.

Next, in one changeset you copied the files from the official hugin repo. 
In the next changeset you add your changes and at the same time you revert 
a lot of changes to an earlier changeset of the Hugin repo- which is also 
unknown. 
So the changeset is more complicated than necessary. It contains your 
changes and a lot of unrelated and unnecessary changes at the same time. 
This makes it very confusing to see your changes only.

Hugins build system is connected with the mercurial repo. By switching to 
git you break this and need to add a file which is (intentional) not under 
revision control in mercurial. (There are special ways to handle the 
releases, but these should not be used in development in between.)

Next your changes in the source code break the compilation on all other 
platforms -> "works for me" is not enough. The changes must not break 
compilation (and running) on other systems.

Also randomly changing numbers and sign in the source code without 
understanding what you do only that it works in *your* single use case is 
not acceptable. I mentioned this already to you but you have ignored this.

Also changing lines in the script and then commenting out the same line is 
a bad style and makes the diff more confuse than needed.

Beside all these mentioned issue it would be recommend to split the changes 
into small chunks: e.g. one changeset with only changes to the build 
script, a second one with the needed code changes.

Combined it is very difficult to review your changes because of all these 
mentioned points.
Currently it can't applied to official repo because it breaks existing code.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ebad2eb4-0ea1-41af-ad9b-ecdf9f7f1c73n%40googlegroups.com.

Re: [hugin-ptx] Re: batch processing same numbered images

[T. Modes]

mpgve...@gmail.com schrieb am Montag, 24. April 2023 um 22:45:50 UTC+2:

however, i can't seem to get the syntax right when i try to change 
sequence image name to an iterating sequence. 

my images are numbered equally eg. 
left/IMG_0001.jpg, right/IMG_0001.jpg, running up to IMG_2880.jpg 

Set the %p variables in the top part: offset with 0, step 1, end 2880, 
number of digits 4
For this use case the counter %i and %x can be ignored.

As name template use
left/IMG_%p.jpg
right/IMG_%p.jpg

see attached screenshot.
(By testing I'm have seen that the original filename in the template is not 
shown correctly. But it shown currently work and I will fix it.)

This is similar to example d) in the documentation: 
https://wiki.panotools.org/Hugin_Batch_Processor#Generate_sequence_from_template


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6982bc8e-0c31-46d9-a7e7-af2f58d4eec5n%40googlegroups.com.

[hugin-ptx] Re: Problem with bright splodge in panorama from enblend.

[T. Modes]

irthoma...@gmail.com schrieb am Donnerstag, 20. April 2023 um 21:35:23 
UTC+2:


Thanks. Raws are here 
https://drive.google.com/drive/folders/1zzjVOqO3pnwZu92LdJuUvTYoCOggfRk6?usp=sharing
I am using 10bit rec2020 raws. 

Could you provide the already converted TIFF(?) files? This would rule out 
differences in the raw converting process.
Also please provide your pto file. This would make it easier.
 

But I noticed this pano was shot with auto-exposure, and I was using 
Photometric > High dynamic range, fixed exposure. I wonder if that causes 
problems?

It can be. Auto-exposure in camera with fixed exposure in the photometric 
optimizer can make problem. It depend how exactly the exposure metadata and 
camera processing for different exposure time is.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b433326a-1dd3-4bf4-8376-4f67f34c1e1bn%40googlegroups.com.

[hugin-ptx] Re: Problem with bright splodge in panorama from enblend.

[T. Modes]

irthoma...@gmail.com schrieb am Donnerstag, 20. April 2023 um 14:27:33 
UTC+2:

My process is to export raws from Darktable with everything disabled, but, 
lens correction.


5: Photometric: High Dynamic Range, Fixed Exposure.

 
This will only optimize vignetting correction. In case of images with a low 
dynamic range (high key/low key images) this may not result in correct 
results and may need manual fine-tune. This blurred spot could be the 
result of an improper vignetting correction.
But when you already corrected this in the raw converter this step may not 
be necessary.

> Using built-in, instead of enblend, gets rid of the blotchy brightness. 
But, this produces it's own problems with seams and hard edges 
The internal blender has also a second blend mode in case there are 
remaining seams. This one has to be selected in the blender options.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a977a03e-fa98-4e6e-8f84-bcb9844978c3n%40googlegroups.com.

[hugin-ptx] Re: Can't add any RAW converter in preferences (linux)

[T. Modes]

Piotr Szczuka schrieb am Montag, 17. April 2023 um 07:26:00 UTC+2:

 installing hugin as flathub i can't import RAW images to it. When I am 
tryng add path to Darktable or to RAWtherapee I cant. Executable files are 
indeed in to /usr/bin directory but some how hugin do not see them in 
file-> preferences ->general -> RAW converter ->choose. 


A short search reveals that in a flatpak the directory /usr is blacklisted: 
https://docs.flatpak.org/en/latest/sandbox-permissions.html
So you can't access the programs in /usr/bin from inside a flatpak 
directly. 
One way would be to install the raw converters in your home directory or 
any other directories which flatpak can access.
Or you can try to fiddle with flatpak-spawn
https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-spawn
https://docs.fedoraproject.org/en-US/fedora-silverblue/tips-and-tricks/ 
to access the programs in /usr/bin from inside a flatpak via this wrapper.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e88ac775-6726-4752-843e-ada127236f0fn%40googlegroups.com.

[hugin-ptx] Re: [Feature request] Create CP's in two images in the UI

[T. Modes]

Hi Casper,

emailt...@gmail.com schrieb am Sonntag, 16. April 2023 um 12:16:42 UTC+2:

I guess I can optimize between two images also?

With a custom optimizer setting you can optimize only these images.
Another way would be to restrict the optimizer to the active images (in 
edit menu) and activate only the 2 images which you are interested. 
(disable all other images)
 

But I can't find the "create cp" button in the control points tab. I see 
the "fine tune" and the "Celeste" button and I can manually add control 
points, but not an "auto" button.

The button labelled with Celeste has a small arrow - indicating a sub-menu. 
Right click on this button and then you can select create cp.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3fd426e5-1152-40e5-a84c-322bb49b25f3n%40googlegroups.com.

[hugin-ptx] Re: [Feature request] Create CP's in two images in the UI

[T. Modes]

Hi Casper,
emailt...@gmail.com schrieb am Sonntag, 16. April 2023 um 11:05:45 UTC+2:

What I look for is a button I can press in the UI which when pressed tries 
to create control points between the two displayed images.


In the control points tab there is already a button "create cp", which will 
run cpfind only on these two images.
Furthermore you can select two or more images in the photo tab and then 
start cpfind from the photo tab. It will then only work on the selected 
images.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/476b07c8-4168-4c6c-9d7a-779e364a20a6n%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Sonntag, 9. April 2023 um 11:16:36 UTC+2:

Hi. Are these numbers applied also to at/nvidia cards or do they apply only 
for other cards not defined? If applied globally tests show no benefit 
having larger dest chunks like 16 + 16 + 8.
More testes shows too high negative numbers will hang processing, while too 
high, as we know corrupts framebuffering.
Question remains. Could code be made more robust removing or changing 
behaviour in this particular place?

You can't simply change randomly numbers and hope that this fixes it. The 
meaning of the number is written directly above the line in the comment.
 

By the way. What is the real cause of the issue here? 

I assume that it reads only the first dest chunk correctly back. The second 
and further one are not correctly read back. But I don't know why it works 
on most systems except the M1 one. Apple must have something special in its 
implementation.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/90105c74-017f-43a6-accf-8bb504c2f86fn%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

Hi Max
dud...@gmail.com schrieb am Sonntag, 9. April 2023 um 07:58:17 UTC+2:

Oki, here´s some conclusions. First. The "fix" in question. In 
*ImageTransformsGPU.cpp 
*I change line 465 to:
*const int bytesPerDestPixel = 2 - 2 - 2*
It was before:
const int bytesPerDestPixel = 16 + 16 + 8

This allows for functioning corruptfree output even with files with wdth 
above 6000(pixels?). Big files in other words. THis didn´t work before. I 
cannot see any speed change by doing this and it can be used also with 
other intel machines with nvidia cards and so on. WIth that said I don´t 
see it as a stable fix for all macs. It works on M1 at least.


First bytesPerDestPixel can now become zero or negative (when using other 
image formats). This breaks the following calculations or results even in a 
crash when dividing by zero.

>From the first runs it was probably that the corruption occurs when using 
more than one dest chunk.
So when you decrease bytesPerDestPixel you increase the size of the dest 
chunk and so nona/align_image_stack is using only one dest chunk and so the 
corruption does not happen. (run none with --debug switch)
So you workaround the issue in your single usecase but don't the fix the 
real cause.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a29f7f76-16bb-4b38-a160-fa2065601ddcn%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Freitag, 31. März 2023 um 14:22:58 UTC+2:

No problem, let me know when you've done it :-)


Okay, I fixed some more issues and did some optimization. It should now 
work better for bigger sequences.
You can download a new version at 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/Hugin_2023.0beta0b.zip/download


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/962ec4be-ce16-4838-98c0-8ff8d51df124n%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

Hi Max,

maximums...@gmail.com schrieb am Freitag, 31. März 2023 um 23:28:51 UTC+2:

I made a patch file with all the 
changes I made to get them to download and build correctly, which I've 
attached to this email. You might need to make more changes to e.g. 
outdated URLs. 


Thanks for the patch. I committed these changes to the repository.
Next time please create the patch file as unified diff against the root 
directory of the repository instead of the mac subdirectory.
I had do to some modification before the patch applied cleanly.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0cdd87c9-24cf-4549-b042-3a700e1f5f13n%40googlegroups.com.

Re: [hugin-ptx] Re: GLEW segfault

[T. Modes]

irthoma...@gmail.com schrieb am Donnerstag, 30. März 2023 um 12:13:08 UTC+2:

Ah, to start with, I was following the hugin build instructions from the 
website.
The website needs updating to tell people to follow the build instructions 
in the download. Otherwise, the path you naturally follow is:  Search for 
hugin > find https://hugin.sourceforge.io/download/ 
> Compile from Source 
> http://wiki.panotools.org/Hugin_Compiling_ubuntu


thanks for the hint. I made some changes to make it more obviously that the 
first source is the INSTALL_cmake file and the links to the panotools wiki 
instructions are community contributed and may not be up-to-date.
We can't update the instructions for all possible distributions. So 
updates/corrections/fixes/clarifications by the users/community are always 
welcomes. This should be straightforward and can be done directly in the 
panotools wiki by the users.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/70702ae3-fca1-4917-a1e7-fa8d8cfa7551n%40googlegroups.com.

Re: [hugin-ptx] Re: GLEW segfault

[T. Modes]

irthoma...@gmail.com schrieb am Mittwoch, 29. März 2023 um 21:33:57 UTC+2:

I read it but didn't know how to activate egl support in glew. I had glew 
version 2.1, which doesn't mention it. Only glew 2.2.0 has it. 

glew 2.1 was released in July 2017, glew 2.2 in January 2021.
So nothing really new.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ed9e1246-c5d7-43eb-b00f-37e89e34b56en%40googlegroups.com.

[hugin-ptx] Re: GLEW segfault

[T. Modes]

This is mentioned in INSTALL_cmake file (which seems nobody is reading...):

On Linux wxWidgets 3.1.5 and later is by default compiled with EGL support 
for the wxGLCanvas class. 
In this case you need to activate EGL support explicitly also in GLEW, 
otherwise there are crashes when
intializing the wxGLCanvas.

For the default branch there is also the following alternative added:
Alternatively you can also use the epoxy library instead of GLEW, which does
the detection at run time. To build with epoxy add -DBUILD_WITH_EPOXY=on to 
the CMake command line.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f6762a36-1942-4490-b5f3-7ea45e22f020n%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Mittwoch, 29. März 2023 um 18:56:38 UTC+2:

Wonderful !
Should I download anew zip archive from sourceforge ?


Sorry, I have not yet uploaded a new compiled version. This adds more work 
for me.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cb34f433-c6ec-4010-bbd8-d69796b533a7n%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Mittwoch, 29. März 2023 um 08:43:13 UTC+2:

Thank you so much !
I could generate a sequence from template of 100 panoramas :-)
Could you increase the number of panorama to one thousand or more ?


I was not aware that the spin controls have a default maximum value of 100. 
This is fixed now in the repository and the maximum if increased.
By doing so I found also a bug in the filename generating code (only when 
using the panoramaXXX.pto type), which is now also fixed.

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f8fed186-b5f9-4415-9b1c-6380260f2d30n%40googlegroups.com.

Re: [hugin-ptx] Re: Insta360 One R dual lens image stitching

[T. Modes]

robert...@gmail.com schrieb am Donnerstag, 23. März 2023 um 18:14:39 UTC+1:

Hi! 
I tried the assistant, but did not get useful results. 

it is the same problem as in the linked thread. The dual lens assistant was 
written for horizontal divided images. But your images are vertical divided.

Attached you will find a pto file for a first try. It is not yet perfect, 
but it may be a starting point. You would need a better scene where more 
details are visible in the overlap area. This image has not enough details 
in the overlap. There are only some areas which can be used, so it can not 
be fully optimized.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e0475403-faba-467a-97d9-73088ad7277an%40googlegroups.com.


test.pto
Description: Binary data

[hugin-ptx] Re: Insta360 One R dual lens image stitching

[T. Modes]

robert...@gmail.com schrieb am Donnerstag, 23. März 2023 um 13:02:24 UTC+1:

I don't have much experience with dual lens cameras and need some 
guidance regarding the Hugin workflow. 
What are the lens parameters? It's over 180 FOV, but I can find the 
exact numbers. 

I'm also a bit stumped regarding crop/mask settings. 


A profile would be perfect! 


An example image would be nice (preferred is a link, this is a mailing 
list, don't attach big images to a mail) . 
Otherwise it's only guessing.

Hugin ships with the dual lens assistant. But not sure if the assistant 
matches to your camera.
There is also some discussion on the list, e.g. 
https://groups.google.com/g/hugin-ptx/c/vYeBUu7_7Ic/m/hDy5vzKWBgAJ

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7b2076da-37a3-4553-a5f9-8f39959cd7afn%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Donnerstag, 23. März 2023 um 15:54:44 UTC+1:

How can I do ? Can't I upload a version of Hugin already compile ? Or 
perahps I can find a step by step to do it ?


There is an outdated instruction on the panotools wiki 
https://wiki.panotools.org/Hugin_SDK_(MSVC_2013)
It was not updated for a long time and some things changed since then.
But if you never compiled before it will be very difficult to do.

I uploaded a zip archive to sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2023.0/Hugin_2023.0beta0.zip/download
Extract to a new folder and run PTBatcherGUI from there. For a first test 
don't overwrite any existing installation. (I've done no installer on 
purpose.)
For information: In Hugin 2023.0 the file format of the batch queue will 
change. So the new version will have it's own queue. And the old version 
will not read the new format.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/644c8a13-0e70-4787-9064-4b5f3861ea93n%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Dienstag, 21. März 2023 um 01:28:26 UTC+1:

I didn't compiled the default branch with all current commits. I never done 
that and don't know how to do it.
I have downloaded all the files from the adresse: 
https://sourceforge.net/p/hugin/hugin/ci/006bd0734fd3dd48e23ff87513746f461ab72446/
I copied and replace the 2 xrc files into the xrc directory of hugin. But I 
don't find where are the .cpp, .txt and .h files in the directory of the 
programme.
 I am sorry, I'm not a computeur programmer.


Yes, it is not done by simply copying these files. I have now seen that you 
are on Windows. It is not so easy for a beginner to compile Hugin.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9f8f6694-4ce6-4bab-af1b-b7eb2b6b8f67n%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

ronan...@gmail.com schrieb am Montag, 20. März 2023 um 13:24:35 UTC+1:

Hi Thomas,
I have created a template pto file for the first pano/frame but
I can't find  "Generate sequence from template" in PTBatcherGUI.


It should in in menu File (Fichier), below item Search in directories 
(Rechercher dans le répertoire).
Have you compiled the default branch with all current commits?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f1152a41-3252-4e31-a50e-74da1faf8been%40googlegroups.com.

[hugin-ptx] Re: How to create a new keyboard shortcut

[T. Modes]

Hi Ronan,

does it works now with the instructions?
I haven't heart anything from you or anybody else trying the new function.
Is there something unclear? Or does it not work?

Thomas

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e2f89bdf-3639-47fe-8cf9-f87d6290c7e3n%40googlegroups.com.

Re: [hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Samstag, 18. März 2023 um 03:25:15 UTC+1:

Or port OPenGL to use Metal :). A quick search shows non support for 
OpenGL. I guess this could cause issues.


If you (or somebody) rewrite the whole code…

And Metal is Apple only. It will not work on Linux and Windows. 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/319a2ab2-b8bf-4599-bd3f-837385828630n%40googlegroups.com.

[hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Mittwoch, 15. März 2023 um 20:22:56 UTC+1:

Cool!
Issue with corrupted fikes reproduced with nona command:
nona -o test --gpu --debug test.pto
Terminal output:

I had a look at the output. But I don't see any obvious errors. The 
information looks very close on my side.
So I don't understand what happens here. But I'm no OpenGL expert. The code 
was written by  Andrew Mihal, and I maintain it only.
It seems Apple OpenGL implementation is slightly different in details from 
Windows/Linux one. But no idea what more to check.

The only workaround would be to remove the --gpu switch and do the 
remapping on the CPU.

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8ebc04e6-2b61-4280-a9bc-45a125eef481n%40googlegroups.com.

[hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Mittwoch, 15. März 2023 um 19:23:56 UTC+1:

Sorry about the confusion. I am using a workflow which integrates some 
older versions in lightroom. I am presenting the lightroom workflow as it 
triggers an error log on my mac. A log which is not triggered when running 
align_image_stack on command line directly.

My conclusion is that too big files will trigger the issue and in lightroom 
aligning will be skipped. If files are below 3000 pixels all is working 
with --gpu enabled.
THis is the error log triggered when testing in lightroom. In this error 
log I am using the official binaries from 2019 taken from here 
*Hugin-2019.2.0.dmg*:


The log indicates a problem with reading back the data from the GPU. This 
matches with the corrupted images.
Align_image_stack has no more debug possibilities for GPU remapping. Here 
we have to use nona.
Try the following:
1. Create a pto file with align_image_stack
align_image_stack -p test.pto drag/three/images/here
2. Then remap the image with nona. Activate gpu remapping and debug output
nona -o test --gpu --debug test.pto
Then provide the output of nona to the terminal (The resulting images 
should be corrupted again. If not the problem is somewhere other. Please 
check this.)
The easiest way would be to redirect the output to test file and provide 
this text file
nona -o test --gpu --debug test.pto >test.txt

Please provide also the pto file. Ideally use the already provided test 
images (DJI_0946.JPG ...)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9c2c43ef-09be-4303-8f14-d346e0c59aa6n%40googlegroups.com.

[hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Sonntag, 12. März 2023 um 18:22:14 UTC+1:

Hi! I did some more research here and I also triggered some error log which 
I put into pastebin for viewing.

I also notice following. Reducing file size to around 3000 pixels from 4000 
pixels processes the file just fine with --gpu enabled. So I guess size 
matters here? Maybe related to some race condition in graphic card/memory? 
Only speculating here.

Also triggered debug log message: *narrowing channel width for output as 
"uint8"*


Sorry, but I'm lost. First there are corrupted images, then it crashes.   
Next time you post debug messages from a 2014 version. 
Then you mentioned unsupported framebuffer format. This issue was fixed in 
2016.0.
So each time the error changes, this makes it hard to do anything 
substantial.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c5736312-0a6d-40bc-9e2b-318a2c3102afn%40googlegroups.com.

[hugin-ptx] Re: help on aligning panos from drone

[T. Modes]

PanoSeek schrieb am Mittwoch, 15. März 2023 um 13:19:53 UTC+1:


This still has some issues, it does not like snowy photos with a lack of 
features and sometimes chokes on photos with lots of water for the same 
reason and the sky is a giant black hole, but overall it produces decent 
panos.  

see https://groups.google.com/g/hugin-ptx/c/Af7TG2Bq-ko
There the information from drone were used to produce a pano including the 
feature-less images.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0bf639e6-5e8e-431f-9a8d-87f211cc9e19n%40googlegroups.com.

[hugin-ptx] Re: Batch stitch images in Hugin without cropping and using a fixed projection?

[T. Modes]

Hi,

gwrich...@gmail.com schrieb am Dienstag, 10. Januar 2023 um 18:33:15 UTC+1:

This then generates the .pto files that the batch processor can then use. 
However, the outputs are cropped and the projection varies between 
panoramas (images are shot on a levelled tripod with rotating motion only, 
the number of images varies). Is there a way to force the batch processor 
to output uncropped images with a cylindrical projection?

As an additional bonus is it possible to output these panoramas with a 
fixed height (in this case, the height of a single image) but with variable 
width depending on number of images?

I committed some changes which extends the assistant. 
There is now an option to select the output parameters depending on other 
variables (e.g. image count, or field of view).
This should be relative flexible to adapt to different use cases.

It is in the default branch. So it needs building from source and it will 
be in the next release.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c4c230eb-93a0-4f4b-8f18-6273ad061bdbn%40googlegroups.com.

[hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

Hi,

dud...@gmail.com schrieb am Dienstag, 7. März 2023 um 18:31:24 UTC+1:

Hi! Thanks a lot for getting back. Tested with correct prefix syntax but 
issue persists.

History. This gpu issue started on recent M1 machines. Early 13 inch models 
did not have this issue. Could be memory related. I could try and seek for 
error messages thorugh console again. I think I triggered an issue around 
framebuffer testing one version a while back ago.
So sorry for these vague descriptions but I will give more info when I have 
more time.


I tested under Windows with 2 different graphic cards. In all cases the 
results are ok. 
So it seems no general problem in align_image_stack. But without access to 
such a failing machine or further informations it is very difficult to 
debug.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2b6a4940-5395-432b-a351-9793a40a388fn%40googlegroups.com.

[hugin-ptx] Re: Mac builds of Hugin

[T. Modes]

dud...@gmail.com schrieb am Dienstag, 7. März 2023 um 17:26:11 UTC+1:

Thanks a lot for the compiled builds for macbook pro M1. I gotta aska very 
specific question. Could you guys reporoduce a potential issue around 
align_image_stack? Every time I enable --gpu when trying to align images 
directly in terminal on my mac I get corrupted files. Could anybody test in 
terminal:
*align_image_stack -a drag/three/images/here --gpu* then ENTER. Output will 
give half images or corrupted images. Something is going on with gpu but 
unclear what. Maybe could be fixed?


There is a problem with the command line: the -a switch expect the prefix 
as argument.
So the command line should be
align_image_stack -a prefix --gpu drag/three/images/here

 Does this happens will all image set or only with a single one? If this 
happens only for a single one (after fixing the command line as above) 
please provide the sample images, so we can check more.

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/50f38cfb-3a9a-4f3f-b9ff-36545dfcf8e1n%40googlegroups.com.