Re: [hugin-ptx] Re: Stereo image alignment

[Chris]

Maybe I read too much into Vladimir's recommendation:
https://wiki.panotools.org/Talk:Align_image_stack *->* 
http://vndlinuxphoto.blogspot.com/2011/01/stereo-image-alignment-in-hugin.html 
*->*
align_image_stack -p aligned.pto -a aligned -m -i -P -C *right.jpg left.jpg*
He names two files and puts them in a specific order - right then left, 
rather than the more logical left then right, so I assumed that's what you 
had to do. Checking the documentation I now see that the -S, _A and -P 
options don't mention files, so I assume the answer is probably the last 
one of those I suggested in my previous post - it makes no assumptions 
about L and R and just matches them all together. The order could be 
modifed by the options --align-to-first and/or --use-given-order 
On Thursday, April 18, 2024 at 9:57:42 PM UTC+1 Chris wrote:

> Yes, I understood that, but this thread is about stereo image alignment.  
> You need 2 images for that, so how does it pick 2 out of for example 10 
> images? Or does it assume the first one in order is the left-hand image and 
> then treat all the others as right-hand ones and match them to it? Or does 
> it make no assumptions about L and R and just match them all together?
>
> On Wednesday, April 17, 2024 at 8:50:21 PM UTC+1 bruno...@gmail.com wrote:
>
>> On Wed, 17 Apr 2024, 20:33 Chris wrote:
>>
>>> OK. It wouldn't have occurred to me do this because there could be ten 
>>> files in the "glob". Would it just take the first 2, and assume that the 
>>> first one was the right-hand image and the second the left-hand?
>>
>>
>> align_image_stack will align as many images as you like. It was 
>> originally devised for creating HDR images from bracketed exposure stacks, 
>> which typically have five or more photos.
>>
>> -- 
>> Bruno
>>
>

-- 
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/b30fcb73-cce3-4139-9c16-baec394d752dn%40googlegroups.com.

Re: [hugin-ptx] Purpose of this list

[Chris]

[image: davi...@gmail.com's profile photo]
davi...@gmail.com
Thank you for your careful reading of my posts, your understanding of the 
reason behind my questions and your support.
Chris


On Thursday, April 18, 2024 at 11:15:02 AM UTC+1 davi...@gmail.com wrote:

> Le 18/04/2024 à 09:19, Greg 'groggy' Lehey a écrit :
>
> On Wednesday, 17 April 2024 at 23:39:07 -0700, Chris wrote:
>
> T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz
> anderes als das englische Wort "gift" :).
> Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie
> haben etwas unterschiedliche Bedeutungen.
>
> (As I am sure you are aware, the German word "Gift" means something quite
> different to the English word "gift" :).
> Perhaps the words "impliziert" and "implies" are false friends - they have
> rather different meanings.)
> On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:
>
>
> Chris, I've seen a lot of messages from you.  This one seems to be the
> second one with identical content.  And most of them seem to have
> nothing to do with the software.
>
> If you feel that you have to attack T.Modes, please do it privately.
>
>
> Greg,
>
> Chris has repeatedly stated that his questions and remarks were about the 
> documentation. While I agree they don't have anything to do with the 
> coding, they do have to do with the software because documentation IMO 
> should be considered as being part of the software. If a documentation 
> tells me something (I am not speaking of the Hugin documentation here) and 
> the software does something else, then this is a bug. I agree this would be 
> a documentation bug, not a coding bug, but it would still be a bug. Or 
> maybe the word "bug" is not appropriate here. Anyhow documentation issues 
> should be addressed just like coding bugs should be fixed.
>
> About your second paragraph: I don't feel that Chris has attacked Thomas. 
> I saw Chris insisting on documentation issues. It happens that Thomas was 
> almost the only one to answer, but I did not feel anything personal in 
> Chris' mails. 
>
> I am glad that someone is checking the exact formulation of the 
> documentation. I don't know who wrote the documentation (although I would 
> not be surprised if it was Thomas), but I know that developers are seldom 
> good documentation writers. I am a software developer, I have tried to 
> write documentation and I don't think I ever achieved something which was 
> simultaneously short enough, clear enough and unambiguous. It is very 
> difficult for a developer to realize that people could understand what he 
> wrote differently from what he meant. It is even more difficult for him to 
> find all the sentences where such gap could exist. 
>
> I know that all the documentation was written by volunteers doing it on 
> their free time (just like the code). Improving the documentation takes 
> time, and the resources are limited. I guess that Thomas enjoys much more 
> coding than writing documentation (I do!).
>
> I enjoyed this discussion up to now because it has taught me a few things 
> about English. And I would appreciate improving the documentation in this 
> way because I am always wary about what I am understanding from a 
> documentation written by someone whose native language is probably not 
> English, even more so because it is not mine either.
>
>
>
>

-- 
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/aa65b98a-9993-4539-86a2-4c316ee90439n%40googlegroups.com.

Re: [hugin-ptx] Re: Stereo image alignment

[Chris]

Yes, I understood that, but this thread is about stereo image alignment.  
You need 2 images for that, so how does it pick 2 out of for example 10 
images? Or does it assume the first one in order is the left-hand image and 
then treat all the others as right-hand ones and match them to it? Or does 
it make no assumptions about L and R and just match them all together?

On Wednesday, April 17, 2024 at 8:50:21 PM UTC+1 bruno...@gmail.com wrote:

> On Wed, 17 Apr 2024, 20:33 Chris wrote:
>
>> OK. It wouldn't have occurred to me do this because there could be ten 
>> files in the "glob". Would it just take the first 2, and assume that the 
>> first one was the right-hand image and the second the left-hand?
>
>
> align_image_stack will align as many images as you like. It was originally 
> devised for creating HDR images from bracketed exposure stacks, which 
> typically have five or more photos.
>
> -- 
> Bruno
>

-- 
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/674044d9-5062-43db-a7db-9a58f7a9300cn%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

[Chris]

T.Modes, Wie du sicher weißt, bedeutet das deutsche Wort "Gift" etwas ganz 
anderes als das englische Wort "gift" :).
Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie 
haben etwas unterschiedliche Bedeutungen.

(As I am sure you are aware, the German word "Gift" means something quite 
different to the English word "gift" :).
Perhaps the words "impliziert" and "implies" are false friends - they have 
rather different meanings.)
On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:

>
> Moved from the other thread:
> T.Modes* "But you repeat often the same phrases: assumes options or 
> implies options means in this context that the corresponding option *[was?] 
> *automatically activated/set and does not need to *[be?] *set manually."*
>
> That's because you haven't clearly explained them before. Those phrases 
> are *meaningless* on their own. I continue to ask for the documentation 
> to be clarified so that anyone else reading it will be clear about what is 
> meant - without having to discover and read through this whole thread.
> There might be exceptions, but English usually needs an explanatory phrase 
> after "assumes" or "implies", or it doesn't make sense. Certainly in this 
> case they do. For example
> Implies *that* x *has been done*.
> Assumes *that* z *will be done*.
> In fact I can't see how either "implies" or "assumes" can be used in this 
> context. 
>
> Alternatively "This option will also set/activate/turn-on X"  uses simple 
> English and the meaning is quite clear.
>
> Why are you reluctant to alter the original phrases? Were they written by 
> someone with high status within the Panotools heirarchy who you do not wish 
> to offend by criticising his/her English? 
> I saw mention on one documentation page of an author with a name that 
> suggested that he was a French speaker, and you are a German speaker. With 
> respect, as a native speaker of English, I think my grasp of the English 
> language is naturally going to be deeper than yours.
>
> I have no axes to grind over this, I just wish to make this amazing 
> software more accessible to ordinary users by ensuring that its functions 
> are clearly exlained.
>
>
>
> On Wednesday, April 17, 2024 at 7:16:09 AM UTC+1 Chris wrote:
>
>> This comes from the other thread as it probably belongs here:
>>
>>
>>
>> *-S Assume stereo images - allow horizontal shift of control points. Adds 
>> all control points as "horizontal lines".-A Align stereo window - assumes 
>> -S. Adds one "normal" control point that is the nearest point, so that 
>> everything will appear behind the display plane.-P Align stereo window with 
>> pop-out effect - assumes -S. Adds one "normal" control point that is the 
>> nearest point from the border areas, so that the center of the image may 
>> appear in front of the display plane.*
>>
>> The language is a little ambiguous here - “assumes -S “ Does this mean
>>
>> -  “Assumes you have also used the –-S parameter?” If not what would 
>> happen?
>>
>> Or
>>
>> -  “This will also set/activate/turn-on the -S option.”
>>
>> On Saturday, April 13, 2024 at 9:53:47 AM UTC+1 Chris wrote:
>>
>>> *--align-to-first*
>>>
>>> …This *implies* also the --use-given-order option.
>>>
>>> To me as a native English speaker this is ambiguous but probably means:
>>>
>>> “*This means **you **must **also use **the **–use-given-order **option*
>>> *.”*
>>>
>>> If so, what would happen if you hadn’t? 
>>>
>>> But I suspect the intended meaning might have been 
>>>
>>> “*This also set**s**/activate**s**/turn**s**-on the --use-given-order 
>>> option.”*
>>>
>>> Looks like an option best avoided due to uncertainty about what it does.
>>>
>>> 
>>>
>>> *--**distortion* Hopefully if there is no distortion information or 
>>> it’s invalid, this process is not performed – rather than the program going 
>>> into an endless loop or aborting.
>>>
>>> I won’t use this option as I don’t want to risk the program hanging or 
>>> aborting.
>>>
>>> 
>>>
>>> *-g gsize*
>>>
>>> Break image into a rectangular grid (gsize x gsize) and attempt to find 
>>> *num* control points in each section (default

Re: [hugin-ptx] Re: Stereo image alignment

[Chris]

OK. It wouldn't have occurred to me do this because there could be ten 
files in the "glob". Would it just take the first 2, and assume that the 
first one was the right-hand image and the second the left-hand?

On Wednesday, April 17, 2024 at 7:38:10 AM UTC+1 bruno...@gmail.com wrote:

> On Wed, 17 Apr 2024, 07:13 Chris wrote:
>
>> T modes:"*No, you can also use placeholder like ? or *. "*
>>
>
> This is undocumented so far as I can see.
>>
>
> This is normal filename globbing. The ? and * characters are usually 
> expanded into a list of files by the operating system. align_image_stack 
> only sees the list of files.
>
> -- 
> Bruno
>

-- 
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/4980683b-d8de-4f4d-b078-6a72abec88c3n%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

[Chris]

T.Modes, Wie du sicher weißt, bedeutet das Wort "Gift" im Deutschen etwas 
ganz anderes als das Wort "Geschenk" 
im Englischen :)
Vielleicht sind die Worte "impliziert" und "implies" falsche Freunde - sie 
haben etwas unterschiedliche Bedeutungen.

