Re: [hugin-ptx] Hugin multipe pto generator script

[Gnome Nomad]

Why not just make a subfolder for each pano, move the corresponding images
into each subfolder, then run whatever PTO generator you like on each
subfolder (I use Linux and the right-click tool it already includes)?

Seems easier to me than all the file renaming need for this script.
Especially if you have a lot of images in each pano.
On Nov 5, 2015 21:49, "Oriol Matavacas" 
wrote:

> Hi All
>
> I created a little script in order to generate the Hugin project file
> automatically for multiple pano images based on the wiki pages:
> http://wiki.panotools.org/Panorama_scripting_in_a_nutshell
>
> The script will create the ".pto" files for all pano images based on the
> file names.
>
> Maybe is usefull for somebody...
>
> *Assumptions\requisites:*
> *Operating System:* MacOS
> *Hugin:* 2014 (I didn't tried with a different version)
> The script should be on the same folder than image files.
> All the files that compon the same panoramic image, should end with the
> same pano number "Pano1", "Pano2", etc..
>
> *Usage:*
> 1) Open script with a text editor and adapt this 2 lines with the number
> of panos (4 in this example) and the format of the images  (tif, tiff, jpg,
> jpeg, etc...)(jpg in this example)
> export PANO_NUM_MAX=4
> export FORMAT=jpg
> 2) Open terminal in MacOS and run:
> ./Hugin_pto_Generator.sh
>
> *Input example:*
> DSC001_Pano1.jpg
> DSC002_Pano1.jpg
> DSC003_Pano1.jpg
> DSC004_Pano1.jpg
>
> DSC030_Pano2.jpg
> DSC031_Pano2.jpg
> DSC032_Pano2.jpg
>
> DSC067_Pano3.jpg
> DSC068_Pano3.jpg
> DSC069_Pano3.jpg
> DSC070_Pano3.jpg
> DSC071_Pano3.jpg
>
> DSC089_Pano4.jpg
> DSC090_Pano4.jpg
> DSC091_Pano4.jpg
> DSC092_Pano4.jpg
> DSC093_Pano4.jpg
> DSC094_Pano4.jpg
>
> 
>
> *Output example:*
> DSC001_Pano1_DSC004_Pano1.pto
> DSC001_Pano1_DSC004_Pano1.pto.log
>
> DSC030_Pano30_DSC032_Pano2.pto
> DSC030_Pano30_DSC032_Pano2.pto.log
>
> DSC067_Pano3_DSC071_Pano3.pto
> DSC067_Pano3_DSC071_Pano3.pto.log
>
> DSC089_Pano4_DSC094_Pano4..pto
> DSC089_Pano4_DSC094_Pano4..pto.log
>
>
> Please find below the script. Copy the text, save it as a
> "Hugin_pto_Generator.sh" on the same folder of images, and grant it
> execution permissions (chmod +x :Hugin_pto_Generator.sh).
>
> --
> #!/bin/bash
>
> #Setting Hugin Path"
> export HUGIN_PATH="/Applications/Hugin/Hugin.app/Contents/MacOS/"
>
> echo "*** Number of PANOS $PANO_NUM_MAX *** "
> export PANO_NUM_MAX=4
> export FORMAT=jpg
>
> for PANO_NUM in $(seq 1 $PANO_NUM_MAX)
> do
>
> echo "*** Setting PANO $PANO_NUM of $PANO_NUM_MAX *** "
> #Setting File Names"
> export PANO_FILES="$(ls *Pano$PANO_NUM.$FORMAT)"
> export PANO_FILES_TMP1="$(ls -1 *Pano$PANO_NUM.$FORMAT | head -n1 |
> cut -d . -f 1)"
> export PANO_FILES_TMP2="$(ls -1 *Pano$PANO_NUM.$FORMAT | tail -n1 |
> cut -d . -f 1)"
> export PANO_NAME=$(echo "$PANO_FILES_TMP1"_"$PANO_FILES_TMP2".pto)
> echo "*** Merging $PANO_FILES *** " >> $PANO_NAME.log
> echo "*** As a name of $PANO_NAME *** " | tee >> $PANO_NAME.log
>
> echo "*** Creating pto file *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/pto_gen -o $PANO_NAME $PANO_FILES >> $PANO_NAME.log
>
> echo "*** Finding control points *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/icpfind -o $PANO_NAME $PANO_NAME >> $PANO_NAME.log
>
> echo "*** Remove control points in clouds *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/celeste_standalone -t 0.5  -o $PANO_NAME -i $PANO_NAME >>
> $PANO_NAME.log
>
> echo "*** Statistical cleaning of control points *** " | tee >>
> $PANO_NAME.log
> $HUGIN_PATH/cpclean -o $PANO_NAME $PANO_NAME >> $PANO_NAME.log
>
> echo "*** Searching for vertical lines *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/linefind -o $PANO_NAME $PANO_NAME  >> $PANO_NAME.log
>
> echo "*** Checking all images are connected *** " | tee >>
> $PANO_NAME.log
> $HUGIN_PATH/checkpto $PANO_NAME >> $PANO_NAME.log
>
> echo "*** Optimise project *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/autooptimiser -a -m -l -s -o $PANO_NAME $PANO_NAME >>
> $PANO_NAME.log
>
> echo "*** Setting output options *** " | tee >> $PANO_NAME.log
> $HUGIN_PATH/pano_modify --canvas=70%% --crop=AUTO -o $PANO_NAME
> $PANO_NAME >> $PANO_NAME.log
>
> done
>
>
>
> --
> 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/60610ff1-e8fb-4ec8-85e8-3b62a06ec3cb%40googlegroups.com
> 

