Re: [hugin-ptx] Re: HDR documentation?

[David Haberthür]

On 03.12.2009, at 20:24, Nicolas Pelletier wrote:
> Thanks David, that's the one. I never seem to remember that name. Not as 
> catchy as photomatix :P


The new version (for linux only at the moment) will be called Luminance [1], so 
that should be easier to remember :)
Habi/David

[1] http://www.flickr.com/groups/qtpfsgui/discuss/72157622927318422/

-- 
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] Automating creation of HDR pano

[hdrpano]

Thanks for the replies!  It would be nice to be able to do everything on the
command line, including finding control points.  But for now, I'm choosing
control points by hand and writing out a PTStitcher file, replacing the
filenames to stitch each exposure.  For example, to create 5 panos for 5
exposures:

nona -r ldr -m TIFF_m -o exp1 PTStitcher1.txt
enblend -w -f8000x4000 -o exp1.tif exp1.tif exp10001.tif exp10002.tif
...
nona -r ldr -m TIFF_m -o exp5 PTStitcher5.txt
enblend -w -f8000x4000 -o exp5.tif exp5.tif exp50001.tif exp50002.tif

This works.  Then I create another PTStitcher to merge the 5 panos into hdr:

nona -r hdr -m EXR_m -o PTStitcher6.txt
hugin_hdrmerge -m avg -c -o pano.exr pano_.exr pano_0001.exr
pano_0002.exr pano_0003.exr pano_0004.exr

This doesn't work.  I'm not sure what's wrong yet but the pano.exr doesn't
seem to be hdr.  It looks like a very bright and washed out ldr.  Will
investigate more tomorrow.

Can all (or any) of the above be done with pfstools?  How does that compare
with hugin?


Bruno Postle-4 wrote:
> 
> On Dec 3, 12:58 pm, Nicolas Pelletier 
> wrote:
>> Following the original posters request, is there a way (i.e. command line
>> tool) to add the crop to the pto automatically? I'd guess that the values
>> are consistent from one picture to another with the same fisheye...
> 
> You can set any value in a project file with Panotools::Script,
> something like this (untested):
> 
>   #!/usr/bin/perl
>   use Panotools::Script;
>   my $pto = new Panotools::Script;
>   $pto->Read ($ARGV[0]);
>   $_->{S} = '-459,2459,-57,2861' for @{$pto->Image};
>   $pto->Write ($ARGV[0]);
> 
>> On Thu, Dec 3, 2009 at 7:40 AM, bruno.postle
>> wrote:
>>
>> > On Dec 3, 9:42 am, Oskar Sander  wrote:
>> > > How does hugin handle all this black void in the image, is this
>> ignored in
>> > > blend & fusing?
>>
>> > Only if you are lucky with seam placement, for circular fisheye photos
>> > you really need to mask out the black areas using the Hugin Crop tab.
> 
> -- 
> 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
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Automating-creation-of-HDR-pano-tp26621718p26635802.html
Sent from the hugin ptx mailing list archive at Nabble.com.

-- 
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] Announce: Enblend/Enfuse version 4.0 - Release Candidate 3

[cspiel]

Hello Everybody!

Today we announce the third release
candidate (RC3) for Enblend/Enfuse version 4.0.
We have put a tar-ball of it at

http://sourceforge.net/projects/enblend/files/

For convenience, we also compiled RC3 binary
archives for the operating systems
* Windows (Thomas Modes) and
* MacOSX (Ingemar Bergmark) with tailored
  versions for
  - 10.4 "Tiger"
  - 10.5 "Leopard"
  - 10.6 "Snow Leopard"

The source archive file on SourceForge is
derived from revision 087a69837701 in the
Mercurial repository.


/Chris
 (Enblend/Enfuse 4.0 Release Manager)

-- 
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] Automating creation of HDR pano

[hdrpano]

Thanks!  Makes sense...


Oskar Sander wrote:
> 
> Actually if you have a 2/3 format and circular fisheye that perfectly
> fills
> the format, the short side FOV is 180deg  and the longside theoretical FOV
> is then 3*180/2=270.  So your figure there sounds perfectly all right
> 
> 2009/12/3 Oskar Sander 
> 
>> Isn't the circular fisheye projecting a circle on the sensor with the
>> rest
>> of the sensore rectangle black?   The HFOV is the sensor long-side field
>> of
>> view, so it could be correct if you would imagine the lens would be
>> projecting outside the circle too.
>>
>> How does hugin handle all this black void in the image, is this ignored
>> in
>> blend & fusing?
>>
>> 2009/12/3 hdrpano 
>>
>>
>>> Focal length: 8 mm
>>> Focal length multiplier: 1
>>> HFOV (v): 257.89
>>>
>>> I enter the first two and hugin fills in the HFOV.  Shouldn't that be
>>> closer
>>> to 180?
>>>
>>>
>> --
>> /O
>>
> 
> 
> 
> -- 
> /O
> 
> -- 
> 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
> 