(As I am sure you are aware, the word "Gift" in German means something 
quite different to the word "gift" in English :)
Perhaps the words "impliziert" and "implies" are false friends - they have 
rather different meanings.)
On Wednesday, April 17, 2024 at 7:33:51 AM UTC+1 Chris wrote:

>
> Moved from the other thread:
> T.Modes* "But you repeat often the same phrases: assumes options or 
> implies options means in this context that the corresponding option *[was?] 
> *automatically activated/set and does not need to *[be?] *set manually."*
>
> That's because you haven't clearly explained them before. Those phrases 
> are *meaningless* on their own. I continue to ask for the documentation 
> to be clarified so that anyone else reading it will be clear about what is 
> meant - without having to discover and read through this whole thread.
> There might be exceptions, but English usually needs an explanatory phrase 
> after "assumes" or "implies", or it doesn't make sense. Certainly in this 
> case they do. For example
> Implies *that* x *has been done*.
> Assumes *that* z *will be done*.
> In fact I can't see how either "implies" or "assumes" can be used in this 
> context. 
>
> Alternatively "This option will also set/activate/turn-on X"  uses simple 
> English and the meaning is quite clear.
>
> Why are you reluctant to alter the original phrases? Were they written by 
> someone with high status within the Panotools heirarchy who you do not wish 
> to offend by criticising his/her English? 
> I saw mention on one documentation page of an author with a name that 
> suggested that he was a French speaker, and you are a German speaker. With 
> respect, as a native speaker of English, I think my grasp of the English 
> language is naturally going to be deeper than yours.
>
> I have no axes to grind over this, I just wish to make this amazing 
> software more accessible to ordinary users by ensuring that its functions 
> are clearly exlained.
>
>
>
> On Wednesday, April 17, 2024 at 7:16:09 AM UTC+1 Chris wrote:
>
>> This comes from the other thread as it probably belongs here:
>>
>>
>>
>> *-S Assume stereo images - allow horizontal shift of control points. Adds 
>> all control points as "horizontal lines".-A Align stereo window - assumes 
>> -S. Adds one "normal" control point that is the nearest point, so that 
>> everything will appear behind the display plane.-P Align stereo window with 
>> pop-out effect - assumes -S. Adds one "normal" control point that is the 
>> nearest point from the border areas, so that the center of the image may 
>> appear in front of the display plane.*
>>
>> The language is a little ambiguous here - “assumes -S “ Does this mean
>>
>> -  “Assumes you have also used the –-S parameter?” If not what would 
>> happen?
>>
>> Or
>>
>> -  “This will also set/activate/turn-on the -S option.”
>>
>> On Saturday, April 13, 2024 at 9:53:47 AM UTC+1 Chris wrote:
>>
>>> *--align-to-first*
>>>
>>> …This *implies* also the --use-given-order option.
>>>
>>> To me as a native English speaker this is ambiguous but probably means:
>>>
>>> “*This means **you **must **also use **the **–use-given-order **option*
>>> *.”*
>>>
>>> If so, what would happen if you hadn’t? 
>>>
>>> But I suspect the intended meaning might have been 
>>>
>>> “*This also set**s**/activate**s**/turn**s**-on the --use-given-order 
>>> option.”*
>>>
>>> Looks like an option best avoided due to uncertainty about what it does.
>>>
>>> 
>>>
>>> *--**distortion* Hopefully if there is no distortion information or 
>>> it’s invalid, this process is not performed – rather than the program going 
>>> into an endless loop or aborting.
>>>
>>> I won’t use this option as I don’t want to risk the program hanging or 
>>> aborting.
>>>
>>> 
>>>
>>> *-g gsize*
>>>
>>> Break image into a rectangular grid (gsize x gsize) and attempt to find 
>>> *num* control points in ea

[hugin-ptx] Re: align_image_stack parameters

[Chris]

Moved from the other thread:
T.Modes* "But you repeat often the same phrases: assumes options or implies 
options means in this context that the corresponding option *[was?] 
*automatically 
activated/set and does not need to *[be?] *set manually."*

That's because you haven't clearly explained them before. Those phrases are 
*meaningless* on their own. I continue to ask for the documentation to be 
clarified so that anyone else reading it will be clear about what is meant 
- without having to discover and read through this whole thread.
There might be exceptions, but English usually needs an explanatory phrase 
after "assumes" or "implies", or it doesn't make sense. Certainly in this 
case they do. For example
Implies *that* x *has been done*.
Assumes *that* z *will be done*.
In fact I can't see how either "implies" or "assumes" can be used in this 
context. 

Alternatively "This option will also set/activate/turn-on X"  uses simple 
English and the meaning is quite clear.

Why are you reluctant to alter the original phrases? Were they written by 
someone with high status within the Panotools heirarchy who you do not wish 
to offend by criticising his/her English? 
I saw mention on one documentation page of an author with a name that 
suggested that he was a French speaker, and you are a German speaker. With 
respect, as a native speaker of English, I think my grasp of the English 
language is naturally going to be deeper than yours.

I have no axes to grind over this, I just wish to make this amazing 
software more accessible to ordinary users by ensuring that its functions 
are clearly exlained.



On Wednesday, April 17, 2024 at 7:16:09 AM UTC+1 Chris wrote:

> This comes from the other thread as it probably belongs here:
>
>
>
> *-S Assume stereo images - allow horizontal shift of control points. Adds 
> all control points as "horizontal lines".-A Align stereo window - assumes 
> -S. Adds one "normal" control point that is the nearest point, so that 
> everything will appear behind the display plane.-P Align stereo window with 
> pop-out effect - assumes -S. Adds one "normal" control point that is the 
> nearest point from the border areas, so that the center of the image may 
> appear in front of the display plane.*
>
> The language is a little ambiguous here - “assumes -S “ Does this mean
>
> -  “Assumes you have also used the –-S parameter?” If not what would 
> happen?
>
> Or
>
> -  “This will also set/activate/turn-on the -S option.”
>
> On Saturday, April 13, 2024 at 9:53:47 AM UTC+1 Chris wrote:
>
>> *--align-to-first*
>>
>> …This *implies* also the --use-given-order option.
>>
>> To me as a native English speaker this is ambiguous but probably means:
>>
>> “*This means **you **must **also use **the **–use-given-order **option*
>> *.”*
>>
>> If so, what would happen if you hadn’t? 
>>
>> But I suspect the intended meaning might have been 
>>
>> “*This also set**s**/activate**s**/turn**s**-on the --use-given-order 
>> option.”*
>>
>> Looks like an option best avoided due to uncertainty about what it does.
>>
>> 
>>
>> *--**distortion* Hopefully if there is no distortion information or it’s 
>> invalid, this process is not performed – rather than the program going into 
>> an endless loop or aborting.
>>
>> I won’t use this option as I don’t want to risk the program hanging or 
>> aborting.
>>
>> 
>>
>> *-g gsize*
>>
>> Break image into a rectangular grid (gsize x gsize) and attempt to find 
>> *num* control points in each section (default: 5 [5x5 grid+)
>>
>> Should I assume that the value of *num* comes from *-c num *if that 
>> option is used, otherwise it is the default of *8* mentioned under -*c?*
>>
>> I won’t use this option as I don’t want to risk the program hanging or 
>> aborting if my assumptions about *num* are incorrect.
>>
>> 
>>
>> *Optimisation phase*
>>
>> I assume x means adjustment along the horizontal pitch axis, y to 
>> adjustment on the vertical yaw axis and z to adjustment on the “out of the 
>> window” roll axis.
>>
>> Shouldn’t it be “Optimize *correction** of *radial distortion”?
>>
>> 
>>
>> *--**gpu *Since there is no information about what might happen if the 
>> GPU was unsuitable or missing (I have a GPU so can’t test that), I won’t 
>> use this option as I don’t wa

[hugin-ptx] Re: align_image_stack parameters

[Chris]

This comes from the other thread as it probably belongs here:



*-S Assume stereo images - allow horizontal shift of control points. Adds 
all control points as "horizontal lines".-A Align stereo window - assumes 
-S. Adds one "normal" control point that is the nearest point, so that 
everything will appear behind the display plane.-P Align stereo window with 
pop-out effect - assumes -S. Adds one "normal" control point that is the 
nearest point from the border areas, so that the center of the image may 
appear in front of the display plane.*

The language is a little ambiguous here - “assumes -S “ Does this mean

-  “Assumes you have also used the –-S parameter?” If not what would 
happen?

Or

-  “This will also set/activate/turn-on the -S option.”

On Saturday, April 13, 2024 at 9:53:47 AM UTC+1 Chris wrote:

> *--align-to-first*
>
> …This *implies* also the --use-given-order option.
>
> To me as a native English speaker this is ambiguous but probably means:
>
> “*This means **you **must **also use **the **–use-given-order **option*
> *.”*
>
> If so, what would happen if you hadn’t? 
>
> But I suspect the intended meaning might have been 
>
> “*This also set**s**/activate**s**/turn**s**-on the --use-given-order 
> option.”*
>
> Looks like an option best avoided due to uncertainty about what it does.
>
> 
>
> *--**distortion* Hopefully if there is no distortion information or it’s 
> invalid, this process is not performed – rather than the program going into 
> an endless loop or aborting.
>
> I won’t use this option as I don’t want to risk the program hanging or 
> aborting.
>
> 
>
> *-g gsize*
>
> Break image into a rectangular grid (gsize x gsize) and attempt to find 
> *num* control points in each section (default: 5 [5x5 grid+)
>
> Should I assume that the value of *num* comes from *-c num *if that 
> option is used, otherwise it is the default of *8* mentioned under -*c?*
>
> I won’t use this option as I don’t want to risk the program hanging or 
> aborting if my assumptions about *num* are incorrect.
>
> 
>
> *Optimisation phase*
>
> I assume x means adjustment along the horizontal pitch axis, y to 
> adjustment on the vertical yaw axis and z to adjustment on the “out of the 
> window” roll axis.
>
> Shouldn’t it be “Optimize *correction** of *radial distortion”?
>
> 
>
> *--**gpu *Since there is no information about what might happen if the 
> GPU was unsuitable or missing (I have a GPU so can’t test that), I won’t 
> use this option as I don’t want to risk the program hanging or aborting.
> That's it with the questions :)/
>
> On Thursday, April 11, 2024 at 6:41:37 PM UTC+1 T. Modes wrote:
>
>> 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 wit

[hugin-ptx] Re: Stereo image alignment

[Chris]

T modes:"*No, you can also use placeholder like ? or *. "*
This is undocumented so far as I can see.

On Wednesday, April 17, 2024 at 6:38:19 AM UTC+1 Chris wrote:

> *T Modes: "Sorry, I did not check correctly. It was a mistake on my side. 
> Take my excuse."*
> Apology accepted.
> *"But you repeat often the same phrases..."*
> I'll answer that* on *https://groups.google.com/g/hugin-ptx/c/StZln-rxsGw 
> where it belongs.
>
> On Monday, April 15, 2024 at 5:46:52 PM UTC+1 T. Modes wrote:
>
>> 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/c08712d2-96cc-4a55-9473-1eef5c70f284n%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

*T Modes: "Sorry, I did not check correctly. It was a mistake on my side. 
Take my excuse."*
Apology accepted.
*"But you repeat often the same phrases..."*
I'll answer that* on *https://groups.google.com/g/hugin-ptx/c/StZln-rxsGw 
where it belongs.

On Monday, April 15, 2024 at 5:46:52 PM UTC+1 T. Modes wrote:

> 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/8a254799-fe6d-4c1c-8f44-6a7f2e802f57n%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

In fact I can't see how either "implies" or "assumes" can be used in this 
context. 
*"This will also set the --use-given-order option"*  uses simple English 
and the meaning is quite clear.

On Monday, April 15, 2024 at 6:01:16 PM UTC+1 Chris wrote:

> OK
> *But you repeat often the same phrases: assumes options or implies options 
> means in this context that the corresponding option [was?] automatically 
> activated/set and does not need to [be?] set manually.*
>
> That's for 2 reasons. Because you've only just explained that clearly 
> here, and because, as I wrote in a message in the other thread, I was 
> hoping that the documentation would be clarified so anyone else reading the 
> documentation page would be clear about what is meant - without having to 
> discover and read through that thread.
> There might be exceptions, but English usually needs a verb after assumes 
> or implies, or it doesn't make sense. Certainly in this case they need a 
> verb. For example
> Implies that x *has been done*.
> Assumes that z *will be done*.
> On Monday, April 15, 2024 at 5:46:52 PM UTC+1 T. Modes wrote:
>
>> 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/79c97e38-c8f4-42c8-9b93-0dc924b1879en%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

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

That's for 2 reasons. Because you've only just explained that clearly here, 
and because, as I wrote in a message in the other thread, I was hoping that 
the documentation would be clarified so anyone else reading the 
documentation page would be clear about what is meant - without having to 
discover and read through that thread.
There might be exceptions, but English usually needs a verb after assumes 
or implies, or it doesn't make sense. Certainly in this case they need a 
verb. For example
Implies that x *has been done*.
Assumes that z *will be done*.
On Monday, April 15, 2024 at 5:46:52 PM UTC+1 T. Modes wrote:

> 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/3325b887-d904-4487-9e70-2ca9becb471an%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

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

On Monday, April 15, 2024 at 5:11:13 PM UTC+1 Chris wrote:

> Sorry, I didn't realise you were a moderator. 
> "on one platform. This is now the third one" I got no reponse on the 
> bugtracker so posted her. What is the third platforms are you referring to?
>
> On Monday, April 15, 2024 at 4:23:34 PM UTC+1 T. Modes wrote:
>
>> 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/13e6c3bb-db7e-45c5-9842-6800d3d2fd4an%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

Sorry, I didn't realise you were a moderator. 
"on one platform. This is now the third one" I got no reponse on the 
bugtracker so posted her. What is the third platforms are you referring to?

On Monday, April 15, 2024 at 4:23:34 PM UTC+1 T. Modes wrote:

> 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/b233223e-74dd-424a-90a9-bddbdc8fdd48n%40googlegroups.com.

[hugin-ptx] Re: Stereo image alignment

[Chris]

 

Vladimir. I have written an app that relies on align-image-stack and your 
3D patch to it. The app is for images taken with a mobile phone or a 
camera, so they won’t be aligned properly and won’t create a 3D image 
without tedious manual alignment or preferably the use of AIS.

I have recently re-read the documentation 
https://wiki.panotools.org/Align_image_stack to try to make the most of AIS 
by using the optimum choice of settings. I found it a bit limited and 
posted some queries here https://groups.google.com/g/hugin-ptx/c/StZln-rxsGw 
with the result that it has been improved.

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

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

   - 
   
   - 
   
   It only names one input file.
   - 
   
   It sets both -A and -P which are contradictory. 
   
I have been using the settings you mention in your link above.

*align_image_stack -p aligned.pto -a aligned -m -i -P -C right.jpg left.jpg*

(It revealed this bug https://bugs.launchpad.net/hugin/+bug/2002813 when 
using -i which caused AIS to hang when the images were blurry, it’s fixed 
now.)

I have since noticed that you have added a statement to the official page:

*align_image_stack -p out.pto -x -s 4 -P -C right.tif left.tif*

*T**he options*
*-S *Assume stereo images - allow horizontal shift of control points. Adds 
all control points as "horizontal lines". 
-A Align stereo window - assumes -S. Adds one "normal" control point that 
is the nearest point, so that everything will appear behind the display 
plane. 
-P Align stereo window with pop-out effect - assumes -S. Adds one "normal" 
control point that is the nearest point from the border areas, so that the 
center of the image may appear in front of the display plane. 

The language is a little ambiguous here - “assumes -S “ Does this mean 

-  “Assumes you have also used the –-S parameter?” If not what would 
happen? 

Or

-  “This will also set/activate/turn-on the -S option.”

-m magnification 

I don’t think the -m is relevant for my application since both L and R 
images would be taken quickly one after the other.

*-i **Optimize image center shift for all image**s*

I assume this means “Optimise matching of centre of image, or weight 
corrections towards the centre rather than the periphery. That seems 
sensible, however it might attempt to match the x axis and I don't think we 
want that ‘corrected’ as it has to be different for the 3D effect.

*-x *That seems wrong to me as I don't think we want that ‘corrected’, as 
it has to be different for the 3D effect. Why did you switch to using this?

*Optimisation phase*

States that yaw pitch and roll are optimised by default. My images are 
likely to be incorrectly matched in the y axis and in roll, so need 
correction. I don’t think they should be adjusted in the x axis or in yaw 
as they are 3D factors. Unfortunately the yaw correction can’t be switched 
off, as it is automatic and there is no parameter for it.

I am going to try align_image_stack -a output.tif -y -P -C right.tif 
left.tif

Would you like to comment on my thoughts?











On Monday, January 31, 2011 at 10:55:14 PM UTC Vladimir Nadvornik wrote:

> Hi,
>
> I wrote a tutorial how to use my stereo patches (attached to bug
> 679753):
>
>
> http://vndlinuxphoto.blogspot.com/2011/01/stereo-image-alignment-in-hugin.html
>
> Comments are welcome.
>
> Vladimir

-- 
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/fd7f6286-d140-4729-a2c2-b70797a0fa20n%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

[Chris]

 

*--align-to-first*

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

To me as a native English speaker this is ambiguous but probably means:

“*This means **you **must **also use **the **–use-given-order **option**.”*

If so, what would happen if you hadn’t? 

But I suspect the intended meaning might have been 

“*This also set**s**/activate**s**/turn**s**-on the --use-given-order 
option.”*

Looks like an option best avoided due to uncertainty about what it does.



*--**distortion* Hopefully if there is no distortion information or it’s 
invalid, this process is not performed – rather than the program going into 
an endless loop or aborting.

I won’t use this option as I don’t want to risk the program hanging or 
aborting.



*-g gsize*

Break image into a rectangular grid (gsize x gsize) and attempt to find 
*num* control points in each section (default: 5 [5x5 grid+)

Should I assume that the value of *num* comes from *-c num *if that option 
is used, otherwise it is the default of *8* mentioned under -*c?*

I won’t use this option as I don’t want to risk the program hanging or 
aborting if my assumptions about *num* are incorrect.



*Optimisation phase*

I assume x means adjustment along the horizontal pitch axis, y to 
adjustment on the vertical yaw axis and z to adjustment on the “out of the 
window” roll axis.

Shouldn’t it be “Optimize *correction** of *radial distortion”?



*--**gpu *Since there is no information about what might happen if the GPU 
was unsuitable or missing (I have a GPU so can’t test that), I won’t use 
this option as I don’t want to risk the program hanging or aborting.
That's it with the questions :)/

On Thursday, April 11, 2024 at 6:41:37 PM UTC+1 T. Modes wrote:

> 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/87ab7e5b-39a8-493d-8335-e2a32f3221e5n%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

[Chris]

--gpu
*Use GPU for remapping*

Presumably if there is no GPU or it’s unsuitable, the CPU is used instead.

I'll look at the 3D imaging later.

On Thursday, April 11, 2024 at 9:20:43 AM UTC+1 Chris wrote:

> *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. * 
>
> Does this mean 
>
>  “Assumes you have also used –use-given-order.” If so, what would 
> happen if you hadn’t? 
>
> Or
>
>   “This will also set/activate/turn-on the -use-given-order option.”
>
> ---
> *-f HFOV* *...use if EXIF info not complete* 
>
> If neither is available what happens?
>
> ---
> *-l* *Assume linear input files are in linera colour space.* 
>
> Is the default gamma colour space?
>
> ---
> *--distortion* *...the lens distortion...is done* 
>
> Perhaps this means “...the lens distortion *correction*...*are* done...” 
> Presumably if there is no distortion information or it’s invalid, this 
> process is just abandoned. 
>
> ---
>
> *-g* *gsize* ...attempt to find num control points… 
>
> i assume that the value of -num comes from -c *num *if it is set, 
> otherwise it is the default of 8 mentioned in that section.
>
> --- 
>
> *Optimisation phase*
>
> How do “(yaw, pitch and roll) “ relate to x, y,z?
>
> --- 
>
> *-**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 . Unless you mean *prioritise*, in which case:
>
>   All of them will be optimised, but -X will be prioritised.
>
> Or
>
>  -X will be optimised, the rest ignored.
> On Tuesday, April 9, 2024 at 7:29:50 PM UTC+1 T. Modes wrote:
>
>> 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 
>>
>> Mu

[hugin-ptx] Re: align_image_stack parameters

[Chris]

 

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

Does this mean 

 “Assumes you have also used –use-given-order.” If so, what would 
happen if you hadn’t? 

Or

  “This will also set/activate/turn-on the -use-given-order option.”

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

If neither is available what happens?

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

Is the default gamma colour space?

---
*--distortion* *...the lens distortion...is done* 

Perhaps this means “...the lens distortion *correction*...*are* done...” 
Presumably if there is no distortion information or it’s invalid, this 
process is just abandoned. 

---

*-g* *gsize* ...attempt to find num control points… 

i assume that the value of -num comes from -c *num *if it is set, otherwise 
it is the default of 8 mentioned in that section.

--- 

*Optimisation phase*

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

--- 

*-**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 . Unless you mean *prioritise*, in which case:

  All of them will be optimised, but -X will be prioritised.

Or

 -X will be optimised, the rest ignored.
On Tuesday, April 9, 2024 at 7:29:50 PM UTC+1 T. Modes wrote:

> 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/87414a41-12fb-4bfb-b0b7-fd170c5dad43n%40googlegroups.com.

[hugin-ptx] Re: align_image_stack parameters

[Chris]

lt is rectilinear?*

-

5+

If -g is used, -c must be used too to supply *num*

-c -g

Affect precision.

-

6x

Mutually exclusive?

-t --corr

Affect precision

What’s the difference between -t and -corr?

-

-

Unrelated to other parameters

-p -v -h

-f -C -s --gpu

--distortion

Tools

Various
On Tuesday, April 9, 2024 at 5:19:52 PM UTC+1 T. Modes wrote:

> 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 
> <https://wiki.panotools.org/index.php?title=Align_image_stack&action=edit>.”*
>
> 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/ae9129f4-e522-4051-a179-b09efd1aad7bn%40googlegroups.com.

[hugin-ptx] Disappearing posts

[Chris]

This is my third post. The previous two attempts have both disappeared. 
There was no suggestion that they might have been awaiting moderation. What 
is going on?
Chris

-- 
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/a85695aa-7b84-4cd2-953f-d65271411af0n%40googlegroups.com.

[hugin-ptx] Re: Preview only showing bottom left quarter of image - Retina M1 MacBook

[Chris Biddle]

Same situation here except I have an intel-based macbook pro. The program 
is unusable because I can't crop any image correctly.

On Sunday, May 15, 2022 at 8:30:27 AM UTC-4 jpat...@gmail.com wrote:

> Firstly thanks for this software which I have running fine on my old iMac.
>
> I have just installed it on my M1 MacBook Pro running macOS 12.3 
> (Monterey). This has a 'Retina' High DPI screen.
>
> When I bring an image into Hugin, only the bottom lower left quarter is 
> showing in the preview area. The image also jumps when I move the sliders - 
> sometimes I get the whole image rendered in this area, sometimes the whole 
> image is shown - but only the bottom left quarter  of the preview area is 
> being used.
>
> I did find a link to a .dmg (Hugin-2019.3.0-ce7c20de1e12.dmg) in another 
> post which was supposed to be a blind fix but unfortunately that wont run 
> and errors out with a -47 error.
>
> I appreciate that you may not have the kit necessary to debug this and I 
> also appreciate that Apple don't make it easy for open source developers :( 
> so not expecting a quick fix but posting this more for info and to see if 
> this was a recognised problem.  I couldn't find anything when I did an 
> (admittedly fairly short) search for similar issues. I have Hugin on my 
> other computer so will just use it there.
>
>

-- 
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/011aac3a-8df2-41a0-b2b1-98033d8af8f8n%40googlegroups.com.

[hugin-ptx] Broken popup halts program

[Chris Biddle]

In image variables window under the lens tab, changing the lens field of 
view to 0 creates a popup that you can't quit out of

-- 
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/9343875f-454e-47ea-974f-59e9b544b916n%40googlegroups.com.

[hugin-ptx] [PATCH] Install MIME type icon into the hicolor theme

[Chris Mayo]

Most Hugin icons are installed into the hicolor theme but the MIME type 
icon is still going into the defunct gnome theme.
The attached patch changes that and removes the gnome-mime- prefix from the 
icon filename.

For me this appears to fix the icon not displaying for .pto files in GNOME 
Files (nautilus).

The patch also updates this filename in artwork-src/update_artwork.sh, I 
only found that with grep and haven't tested it.

Chris

-- 
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/5dfdadb8-5178-4fa9-890b-b923e91e2ba4%40googlegroups.com.
diff --git a/artwork-src/update_artwork.sh b/artwork-src/update_artwork.sh
--- a/artwork-src/update_artwork.sh
+++ b/artwork-src/update_artwork.sh
@@ -270,7 +270,7 @@
 O_LIN="src${S}hugin1${S}hugin${S}xrc${S}data${S}pto_icon.png"
 Iconify
 # extra Linux option for the gnome MIME type
-cp "./${SRC}/${F}.48.png" "${P}src${S}hugin1${S}hugin${S}gnome-mime-application-x-ptoptimizer-script.png"
+cp "./${SRC}/${F}.48.png" "${P}src${S}hugin1${S}hugin${S}application-x-ptoptimizer-script.png"
 
 
 # -
diff --git a/src/hugin1/hugin/CMakeLists.txt b/src/hugin1/hugin/CMakeLists.txt
--- a/src/hugin1/hugin/CMakeLists.txt
+++ b/src/hugin1/hugin/CMakeLists.txt
@@ -232,7 +232,7 @@
   IF(UNIX)
 # install further stuff (icons etc.)
 INSTALL(FILES hugin.desktop DESTINATION ${DATADIR}/applications)
-INSTALL(FILES gnome-mime-application-x-ptoptimizer-script.png DESTINATION ${DATADIR}/icons/gnome/48x48/mimetypes)
+INSTALL(FILES application-x-ptoptimizer-script.png DESTINATION ${DATADIR}/icons/hicolor/48x48/mimetypes)
 INSTALL(FILES hugin.xml DESTINATION ${DATADIR}/mime/packages)
   ENDIF(UNIX)
 ENDIF(APPLE)
diff --git a/src/hugin1/hugin/gnome-mime-application-x-ptoptimizer-script.png b/src/hugin1/hugin/application-x-ptoptimizer-script.png
rename from src/hugin1/hugin/gnome-mime-application-x-ptoptimizer-script.png
rename to src/hugin1/hugin/application-x-ptoptimizer-script.png

Re: [hugin-ptx] Stitching scanned images

['Chris H' via hugin and other free panoramic software]

aks,

Masking worked like a charm! Thanks a lot!

On Friday, 8 November 2019 01:02:23 UTC, aks wrote:
>
> Yes, use masks. On image A you mask off the part of image B you do not 
> want to come from image A. On image B you mask off the part of image A you 
> do not want to come from image B. By the way, if you had multiple image As 
> and image Bs where each is a stack of the same image at different exposures 
> then you would need to use the exact same mask for the As and the exact 
> same mask for the Bs. That is when the mask copy paste ability comes in 
> handy.
>
> Regarding the sentence, depending on how many of these you need to do and 
> also how well produced the finished product needs to look, I would add in 
> the sentence with another application. The sentence text can be added with 
> an opaque background so that the new text covers up the poorly stitched 
> sentence.
>
> On Nov 7, 2019, at 4:44 PM, 'Chris H' via hugin and other free panoramic 
> software > wrote:
>
> Hi,
>
> My first post here so hello to all!
> I have a question regarding stitching scanned images. 
> So I am scanning a book that is slightly wider than A4 so I end up with 
> two scans for every page, the left and the right scans that need to be 
> stitched.
> I came across this tutorial 
> http://hugin.sourceforge.net/tutorials/scans/en.shtml and am almost 
> there, the only problem is Hugin by default seems to be overlapping those 
> two images, so as a result if the right edge of the left scan has some 
> imperfections resulting from for example that scan not being firmly pressed 
> into the scanner along that edge, they will be reflected in the resulting 
> panorama image, obviously same thing happens if there are some 
> imperfections with the left edge of the right scan.
> But more importantly what I am scanning is a book so the written sentences 
> from both left and right image are also stitched with some kind of 
> overlapping, but after that's done the edges of the letters on the 
> resulting panorama are far from being as smooth as they are if you look at 
> each image separately.
>
> So the question... Is there a way to configure the stitcher so that 
> everything to the left of the "stitching line" would come from the left 
> image only and similarly everything to the right of the stitching line from 
> the right image only?
>
> Thanks in advance for any suggestions!
> Chris
>
> -- 
> 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 hugi...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/86994b19-d5d6-46b9-8598-9923015f7617%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/hugin-ptx/86994b19-d5d6-46b9-8598-9923015f7617%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
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/b38142f0-bed4-454a-bc70-46f4a677db19%40googlegroups.com.

[hugin-ptx] Stitching scanned images

['Chris H' via hugin and other free panoramic software]

Hi,

My first post here so hello to all!
I have a question regarding stitching scanned images. 
So I am scanning a book that is slightly wider than A4 so I end up with two 
scans for every page, the left and the right scans that need to be stitched.
I came across this tutorial 
http://hugin.sourceforge.net/tutorials/scans/en.shtml and am almost there, 
the only problem is Hugin by default seems to be overlapping those two 
images, so as a result if the right edge of the left scan has some 
imperfections resulting from for example that scan not being firmly pressed 
into the scanner along that edge, they will be reflected in the resulting 
panorama image, obviously same thing happens if there are some 
imperfections with the left edge of the right scan.
But more importantly what I am scanning is a book so the written sentences 
from both left and right image are also stitched with some kind of 
overlapping, but after that's done the edges of the letters on the 
resulting panorama are far from being as smooth as they are if you look at 
each image separately.

So the question... Is there a way to configure the stitcher so that 
everything to the left of the "stitching line" would come from the left 
image only and similarly everything to the right of the stitching line from 
the right image only?

Thanks in advance for any suggestions!
Chris

-- 
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/86994b19-d5d6-46b9-8598-9923015f7617%40googlegroups.com.

[hugin-ptx] Exif + Intermediate files

[Chris Brown]

I'm using Hugin to align 'then & now' photos and I'm trying to figure out 
how to keep exif data from the original 'now' photos for the remapped 
intermediate files. 

I'd also like to save values for each photo from the optimiser tab 
(orientation & lens parameters - y,p,r etc) in the exif of the intermediate 
so I can keep track of how originals have been changed.

I'm wondering what values can be saved using the argfiles in hugin 
preferences and if there is any further documention about it?

-- 
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/650b6696-ff8f-4a7f-bb72-5807ba86d270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] 2016.2.0 RC.1 Windows x64 Problem with large HDR output above 5000x2500 pixels

[Chris Blunt]

Hi folks, 

I've been really interested in panoramas for some time now and recently 
invested in some kit to get going on this.  When it comes to stitching I 
have been trying to get to grips with Hugin and after some perseverance I 
have made some good results.  

I do however have some issues and could really use some expert guidance. 
 To get a nice exposure I have shot my images bracketed -1, 0, +1, load 
those into Hugin which seems be OK at detecting the stacks, the panorama 
all looks good and I can stitch to an HDR output without any problems to a 
size of approximately 5000 x 2500 once I start heading up above there 
towards the native resolution of the images 18000 x 9000 my resulting image 
is missing a section.  If I just export to LDR JPG it will stitch full size 
but of course I loose the dynamic range.

I originally tried the Stable 32 bit version and it would suffer running 
out of memory, I then moved to this version: 2016.2.0.48cb11a23351 built by 
Thomas and now have 16 gig of RAM on an i5.

I don't want to give up on Hugin and my budget is cooked on the hardware.

Your guidance and support would be much appreciated.

Best regards

Chris





-- 
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/4000ef2f-c205-4bc8-9786-77c5125b345d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Crash on image load Windows 7 64 bit

[Chris Mellinger]

Hi, I'm having the exact same issue. I looked for updates, but it looks 
like I have everything current. Here's my specs:

Hugin 2013.0.0
Lenovo Z560
Intel i3 M 380
4 Gb RAM
Windows 7 64
Intel HD integrated graphics

It's strange because Hugin never gets to the point of actually aligning the 
photos. As mrf said, it's immediately after clicking "Ok" on the FOV 
dialog. I can't even test the alignment because I can't get images into the 
program.

Thanks to anyone who has an idea about this!

On Saturday, November 30, 2013 3:57:02 PM UTC+9, mrf wrote:
>
> Every time I load an image I get a crash.
>
> I had installed over an older version (unknown version).
>
> I tried
>
>- rebooting
>- resetting all the defaults in each tab of Preferences
>- uninstalling and re-installing
>- loading different JPGs from different cameras
>- changing the default Control Point to Autopano-SIFT-C or to 
>- converting to PNG before loading - asks for focal length and then 
>crashes on Ok press
>- toggling all the checkboxes (Align image after loading etc.) in the 
>Preferences/Assistant tab
>- switching to Advanced and Expert mode
>
> None of the above help.
> Details from the crash dialog:
>
> Problem signature:
>   Problem Event Name:APPCRASH
>   Application Name:hugin.exe
>   Application Version:0.0.0.0
>   Application Timestamp:523cb338
>   Fault Module Name:StackHash_ac8d
>   Fault Module Version:6.1.7601.18247
>   Fault Module Timestamp:521eaf24
>   Exception Code:c374
>   Exception Offset:000c4102
>   OS Version:6.1.7601.2.1.0.256.48
>   Locale ID:5129
>   Additional Information 1:ac8d
>   Additional Information 2:ac8d7bc04980805de53396cfaeda9dbb
>   Additional Information 3:84e6
>   Additional Information 4:84e6441859e1c67096e24f26f4cab6b1
>
> Any suggestions please?
>

-- 
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/eb403ea3-598f-4d13-9fa5-3132c6179daa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Curiosity's panoramic images

[Chris Dennis]

On 14/08/12 19:44, Thomas Pryds wrote:

On the same topic, see

http://360cities.net/image/curiosity-rover-martian-solar-day-2


Ha!  Capricorn One was right!  According to that link, the picture was 
taken by Curiosity in New Mexico.


cheers

Chris
--
Chris Dennis  cgden...@btinternet.com
Fordingbridge, Hampshire, UK

--
You received this message because you are subscribed to the Google Groups "Hugin and 
other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Unexpected artefacts in equirectangular output.

[Chris Godfrey]

Thanks for the responses.

Whilst awaiting a response I tried increasing hfov of the Terragen
camera to 95 degrees. Did the trick ..

I might try the remapping as well to see if that works, but it's nicer
to do it all in one app if possible. (Or am I just being
lazy ?  ;o) )

I'd already confirmed that the images lined up in Photoshop. The
Terragen renderer is pretty accurate in that respect.

Thanks

Chris


On Jun 12, 12:30 pm, Carl von Einem  wrote:
> Hi Chris,
>
> as a first test: can you assemble your cube faces to one cross manually
> in an image editor, i.e. do they fit together at the edges?
>
> If that's the case you'll need to make sure no blending tries to do
> something to your edges which have no overlap at all.
>
> I'm not sure if there's a way to disable enblend at all inside Hugin's
> user interface (preferable in this case) so one solution is to output
> 'Remapped Images:' -> 'No exposure correction, low dynamic range'
> and set
> 'Processing:' -> 'Remapper' -> 'Nona' to "Don't save cropped images".
>
> The resulting remapped images can now be easily combined in your image
> editor: duplicate layers into one file, set all layers to only use the
> lighter information and flatten.
>
> It'll be simpler from the command line though if you plan to do several
> equirects.
>
> Cheers,
> Carl
>
> Chris Godfrey schrieb am 12.06.12 12:41:
>
>
>
>
>
>
>
> > Hi,
>
> > I am trying to create equirectangular panoramas for use as environment
> > maps in 3DS Max.
>
> > The skies are created in Terragen 2. I set up a camera with a 90 deg
> > hfov and render 6 square images. 4 with 0 deg pitch at 90 deg
> > intervals and then 1 with 0 deg yaw 90 deg pitch for sky and the last
> > being 0 deg yaw with -90 deg pitch.
>
> > The six image files are brought into Hugin and the rotational
> > parameters for each image are adjusted accordingly.
>
> > All looks fine in the preview, however, when I stitch the resulting
> > output has a mixture of black lines and/or black areas at the edges of
> > each image.
>
> > The areas differ between standard and hdr output.
>
> > Am I missing a setting before stitching. ?

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Unexpected artefacts in equirectangular output.

[Chris Godfrey]

Hi,

I am trying to create equirectangular panoramas for use as environment
maps in 3DS Max.

The skies are created in Terragen 2. I set up a camera with a 90 deg
hfov and render 6 square images. 4 with 0 deg pitch at 90 deg
intervals and then 1 with 0 deg yaw 90 deg pitch for sky and the last
being 0 deg yaw with -90 deg pitch.

The six image files are brought into Hugin and the rotational
parameters for each image are adjusted accordingly.

All looks fine in the preview, however, when I stitch the resulting
output has a mixture of black lines and/or black areas at the edges of
each image.

The areas differ between standard and hdr output.

Am I missing a setting before stitching. ?

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: no output photo created

[Chris Richburg]

More information on my setup:
- Windows 7 SP1 64-bit
- Hugin Version: 2011.4.0.cf9be9344356 built by Matthew Petroff
downloaded from the Hugin web page
- I was trying to stitch a panorama, which I have done dozens of
times.  I used the assistant tab to load, align, and create panorama.
Everything looks normal, and there are no error messages.  However, no
jpg/tiff file is created, only the project file and make file.

Is there a way to download an older Hugin version?  The other people
paolobenve linked to are also using 2011.4.0.  Also, I never had this
problem on an older version on a different machine (which I no longer
have access to).

Thanks for the help!

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] no output photo created

