Nabble - hugin ptx

Re: Announce: Enblend/Enfuse version 4.0 - Release Candidate 2 (long post!)

2009-11-27T07:38:01Z

Alexandre -

On Nov 27, 12:56 pm, prokoudine <alexandre.prokoud...@...>
wrote:
> On 26 ноя, 10:39, cspiel <csp...@...> wrote:
> What about a brief overview of changes? :)

A summary of chnges and improvements can be
found in file "README" in each of the tarballs. For those
too lazy to download and unpack, here is the section on
version 4.0. Sorry, but it is a long read!

** Improvements

- Huge new documentation in Info, PS, PDF, HTML formats. XHTML format
is still experimental.

- New manual pages.

- Automatic bit depth conversion between input and output images if
necessary.

For example: given 16-bit TIFF input images and a JPEG output image
Enblend and Enfuse automatically convert from 16-bit to 8-bit before
writing the JPEG file.

- Compilation without image cache works again
("--disable-image-cache"). Speedups of up to 30% have been reported
on the amd64 architecture.

- Enblend and Enfuse accept repsonse files in addition to literal
image files. Response files contain lists of image filenames or
names of other response files.

- Lots of new warnings if a command-line option has no effect, like,
for example, combining a mask optimization option with
"--no-optimize".

- Enblend shows the initial, unoptimized seam line in addition to the
optimized one in all seam-line visualization images (option
"--visualize").

- Enblend and Enfuse read multi-layer TIFF files ("multi directory" in
TIFF jargon). It is even possible to mix multi-layer with single
layer images. This partially fixes SourceForge bug ID 1170329.

- Save masks with (lossless) "Deflate" compression.

- An improved wrap-around option, formerly only "-w", now "-wMODE" and
"--wrap=MODE", lets the user determine whether to create a 360
degrees horizontal or vertical panorama. It is possible to wrap
around vertically and horizontally at the same time.

- Without any output filename given, i.e. no "-o" option, the output
filename now defaults to "a.tif", making "-o" truly an option.

- The user has better control of the number of pyramid levels.
Previously only the maximum number in any blend could be reduced
by the "-l" option. Now, the maximum number can be reduced by a
fixed amount no matter what the actual maximum number of permissible
pyramid levels is.

- Use OpenMP to make better use of multi-processor machines. As the
image cache is not reentrant, OpenMP can only be activated when the
image cache is disabled.

- Enblend and Enfuse issue messages following the GNU standard.

** Bug Fixes

- Fix the calculation of the number of blending levels. Previously,
it was off by one in most cases.

- A longstanding bug (SourceForge ID 2160427) in the primary seam line
generation that caused a sub-optimal seam line was fixed. As a side
effect the new seam line algorithm is at least 20% faster than the
old one.

- Another longstanding bug (SourceForge ID 1891785) that caused wrong
output for images with holes was also fixed.

- Fix a well hidden but serious bug in the seam line optimization.
Both, the GPU and non-GPU versions of the optimizer were affected.

- Make Enblend and Enfuse aware of the input images' resolution. Use
the input resolution in the output file.

With this change masks get the correct offsets. This fixes the bug
that masks do not end up at the correct position with respect to the
input files.

- Fix MacOS problem of parsing floating-point parameters at the
command line.

** New Commandline Options

- All Enfuse options have been converted to Enblend's option naming
scheme. This is, camel-casing has been replaced by lowercase plus
dashes. The new option name are more systematically constructed,
too. The old options will completely dissapear in the next release,
4.1.

Old Option New Option
==================== ========================
--ContrastWindowSize --contrast-window-size
--EdgeScale --contrast-edge-scale
--EntropyCutoff --entropy-cutoff
--EntropyWindowSize --entropy-window-size
--GrayProjector --gray-projector
--HardMask --hard-mask
--MinCurvature --contrast-min-curvature
--SaveMasks --save-masks
--SoftMask --soft-mask
--wContrast --contrast-weight
--wEntropy --entropy-weight
--wExposure --exposure-weight
--wExposureMu --exposure-mu
--wExposureSigma --exposure-sigma
--wSaturation --saturation-weight

- New option to control the output bit depth ("--depth").

- Mask filenames can be specified with templates.

* Enblend ("--save-masks", "--load-masks", "--visualize"): Save and
load all masks of a project in a single run. Same for seam line
visualization files.

* Enfuse ("--save-masks"): Save soft and hard masks according to
path given in template.

- New option to control the mask vectorization, which is done before
any mask optimizations ("--mask-vectorize").

- New option to control the Simulated Annealing optimizer called
strategy 1 ("--anneal").

- New option to control the relative weights of the distance to the
initial seam line and the total mismatch ("--optimizer-weights").

- New option to control the Dijkstra path minimizer called strategy 2
("--dijkstra").

- Option "--coarse-mask" takes an optional (linear) reduction factor.
The default remains at 8.

