How do I get past this?
I'm brief here because I don't know what information is important. So ask
and I'll try to be as complete as possible in my reply.
Tom Sharpless wrote:
> I've posted the following changes to the autopano source tree. 1) a
> new file, APSCmain.c,
Beside the warnings I've posted two weeks ago or so, on my Linux box
(openSuSE 10.3, x86_64) it spits out a bunch of new warnings:
[ 90%] Building C object CMakeFiles/APSC.dir/APSCmain.o
autopano-sift-C.r2799/APSCmain.c: In function ‘WritePTOFile’:
autopano-sift-C.r2799/APSCmain.c:435: warning: cast to pointer from integer of different size
autopano-sift-C.r2799/APSCmain.c:488: warning: cast from pointer to integer of different size
autopano-sift-C.r2799/APSCmain.c:488: warning: cast from pointer to integer of different size
autopano-sift-C.r2799/APSCmain.c:492: warning: cast from pointer to integer of different size
autopano-sift-C.r2799/APSCmain.c:492: warning: cast from pointer to integer of different size
autopano-sift-C.r2799/APSCmain.c: In function ‘main’:
autopano-sift-C.r2799/APSCmain.c:746: warning: comparison with string literal results in unspecified behaviour
autopano-sift-C.r2799/APSCmain.c:759: warning: comparison with string literal results in unspecified behaviour
Linking C executable APSC
Rgds,
Stephan.
Hi Ken,
you should try that with the latest build, beta 3 is outdated. Yuv has a
fine little list of available downloads here:
<http://panospace.wordpress.com/downloads/>
If I understand your description correctly you tried to set a CP very
close to the image border, maybe it's the left border. You possibly
activated both options (auto fine-tune, auto estimate) to compute an
optimal pair of CPs. My guess is that hugin now tries to set a CP
outside the actual image frame and fails. A wild guess though.
Can you just deactivate the optimizing options (auto fine-tune / auto
estimate) and manually add your CP? You could drag that around or use
the boxes at the bottom of that tab to enter a different value for the x
and y coordinates.
Does that workaround help in any way?
Carl
- - -
Note to Yuv related to "DISCLAIMER - Never trust a software
download...": md5 is available on OS X, a simple check on 10.3.9:
man md5
...outputs the usual man page
However I also found a related description at Apple's knowledge base
that suggests openssl:
<http://docs.info.apple.com/article.html?artnum=75510>
/usr/bin/openssl md5 /Users/carl/Desktop/hugin0.7_svn2765_20080202.dmg
MD5(/Users/carl/Desktop/hugin0.7_svn2765_20080202.dmg)=
499bed5a12e4bdfcc3d0660a5ae3eb08
which gives me the same result as using md5
md5 /Users/carl/Desktop/hugin0.7_svn2765_20080202.dmg
MD5 (/Users/carl/Desktop/hugin0.7_svn2765_20080202.dmg) =
499bed5a12e4bdfcc3d0660a5ae3eb08
Somewhere else I found this description:
Using hdiutil to Work with System Images
[...] To verify an image against its internal checksum:
$ hdiutil verify myimage.img
This returns some checks and
hdiutil: verify: checksum of
"/Users/carl/Desktop/hugin0.7_svn2765_20080202.dmg" is VALID
You might want to add a short description on that paragraph how to
easily get the correct path to the .dmg file (actually it comes as a
.dmg.gz but I unpacked it first), something like that:
type 'md5 ' (without the single quotes) into a terminal window
(Terminal.app is in Applications/Utilities/), then just drag the file
into that same window. The provided checksum is for the .dmg file, so if
the download didn't uncompress automatically you have to double click
the .dmg.gz first.
Your capability for guessing approaches prescience :-)
You guessed the exact situation. Deactivating auto fine-tune and auto estimate
let me add a few control points. Only added 3 or 4 to each side of the image
that didn't have control points added by Hugin. The image is an inside wall
with a small framed photograph in the middle. I used faint shadows on slightly
textured paint but Hugin and nona completed the stitch.
Thanks -- I'll take a look a the new (to me) stuff in the downloads area.
Ken
I had already seen these errors when building (standard) autopano, and
have not found a problem with the resulting program (it's a warning).
I suggest that autopano and generatekeys are still compiled. As you
say, they can still be used for legitimate reasons.
Cheers,
Seb
If I only knew the next lottery numbers!
> You guessed the exact situation. Deactivating auto fine-tune and auto estimate
> let me add a few control points. Only added 3 or 4 to each side of the image
> that didn't have control points added by Hugin. The image is an inside wall
> with a small framed photograph in the middle. I used faint shadows on slightly
> textured paint but Hugin and nona completed the stitch.
Great that it helped.
>
> Thanks -- I'll take a look a the new (to me) stuff in the downloads area.
I tried but wasn't able yet to reproduce this behaviour in the latest
Mac svn. So if that same problem still exists using a newer build please
report that as a bug on hugin's bugtracker. It then would help a lot if
you were able to post the project files somewhere so I can test with the
same set of files.
Carl
Can you run your test on just the three relevant image files? That's
all that where really involved. I could upload them to my web site
along with the pto files now if that will help.
It will be a while before I get to the new downloads...
Carl
http://pancyl.com/images/CPTest/left.TIF
http://pancyl.com/images/CPTest/middle.TIF
http://pancyl.com/images/CPTest/right.TIF
http://pancyl.com/images/CPTest/Inside1.pto
http://pancyl.com/images/CPTest/Inside1.pto.mk
The pto and mk files are the project files that
I eventually used for a successful stich.
The TIF's are 20meg...
Let me know what you find out...
Tom Sharpless wrote:
> Please check this out on Linux and OSX.
When running it with the options as described in the original
posting from within hugin it stops with an error message stating
can't open /tmp/ap_rese7935M0.oto
Right, in my tmp is only an ap_rese7935M file, without the 0.oto
extension.
Any idea what went wrong ?
I'm on openSuSE 10.3, x86_64.
Rgds,
Stephan.
> Hi all,
>
> Tom Sharpless wrote:
> > Please check this out on Linux and OSX.
> When running it with the options as described in the original
> posting from within hugin it stops with an error message stating
> can't open /tmp/ap_rese7935M0.oto
> Right, in my tmp is only an ap_rese7935M file, without the 0.oto
> extension.
>
> Any idea what went wrong ?
You have set Hugin to use the Autopano from A. Jenny. This is not call compatible with the one for autopano-sift (-c)
This is confusing, and I'm tempted to remove support for the (windows only) autopano.exe by A. Jenny from Hugin,
once autopano-sift-c works fine.
ciao
Pablo
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
it's unsupported, i don't even know if we have the code, and thanks to
the efforts of Tom and Bruno it is now absolutely redundant, like my VBS
script too.
I vote for remove of both redundant things.
Yuv
You have set Hugin to use the Autopano from A. Jenny. This is not call compatible with the one for autopano-sift (-c) This is confusing, and I'm tempted to remove support for the (windows only) autopano.exe by A. Jenny from Hugin, once autopano-sift-c works fine. ciao Pablo