Re: [hugin-ptx] Shooting and stitching to make Giclee prints

[Markku Kolkka]

6.11.2015, 1:52, Terry Duell kirjoitti:
>
>>> OK, thanks. I'll see if I can find some lens tests to compare.
> 
> ...to compare with the performance of my 150-450.

Ephotozine has tested both lenses, but on different bodies (K-5 IIs vs.
K-3) so the measurements aren't necessarily directly comparable.
https://www.ephotozine.com/article/pentax-hd-pentax-d-fa-150-450mm-f-4-5-5-6-ed-dc-aw-review-27359#Performance
https://www.ephotozine.com/article/pentax-d-fa-100mm-f-2-8-macro-wr-lens-review-24103#Performance
-- 
Markku Kolkka
markku.kol...@iki.fi

-- 
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/563C9D09.4080604%40iki.fi.
For more options, visit https://groups.google.com/d/optout.

Fwd: [hugin-ptx] Shooting and stitching to make Giclee prints

[dgjohnston]

I also use DxO. And hugin of course. The nice thing about DxO is that 
correction modules are available for most cameras and lens combinations. It 
corrects for distortion, vignetting etc. Then hugin can do its magic without 
having to also correct all that stuff.


Sent from my Samsung device

 Original message 
From: Bill Brody  
Date: 2015-11-06  9:27 AM  (GMT-06:00) 
To: hugin and other free panoramic software  
Subject: [hugin-ptx] Shooting and stitching to make Giclee prints 

I suggest a prime lens rather than any kind of zoom. They are much sharper. 
Many lens are sharpest at f8. Check the literature for your lens. 
Assuming a size of six feet for the largest dimension of the canvas, then at 
300 ppi you will need your output to be 300 x 12 X 6 or 21,600 pixels along 
that side. This comes out to 466,560,000 or about 450 megapixels. You do not 
want to use the entire frame of each source image since the peripheral pixels 
are always less sharp than the ones closer to the center. Even though I use the 
free hugin for stitching, I use a commercial product,  DXO,  for preprocessing 
my images. 

One way to ensure that your images are all taken with the lens pointing 
directly at the portion of the canvas you want is to mark that point with 
masking tape or using two crossed segments of mason twine. Both artwork and 
camera should be absolutely level, something you can accomplish ith a 
carpenter's level. Attach a laser pointer alng one leg of a large 45 degree 
right triangle. Place the other leg of triangle at the intersection point and 
swing it back and forth to see if the laser points at the center of the lens. 
If it does with the triangle oriented along the two perpendicular lines define 
by the mason twin, then your camera is in exactly the right spot. The laser 
pointer method is from watching James Barker, a professional photographer, take 
professional medium format slides. You will have probably do better if you hire 
him to do the photography for you. 

-- 
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/b1615f67-a327-4b37-a325-db8b2d3e382c%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/kc9teow92ebs9o73y88x7nd7.1446837350493%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Alignment of multi-row images

[Mike Cowlishaw]

>
>
> Many thanks for that.  Making progress :-).   My script generates the 
> correct commands, I think:
>

  pto_gen -o project.pto p*.jpg
  pto_var "--set=y=(i%6)*92.9654310-232.413578,p=0-(floor(i/6)*88.1947662)" 
--output=project.pto project.pto
  cpfind --output=project.pto --prealigned project.pto
  geocpset --output=project.pto project.pto


but the cpfind command gives the following errors (varies according to the 
> run):
>
 

i0 : Analyzing image...

i1 : Analyzing image...

i2 : Analyzing image...

i3 : Analyzing image...

i4 : Analyzing image...

i5 : Analyzing image...

i6 : Analyzing image...

i7 : Analyzing image...

An error happened while loading image : caught exception: bad allocation

i8 : Analyzing image...

An error happened while loading image : caught exception: bad allocation

i9 : Analyzing image...

An error happened while loading image : caught exception: bad allocation

i10 : Analyzing image...

An error happened while loading image : caught exception: bad allocation


[more of the same deleted]

The geocpset command seems to work, but when I then open the .pto file in 
Hugin there are severe stitching errors -- presumably only the geometrical 
control points are being used. 
 