-- 
View this message in context: 
http://old.nabble.com/Automating-creation-of-HDR-pano-tp26621718p26635794.html
Sent from the hugin ptx mailing list archive at Nabble.com.

-- 
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: Command lines to make a panorama

[Bob]

How about using PTStitcher to make a panorama? (Supposed I need to
mosaic two images leftImage.jpg and rightImage.jpg)
What's the command lines step by step?

-- 
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] Hugin and "fit"

[James Legg]

On Thu, 2009-12-03 at 20:16 -0500, Brian Sullivan wrote:
> I am using Hugin Version 2009.2.0.4461 on Vista to process shots taken
> with a Peleng fisheye on a Nikon D50 using Nodal Ninja 2 jig.
> 
> I am getting pretty good results using standard settings and auto
> alignment with Auto-SIFT-C. Sometimes after the alignment I get the
> bad fit indication, sometimes good fit (with different picture sets).
> The resultant stitching, equirectangular tiff and QTVR panorama though
> seem to be OK regardless of the align bad/good information.

The warning is based on the average distance of the control point pairs
in the stitched panorama.

The error is measured in output pixels, so if you scale the panorama
down, it will have a lower error. It is only calculated when you
reoptimize though.

> Is there something I should be expecting in the output based on the
> align warning that I am missing? From where I am sitting the
> information seems not very useful.

Zoom in to one of your panos and look at long lines. See if you can spot
any kinks.

If you have a lot of control points with a high error on sharp lines you
will probably notice misalignment in the stitch, so this warning is
useful sometimes. If you have only control points with a high error in
sky, water, or something else where the seem won't be noticeable, you
probably won't see any error, even though Hugin may report a bad fit.

If you get 'Very bad fit' you should do something to fix it, but any of
the other states will do if your Panorama doesn't have many long lines.

-James

-- 
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 and "fit"

[Brian Sullivan]

I am using Hugin Version 2009.2.0.4461 on Vista to process shots taken
with a Peleng fisheye on a Nikon D50 using Nodal Ninja 2 jig.

I am getting pretty good results using standard settings and auto
alignment with Auto-SIFT-C. Sometimes after the alignment I get the
bad fit indication, sometimes good fit (with different picture sets).
The resultant stitching, equirectangular tiff and QTVR panorama though
seem to be OK regardless of the align bad/good information.

Is there something I should be expecting in the output based on the
align warning that I am missing? From where I am sitting the
information seems not very useful.

-- 
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: Command line tool to add Exposure info to pto

[Nicolas Pelletier]

Thanks, I'll look into that!

nick

On Thu, Dec 3, 2009 at 3:58 PM, Bruno Postle  wrote:

> On Thu 03-Dec-2009 at 14:23 -0500, Nicolas Pelletier wrote:
> >In order to spend less time doing tedious tasks, I'm trying to have 60-80%
> >of the process done automatically.
> >
> >I have a python script that takes all images in a folder, run panomatic,
> >then run nona. I want to add cpclean, change some optimization values
> along
> >with adding the exposure since I run mostly hdr. Then I'd run a first
> medium
> >rez output. Then I'd only have to spend time correcting problems.
>
> I suggest you look at panostart in Panotools::Script, it does a lot
> of this stuff, though it is perl not python.
>
> The version that I'll release soon has things like Eev calculation
> via Image::ExifTool already (which is how I knew where to look).
>
> --
> 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
>

-- 
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: Command line tool to add Exposure info to pto

[Bruno Postle]

On Thu 03-Dec-2009 at 14:23 -0500, Nicolas Pelletier wrote:
>In order to spend less time doing tedious tasks, I'm trying to have 60-80%
>of the process done automatically.
>
>I have a python script that takes all images in a folder, run panomatic,
>then run nona. I want to add cpclean, change some optimization values along
>with adding the exposure since I run mostly hdr. Then I'd run a first medium
>rez output. Then I'd only have to spend time correcting problems.

I suggest you look at panostart in Panotools::Script, it does a lot 
of this stuff, though it is perl not python.