- New option "--smooth-difference" to blur difference images prior to
seam-line optimization.

- Long option "--levels" to control the number of levels; duplicates
functionality of short option "-l".

** Removed Commandline Options

- After having been deprecated for a long time, Enfuse's option
"--debug", which saved the masks used in fusing, was removed.
Option "--save-masks" now provides a superset of the previous
functionality.

- After having been deprecated for a long time, Enblend's and Enfuse's
option "-z", which compressed TIFF-output files with the LZW
algorithm, was removed. Option "--compression" now provides a
superset of the previous functionality and "--compression=LZW" is a
substitute for "-z".

** Developer Stuff

- VPATH builds work. This makes it easy to compile for differently
configured versions, like for example with and without image cache.

- The target "make distcheck" works again.

- Introduce additional Make variables to control the Make process
after the project was configured. See "README" file.

- Debugging of dynamic memory allocation has been eased by the
integration of the DMalloc package; "configure --with-dmalloc"

- Use only m4 files that clearly have a GPL license. This fixes
SourceForge feature request ID 2152850.

- Remove all files that are meant to be generated auto Autoconf. This
fixes SourceForge bug ID 2036031.

- Install m4 file to detect the M$ compiler. This fixes SourceForge
bug ID 2036034.

- Make "configure" report that extra features will get compiled and if
they cannot tell the developer why not.

- Pull version of program and documentation into file "VERSION". Both
program and documentation automatically use this information on
every build.

** What is known not to work?

- Documentation generation is not as reliable and smooth as it ought
to be. The culprit is Automake; see PR/486.

> P.S. Space balls rock :)

Right. Even more now as Episodes 1-3 of the "original"
have left me slightly disappointed.

/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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Announce: Enblend/Enfuse version 4.0 - Release Candidate 2

2009-11-27T03:56:24Z

On 26 ноя, 10:39, cspiel <csp...@...> wrote:
> Hi all!
>
> Everybody who thinks, he missed out on
> release candidate 1 (RC1), please put your mind
> at rest. We did not announce RC1 in public.
>
> Self-Destruction Computer: Ten, nine, eight, six
> President Skroob: Six? What happened to seven?
> Self-Destruction Computer: Just kidding!

What about a brief overview of changes? :)

P.S. Space balls rock :)

Alexandre

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: tortoise

2009-11-26T21:01:02Z

Tortoise embeds itself into the explorer. You need to uninstall it (control panel, add remove programs, then uninstall tortoise).

nick

On Thu, Nov 26, 2009 at 7:00 PM, michael crane <mick.crane@...> wrote:

hello,
I installed the tortoise server and client thingy on windose vista as
suggested and it will not go away.
I removed it from the start up programs but each time I reboot it is
still there. I would like to know how it does that and stop it

thanks.

mick

--
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

tortoise

2009-11-26T16:00:22Z

hello,
I installed the tortoise server and client thingy on windose vista as
suggested and it will not go away.
I removed it from the start up programs but each time I reboot it is
still there. I would like to know how it does that and stop it

thanks.

mick

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Panomatic

2009-11-26T07:39:54Z

For anyone interested, found the problem with the version. Mail me if you want the source.

nick

On Sat, Nov 21, 2009 at 7:59 AM, Nicolas Pelletier <nicolas.pelletier@...> wrote:

I mentioned sourceforge because if I get the 64 bit running properly, there is no place to upload the changes if the source code is not going to be kept there.

But I'll contact him directly for the important questions.

nick

On Sat, Nov 21, 2009 at 7:07 AM, Harry van der Wolf <hvdwolf@...> wrote:

2009/11/21 Nicolas Pelletier <nicolas.pelletier@...>
I'll contact him, but this is where I got the source and the win32 binary for comparison.

nick

OK, but you mentioned sourceforge. This is his "private" address.

Harry

--
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Announce: Enblend/Enfuse version 4.0 - Release Candidate 2

2009-11-25T23:39:11Z

Hi all!

Everybody who thinks, he missed out on
release candidate 1 (RC1), please put your mind
at rest. We did not announce RC1 in public.

Self-Destruction Computer: Ten, nine, eight, six
President Skroob: Six? What happened to seven?
Self-Destruction Computer: Just kidding!

However, now we are glad to announce the second
release candidate (RC2) for Enblend/Enfuse
version 4.0. We have put a tar-ball of it at

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

The archive file there is derived from revision
3c803dd7ab5f in the Mercurial repository

http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/

As a release candidate for Enblend/Enfuse 4.0,
it should be almost ready for final release.
However, there still might be a few remaining
issues. The purpose of the release candidate is
to discover any _major_ issues, which have _not_
been recorded in the bug tracker yet, before the
final version. The release candidate may not be
suitable for production systems, but it is ready
for contributors who want to help with testing
and development for version 4.0.

Please, could all the first-adopters out there
give it a try on their architecture and report
whether something is seriously broken?