[Chris Richburg]

I need some help with Hugin.  I had it working on a new computer, but
then it stopped creating output photos.  I get the Hugin PTO and
makefiles in the output directory, but no photo (tiff).  I also tried
searching the whole hard drive and could not locate the output photo.
Since it Hugin worked correctly on this computer before, I am assuming
I changed a setting that caused this problem.  I also tried
uninstalling and re-installing with the clear registry option, but
that didn't fix it. Can anyone help me out?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Hugin WITHOUT enblend

[Chris Dennis]

Hello panoramists

Enblend does a wonderful job, but sometimes I want to create a
panorama without it.

For example, I want to demonstrate how hugin lays out the images by
added a thin black border to each image that will show the edge of
each image in the final panorama.

That works fine -- the borders show up in the preview.  But when I
stitch it, enblend cleverly blends away the borders!

Is there a way to turn off enblend from within the hugin GUI?  I tried
various combinations of options, but none of them have worked.

An alternative might be to do it from the command line: as a shortcut
to learning which options to use, I've tried capturing the output in
the stitching window, but it disappears too quickly.  Is there a way
to capture the list of commands that hugin is running?

cheers

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Hardware: Cost efficient cluster for stitching?

[Chris Erskine]

have you seen this?
http://helmer.sfe.se/

its a couple of years old now, and I'd prob do it now something like the
2600. or i guess more of them with a cheaper chip. but that it a good cpu
for the price

the other option you can go is something like a 4p opteron system with
either 32 or 48 cores. if you get the base cpu they work out quite well
price/performance. though you would need a fast storage to feed it. and you
probably would want to make a bunch of virtual machines out of it.

I'm not sure which hugin would prefer but your work load is probably more
suited to more low end nodes.

here's a list cpu's value/performance
http://www.cpubenchmark.net/cpu_value_available.html



On Fri, Jan 13, 2012 at 12:21 PM, Zachary  wrote:

>  i think you sent this to the wrong person i just tried to post a question
> about hugin that's probably where you got mu email from
>
>
> On 1/12/2012 7:35 PM, Chris Erskine wrote:
>
> how much ram is it using?
>
> and have you tried running muiltiple renders on your 6 core amd?
>
> my first thought is your transfer speed may become a bottleneck.
>
> my thought would be to get an intel 2600 enough ram to cover 8 jobs at
> once and an ssd that good at multitreaded read.
>
> though it may run faster to disable hyperthreading and just run 4 jobs at
> once.
>
>
> On Fri, Jan 13, 2012 at 3:23 AM, Tim Nugent  wrote:
>
>> Have a look at Xbox (and maybe PS3 - not sure if these still let you run
>> Linux) clusters. Lots of people are going to be building clusters using
>> Raspberry Pi's when they go on sale hopefully later this month (700Mhz
>> ARM/Linux machines for ~$25). Whether or not you get the performance you're
>> after, it'd be a fun project putting something like that together. I have
>> quite a lot of experience with Sun Grid Engine on very large/expensive
>> compute clusters and Hugin jobs run fine.
>>
>>  Tim
>>
>>
>> On 12 January 2012 14:49, Jan Martin wrote:
>>
>>> It is time to reveal a few more facts to allow for better judgment.
>>>
>>> Each image set is 13.2 MB per panorama only.
>>> Stitching, blending, cubing and tiling needs 8.5 seconds altogether on a
>>> 6 core AMD PC for USD 750.
>>>
>>> What I am looking for is to build a cluster from many cheap boards and
>>> CPUs, that provides a "better performance per Dollar".
>>> Not a "fast PC on a budget".
>>>
>>> Something like "10 boards of 150 USD each" that provide 6 times the
>>> performance, bust just cost twice.
>>>
>>> Is there really nobody whom runs a rendering farm?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Hugin and other free panoramic software" group.
>>> A list of frequently asked questions is available at:
>>> http://wiki.panotools.org/Hugin_FAQ
>>> To post to this group, send email to hugin-ptx@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> hugin-ptx+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/hugin-ptx
>>>
>>
>>--
>> You received this message because you are subscribed to the Google Groups
>> "Hugin and other free panoramic software" group.
>> A list of frequently asked questions is available at:
>> http://wiki.panotools.org/Hugin_FAQ
>> To post to this group, send email to hugin-ptx@googlegroups.com
>> To unsubscribe from this group, send email to
>> hugin-ptx+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Hardware: Cost efficient cluster for stitching?