The version that I'll release soon has things like Eev calculation 
via Image::ExifTool already (which is how I knew where to look).

-- 
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: Control Point Detectors on hugin-mac-2009.2

[Rick Workman]

Thanks Harry, at least my sanity is no longer in question. (Well not
for this reason.)

Looking forward to your resolution,

Rick


On Dec 3, 1:54 pm, Harry van der Wolf  wrote:
> Align_Image_Stack is currently not in or with the bundle. It needs to be
> added asap. The problem is that after changing in version 2009.2 to the new
> plugin structure it's not so easy to implement align_image_stack in the
> bundle now. I will pick this up asap.
> I do host align_image_stack binaries on my my website [0] which you could
> use, but since 2 days my provider has problems. Since 1 hour I can get on
> the internet again, but "the internet" still can't get on my server.
>
> When things are back to normal I let you know. I hope it will be very soon
> :-(
>
> Harry
>
> [0]: 
> 
>
> 2009/12/3 Rick Workman 
>
>
>
> > Thanks to all for the replies.
>
> > So I've now have Autopano-SIFT set up (using info from Bruno's post of
> > Sept. 6), so the basics are there.
>
> > I'm actually more interested in using align_image_stack for setting up
> > bracketed exposures. Bruno's post provides info on possible parameters
> > ("-f %v -p %o %i"), but what do I put in the Program field and what do
> > I select from the Type menu.
>
> > If I do the obvious thing and put "align_image_stack" in the program
> > string, when I select a set of bracketed images and try to set control
> > points to align them, it produces a "wxExecute Error" alert with error
> > code 255. I'm guessing that it can't find the program. (I certainly
> > can't.)
>
> > Any help appreciated,
>
> > Rick
>
> > P.S. There's definitely a U.S. patent on SIFT (US Patent 6,711,293
> > awarded March 23, 2004).
>
> > On Dec 2, 3:01 pm, Bruno Postle  wrote:
> > > On Wed 02-Dec-2009 at 08:16 -0800, Rick Workman wrote:
>
> > > >P.S. Are all the generators, including align_image stack, subject to
> > > >patent restrictions?
>
> > > As far as we know there are patents on SIFT and SURF.
>
> > > align_image_stack isn't effected, but it isn't an all-purpose
> > > control-point generator.
>
> > > --
> > > 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 > .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: HDR documentation?

[Nicolas Pelletier]

Thanks David, that's the one. I never seem to remember that name. Not as
catchy as photomatix :P

On Thu, Dec 3, 2009 at 12:04 PM, David Haberthür  wrote:

> Hey all
>
> On 03.12.2009, at 13:56, Nicolas Pelletier wrote:
> > For doing the processing, I think one open source software is QTVGUI or
> something like that. It's on sourcefore.
>
> http://qtpfsgui.sourceforge.net/ is the name of the tonemapping software
> you're looking for. if the images are perfectly aligned - shot on a tripod -
> then you can also make an HDR with qtpfsgui without using hugin.
>
> A nice GUI for exposure blending with enfuse is provided by Harry van der
> Wolf, be it either as Imagefuser for OSX [1] or for KImageFuser for Linux
> [2]
>
> [1]: http://tinyurl.com/imagefuser  which seems to be down at the moment.
> Harry?
> [2]:
> http://groups.google.com/group/hugin-ptx/browse_thread/thread/697f3cee1cf30c38/529d72978eea170c
>
> --
> 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: Command line tool to add Exposure info to pto

[Nicolas Pelletier]

In order to spend less time doing tedious tasks, I'm trying to have 60-80%
of the process done automatically.

I have a python script that takes all images in a folder, run panomatic,
then run nona. I want to add cpclean, change some optimization values along
with adding the exposure since I run mostly hdr. Then I'd run a first medium
rez output. Then I'd only have to spend time correcting problems.

Knowing which value to use, I'll be able to add this to some regex in
python. Thanks,

nick

On Thu, Dec 3, 2009 at 11:17 AM, bruno.postle wrote:

> On Dec 3, 2:48 am, Nicolas Pelletier 
> wrote:
> >
> > Is there a way through command line to have the exposure for all pictures
> in
> > a project set to their exif values? Kind of the same as doing reset to
> exif
> > from hugin itself?
>
> There isn't any Hugin tool to do this, but the exiftool LightValue tag
> is calculated identically to the Hugin Eev value so this could be
> scripted quite easily.
>
> What would you use this for?
>
> --
> 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: Control Point Detectors on hugin-mac-2009.2