/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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Re: autopano-sift problem with lots of large images

2009-11-25T13:29:48Z

On Wed, 25 Nov 2009, Seb Perez-D wrote:

> On Wed, Nov 25, 2009 at 18:28, wb <wblock@...> wrote:
>> Done: dumont.pto and (.mk). This is just after the "Load images..."
>> step. If you mean after an additional optimization, I can add that.
>
> You have three wrong control points between images 0 and 3. They are
> throwing everything off. Delete them and reoptimize, and everything
> works.

Aha. Now that I look back at an earlier pano, I see the same problem:
a few wrong control points between image 0 and unrelated other images;
four to image 2 and three 3 image 4 in that case.

> Have you tried with cpclean?

As best I can tell, it's not yet in the FreeBSD port of Hugin. Now that
I know where the problem is, it's easier to correct than manually
setting control points.

-Warren Block * Rapid City, South Dakota USA

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Re: autopano-sift problem with lots of large images

2009-11-25T10:19:01Z

On Wed, Nov 25, 2009 at 18:28, wb <wblock@...> wrote:
> Done: dumont.pto and (.mk). This is just after the "Load images..."
> step. If you mean after an additional optimization, I can add that.

You have three wrong control points between images 0 and 3. They are
throwing everything off. Delete them and reoptimize, and everything
works.

Have you tried with cpclean?

Cheers,

Seb

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: autopano-sift problem with lots of large images

2009-11-25T09:28:52Z

On Nov 25, 9:52 am, Seb Perez-D <sbprzd+...@...> wrote:
> On Wed, Nov 25, 2009 at 17:46, Warren Block <wbl...@...> wrote:
> > The control points appear to be fine. It's the position of the images
> > that is completely wrong.
>
> Thanks for the images!
>
> It would help if you posted the pto file just after optimisation.

Done: dumont.pto and (.mk). This is just after the "Load images..."
step. If you mean after an additional optimization, I can add that.

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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: autopano-sift problem with lots of large images

2009-11-25T08:52:25Z

On Wed, Nov 25, 2009 at 17:46, Warren Block <wblock@...> wrote:
> The control points appear to be fine. It's the position of the images
> that is completely wrong.

Thanks for the images!

It would help if you posted the pto file just after optimisation.

Best,

Seb

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: autopano-sift problem with lots of large images

2009-11-25T08:46:48Z

On Wed, 25 Nov 2009, Seb Perez-D wrote:

> On Tue, Nov 24, 2009 at 20:49, wb <wblock@...> wrote:
>> autopano-sift and autopano-sift-C have problems with a panorama of six
>> 4000x3000 images. Images end up upside down or twisted, and not
>> related to each other at all. panomatic has no trouble with the same
>> images.
>
> Is the problem that you cannot find control points between the images
> in autopano-sift, or that the control points are bad?

The control points appear to be fine. It's the position of the images
that is completely wrong. In this simple left-to-right set of images,
the roll angles are detected as:

12.9
-173
167.2
-19.4
-0.7
13.9

Turns out there is a 10M per file limit preventing upload of an archive
of all the pictures anyway. I've put them here temporarily:

http://www.wonkity.com/~wblock/autopano-sift/

There's a readme.txt there also with steps to duplicate the problem.

> I find it difficult to believe that this is a resource problem: do you
> see any output on the command line that looks suspicious? I've run
> APSCpp on several large projects (+100 images) and have not recently
> had any issues.

I'm probably too ignorant on what would be suspicious to be helpful
there.

> If the control points are bad, you could try using cpclean.
>
> If you do not find control points, have you tried changing the maxdim
> parameter?

Tried adding --maxdim 4000 to the autopano-sift command line just now.
It takes much longer to run, of course. The first (0/1) and last (4/5)
pair of images are aligned with each other. #2 is upside down and
misplaced, and #3 is just misplaced.

> If the images are from a fish-eye or a ultrawide angle lens, have you
> tried using the stereographic projection feature?

Just a Canon SD950 point-and-shoot at its widest angle (36mm equiv).

-Warren Block * Rapid City, South Dakota USA

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: autopano-sift problem with lots of large images

2009-11-25T00:05:47Z

On Tue, Nov 24, 2009 at 20:49, wb <wblock@...> wrote:
> autopano-sift and autopano-sift-C have problems with a panorama of six
> 4000x3000 images. Images end up upside down or twisted, and not
> related to each other at all. panomatic has no trouble with the same
> images.

Is the problem that you cannot find control points between the images
in autopano-sift, or that the control points are bad? I find it
difficult to believe that this is a resource problem: do you see any
output on the command line that looks suspicious? I've run APSCpp on
several large projects (+100 images) and have not recently had any
issues.

If the control points are bad, you could try using cpclean.

If you do not find control points, have you tried changing the maxdim
parameter? If the images are from a fish-eye or a ultrawide angle
lens, have you tried using the stereographic projection feature?