[Chris Erskine]

how much ram is it using?

and have you tried running muiltiple renders on your 6 core amd?

my first thought is your transfer speed may become a bottleneck.

my thought would be to get an intel 2600 enough ram to cover 8 jobs at once
and an ssd that good at multitreaded read.

though it may run faster to disable hyperthreading and just run 4 jobs at
once.


On Fri, Jan 13, 2012 at 3:23 AM, Tim Nugent  wrote:

> Have a look at Xbox (and maybe PS3 - not sure if these still let you run
> Linux) clusters. Lots of people are going to be building clusters using
> Raspberry Pi's when they go on sale hopefully later this month (700Mhz
> ARM/Linux machines for ~$25). Whether or not you get the performance you're
> after, it'd be a fun project putting something like that together. I have
> quite a lot of experience with Sun Grid Engine on very large/expensive
> compute clusters and Hugin jobs run fine.
>
> Tim
>
>
> On 12 January 2012 14:49, Jan Martin  wrote:
>
>> It is time to reveal a few more facts to allow for better judgment.
>>
>> Each image set is 13.2 MB per panorama only.
>> Stitching, blending, cubing and tiling needs 8.5 seconds altogether on a
>> 6 core AMD PC for USD 750.
>>
>> What I am looking for is to build a cluster from many cheap boards and
>> CPUs, that provides a "better performance per Dollar".
>> Not a "fast PC on a budget".
>>
>> Something like "10 boards of 150 USD each" that provide 6 times the
>> performance, bust just cost twice.
>>
>> Is there really nobody whom runs a rendering farm?
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Hugin and other free panoramic software" group.
>> A list of frequently asked questions is available at:
>> http://wiki.panotools.org/Hugin_FAQ
>> To post to this group, send email to hugin-ptx@googlegroups.com
>> To unsubscribe from this group, send email to
>> hugin-ptx+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] ======> Best software to recover deleted pictures <======

[chris jeraco]

Photo Recovery Software

===

  http://www.photorecoverysoftwares.net

===
Now-a-days, deleting pictures has become very common issue. But need
not be anxious, as you can recover deleted pictures without difficulty
using the top most ADI Software’s Photo Recovery Tool.

At the same phase, it is most important to know that, the deleted
photos should not be overwritten by any case. Cases might be the usage
of the same drive from which deletion has happened for further saving
purpose. Doing so will overwrite the deleted data and further causes
permanent data loss.

ADI Software’s Photo Recovery Tool is highly developed and designed
for all levels of computer users, resulting in effective recovery
through user friendly interface. Software supports all major images,
audio and video file formats. It also includes professional RAW
photographic file formats.

Trial version of the software can be tried and tested for absolutely
FREE.  Using this trial version you can preview the recovered pictures
on which you can trust and purchase the full version to recover
deleted pictures.

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: open source close range photogrammetry

[Chris Erskine]

that insight3d looks amazing.

I'm going to have a look at this.

On Sun, Nov 28, 2010 at 2:02 AM, Gerhard Killesreiter <
gerh...@killesreiter.de> wrote:

>
>
> On 27 Nov., 03:24, luca vascon  wrote:
> > http://insight3d.sourceforge.net/
> >
> > I would invite this guy to join us!!!
> >
>
> Where can one join? The website only gived the mail address of the
> author.
>
> Also, did anybody get this to run? I managed to compile it on Linux
> after some tinkering, but only got a segfault after trying to match
> images.
>
> Cheers,
> Gerhard
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Measure buildings from a panorama?

[Chris Erskine]

i should add you still need mutliple pano's to do it in image modeller.

its just that its easier to get a lot of control points between different
panos. so you could probably get away with say 3 pano's vs 10 - 20 photos.
but i haven't tried it out yet with the pano's.

and you still need to add in know messurement somewhere otherwise you won't
be able to figure out the scale.


On Thu, Nov 25, 2010 at 1:54 PM, Tduell  wrote:

> Hullo Jan,
>
> On Nov 25, 11:50 am, Jan Martin  wrote:
>
> [snip]
>
> > If one knows the size of a single object, e.g. of a car, in a digital
> image,
> > one should be able to measure anything else in it. IS this true for panos
> > to?
>
> I don't think that is possible without having a stereo pair and some
> real world 3d coordinates of control objects in the image.
> The problem is that a normal digital image, and a derived pano are
> only 2D, and while you will be able to a measure relative sizes of
> objects on the 2D plane of the image, you don't have the info to know
> where the objects are in the 3rd dimension, hence could a small object
> close, or a large object further away.
>
> Cheers,
> Terry
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: Measure buildings from a panorama?

[Chris Erskine]

this is one thing photogrammetry is good for... as well as making the 3d
models.

you still need to tell it the size of something then you can work everything
else out.

i've been using image modeller (formally realviz now autodesk). it works
with normal photos of 360 pano's.

but as i said in another thread it could be a lot faster to do it. and maybe
something that could be built into hugin which could do a better job.

On Thu, Nov 25, 2010 at 11:50 AM, Jan Martin
wrote:

> Hi Terry,
>
> for sure it is interesting.
>
> I am looking more for a solution to do this in a industrial scale.
>
> My setup:
> I have a rig that takes all images for a pano at once.
> Then the panos are stitched using a never-changing template.
>
> If one knows the size of a single object, e.g. of a car, in a digital
> image, one should be able to measure anything else in it. IS this true for
> panos to?
>
> I wonder if one can calculate the distance from the rig to an object from
> the parallax error?
>
> Does anyone know software to measure the real world size of objects from
> images?
>
> Jan
>
>
>
>
>
>
> On Wed, Nov 24, 2010 at 5:33 PM, Tduell  wrote:
>
>> Hullo Jan,
>>
>> On Nov 25, 10:53 am, Jan Martin  wrote:
>> > Hi all,
>> >
>> > what options exist to measure the size of e.g. a building from a
>> panorama?
>>
>> Have you seen Bruno's tutorial on using Hugin to survey buildings?
>> You can find it here > en.shtml >
>>
>> Cheers,
>> Terry
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Hugin and other free panoramic software" group.
>> A list of frequently asked questions is available at:
>> http://wiki.panotools.org/Hugin_FAQ
>> To post to this group, send email to hugin-ptx@googlegroups.com
>> To unsubscribe from this group, send email to
>> hugin-ptx+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>>
>
>
>
> --
> http://www.DIY-streetview.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Re: open source close range photogrammetry

[Chris Erskine]

cheers, I hadn't seen this before.

On Thu, Nov 25, 2010 at 11:08 AM, Tduell  wrote:

> Hullo Chris,
>
> On Nov 25, 10:06 am, Chris Erskine  wrote:
> > Hi,
> >
> > I'm looking for a something to do close range photogrammetry. in at least
> a
> > semi-automated way.
>
> I suspect that this  <http://stereo.sourceforge.net/> isn't going to
> do what you really want, but may be useful in some respects.
> I would like to see this concept taken further with tools for adding
> control points similar to those in Hugin.
> I think a lot of what is needed to incorporate a stereo capability
> into Hugin is in the PTStereo source, which hasn't been released.
>
> Cheers,
> Terry
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] open source close range photogrammetry

[Chris Erskine]

Hi,

I'm looking for a something to do close range photogrammetry. in at least a
semi-automated way.

I have image modeller (formally realviz) thanks to an autodesk subscription.
but I'm finding this really hasn't moved much in years compared to the
software for stitching 360 panos (i must admit i use ptgui by i have been
following hugin for a few years now). now its seems like there a lot of
hugin that could transfer over to photogrammetry. esp the automated control
point detection. or a semi automated where after the camera views had been
calibrated you could pick control points in one view and it gets added to
the other views.

I guess it would mean changing from a single point in space to a real 3d
workspace. but it seems to me that a pano stitcher could be intergrated with
photogrammetry and they would both work really well together. and that would
also mean mosics would work really well too.

anyway I'm not a programmer and I'm sure this is quite a lot of work. so if
you know any other open source software out there that can do this I'd be
really interested.

it just seems like all the commerical software for this isn't really going
anywhere.

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Hugin PPA Packagers - Add libpano13-bin dependency?

[Chris]

Hi,

A big thanks to the Hugin PPA Packagers - I just used your services.
I've just got one suggestion - could you add in the libpano13-bin
dependency?
This is for the x86-64 version.

To avoid errors such as:

::~/$sudo apt-get install hugin
...
The following extra packages will be installed:
  hugin-data hugin-tools
The following packages will be upgraded:
  hugin hugin-data hugin-tools
3 upgraded, 0 newly installed, 0 to remove and 39 not upgraded.
Need to get 14.2MB of archives.
After this operation, 2,167kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://ppa.launchpad.net/hugin/hugin-builds/ubuntu/ lucid/main
hugin 2010.2.0-0ubuntu2~lucid [1,349kB]
Get:2 http://ppa.launchpad.net/hugin/hugin-builds/ubuntu/ lucid/main
hugin-tools 2010.2.0-0ubuntu2~lucid
[3,681kB]
Get:3 http://ppa.launchpad.net/hugin/hugin-builds/ubuntu/ lucid/main
hugin-data 2010.2.0-0ubuntu2~lucid [9,159kB]
...