[Harry van der Wolf]

Align_Image_Stack is currently not in or with the bundle. It needs to be
added asap. The problem is that after changing in version 2009.2 to the new
plugin structure it's not so easy to implement align_image_stack in the
bundle now. I will pick this up asap.
I do host align_image_stack binaries on my my website [0] which you could
use, but since 2 days my provider has problems. Since 1 hour I can get on
the internet again, but "the internet" still can't get on my server.

When things are back to normal I let you know. I hope it will be very soon
:-(

Harry


[0]: <
http://panorama.dyndns.org/index.php?lang=EN&subject=Hugin&texttag=Hugin>


2009/12/3 Rick Workman 

> Thanks to all for the replies.
>
> So I've now have Autopano-SIFT set up (using info from Bruno's post of
> Sept. 6), so the basics are there.
>
> I'm actually more interested in using align_image_stack for setting up
> bracketed exposures. Bruno's post provides info on possible parameters
> ("-f %v -p %o %i"), but what do I put in the Program field and what do
> I select from the Type menu.
>
> If I do the obvious thing and put "align_image_stack" in the program
> string, when I select a set of bracketed images and try to set control
> points to align them, it produces a "wxExecute Error" alert with error
> code 255. I'm guessing that it can't find the program. (I certainly
> can't.)
>
> Any help appreciated,
>
> Rick
>
> P.S. There's definitely a U.S. patent on SIFT (US Patent 6,711,293
> awarded March 23, 2004).
>
>
> On Dec 2, 3:01 pm, Bruno Postle  wrote:
> > On Wed 02-Dec-2009 at 08:16 -0800, Rick Workman wrote:
> >
> >
> >
> > >P.S. Are all the generators, including align_image stack, subject to
> > >patent restrictions?
> >
> > As far as we know there are patents on SIFT and SURF.
> >
> > align_image_stack isn't effected, but it isn't an all-purpose
> > control-point generator.
> >
> > --
> > 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
>

-- 
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: HDR documentation?

[David Haberthür]

Hey all

On 03.12.2009, at 13:56, Nicolas Pelletier wrote:
> For doing the processing, I think one open source software is QTVGUI or 
> something like that. It's on sourcefore.

http://qtpfsgui.sourceforge.net/ is the name of the tonemapping software you're 
looking for. if the images are perfectly aligned - shot on a tripod - then you 
can also make an HDR with qtpfsgui without using hugin.

A nice GUI for exposure blending with enfuse is provided by Harry van der Wolf, 
be it either as Imagefuser for OSX [1] or for KImageFuser for Linux [2]

[1]: http://tinyurl.com/imagefuser  which seems to be down at the moment. Harry?
[2]: 
http://groups.google.com/group/hugin-ptx/browse_thread/thread/697f3cee1cf30c38/529d72978eea170c

-- 
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: Control Point Detectors on hugin-mac-2009.2

[Rick Workman]

Thanks to all for the replies.

So I've now have Autopano-SIFT set up (using info from Bruno's post of
Sept. 6), so the basics are there.

I'm actually more interested in using align_image_stack for setting up
bracketed exposures. Bruno's post provides info on possible parameters
("-f %v -p %o %i"), but what do I put in the Program field and what do
I select from the Type menu.

If I do the obvious thing and put "align_image_stack" in the program
string, when I select a set of bracketed images and try to set control
points to align them, it produces a "wxExecute Error" alert with error
code 255. I'm guessing that it can't find the program. (I certainly
can't.)

Any help appreciated,

Rick

P.S. There's definitely a U.S. patent on SIFT (US Patent 6,711,293
awarded March 23, 2004).


On Dec 2, 3:01 pm, Bruno Postle  wrote:
> On Wed 02-Dec-2009 at 08:16 -0800, Rick Workman wrote:
>
>
>
> >P.S. Are all the generators, including align_image stack, subject to
> >patent restrictions?
>
> As far as we know there are patents on SIFT and SURF.  
>
> align_image_stack isn't effected, but it isn't an all-purpose
> control-point generator.
>
> --
> 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: Command line tool to add Exposure info to pto

[bruno.postle]

On Dec 3, 2:48 am, Nicolas Pelletier 
wrote:
>
> Is there a way through command line to have the exposure for all pictures in
> a project set to their exif values? Kind of the same as doing reset to exif
> from hugin itself?