Cheers,

Seb

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Re: enblend documentation does not compile anymore

2009-11-24T22:01:42Z

Am Wednesday 25 November 2009 schrieb Bruno Postle:

> On Tue 24-Nov-2009 at 14:45 +0100, Kornel Benko wrote:
> >Am Tuesday 24 November 2009 schrieb cspiel:
> >> Could it be that you need at least texinfo-4.11
> >> to get @textdegree?
> >
> >Unfortunatelly I had to compile it. No such package for openSuSE 10.3.
>
> Alternatively the enblend hg repository already has an up-to-date
> enblend.info file, so you can avoid rebuilding it by updating the
> timestamp with `touch`.

Yes, but this is a nogo for someone trying to modify the documentation :)
(Not that I am doing this, but who knows what the future will be)

> --
> Bruno
>

Kornel

--
Kornel Benko
Kornel.Benko@...

signature.asc (201 bytes) Download Attachment

Re: Re: enblend documentation does not compile anymore

2009-11-24T15:54:14Z

On Tue 24-Nov-2009 at 14:45 +0100, Kornel Benko wrote:
>Am Tuesday 24 November 2009 schrieb cspiel:
>> Could it be that you need at least texinfo-4.11
>> to get @textdegree?
>
>Unfortunatelly I had to compile it. No such package for openSuSE 10.3.

Alternatively the enblend hg repository already has an up-to-date
enblend.info file, so you can avoid rebuilding it by updating the
timestamp with `touch`.

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

autopano-sift problem with lots of large images

2009-11-24T11:49:41Z

autopano-sift and autopano-sift-C have problems with a panorama of six
4000x3000 images. Images end up upside down or twisted, and not
related to each other at all. panomatic has no trouble with the same
images.

This seems to be a resource problem. The images are about 34M
combined. In trying to make a reasonably-sized example for this post,
I found that using fewer images or a higher jpeg compression made the
problem go away.

I started to upload the 34M demo file to the file area here, but
stopped after seeing that it would eat up most of the remaining
quota. If that's all right, I'll upload it later.

FreeBSD 8 with 2G of RAM

hugin-2009.0.2
autopano-sift-C-2.5.1
panomatic-0.9.4

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Control Point Generators Installation on Mac

2009-11-24T11:17:46Z

This worked. But oddly, I had to close all finder windows before this
would work properly.

Thanks so much!

-Val

On Nov 24, 12:12 pm, Carl von Einem <c...@...> wrote:

> I suspect you downloaded and mounted the hugin image (a .dmg), than
> directly from this mounted image you mounted the next .dmg files
> contained in it, right?
>
> This was reported before, please do the following: drag the CP generator
> images temporarily to your desktop and doubleclick those. Now it should
> work as expected.
>
> Carl
>
> Val schrieb am 24.11.2009 18:07 Uhr:
>
>
>
> > Hello Hugin folks,
>
> > I'm trying to install Hugin for the first time. I'm working on an
> > Intel Mac. When I attempt to run the Installer....app for either of
> > the control point generators the installer bounces in the launcher for
> > maybe 30 seconds, then stops bouncing but nothing further happens. The
> > installer doesn't respond to anything, nothing gets installed. I have
> > to "force-quit" the installer. If I "drag and drop" the generator code
> > into the installer script I get the same result.
>
> > I searched the list and didn't seem to find someone else having a
> > similar problem. So I thought I'd ask, am I doing something wrong?
>
> > Thanks,
>
> > Val

Re: Control Point Generators Installation on Mac

2009-11-24T09:12:06Z

I suspect you downloaded and mounted the hugin image (a .dmg), than
directly from this mounted image you mounted the next .dmg files
contained in it, right?

This was reported before, please do the following: drag the CP generator
images temporarily to your desktop and doubleclick those. Now it should
work as expected.

Carl

Val schrieb am 24.11.2009 18:07 Uhr:

> Hello Hugin folks,
>
> I'm trying to install Hugin for the first time. I'm working on an
> Intel Mac. When I attempt to run the Installer....app for either of
> the control point generators the installer bounces in the launcher for
> maybe 30 seconds, then stops bouncing but nothing further happens. The
> installer doesn't respond to anything, nothing gets installed. I have
> to "force-quit" the installer. If I "drag and drop" the generator code
> into the installer script I get the same result.
>
> I searched the list and didn't seem to find someone else having a
> similar problem. So I thought I'd ask, am I doing something wrong?
>
> Thanks,
>
> Val
>

Control Point Generators Installation on Mac

2009-11-24T09:07:15Z

Hello Hugin folks,

I'm trying to install Hugin for the first time. I'm working on an
Intel Mac. When I attempt to run the Installer....app for either of
the control point generators the installer bounces in the launcher for
maybe 30 seconds, then stops bouncing but nothing further happens. The
installer doesn't respond to anything, nothing gets installed. I have
to "force-quit" the installer. If I "drag and drop" the generator code
into the installer script I get the same result.