This is on Windows 64 with 16GB of RAM (free RAM typically 10-12GB).  Any 
ideas?

Mike

-- 
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/53d1995c-f51b-471f-a087-6bc2eba2dcfb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Alignment of multi-row images

[Mike Cowlishaw]

[Last post had wrong command copy .. retry...]


Many thanks for that.  Making progress :-).   My script generates the 
correct commands, I think:

  pto_gen -o project.pto p*.jpg
  pto_var 
"--set=y=(floor(i/6)*13.5719189)-20.3578783,p=25.5922968-(i%6)*10.2369187" 
--output=project.pto project.pto
  cpfind --output=project.pto --prealigned project.pto
  geocpset --output=project.pto project.pto


but the cpfind command gives the following errors (varies according to the 
run):
 
  
  i0 : Analyzing image...
  i1 : Analyzing image...
  i2 : Analyzing image...
  i3 : Analyzing image...
  i4 : Analyzing image...
  i5 : Analyzing image...
  i6 : Analyzing image...
  i7 : Analyzing image...
  An error happened while loading image : caught exception: bad allocation
  i8 : Analyzing image...
  An error happened while loading image : caught exception: bad allocation
  i9 : Analyzing image...
  An error happened while loading image : caught exception: bad allocation
  i10 : Analyzing image...
  An error happened while loading image : caught exception: bad allocation

  [more of the same deleted]

The geocpset command seems to work, but when I then open the .pto file in 
Hugin there are severe stitching errors -- 

presumably only the geometrical control points are being used. 
 
This is on Windows 64 with 16GB of RAM (free RAM typically 10-12GB).  Any 
ideas?

Mike

-- 
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/bff7d13c-1e19-4cb8-9e9d-db0a10da9a45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Shooting and stitching to make Giclee prints

[Bill Brody]

I suggest a prime lens rather than any kind of zoom. They are much sharper. 
Many lens are sharpest at f8. Check the literature for your lens. 
Assuming a size of six feet for the largest dimension of the canvas, then at 
300 ppi you will need your output to be 300 x 12 X 6 or 21,600 pixels along 
that side. This comes out to 466,560,000 or about 450 megapixels. You do not 
want to use the entire frame of each source image since the peripheral pixels 
are always less sharp than the ones closer to the center. Even though I use the 
free hugin for stitching, I use a commercial product,  DXO,  for preprocessing 
my images. 

One way to ensure that your images are all taken with the lens pointing 
directly at the portion of the canvas you want is to mark that point with 
masking tape or using two crossed segments of mason twine. Both artwork and 
camera should be absolutely level, something you can accomplish ith a 
carpenter's level. Attach a laser pointer alng one leg of a large 45 degree 
right triangle. Place the other leg of triangle at the intersection point and 
swing it back and forth to see if the laser points at the center of the lens. 
If it does with the triangle oriented along the two perpendicular lines define 
by the mason twin, then your camera is in exactly the right spot. The laser 
pointer method is from watching James Barker, a professional photographer, take 
professional medium format slides. You will have probably do better if you hire 
him to do the photography for you. 

-- 
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/b1615f67-a327-4b37-a325-db8b2d3e382c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Shooting and stitching to make Giclee prints

[Terry Duell]

Hello Bill,

On Sat, 07 Nov 2015 02:27:33 +1100, Bill Brody  wrote:

I suggest a prime lens rather than any kind of zoom. They are much  
sharper. Many lens are sharpest at f8. Check the literature for your  
lens.


My choice of the Pentax 150-450 is because it's what I have.
The reports for this lens are good, particularly at about 300 and f8.
We aren't going to get another lens just for this experiment, but that  
maybe what is done later if it all works out OK.


Even though I use the free hugin for stitching, I use a commercial  
product,  DXO,  for preprocessing my images.


It'll be Hugin...from what I can find DxO is not available for Linux.

Thanks for your advice.

Cheers,
--
Regards,
Terry Duell

--
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/op.x7o9e2fcrs0ygh%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Alignment of multi-row images

[Terry Duell]

Hello Mike,

On Sat, 07 Nov 2015 02:24:32 +1100, Mike Cowlishaw   
wrote:



[Last post had wrong command copy .. retry...]


Many thanks for that.  Making progress :-).   My script generates the
correct commands, I think:

  pto_gen -o project.pto p*.jpg
  pto_var
"--set=y=(floor(i/6)*13.5719189)-20.3578783,p=25.5922968-(i%6)*10.2369187"
--output=project.pto project.pto
  cpfind --output=project.pto --prealigned project.pto
  geocpset --output=project.pto project.pto


but the cpfind command gives the following errors (varies according to  
the run):


One thing I do when first writing scripts like this is to have each step  
generate a new .pto file, then when it's done you can load each one in  
turn into Hugin and see if it has done what you want.


Cheers,
--
Regards,
Terry Duell

--
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/op.x7o9m2bers0ygh%40localhost.
For more options, visit https://groups.google.com/d/optout.