There isn't any Hugin tool to do this, but the exiftool LightValue tag
is calculated identically to the Hugin Eev value so this could be
scripted quite easily.

What would you use this for?

-- 
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: Automating creation of HDR pano

[bruno.postle]

On Dec 3, 12:58 pm, Nicolas Pelletier 
wrote:
> Following the original posters request, is there a way (i.e. command line
> tool) to add the crop to the pto automatically? I'd guess that the values
> are consistent from one picture to another with the same fisheye...

You can set any value in a project file with Panotools::Script,
something like this (untested):

  #!/usr/bin/perl
  use Panotools::Script;
  my $pto = new Panotools::Script;
  $pto->Read ($ARGV[0]);
  $_->{S} = '-459,2459,-57,2861' for @{$pto->Image};
  $pto->Write ($ARGV[0]);

> On Thu, Dec 3, 2009 at 7:40 AM, bruno.postle 
> wrote:
>
> > On Dec 3, 9:42 am, Oskar Sander  wrote:
> > > How does hugin handle all this black void in the image, is this ignored in
> > > blend & fusing?
>
> > Only if you are lucky with seam placement, for circular fisheye photos
> > you really need to mask out the black areas using the Hugin Crop tab.

-- 
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: Automating creation of HDR pano

[Nicolas Pelletier]

Following the original posters request, is there a way (i.e. command line
tool) to add the crop to the pto automatically? I'd guess that the values
are consistent from one picture to another with the same fisheye...

nick

On Thu, Dec 3, 2009 at 7:40 AM, bruno.postle wrote:

> On Dec 3, 9:42 am, Oskar Sander  wrote:
> > Isn't the circular fisheye projecting a circle on the sensor with the
> rest
> > of the sensore rectangle black?   The HFOV is the sensor long-side field
> of
> > view, so it could be correct if you would imagine the lens would be
> > projecting outside the circle too.
> >
> > How does hugin handle all this black void in the image, is this ignored
> in
> > blend & fusing?
>
> Only if you are lucky with seam placement, for circular fisheye photos
> you really need to mask out the black areas using the Hugin Crop tab.
>
> --
> 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: HDR documentation?

[Nicolas Pelletier]

On thing I want to add in case it is not already clear.

HDR we see on the net are not HDR per say. They are LDR images (like
anything the camera shoots) that was processed to an HDR and then back to an
LDR.

In short:

Multiple exposures LDR => merging => HDR => Processing => LDR that we
typically call HDR on the net.

The steps you mention bring you to the HDR step, but you'll need to find
something to do the processing to LDR

Enfuse (part of hugin) does what some people call Exposure Fusion or
Exposure Blending, which basically brings multiple LDR to a HDR style LDR
without actually going through HDR.

Like Bruno, I recommend you try the enfused output before.

For doing the processing, I think one open source software is QTVGUI or
something like that. It's on sourcefore.

nick

On Thu, Dec 3, 2009 at 7:50 AM, bruno.postle wrote:

> On Dec 3, 8:11 am, Luis  wrote:
> >
> > What I tried with the 2009.2, running on F11:
> >
> > 1) loaded two images, taken right after the other with only exposure
> > changed
> > 2) hit 'align'; was told the two images were out of alignment
> > 3) poked around the images tab; found 'align image stack', which
> > seemed more correct, and created control points with that. manually
> > inspected the control points and they looked good.
>
> Yes, that should do it, though if this is a panorama, you need control
> points between adjacent photos too.
>
> > 4) under 'exposure', selected 'custom parameters below' and selected
> > exposure for both.
>
> You don't need to do this if the EXIF exposure was read correctly,
> i.e. if each image in the stack has a different EV value in the Camera
> and Lens tab.
>
> > 5) under 'stitcher', selected HDR merged and blended panorama, and
> > tiff output, and hit 'stitch now'.
> >
> > What I got was a completely transparent tiff. :)
>
> No idea, you should see something in the preview window. Note that if
> you only have a single stack of images, optimising field of view will
> always produce a bad result - The images may be too small to see in
> your output.
>
> I'd recommend starting with the Exposure blended output first, and
> once you have good results with that, try stitching the exact same
> project to HDR - Working with HDR data is a pain and you don't need it
> until you are happy with the alignment etc...
>
> --
> 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] Re: HDR documentation?

[bruno.postle]

On Dec 3, 8:11 am, Luis  wrote:
>
> What I tried with the 2009.2, running on F11:
>
> 1) loaded two images, taken right after the other with only exposure
> changed
> 2) hit 'align'; was told the two images were out of alignment
> 3) poked around the images tab; found 'align image stack', which
> seemed more correct, and created control points with that. manually
> inspected the control points and they looked good.