I searched the list and didn't seem to find someone else having a
similar problem. So I thought I'd ask, am I doing something wrong?

Thanks,

Val

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Re: enblend documentation does not compile anymore

2009-11-24T05:45:35Z

Am Tuesday 24 November 2009 schrieb cspiel:
> Could it be that you need at least texinfo-4.11
> to get @textdegree?

Unfortunatelly I had to compile it. No such package for openSuSE 10.3.

Nonetheless, it's ok here now. Thanks.

Kornel
--
Kornel Benko
Kornel.Benko@...

signature.asc (201 bytes) Download Attachment

Re: Re: enblend documentation does not compile anymore

2009-11-24T02:58:04Z

Am Tuesday 24 November 2009 schrieb cspiel:

> Kornel -
>
> On Nov 24, 8:31 am, Kornel Benko <Kornel.Be...@...> wrote:
> > enfuse.texi:673: Unknown command `textdegree'.
>
> Obviously, your only problem is the missing
> "@textdegree" macro.
>
> > Maybe it depends on my tex-installation in combination to the texinfo package (which includes texi2dvi and makeinfo):
> > texlive2009,
> > texinfo-4.9-15 (on openSuSE)
>
> Could it be that you need at least texinfo-4.11
> to get @textdegree? Have you grepped for its
> definition in your texinfo.tex file?

Maybe. Will try to get new package. But I fear, I have to compile them myself :(

Yes, I did. And it was defined.

> /Chris
>

--
Kornel Benko
Kornel.Benko@...

signature.asc (201 bytes) Download Attachment

Re: enblend documentation does not compile anymore

2009-11-24T00:34:27Z

Kornel -

On Nov 24, 8:31 am, Kornel Benko <Kornel.Be...@...> wrote:
> enfuse.texi:673: Unknown command `textdegree'.

Obviously, your only problem is the missing
"@textdegree" macro.

> Maybe it depends on my tex-installation in combination to the texinfo package (which includes texi2dvi and makeinfo):
> texlive2009,
> texinfo-4.9-15 (on openSuSE)

Could it be that you need at least texinfo-4.11
to get @textdegree? Have you grepped for its
definition in your texinfo.tex file?

/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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

enblend documentation does not compile anymore

2009-11-23T23:31:58Z

Hi