::~/$ hugin
hugin: error while loading shared libraries: libpano13.so.2: cannot
open shared object file: No such file or directory

::~/$ sudo apt-get install libpano13-bin

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] how do I stop getting emails?

[Chris]

 

 

 

 

Chris Howe

58 Horn Hill, Whitwell, Herts, SG4 8AR

01438 871369 

 

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
<>

[hugin-ptx] Re: How Does Hugin Calculate EV (Eev)?

[Chris Parrish]

Ok, so perhaps I've found a Hugin bug. The EV's I posted earlier were
auto calculated by Hugin when I added my JPEGs to the project.  I just
selected them all now and did a reset in the camera tab (selecting
only to reset the EXIF values), and now they are all properly
(consistently) calculated.  When I get some free time, I'll see if I
can reproduce it.

My calculations now all match Hugin's with two exceptions:
  1.)  Hugin is definitely not making any corrections for ISO Speed.
  2.)  Hugin is using (or assuming) more accurate values for the
Shutter Speed.  Where EXIFTOOL rounds 0.3s, Hugin is using 1/3s.

Oh, and I did find where EXIF is calculating LV which it refers to as
EV with ISO Speed accounted for (see #1 above).  But it is pretty
imprecise as it seems to use rounded values for shutter speed (one
decimal place) and then rounds the final value too (one decimal
place).  Hugin's is much more accurate.

So my only questions are:
  * Is Hugin somehow getting EXIFTOOL to output more precise values
(like 0.33s vs 0.3) or is Hugin just making its own assumptions?
  * Should Hugin be calculating EV taking ISO speed into account?

-Chris

On Feb 1, 10:37 am, Chris Parrish 
wrote:
> Actually, it looks like Hugin is not compensating for ISO Speed. The
> values that it's using are more like:
>   ( 2*log($aperture) - log($et) ) / log(2)
>
> I'm not sure if that's a bug in Hugin or intentional.
>
> And I can't find any documentation that shows that EXIFTOOL calculates
> EV at all.  Does/can it?
>
> It also appears that Hugin is converting shutter speed values such as
> "1.3" to more precise values such as "1 + 1/3" (unless there's some
> way to get EXIFTOOL to output more precise values that I've never
> figured out).  Do you have any insight here?
>
> But where I'm really confused is that I have a project with different
> JPEG files -- all with the same exposure settings (each is the third
> shot of a bracketed set and the EXIF info shows each to have: ISO=400,
> Aperture=18.0, Shutter Speed=1.3).  But, for some reason, Hugin
> calculates different EV's for each:
>   Image 1: Eev7.96133843254863
>   Image 2: Eev8.22471080582863
>   Image 3: Eev8.01714501898585
>   Image 4: Eev7.92977368023845
>   Image 5: Eev7.92771999334261
>   Image 6: Eev7.91554178809828
>   Image 7: Eev7.9863593751747
>   Image 8: Eev7.94803346282545
>   Image 9: Eev7.87540508845236
>
> Even more strange, Hugin calculates the EV's consistently for the 1st
> and 2nd shots in the bracketed sets (all the 1st shots get exactly the
> same Eev as do all the 2nd shots).  It's just this 3rd set of image
> that have this weird variation.
>
> Is there some other weird factor that Hugin is using to calculate EV
> that I'm not accounting for?  Or is there a high-precision mode to use
> to get data via EXIFTOOL?
>
> -Chris
>
> On Feb 1, 2:11 am, "bruno.postle"  wrote:
>
> > On Feb 1, 6:28 am, Chris Parrish 
> > wrote:
>
> > > I am building a script that batch creates PTO and PTO.MK files for
> > > sets of pano images.  I do this based on templates of these files (I
> > > use a pano head allowing me to reuse the same script settings in these
> > > templates).
>
> > > The problem is that, while I can keep the lens and transform settings,
> > > I do need to change the Eev value to match the actual images' exposure
> > > values.  I can get all the data using EXIFTOOL but when I calculate
> > > the EV I don't get what Hugin is getting.
>
> > > Does anyone know Hugin's actual formula?
>
> > EV (light value) is fairly standard, Hugin should be doing it the same
> > as exiftool (and does as far as I know).
>
> > It's a log scale where a value of 0.0 is defined as f/1.0 at 1.0
> > second with ISO 100), this is how it is calculated:
>
> >     (2*log ($aperture) - log($et) - log($iso/100)) / log(2)
>
> > --
> > Bruno

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: How Does Hugin Calculate EV (Eev)?

[Chris Parrish]

Actually, it looks like Hugin is not compensating for ISO Speed. The
values that it's using are more like:
  ( 2*log($aperture) - log($et) ) / log(2)

I'm not sure if that's a bug in Hugin or intentional.

And I can't find any documentation that shows that EXIFTOOL calculates
EV at all.  Does/can it?

It also appears that Hugin is converting shutter speed values such as
"1.3" to more precise values such as "1 + 1/3" (unless there's some
way to get EXIFTOOL to output more precise values that I've never
figured out).  Do you have any insight here?

But where I'm really confused is that I have a project with different
JPEG files -- all with the same exposure settings (each is the third
shot of a bracketed set and the EXIF info shows each to have: ISO=400,
Aperture=18.0, Shutter Speed=1.3).  But, for some reason, Hugin
calculates different EV's for each:
  Image 1: Eev7.96133843254863
  Image 2: Eev8.22471080582863
  Image 3: Eev8.01714501898585
  Image 4: Eev7.92977368023845
  Image 5: Eev7.92771999334261
  Image 6: Eev7.91554178809828
  Image 7: Eev7.9863593751747
  Image 8: Eev7.94803346282545
  Image 9: Eev7.87540508845236

Even more strange, Hugin calculates the EV's consistently for the 1st
and 2nd shots in the bracketed sets (all the 1st shots get exactly the
same Eev as do all the 2nd shots).  It's just this 3rd set of image
that have this weird variation.

Is there some other weird factor that Hugin is using to calculate EV
that I'm not accounting for?  Or is there a high-precision mode to use
to get data via EXIFTOOL?

-Chris

On Feb 1, 2:11 am, "bruno.postle"  wrote:
> On Feb 1, 6:28 am, Chris Parrish 
> wrote:
>
> > I am building a script that batch creates PTO and PTO.MK files for
> > sets of pano images.  I do this based on templates of these files (I
> > use a pano head allowing me to reuse the same script settings in these
> > templates).
>
> > The problem is that, while I can keep the lens and transform settings,
> > I do need to change the Eev value to match the actual images' exposure
> > values.  I can get all the data using EXIFTOOL but when I calculate
> > the EV I don't get what Hugin is getting.
>
> > Does anyone know Hugin's actual formula?
>
> EV (light value) is fairly standard, Hugin should be doing it the same
> as exiftool (and does as far as I know).
>
> It's a log scale where a value of 0.0 is defined as f/1.0 at 1.0
> second with ISO 100), this is how it is calculated:
>
>     (2*log ($aperture) - log($et) - log($iso/100)) / log(2)
>
> --
> Bruno

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: parameters for the 10.5 nikkor on a Nikon camera?

[Chris Parrish]

Oops, forgot to post the two values:

These are with a Nikon D70...

RAW:
v133.377308103937 a-0.0140794442639724 b0.00394253004818905
c-0.0265682687033203

JPEG:
v132.345169793726 a-0.0158642392439734 b0.0085414764052365
c-0.0281563572962174

-Chris

On Jan 31, 11:37 pm, Chris Parrish
 wrote:
> In RAW or JPG mode?
>
> My D70 offers a few more pixels in each direction in RAW mode and this
> affects FOV a bit.
>
> -Chris
>
> On Jan 31, 8:40 pm, Jim Watters  wrote:
>
> > On 2010/01/31 4:30 PM, dmg wrote:> Hi Everybody,
>
> > > does anybody have the parameters FOV, a, b, and c for a 10.5 on a
> > > Nikon Camera? Either vertical or horizontal?
>
> > For D70s, focal length multiplier = 1.5278545
> > v=132.05625  a=-0.0084945092, b=-0.012022472, c=-0.010075328
>
> > --
> > Jim Wattershttp://photocreations.ca

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: parameters for the 10.5 nikkor on a Nikon camera?

[Chris Parrish]

In RAW or JPG mode?

My D70 offers a few more pixels in each direction in RAW mode and this
affects FOV a bit.

-Chris

On Jan 31, 8:40 pm, Jim Watters  wrote:
> On 2010/01/31 4:30 PM, dmg wrote:> Hi Everybody,
>
> > does anybody have the parameters FOV, a, b, and c for a 10.5 on a
> > Nikon Camera? Either vertical or horizontal?
>
> For D70s, focal length multiplier = 1.5278545
> v=132.05625  a=-0.0084945092, b=-0.012022472, c=-0.010075328
>
> --
> Jim Wattershttp://photocreations.ca

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] How Does Hugin Calculate EV (Eev)?

[Chris Parrish]

I am building a script that batch creates PTO and PTO.MK files for
sets of pano images.  I do this based on templates of these files (I
use a pano head allowing me to reuse the same script settings in these
templates).

The problem is that, while I can keep the lens and transform settings,
I do need to change the Eev value to match the actual images' exposure
values.  I can get all the data using EXIFTOOL but when I calculate
the EV I don't get what Hugin is getting.

Does anyone know Hugin's actual formula?

-Chris

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Windows Executables for Hugin's Panotools-Script

[Chris Parrish]

Thanks for the prompt reply Bruno!

Here's what I've figured out so far:

1.)  I'm ignoring the dmake test errors as you suggested.

2.)  I found that there's an issue with the scripts not liking my temp
directory (presumably since the path includes white space
characters).  The output I posted earlier was for a workaround (I
changed the environment variable to one without the spaces). I'm
assuming this is a bug in the scripts.

3.)  My ImageMagick seems to be working OK but I noticed that the
command being issued here is "composite" Does nona-mask work with two
separate files or does it composite the mask onto the input image? The
reason I'm wondering is that my input images are .HDR images and I
wonder if ImageMagick is choking on trying to add a mask to that
filetype.  In any case I was able to get rid of the messages by
changing my input to TIFF file.

4.)  The nona-isn't-in-your-path error still confuses me because the
hugin\bin directory is in my path and I can freely execute nona from a
command prompt.  Again, I was able to remove some errors by moving my
whole project to a path with no white spaces (not just my temp
directory).

I still don't have any real results yet -- just fewer errors.  I may
post more issues as/if I find them.

Thanks again for the help,
-Chris

