Yuval Levy goo...@levy.ch wrote:
Almost a year ago I proposed a small change to how Hugin handles the caching
of images [0]. It's a simple and dumb workaround and indeed in the ensuing
discussion improvements such as the using of wxThreads were discussed.
[...]
This does not help for the
Excellent! Now it all runs smoothly. Your solution to omit the
'Autopano-SIFT-C (multirow/stacked)' entry is actually the cleanest
solution, since the creation of panoramas from brackets with special
treatment for stacks is something quite advanced anyway. Best to leave
it out of the
Hi Yuv,
Almost a year ago I proposed a small change to how Hugin handles the caching
of images [0]. It's a simple and dumb workaround and indeed in the ensuing
discussion improvements such as the using of wxThreads were discussed.
Moreover, the integration of layout mode was of higher
Hi Jim,
Sorry, my fault. :( I got it working. I was in the wrong folder.
Thomas, no more black image but it did get mirrored horizontal (left to right)
image. It is true the image was reversed and that information was stored in
the
Exif data but I did not expect fulla to use that data.
Hi Jim
Only to find the optimization of vignetting is broken in Hugin when using
images
that have selection(crop).
I discovered this by using images that have some areas on the edge of the
images
that I do not want in the final pano because they don't belong. I used the
used
the crop
Am Sonntag 26 September 2010 schrieb Bruno Postle:
The Hugin 2010.2.0 branch doesn't build on fedora f14 (gcc-4.5.1
glibc-2.12.90), because some libraries need to be explicitly linked
with vigra_impex. I can fix this here by changing this line in
src/foreign/vigra/vigra_impex/CMakeLists.txt:
Pablo d'Angelo pablo.dangelo at web.de wrote on 2009-09-20:
[...]
6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream;
wait for vigra-1.7 with the changes; then make Hugin work with
[vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work
to go into
Am Sonntag 26 September 2010 schrieb T. Modes:
Hi Yuv,
Almost a year ago I proposed a small change to how Hugin handles the
caching of images [0]. It's a simple and dumb workaround and indeed in
the ensuing discussion improvements such as the using of wxThreads were
discussed.
On Sep 26, 9:18 am, T. Modes thomas.mo...@gmx.de wrote:
That's simply wrong. The multirow/stack option has also advantages for
simple panoramas. It is faster (in most cases) in comparision to
match all images at once, and more important it reduces drastically
the risk of getting wrong
Hi all!
I am working on a Python script to go between hugin and the CPGs. I'm
using hugin for windows 2010.2.0. I can call the script if I give it
a .cmd extension and add the rather ugly first line:
@setlocal enableextensions python -x %~f0 %* goto :EOF
Then it works as intended. But I can't
Hi Thomas,
On September 26, 2010 04:54:50 am T. Modes wrote:
Even deactivated it crashes on Windows. I can not load projects, add
images - crash.
sorry for that. Are you sure this change is the culprit? There have been
crash reports from right after the merge of the two GSoC2010 branches
Perhaps this is a silly question but I cannot manage to get my
panoramas saved as one continuous image. When I hit create panorama or
stitch all I get is multiple images and no stitched panorama.
Any idea of what I am doing wrong?
Cheers
J
--
You received this message because you are
Hi Yuv,
Even deactivated it crashes on Windows. I can not load projects, add
images - crash.
sorry for that. Are you sure this change is the culprit? There have been
crash reports from right after the merge of the two GSoC2010 branches [0]
Yes, I'm sure, your changeset is the culprit.
Just removing it from the installer doesn't mean the user can't use it
in the future. It's just a matter of creating a new CPG entry and
populating it with the desired calls. I agree that stacks are a good
thing, that's why I tried to find a way of keeping the entry by
replacing the two-step
On Sep 26, 1:25 pm, jakob_g jakobg...@gmail.com wrote:
Perhaps this is a silly question but I cannot manage to get my
panoramas saved as one continuous image. When I hit create panorama or
stitch all I get is multiple images and no stitched panorama.
Any idea of what I am doing wrong?
In
On Sat, 2010-09-25 at 23:33 -0400, Yuval Levy wrote:
Almost a year ago I proposed a small change to how Hugin handles the caching
of images [0]. It's a simple and dumb workaround and indeed in the ensuing
discussion improvements such as the using of wxThreads were discussed.
Even if it is
On Sep 26, 6:04 pm, T. Modes thomas.mo...@gmx.de wrote:
You can use the multi-row detector also with other cp detectors (like
panomatic, select then one-step detector).
But using the two-step approach (involving autopano/generatekeys from
autopano-sift-c) has advantages. In this case each
Hi Thomas,
On September 26, 2010 11:58:11 am T. Modes wrote:
Yes, I'm sure, your changeset is the culprit.
Changeset 22828bb9df09 works ok, but changeset d14b0775fbfa crashes.
You may be sure but I am not so sure - I had this kind of symptoms before
applying this changeset. They appeared a
On Sun 26-Sep-2010 at 12:38 +0200, Kornel Benko wrote:
Am Sonntag 26 September 2010 schrieb Bruno Postle:
The Hugin 2010.2.0 branch doesn't build on fedora f14 (gcc-4.5.1
glibc-2.12.90), because some libraries need to be explicitly linked
with vigra_impex.
set(EXTRA_LIBS)
find_library(RT_LIB
Am Samstag 25 September 2010 schrieb Yuval Levy:
Hi all,
I have committed smart undo to the default branch in the Hugin repository.
Because it changes the behavior of the application, I have made it a
preference. Users have to enable it in the preferences panel (it is
disabled by
On Sat 25-Sep-2010 at 08:43 -0700, kfj wrote:
On Sep 25, 2:52 pm, Bruno Postle br...@postle.net wrote:
This is an older version of match-n-shift, recent versions use
autopano-sift-c directly instead of generatekeys/autopano.
Thanks for pointing that out. Where could I get a recent version of
On Sun 26-Sep-2010 at 10:20 -0700, kfj wrote:
I'd like to understand this process properly. I ran a test with a
panorama from 8 brackets of 3 images each, using align_image_stack as
the stack aligner and the generatekeys/autopano combination for the
interstack alignment. First CPs were
Hullo Oskar,
On Sep 25, 11:08 pm, Oskar Sander oskar.san...@gmail.com wrote:
Hi!
No, it is yet another format, I think they call it photomerge composition
file, see here for example:
http://graphicssoft.about.com/cs/photoshop/qt/csphotomerge.htm
I have been trying to find an xxx.pmg file
Hi Emad,
On September 25, 2010 02:09:49 am Emad ud din Btt wrote:
First I load images into Autopano Pro Trial and get this first image in
very less time. Than I export its PTO file. Load it in hugin and its final
image is still intact or pre-alligned. Autopano removes CPs. I manually
add more
On September 26, 2010 03:18:49 am T. Modes wrote:
The multirow/stack option has also advantages for
simple panoramas.
it is IMHO probably the best default choice. Advanced users can fiddle with
other things if they want.
Yuv
signature.asc
Description: This is a digitally signed message
Hi Emad,
On September 25, 2010 01:41:14 am Emad ud din Btt wrote:
Its open source but I think this feature is for developers.
that's a misconception. Open Source has more advantages for the users than
for the developers. Contrast the history of Freehand [0] with that of Blender
[1] and
On September 26, 2010 05:59:04 pm Kornel Benko wrote:
Yuv, wenn ich smart undo aktiviere, habe ich den in einer anderen mail
erwähnten crash. Brauchst Du genaueren stack-trace?
Kornel
P.S.
Diese direkte mail an Dich ist Absicht.
Hi Kornel,
obviously not a direct mail to me, and
On Sat, Sep 25, 2010 at 00:41, Emad ud din Btt xyzt...@gmail.com wrote:
Normal user will not want to go and add %p %o %s in autopano-sift parameters
for multirow pano.
What are you talking about?
He will want to just load pics and get pano :)
That is essentially the kind of experience I
Yuv,
APPro beats Hugin in alignment hands down. There is no contest there. It
matters not what CP detector one uses (with exception of GeoDiasy (untested)).
Feed it the same images from two different directories so there is no
contamination, and APPro comes out on top every time.
In
29 matches
Mail list logo
