headers
SourceForge.net | 1 Oct 2004 02:22
Picon
Favicon

[ hugin-Bugs-1038138 ] after auto add image slides to totally different area

Bugs item #1038138, was opened at 2004-09-30 20:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=550441&aid=1038138&group_id=77506

Category: interface
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Marek Januszewski (specu)
Assigned to: Nobody/Anonymous (nobody)
Summary: after auto add image slides to totally different area

Initial Comment:
In hugin_2004_09_15-01_30_win32.zip, I have auto fine
tune, auto add and auto estimate on, and zoom is 200%.
After point is autoadded, image slides to a totally
different area then where the point was added (in my
case left upper area). Expected behaviour is to slide
the image so that the last added points were added.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=550441&aid=1038138&group_id=77506
Permalink | Reply | 0 comments |
headers
Mark | 1 Oct 2004 09:27

Problems with Autopano-Sift, Hugin, Enblend workflow for windows

I'm trying to put together a reasonable install/process workflow for windows
that we can use.

I've grovelled the archives with little to show, of course my groveller may 
be v1.0...

Here's what I encounter (please send updates to show where I must have
messed up):

Installation (XPsp2)

1. Install Autopano-sift 
(http://user.cs.tu-berlin.de/~nowozin/autopano-sift/autopano-sift-1.7-win-1.exe).
2. Install Mono/GTK# 
(http://forge.novell.com/modules/xfcontent/file.php/monowin32/Mono%20Win32%20Combined%20Installer/v1.0.2.7/mono-1.0.2-gtksharp-1.0.2-win32-0.7.exe)
3. Install Hugin 
(http://hugin.sourceforge.net/snapshots/windows/hugin_2004_09_15-01_30_win32.zip)
4. Install Enblend 
(http://www-cad.eecs.berkeley.edu/~mihal/enblend/enblend-1.3.zip)

Running autopano-sift:
1. (Ugly, first crack, you can improve on this) in CMD do (yeah, default 
places):
    "c:\Program Files\Mono-1.0.2\bin\mono" "c:\Program 
Files\Autopano-SIFT-1.7\autopanog.exe"
    to get the autopano GUI started. Watch the error/warnings fly by. One
    would think that proper programming would NEVER produce these...
2. Load the images. The UI isn't standard, but you can get there...
3. Click "Compute"...
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mark | 1 Oct 2004 10:07

Re: Problems with Autopano-Sift, Hugin, Enblend workflow for windows

Instead of running mono and autopanog, I've tried hugin

I add the images, click on CreateCtrlPoints and get a popup asking for 
autopano / frontend script.

1) Navigate to Autopano sift directory and point to autopano.exe, it dies 
with an exception that I can't get to since the window closes so fast.
2) Point to GenerateKeys. Ditto.
3) Point to win-autopano-sift.vbs. Can't execute with error 193.
4) Point to win-autopano-sift-cmdline. Can't execute with error 193.

I'm stuck!

----- Original Message ----- 
From: "Mark" <nestor <at> nwlink.com>
To: <ptx <at> email-lists.org>
Sent: Friday, October 01, 2004 12:27 AM
Subject: Problems with Autopano-Sift, Hugin, Enblend workflow for windows

> I'm trying to put together a reasonable install/process workflow for 
> windows
> that we can use.
>
> I've grovelled the archives with little to show, of course my groveller 
> may be v1.0...
>
> Here's what I encounter (please send updates to show where I must have
> messed up):
>
> Installation (XPsp2)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Runge | 1 Oct 2004 10:17

Re: Problems with Autopano-Sift, Hugin, Enblend workflow for windows


Hi Mark,
I'm using autopano-sift 1.7/hugin/enblend on wxpSP2.
See my comments between the lines

>
>Installation (XPsp2)
>
>1. Install Autopano-sift
>(http://user.cs.tu-berlin.de/~nowozin/autopano-sift/autopano-sift-1.7-win-1.exe).

>2. Install Mono/GTK#
>(http://forge.novell.com/modules/xfcontent/file.php/monowin32/Mono%20Win32%20Combined%20Installer/v1.0.2.7/mono-1.0.2-gtksharp-1.0.2-win32-0.7.exe)
I didn't installed this one

- Install pano tools (at least pano12.dll and PTOptimiser)

>3. Install Hugin
>(http://hugin.sourceforge.net/snapshots/windows/hugin_2004_09_15-01_30_win32.zip)
>4. Install Enblend
>(http://www-cad.eecs.berkeley.edu/~mihal/enblend/enblend-1.3.zip)
>
>Running autopano-sift:

>1. (Ugly, first crack, you can improve on this) in CMD do (yeah, default
>places):
>    "c:\Program Files\Mono-1.0.2\bin\mono" "c:\Program
>Files\Autopano-SIFT-1.7\autopanog.exe"
>    to get the autopano GUI started. Watch the error/warnings fly by. One
>    would think that proper programming would NEVER produce these...
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Runge | 1 Oct 2004 10:21

Re: Problems with Autopano-Sift, Hugin, Enblend workflow for windows


Hi Mark,
I didn't managed so far to run autopano-sift directly out of hugin on
wxp.
autopano(without sift! http://www.le-geo.com/kolor/autopano/ ) will work
well directly out of hugin, but I got better points using autopano-sift
like described in my previous mail.

best, mike

On 10/1/2004, "Mark" <nestor <at> nwlink.com> wrote:

>Instead of running mono and autopanog, I've tried hugin
>
>I add the images, click on CreateCtrlPoints and get a popup asking for
>autopano / frontend script.
>
>1) Navigate to Autopano sift directory and point to autopano.exe, it dies
>with an exception that I can't get to since the window closes so fast.
>2) Point to GenerateKeys. Ditto.
>3) Point to win-autopano-sift.vbs. Can't execute with error 193.
>4) Point to win-autopano-sift-cmdline. Can't execute with error 193.
>
>I'm stuck!
>
>----- Original Message -----
>From: "Mark" <nestor <at> nwlink.com>
>To: <ptx <at> email-lists.org>
>Sent: Friday, October 01, 2004 12:27 AM
>Subject: Problems with Autopano-Sift, Hugin, Enblend workflow for windows
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark | 2 Oct 2004 07:27

Re: Problems with Autopano-Sift, Hugin, Enblend workflow for windows

Thanks for your pointers.  Further investigation (read: insane amount of 
grovelling)
showed that an app that I use for archiving to CD/DVD had installed and 
registered
an ancient version of a DLL. Reinstalling the latest version of Wscript gave 
me the
power to drag-n-drop onto the .vbs scripts.

Once I get things into hugin:
1. I can't use LoadExif; it apparently only works from .jpg's while 
autopano-sift
    only reads .tiff.
2. Exiting HUGIN always results in an access violation. It'd be nice if 
there were
    PDB symbols around so I could debug it... Is there a Visual Studio 
project
    (sorry!) around for it? I hate to duplicate someone else's efforts 
there...
3. Running with PTOptimizer results in the apply/cancel dialog boxes 
appearing but
    you can never close them. Worse, you can't close hugin either.
4. It'd be nice to get hugin to call out to autopano-sift to get the control 
points generated.
    From what I can divine, it is calling CreateProcess on the .vbs file. 
There are two
    problems in this. First, the name being passed is not properly quoted 
(if there's spaces
    in the path, like Program_Files, it fails); this isn't a problem in most 
cases, but it's
    possible to spoof it. Second, it is treating the .vbs file as an
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jake Kauth | 1 Oct 2004 17:32
Picon
Favicon

high colorimetry, auto-luminance for stop-motion work

Hello all!

My friend Mark is starting a stop-motion animation project, and we
talked several minutes yesterday about the problems he will face.

He plans to use a high-resolution digital camera to capture the
stills for the animation, but one of the problems is frame-to-frame
luminance.  Even with infinitesimal color or brightness variance,
a "throbbing" or pulsing effect will appear if the individual frames
are not color-corrected.

I remember reading something like this on the list, but I don't recall
exactly when... so my question is this:  could Panotools & friends be
used to do micro-adjustments of luminance to force many frames to
match a reference frame baseline?  Any suggestions on technique or 
pipeline?

Secondly, Mark would love to shoot the stop-motion shots with multiple
exposure brackets, and recombine them into one single image with very 
high
color ranges.  The idea is to get more of the color richness of analog 
film
without the terrible turn-around time.

Thanks for your advise!

jake
******
(Continue reading)

Permalink | Reply | 1 comment |
headers
Markku Kolkka | 3 Oct 2004 00:50
Picon
Picon

Re: high colorimetry, auto-luminance for stop-motion work

Jake Kauth kirjoitti viestissään (lähetysaika perjantai, 1. 
lokakuuta 2004 18:32):
> Secondly, Mark would love to shoot the stop-motion shots with
> multiple exposure brackets, and recombine them into one single
> image with very high
> color ranges.

This program was mentioned some time ago on this list: 
http://auricle.dyndns.org/ALE/

--

-- 
 Markku Kolkka
 markku.kolkka <at> iki.fi
Permalink | Reply | 0 comments |
headers
Douglas Wilkins | 3 Oct 2004 10:35
Picon

Problem - Changes to CVS - 040930

Hi there,
The latest changes checked into CVS do not compile under linux (GCC
3.4.1). 
Specifically, if you want to use this in PointMatching.h (line 191):

__gnu_cxx::random_sample(feat1.begin(), feat1.end(),
           ^^^^^^^^^^^^^
you need this:

// BAD: sgi stl extension
#include <ext/algorithm>

Not sure what other effects re-including this header will have on other
platforms but the attached patch reverts the change. hugin compiled with
this patch seems to run correctly.

Perhaps the better fix might be to add random_sample to stl_utils ?

regards,
Doug

PS I like the new logo! :-)
Attachment (hugin-stl.patch): text/x-patch, 432 bytes
Permalink | Reply | 3 comments |
headers
Pablo d'Angelo | 3 Oct 2004 12:20
Picon

Re: Problem - Changes to CVS - 040930

On Sun, 03 Oct 2004, Douglas Wilkins wrote:

> Not sure what other effects re-including this header will have on other
> platforms but the attached patch reverts the change. hugin compiled with
> this patch seems to run correctly.
> 
> Perhaps the better fix might be to add random_sample to stl_utils ?

Yes, I'll do that. 

> regards,
> Doug
> 
> PS I like the new logo! :-)

Me too. It was created by Luca Vascon.

ciao
  Pablo
--

-- 
http://wurm.wohnheim.uni-ulm.de/~redman/
Please use PGP.
Permalink | Reply | 2 comments |

Gmane