Yes, that should do it, though if this is a panorama, you need control
points between adjacent photos too.

> 4) under 'exposure', selected 'custom parameters below' and selected
> exposure for both.

You don't need to do this if the EXIF exposure was read correctly,
i.e. if each image in the stack has a different EV value in the Camera
and Lens tab.

> 5) under 'stitcher', selected HDR merged and blended panorama, and
> tiff output, and hit 'stitch now'.
>
> What I got was a completely transparent tiff. :)

No idea, you should see something in the preview window. Note that if
you only have a single stack of images, optimising field of view will
always produce a bad result - The images may be too small to see in
your output.

I'd recommend starting with the Exposure blended output first, and
once you have good results with that, try stitching the exact same
project to HDR - Working with HDR data is a pain and you don't need it
until you are happy with the alignment etc...

-- 
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: Automating creation of HDR pano

[bruno.postle]

On Dec 3, 9:42 am, Oskar Sander  wrote:
> Isn't the circular fisheye projecting a circle on the sensor with the rest
> of the sensore rectangle black?   The HFOV is the sensor long-side field of
> view, so it could be correct if you would imagine the lens would be
> projecting outside the circle too.
>
> How does hugin handle all this black void in the image, is this ignored in
> blend & fusing?

Only if you are lucky with seam placement, for circular fisheye photos
you really need to mask out the black areas using the Hugin Crop tab.

-- 
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] Automating creation of HDR pano

[Oskar Sander]

Actually if you have a 2/3 format and circular fisheye that perfectly fills
the format, the short side FOV is 180deg  and the longside theoretical FOV
is then 3*180/2=270.  So your figure there sounds perfectly all right

2009/12/3 Oskar Sander 

> Isn't the circular fisheye projecting a circle on the sensor with the rest
> of the sensore rectangle black?   The HFOV is the sensor long-side field of
> view, so it could be correct if you would imagine the lens would be
> projecting outside the circle too.
>
> How does hugin handle all this black void in the image, is this ignored in
> blend & fusing?
>
> 2009/12/3 hdrpano 
>
>
>> Focal length: 8 mm
>> Focal length multiplier: 1
>> HFOV (v): 257.89
>>
>> I enter the first two and hugin fills in the HFOV.  Shouldn't that be
>> closer
>> to 180?
>>
>>
> --
> /O
>



-- 
/O

-- 
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] Automating creation of HDR pano

[Oskar Sander]

Isn't the circular fisheye projecting a circle on the sensor with the rest
of the sensore rectangle black?   The HFOV is the sensor long-side field of
view, so it could be correct if you would imagine the lens would be
projecting outside the circle too.

How does hugin handle all this black void in the image, is this ignored in
blend & fusing?

2009/12/3 hdrpano 

>
> Focal length: 8 mm
> Focal length multiplier: 1
> HFOV (v): 257.89
>
> I enter the first two and hugin fills in the HFOV.  Shouldn't that be
> closer
> to 180?
>
>
-- 
/O

-- 
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] HDR documentation?

[Luis]

Hey, all-
I am a pretty complete HDR newbie, but took some potential HDR source
shots on my recent trip and thought I'd look into using hugin to
create the images when I returned.

Unfortunately (as I'm sure most of you know) the documentation is
pretty out of date, and the process isn't as easy/intuitive as it is
for panoramas (by which I mean, it took me a few minutes to figure out
panoramas with hugin and still after several hours I haven't figured
out how to do HDR with hugin.)

I'm willing to write/update the documentation myself if someone here
or elsewhere can help me figure out the process.

What I tried with the 2009.2, running on F11:

1) loaded two images, taken right after the other with only exposure
changed
2) hit 'align'; was told the two images were out of alignment
3) poked around the images tab; found 'align image stack', which
seemed more correct, and created control points with that. manually
inspected the control points and they looked good.
4) under 'exposure', selected 'custom parameters below' and selected
exposure for both.
5) under 'stitcher', selected HDR merged and blended panorama, and
tiff output, and hit 'stitch now'.

What I got was a completely transparent tiff. :)

So... what am I doing wrong? any suggestions? Like I said, once I
figure this out, I can rip and replace the old docs in the wiki
(http://wiki.panotools.org/HDR_workflow_with_hugin) so that everyone
can benefit.

Thanks-
Luis

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