On Jan 27, 11:55 am, Bruno Postle  wrote:
> On Wed 27-Jan-2010 at 07:27 -0800, Chris Parrish wrote:
>
>
>
> >and the test is generating the following errors:
>
> >Test Summary Report
> >---
> >t/101.makerule.t      (Wstat: 7424 Tests: 59 Failed: 29)
> >Failed 1/20 test programs. 29/265 subtests failed.
>
> Don't worry about this, it needs fixing or documenting but it isn't
> related to getting nona-mask working.
>
> >2.)  Not knowing if these errors were critical or not (I only need
> >nona-mask), I installed (dmake install). I then changed my pto.mk file
> >to include: NONA=C:\Perl\site\bin\nona-mask.bat (Yes I know we're not
> >dealing with windows exe files at this point.  For now I want to get
> >anything to work).  When I run this, however, I get the following
> >output:
>
> >composite: `%s': %s ra_ppm -g 1.0 "magick-GpCOF7gK" "magick-ZRMKxT5m"
> >@ utility.c/SystemCommand/1993.
> >composite: Delegate failed `ra_ppm -g 1.0 "%i" "%o"' @ delegate.c/
> >InvokeDelegate/1062.
> >composite: unable to open image `magick-LIzcqNhs': No such file or
> >directory @ blob.c/OpenBlob/2482.
>
> This is a problem with your ImageMagick installation, try some
> simple ImageMagick commands and see if they work:
>
>    convert.exe somepicture.jpg output.tif
>
> >'nona' is not recognized as an internal or external command,operable
> >program or batch file.
>
> This is because the nona.exe file isn't in your PATH, you need to
> modify the 'dos window' properties and add this to your PATH:
>
> "C:\Program Files\Hugin\bin"
>
> >C:\Program\ Files\Hugin\bin\enblend  -w -f500x250 -o Pano\ 1.png Pano\ 
> >1.tif Pano\ 10001.tif Pano\ 10002.tif Pano\ 10003.tif Pano\ 10004.tif 
> >Pano\ 10005.tif Pano\ 10006.tif Pano\ 10007.tif Pano\ 10008.tif
> >enblend: no input files specified
>
> Presumably if you fix the other errors this will go away.
>
> --
> Bruno

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Windows Executables for Hugin's Panotools-Script

[Chris Parrish]

Aaargh... Still having issues. Can someone make sense of these errors
I'm getting?

1.)  When making Panotools-Script-0.24 I am typing:
  perl makefile.pl
  dmake
  dmake test

and the test is generating the following errors:

...
t/034.angle.t ... ok
t/101.makerule.t  1/? d:\tmp\make75882.sh: command not found:
cp [1]
make: *** [Westward Ho!_out] Error 1

#   Failed test at t/101.makerule.t line 74.
d:\tmp\make65322.sh: command not found: cp [1]
make: *** [foo bar_out] Error 1

#   Failed test at t/101.makerule.t line 74.
d:\tmp\make66202.sh: command not found: cp [1]
make: *** [foo&bar_out] Error 1

#   Failed test at t/101.makerule.t line 74.
t/101.makerule.t  9/? d:\tmp\make51962.sh: command not found:
cp [1]
make: *** [foo{bar_out] Error 1

...More of the same Errors...

#   Failed test at t/101.makerule.t line 74.
cannot remove path when cwd is D:/tmp/TS6FP_P5fA for D:\tmp
\TS6FP_P5fA:  at C:/P
erl/lib/File/Temp.pm line 902
# Looks like you failed 29 tests of 59.
t/101.makerule.t  Dubious, test returned 29 (wstat 7424,
0x1d00)
Failed 29/59 subtests
t/102.platform.t  ok
t/103.platform.t  ok
t/104.metachars.t ... ok
t/105.vars.t  ok
t/106.photos.t .. ok

Test Summary Report
---
t/101.makerule.t  (Wstat: 7424 Tests: 59 Failed: 29)
  Failed tests:  2, 4, 8, 14-15, 18-20, 22-27, 29, 33, 38-39
42-44, 46-53
  Non-zero exit status: 29
Files=20, Tests=265,  6 wallclock secs ( 0.23 usr +  0.03 sys =  0.27
CPU)
Result: FAIL
Failed 1/20 test programs. 29/265 subtests failed.
dmake.exe:  Error code 255, while making 'test_dynamic'


2.)  Not knowing if these errors were critical or not (I only need
nona-mask), I installed (dmake install). I then changed my pto.mk file
to include: NONA=C:\Perl\site\bin\nona-mask.bat (Yes I know we're not
dealing with windows exe files at this point.  For now I want to get
anything to work).  When I run this, however, I get the following
output:

D:\Chris\Real Idaho\temp\Fox Run\Great Rm>"C:\Program Files\Hugin\bin
\make" -f project.pto.mk
C:\Perl\site\bin\nona-mask.bat   -r ldr -m TIFF_m -o Pano\ 1 -i 0 D:
\Chris\Real\ Idaho\temp\Fox\ Run\Great\ Rm\Pano\ 1.pto
Using mask DSC_0073_4_5HDRI_mask.tif
composite: `%s': %s ra_ppm -g 1.0 "magick-GpCOF7gK" "magick-ZRMKxT5m"
@ utility.c/SystemCommand/1993.
composite: Delegate failed `ra_ppm -g 1.0 "%i" "%o"' @ delegate.c/
InvokeDelegate/1062.
composite: unable to open image `magick-LIzcqNhs': No such file or
directory @ blob.c/OpenBlob/2482.
composite: unable to open module file `C:\Program Files
\ImageMagick-6.5.9-Q16\modules\coders\IM_MOD_RL_RAD_.dll': No such
file or directory @ module.c/GetMagick
ModulePath/669.
composite: unable to open file `magick-LIzcqNhs': No such file or
directory @ constitute.c/ReadImage/571.
composite: missing an image filename `\tmp\TtNY8S3xLu\0.tif' @
composite.c/CompositeImageCommand/1610.
'nona' is not recognized as an internal or external command,operable
program or batch file.

... more of the same error (1 for each image file)...

C:\Program\ Files\Hugin\bin\enblend  -w -f500x250 -o Pano\ 1.png Pano\
1.tif
 Pano\ 10001.tif Pano\ 10002.tif Pano\ 10003.tif Pano\ 10004.tif Pano\
10005.tif
 Pano\ 10006.tif Pano\ 10007.tif Pano\ 10008.tif
enblend: no input files specified
C:\Program Files\Hugin\bin\make: *** [Pano 1.png] Error 1


Can someone shed some light here?  I don't know where to start.

On Jan 26, 10:19 pm, Chris Parrish
 wrote:
> Does anyone have any win32 executables made of the latest panotools-
> script (v0.24)?
>
> I've been killing myself all afternoon/evening trying to figure out
> enough to get these to compile.  (And to save anyone the obvious, yes
> I have seen:http://wiki.panotools.org/Install_Panotools-Script_on_Windows).
>
> Of course I'd welcome a foolproof list of steps to follow, too.
>
> Thanks,
> Chris

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Windows Executables for Hugin's Panotools-Script

[Chris Parrish]

Nevermind.

I should have known that soon after posting I'd get a breakthrough.
Should've posted earlier ;-)

On Jan 26, 10:19 pm, Chris Parrish
 wrote:
> Does anyone have any win32 executables made of the latest panotools-
> script (v0.24)?
>
> I've been killing myself all afternoon/evening trying to figure out
> enough to get these to compile.  (And to save anyone the obvious, yes
> I have seen:http://wiki.panotools.org/Install_Panotools-Script_on_Windows).
>
> Of course I'd welcome a foolproof list of steps to follow, too.
>
> Thanks,
> Chris

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Windows Executables for Hugin's Panotools-Script

[Chris Parrish]

Does anyone have any win32 executables made of the latest panotools-
script (v0.24)?

I've been killing myself all afternoon/evening trying to figure out
enough to get these to compile.  (And to save anyone the obvious, yes
I have seen: http://wiki.panotools.org/Install_Panotools-Script_on_Windows).

Of course I'd welcome a foolproof list of steps to follow, too.

Thanks,
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Using External Masks with Nona/Enblend/Enfuse

[Chris Parrish]

Thanks for the reply. I have a couple of questions though:
  * Do I need enblend-mask and enfuse-mask or will nona-mask do the
trick?  In other words, if I mask the original images, won't nona spit
out a masked tranformed image for enblend to work with?  Likewise with
enfuse?
  * I'd already found your "Panorama scripting in a nutshell" link and
it looks like everything I need is in there.  But while the document
says it's possible to do, it doesn't exactly say how.  Is there a
tutorial on this sort of thing available somewhere?

-Chris

On Jan 26, 4:45 pm, Bruno Postle  wrote:
> On Tue 26-Jan-2010 at 09:21 -0800, Chris Parrish wrote:
>
>
>
> >Essentially, I am looking for a workflow similar to the old nona-mask
> >(which seems now defunct).  But it looks like the latest versions of
> >nona/enblend/enfuse seem to have mask capabilities built-in (I just
> >have no idea how they work).
>
> nona-mask, enblend-mask and enfuse-mask are still usable, but since
> they create temporary files and manipulate the masks with
> ImageMagick they are not ideal:
>
> http://search.cpan.org/dist/Panotools-Script/bin/nona-maskhttp://search.cpan.org/dist/Panotools-Script/bin/enblend-maskhttp://search.cpan.org/dist/Panotools-Script/bin/enfuse-mask
>
> It is also not currently possible to substitute nona with nona-mask
> using the Hugin GUI.  Though easy enough if using command-line
> stitching:
>
> http://wiki.panotools.org/Panorama_scripting_in_a_nutshell#make_options
>
> Basically there isn't a simple solution for masking photos before
> stitching, we have discussed replacing the Hugin Crop tab with a
> full featured vector mask editor, but this hasn't happened (yet).
>
> --
> Bruno

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Using External Masks with Nona/Enblend/Enfuse

[Chris Parrish]

What is the current way to provide nona with external mask images?

I am NOT looking to edit my input images and add an alpha mask channel
everytime as my masks are reused with every pano (they mask out places
where the pano head is in the shot).  Instead I want to have pano
image files (JPEG or HDR) and asociated mask files (TIFF or PNG) and
tell nona/enblend/enfuse to use them in tandem.

Essentially, I am looking for a workflow similar to the old nona-mask
(which seems now defunct).  But it looks like the latest versions of
nona/enblend/enfuse seem to have mask capabilities built-in (I just
have no idea how they work).

Thanks,
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx