[hugin-ptx] Offensive behaviour (was: BigTIFF)

[Greg 'groggy' Lehey]

This is mainly addressed to Thomas Modes, but since it's not the first
time I've seen him behave like this, I think it's time to come out in
the open.

On Tuesday, 18 September 2018 at 10:00:34 -0700, T. Modes wrote:
> Am Dienstag, 18. September 2018 05:46:34 UTC+2 schrieb Groogle:
>>
>> There is one at
>> https://wiki.panotools.org/Panorama_scripting_in_a_nutshell, but it's
>> horribly out of date.  I've been meaning to update it, but I've always
>> found something more rewarding to do.  In particular, it makes
>> reference to obsolete programs.
>
> Sorry, but is wrong. The main part with the description is up to
> date.  The only one obsolete program in the main part is
> autopano-sift-c - but this is only shown as alternative; the
> mentioned main program cpfind is still part of Hugin.

Sorry, but is wrong.  I spent quite a bit of time going through this
page a while back, and it contains numerous issues.  Apart from
autopano-sift-c, in the main text there are also references to
autopano-sift, match-n-shift, ptoinfo, ptscluster, ptoclean,
ptovariable and panostart, as well as to the pano.mk file that no
longer exists.

In the "Full list of command-line [sic] tools", only 5 of the first 10
tools still exist.  I also seem to recall that some of the options are
also no longer relevant, though I could be wrong here.

This list also contains the line:

autopano - Keypoint matcher, part of autopano-sift-c and not to be confused 
with autopano

Well, I'm confused.  Beginners certainly will be.

Maybe you have a different definition, but for me this is very out of
date.

I had intended to bring this page up to date.  Based on this attack,
you will understand that I am now disinclined to do so.  It will
remain out of date until somebody else who recognizes the problem also
finds time and inclination to do something about it.

> The next time be more precises what you are referring instead of
> make such general and diffuse statements.

Next time, before answering, check your facts.  You come across as
offensive and inaccurate, not for the first time.  This attitude also
greatly reduces people's willingness to cooperate in the project.  A
few years back a whole lot of people were involved in the project.
Now you seem to be the only one.  It would be easy to get the
impression that your attitude has something to do with this.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

-- 
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/20180919040003.GU76566%40eureka.lemis.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

[hugin-ptx] Re: BigTIFF

[Battle]

Thomas,
Thanks for your replies so far.  I'm looking at the user defined output 
sequences, and am not quite sure where to put the command line and 
parameters for big tiff.  
from user defined menu the executor file for normal smart blend reads as 
follows:  

[Step0]
Description=Remapping images
Type=remap
Arguments=-r ldr -m TIFF_m


[Step1]
Description=Blending with smartblend
Type=merge
Input=all
Program=smartblend
Result=%prefix%.tif
Arguments=-o %result% %input%
WrapArgument=


Presumably they go in the Arguments line...

In [Step0] it doesn't look like nona is specifically called as the 
remapper.  But presumably I would add --bigtiff as follows

Arguments=--bigtiff -r ldr -m TIFF_m

And for [Step1] similarly 

Arguments=--bigtiff -o %result% %input%

or if using normal enblend u.d.o. script --parameter=export-bigtiff

Am I on the right track here?
Thanks,
Battle
On Monday, September 17, 2018 at 2:29:40 PM UTC-4, T. Modes wrote:
>
>
>
> Am Montag, 17. September 2018 12:53:11 UTC+2 schrieb Battle:
>>
>> I working on some large panoramas, and have run into the file size limit 
>> of TIF > 4GB.  
>> I see from 2018.0 that BigTif is possible.
>> The release announcement says
>>
>> * Nona, verdandi and hugin_stacker can now write BigTIFF images (for 
>> files >4 GB). The output of BigTIFF has to manually activated on the 
>> command line. It is not set automatically. (For a complete panorama in 
>> BigTIFF you will probably also need enblend/enfuse from repository. The 
>> last released version of enblend does not yet support writing BigTIFF 
>> files.)
>>
>> I need a bit of help figuring out how to make this happen.  I'm using OS 
>> X 2018.0.0, but have a Windows box available if necessary.  
>>
>
> For nona, verdandi and hugin_stacker add the switch --bigtiff to the 
> command line. The development versions from enblend/enfuse require 
> --parameter=export-bigtiff
> The easiest way to use this would be to create a user defined output 
> sequence.
>
> Thomas
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/141cc7af-d654-45aa-93a6-c442c97eb763%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: BigTIFF

[Battle]

So if I use the builtin blender instead of enblend  I can use the —big tiff 
switch and that will output BigTIFF?

-- 
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/a93c047f-fcfa-4381-9c04-387531020d49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Dimension position parameters TRx Try TRz

[dgjohnston]

Sorry, I’ve exhausted my knowledge on how hugin might be calculating and using 
these numbers; it doesn’t seem to match the theory written up in the links I 
put up.

Would any of the developers / support guys have any thoughts on this for Kai?

Don

> On Sep 18, 2018, at 11:04 AM, Kai M  wrote:
> 
> Hey Donald,
> 
> i tried everything to calculate. But i cant figure out the parameters. The 
> Exif Data is readable. The Distance was 40cm from the object. Do you think 
> its possible to calculate it in Pixels?
> 
> Best Regards
> 
> Kai
> 
> -- 
> 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/b754d685-6c37-4c7b-a606-8b982d51abaa%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/12B3E566-F84D-4A2C-B673-667DE55B7116%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Dimension position parameters TRx Try TRz

[Kai M]

Hey Donald,

i tried everything to calculate. But i cant figure out the parameters. The 
Exif Data is readable. The Distance was 40cm from the object. Do you think 
its possible to calculate it in Pixels?

Best Regards

Kai

-- 
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/b754d685-6c37-4c7b-a606-8b982d51abaa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: BigTIFF

[T. Modes]

@Greg

Am Dienstag, 18. September 2018 05:46:34 UTC+2 schrieb Groogle:
>
> There is one at 
> https://wiki.panotools.org/Panorama_scripting_in_a_nutshell, but it's 
> horribly out of date.  I've been meaning to update it, but I've always 
> found something more rewarding to do.  In particular, it makes 
> reference to obsolete programs. 
>

Sorry, but is wrong. The main part with the description is up to date. The 
only one obsolete program in the main part is autopano-sift-c - but this is 
only shown as alternative; the mentioned main program cpfind is still part 
of Hugin. All other program are still there. Maybe in the list at the end 
there are some obsolete programs, but not in the main part. 

The next time be more precises what you are referring instead of make such 
general and diffuse statements.

Thomas

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9bb4c5a0-5803-42e4-ba56-8c44540eab14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: BigTIFF

[T. Modes]

Am Dienstag, 18. September 2018 01:30:18 UTC+2 schrieb Battle:
>
> HI Thomas,
> I hate to be a kludge, but I'm not finding any development versions of 
> Enblend.  Maybe I don't know where to look.  Looks like the last version at 
> source forge is 4.2 in 2016.  
>
I know of no binary development version of enblend. You need to compile 
enblend for yourself or using the internal blender.

I see that in regular Hugin Stitcher tab I can add command line options for 
> enabled, but I don't see a way to do that for nona.  So that means using 
> terminal I suppose.  Is there a tutorial on command line?  
>
No need to use the terminal. As I already wrote an user defined output 
sequence would be sufficient and can be simply called from the GUI.

Thomas



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cccfbdfb-d20a-4d15-8047-21f9523abd63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.