since last change I cannot create new documentation. (To be sure, I tried with automake as well)
This is the error I get now:
...
if /bin/sh /Creatable/src/enblend/enblend/missing --run makeinfo -I .. -I . --css-include=./default.css -I . \
-o enfuse.info enfuse.texi; \
then \
rc=0; \
cd .; \
else \
rc=$?; \
cd . && \
$restore $backupdir/* `echo "./enfuse.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
enfuse.texi:673: Unknown command `textdegree'.
enfuse.texi:673: Misplaced {.
enfuse.texi:673: Misplaced }.
enfuse.texi:727: Unknown command `textdegree'.
enfuse.texi:727: Misplaced {.
enfuse.texi:727: Misplaced }.
enblend.texi:550: Unknown command `textdegree'.
enblend.texi:550: Misplaced {.
enblend.texi:550: Misplaced }.
enblend.texi:604: Unknown command `textdegree'.
enblend.texi:604: Misplaced {.
enblend.texi:604: Misplaced }.
enblend.texi:478: Unknown command `textdegree'.
enblend.texi:478: Misplaced {.
enblend.texi:478: Misplaced }.
makeinfo: Removing output file `enblend.info' due to errors; use --force to preserve.
enfuse.texi:601: Unknown command `textdegree'.
enfuse.texi:601: Misplaced {.
...
Maybe it depends on my tex-installation in combination to the texinfo package (which includes texi2dvi and makeinfo):
texlive2009,
texinfo-4.9-15 (on openSuSE)

Kornel
--
Kornel Benko
Kornel.Benko@...

signature.asc (201 bytes) Download Attachment

Re: Hugin crashing when aligning

2009-11-23T22:59:52Z

2009/11/24 paulzizka@... <paulzizka@...>:

> Hi guys.
>
> I can't seem to be able to stitch 7 tiffs without Hugin crashing. Out
> of all the info that's out there, I gathered I need Autopano-sift-c if
> I don[t want to mess around with control points myself - is that
> correct? If so, how do I get Hugin to use Autopano-sift-c to stop
> crashing?
>
> Thanks very much for sharing the knowledge,
>
> Paul
>
> --
> 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@...
> To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/hugin-ptx

Hi,
maybe you should share more information about your problem with us.
Like what platform do you use, which hugin version and where you get
it.

Lukas

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Hugin crashing when aligning

2009-11-23T21:17:19Z

Hi guys.

I can't seem to be able to stitch 7 tiffs without Hugin crashing. Out
of all the info that's out there, I gathered I need Autopano-sift-c if
I don[t want to mess around with control points myself - is that
correct? If so, how do I get Hugin to use Autopano-sift-c to stop
crashing?

Thanks very much for sharing the knowledge,

Paul

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

New groups for Panini users

2009-11-23T09:30:14Z

Users of the Panini pano viewer / perspective tool are invited to join
two new groups devoted to that program.

The Google group http://groups.google.com/group/panini-support is for
primarily text-based help and discussion.

The flickr group "Panini perspective tool" (http://www.flickr.com/
groups/1293783@N21/) is for image-based discussions, examples,
tutorials (only flickr members can post; but it's easy to join).

Please share your experience and suggestions for improving Panini.

-- Tom Sharpless

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Panomatic

2009-11-21T04:59:12Z

I mentioned sourceforge because if I get the 64 bit running properly, there is no place to upload the changes if the source code is not going to be kept there.

But I'll contact him directly for the important questions.

nick

On Sat, Nov 21, 2009 at 7:07 AM, Harry van der Wolf <hvdwolf@...> wrote:

2009/11/21 Nicolas Pelletier <nicolas.pelletier@...>
I'll contact him, but this is where I got the source and the win32 binary for comparison.

nick

OK, but you mentioned sourceforge. This is his "private" address.

Harry

--
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Panomatic

2009-11-21T04:07:50Z

2009/11/21 Nicolas Pelletier <nicolas.pelletier@...>

I'll contact him, but this is where I got the source and the win32 binary for comparison.

nick

OK, but you mentioned sourceforge. This is his "private" address.

Harry

Re: Panomatic

2009-11-21T03:58:19Z

I'll contact him, but this is where I got the source and the win32 binary for comparison.

nick

On Sat, Nov 21, 2009 at 2:21 AM, Harry van der Wolf <hvdwolf@...> wrote:

Naouel's homepage is at http://aorlinsk2.free.fr/panomatic/

He also has windows binaries there and you can also find the source there. Maybe if you get in direct contact with him you might get your answers.

Harry

2009/11/21 Nicolas Pelletier <nicolas.pelletier@...>

Hi,

Many questions about panomatic (btw, still targetting to setup and help on windows, but this itched a little more)

First, is there a reason that the panomatic project on SF has files but no source?

Second, if I don't want to get into trouble with patent... where is the limit?
- Publishing the source?
- Contributing a new version?
- Uploading\encouraging people to use it?

I'm asking because I was limited on the 32 bit version because of the memory limit (only 1 or 2 thread running) so I recompiled a 64 bit version. I'm all for sharing, but don't want any trouble.

As I'm testing the result, I'm hitting one problem. My benchmarks are running, but here is the preliminary:
DL version (binary for windows) runs a test in 350 seconds
Compiled 32 version (in release, fully optimized) runs the same test in 895 seconds.

This is baffling me. Anybody has any clue? Does the source actually match what was used to build it? (I may have done a dumb mistake, worked on this instead of sleeping... but I typically know what I'm doing with code...)

These results are king of killing the purpose of building a faster version... If the original is still 2-3 times faster, tough to beat!

Also, this is more technical, but here we go.
Panomatic seems to have 2 phases in the same way that Sift does; 1st find control points. 2nd, match points between images and purge everything else.
In Panomatic, the 2nd phase is awfully long, taking over 90% of the processing time. It seems that one major difference between sift and surf in their classic impementation is that in sift, it is done single thread and in one global run, while for surf, it is done per pair of images, multi thread. The pair thing is killing me since I typically shoot 51 images per pano.

Now, the question for the experts. Is that second phase the same\similar\completely different between autopanoSIFT-c and Panomatic? Could the second one be improved with the way the first one was coded?

There you go. Hope this mail is not too long.

nick

--
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: Panomatic

2009-11-20T23:21:21Z

Naouel's homepage is at http://aorlinsk2.free.fr/panomatic/

He also has windows binaries there and you can also find the source there. Maybe if you get in direct contact with him you might get your answers.

Harry

2009/11/21 Nicolas Pelletier <nicolas.pelletier@...>

Hi,

Many questions about panomatic (btw, still targetting to setup and help on windows, but this itched a little more)

First, is there a reason that the panomatic project on SF has files but no source?

Second, if I don't want to get into trouble with patent... where is the limit?
- Publishing the source?
- Contributing a new version?
- Uploading\encouraging people to use it?

I'm asking because I was limited on the 32 bit version because of the memory limit (only 1 or 2 thread running) so I recompiled a 64 bit version. I'm all for sharing, but don't want any trouble.

As I'm testing the result, I'm hitting one problem. My benchmarks are running, but here is the preliminary:
DL version (binary for windows) runs a test in 350 seconds
Compiled 32 version (in release, fully optimized) runs the same test in 895 seconds.

This is baffling me. Anybody has any clue? Does the source actually match what was used to build it? (I may have done a dumb mistake, worked on this instead of sleeping... but I typically know what I'm doing with code...)

These results are king of killing the purpose of building a faster version... If the original is still 2-3 times faster, tough to beat!

Also, this is more technical, but here we go.
Panomatic seems to have 2 phases in the same way that Sift does; 1st find control points. 2nd, match points between images and purge everything else.
In Panomatic, the 2nd phase is awfully long, taking over 90% of the processing time. It seems that one major difference between sift and surf in their classic impementation is that in sift, it is done single thread and in one global run, while for surf, it is done per pair of images, multi thread. The pair thing is killing me since I typically shoot 51 images per pano.

Now, the question for the experts. Is that second phase the same\similar\completely different between autopanoSIFT-c and Panomatic? Could the second one be improved with the way the first one was coded?

There you go. Hope this mail is not too long.

nick

--
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@...
To unsubscribe from this group, send email to hugin-ptx%2Bunsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Panomatic

2009-11-20T19:18:46Z

Hi,

Many questions about panomatic (btw, still targetting to setup and help on windows, but this itched a little more)

First, is there a reason that the panomatic project on SF has files but no source?

Second, if I don't want to get into trouble with patent... where is the limit?

- Publishing the source?

- Contributing a new version?

- Uploading\encouraging people to use it?

I'm asking because I was limited on the 32 bit version because of the memory limit (only 1 or 2 thread running) so I recompiled a 64 bit version. I'm all for sharing, but don't want any trouble.

As I'm testing the result, I'm hitting one problem. My benchmarks are running, but here is the preliminary:

DL version (binary for windows) runs a test in 350 seconds

Compiled 32 version (in release, fully optimized) runs the same test in 895 seconds.

This is baffling me. Anybody has any clue? Does the source actually match what was used to build it? (I may have done a dumb mistake, worked on this instead of sleeping... but I typically know what I'm doing with code...)

These results are king of killing the purpose of building a faster version... If the original is still 2-3 times faster, tough to beat!

Also, this is more technical, but here we go.

Panomatic seems to have 2 phases in the same way that Sift does; 1st find control points. 2nd, match points between images and purge everything else.

In Panomatic, the 2nd phase is awfully long, taking over 90% of the processing time. It seems that one major difference between sift and surf in their classic impementation is that in sift, it is done single thread and in one global run, while for surf, it is done per pair of images, multi thread. The pair thing is killing me since I typically shoot 51 images per pano.

Now, the question for the experts. Is that second phase the same\similar\completely different between autopanoSIFT-c and Panomatic? Could the second one be improved with the way the first one was coded?

There you go. Hope this mail is not too long.

nick

Re: Masking in hugin

2009-11-19T19:39:03Z

On Nov 20, 4:13 am, Seb Perez-D <sbprzd+...@...> wrote:
>
> > That being said, the gimp solution is not so nice for positive
> > masking. Then again, neither is the inkscape approach. In both cases,
> > we basically have to erase the desired area from all pano layers
> > except the current one. That's a lot of boring, manual work when there
> > are many layers.
>
> What I do in those cases is to add a layer on the enblended panorama,
> add a black mask and paint in the positive parts.

Thank you for another very good tip! I'm not very good with gimp but
it looks like it's time I learn a little more.

Cheers!
Tim.

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Thank you for Hugin!

2009-11-19T18:14:12Z

Hey all,

I've produced the first pano I am really happy with, and I'm loving
hugin more and more everyday!

So I'd like to say a big "Thank you" to all developers for making such
a fantastic tool, and for making me have so much fun with it; you guys
rock!

Cheers!
Tim.

PS: the pano in question:
http://www.flickr.com/photos/29200847@N06/4118896292/

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: 2009.4.0 release notes proof reading/translation

2009-11-19T15:44:37Z

On Thu 19-Nov-2009 at 23:58 +0100, Eduardo Pérez wrote:
>Attached is the Spanish translation; I did not find any mistakes at the
>original, by the way.

Thanks, I've added it to the site.

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: 2009.4.0 release notes proof reading/translation

2009-11-19T14:58:00Z

Attached is the Spanish translation; I did not find any mistakes at the
original, by the way.

On Mon, 2009-10-19 at 13:14 +0100, Bruno Postle wrote:
> Hi all, there are some initial release notes for 2009.4.0 here:
>
> http://hugin.sourceforge.net/releases/
> http://hugin.svn.sourceforge.net/viewvc/hugin/htdocs/releases/2009.4.0/en.shtml
>
> Suggestions for improvement and translations welcome.
>

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Hugin-2009.4.0 notas de la versión

Hugin-2009.4.0 notas de la versión

Hugin es un generador de panorámicas y más.

Cambios desde 2009.2.0

La última versión fue hace escasamente un mes, pero teníamos listo un montón de nuevas funcionalidades. Por eso, fieles a nuestra intención de seguir el desarrollo de cerca con versiones más frecuentes, Hugin llega con dos nuevas características importantes, así como las habituales correcciones y mejoras incrementales:

Calibración automática de objetivos

Hugin ya es una herramienta estupenda para calibrar objetivos; al empalmar una panorámica, Hugin automáticamente calculará la distorsión de barril, el viñeteado, y el ángulo de visión de cualquier objetivo. Ademas, hay todo lo que un usuario avanzado pueda desear: objetivos diferentes se calibran en un único proyecto, los ojos de pez y los objetivos descentrables no suponen ningún problema para el optimizador de Hugin.

Sin embargo, empalmar una panorámica no es la única manera de calcular los parámetros de un objetivo; la distorsión de barril transforma líneas rectas en curvas, y por tanto descubrir cómo enderezarlas de nuevo es suficiente para calibrar un objetivo de forma precisa - Todo lo que se necesita es un objeto con muchas líneas rectas, tal como un edificio moderno, y una o varias fotografías.

Este año Tim Nugent fue contratado por Google Summer or Code para añadir una nueva herramienta a Hugin llamada calibrate_lens, que toma esas fotos como entrada y produce parámetros de calibrado como salida. Todavía no hay una interfaz gráfica, y la herramienta de línea de comandos aún requiere trabajo para producir una salida compatible con Hugin, pero esta versión proporciona una base para construir futuras herramientas.

Limpieza de puntos de control

Hugin alinea las fotos usando un sistema de puntos de control; son características de la escena que aparecen en cada par de fotos solapadas. Normalmente sólo son necesarias un puñado de características para obtener un buen resultado, pero tienen que ser identificadas - Esto puede hacerse bien indicándolas en la pestaña Puntos de Control de Hugin o bien usando uno de los módulos generadores de puntos de control automáticos tales como autopano-sift-C o pan-o-matic.

Estos generadores de puntos de control son increíblemente útiles, pero aun así cometen errores que son obvios para el ojo humano. Ahora Hugin filtra los puntos de control generados automáticamente para eliminar aquellos que sean estadísticamente improbables. El mismo filtro puede usare para 'limpiar' un proyecto existente en la pestaña Imágenes, y está disponible como herramienta automatizable para la línea de comandos llamada cpclean.

Idiomas

La aplicación Hugin se traduce a veinte idiomas, y la mayor parte de esas traducciones han sido actualizadas para esta versión.

Otras mejoras

Esta versión también tiene las mejoras incrementales habituales: la compilación para Windows, Linux y OS X es ahora más fácil, se han corregido algunos errores que sólo se presentaban en circunstancias oscuras, la pestaña Imágenes muestra ahora más metadatos EXIF útiles de las fotos, se ha actualizado el manual para recoger las nuevas funcionalidades y ahora se muestra en el navegador preferido, se ha corregido un error que confundía al empalmador con rectángulos de recorte invertidos, y también se ha eliminado un molesto problema que hacía que se perdiese la configuración de los puntos de control entre sesiones.

Generadores de puntos de control

Hugin aún no se distribuye con un generador de puntos de control 'Libre de Patentes'. Así que necesitarás indicar los puntos de control manualmente - No es tan difícil como suena - o instalar y configurar como 'módulos' uno de los siguientes generadores de puntos de control:

autopano-sift-C
panomatic
match-n-shift
Autopano-SIFT
Autopano versión freeware

Actualización

La actualización desde versiones anteriores de Hugin no debería causar quebraderos de cabeza. Si tienes problemas con configuraciones antiguas, se pueden restaurar en Preferencias haciendo click sobre 'Cargar predeterminados'.

Para usuarios que compilen desde el código fuente: téngase en cuenta que la versión mínima de wxWidgets soportada es ahora la 2.7.0, libpano13 tiene que ser al menos la versión 2.9.14, y Hugin requiere GLEW "the OpenGL Extension Wrangler Library", freeglut "the OpenGL utility toolkit", y libGLU "the OpenGL utility library".

El soporte para la librería obsoleta libpano12 ha finalizado.

Mira los ficheros README y INSTALL_cmake para más información.

Gracias a todos los que han contribuido a esta versión y a los miembros de la lista de distribución hugin-ptx, demasiados para mencionarlos a todos aquí.

Puedes encontrar Hugin en http://hugin.sourceforge.net/.

Puedes descargar el código fuente de Hugin desde sourceforge: http://sourceforge.net/projects/hugin/files/hugin/.

Re: Re: Masking in hugin

2009-11-19T12:13:51Z

On Thu, Nov 19, 2009 at 18:52, Timothee <timothee.groleau@...> wrote:
>
> That being said, the gimp solution is not so nice for positive
> masking. Then again, neither is the inkscape approach. In both cases,
> we basically have to erase the desired area from all pano layers
> except the current one. That's a lot of boring, manual work when there
> are many layers.

What I do in those cases is to add a layer on the enblended panorama,
add a black mask and paint in the positive parts.

Cheers,

Seb

--
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx