Re: [hugin-ptx] One photo taken without tripod

[Rogier Wolff]

On Wed, May 27, 2015 at 11:35:31PM +0100, 'boomslang' via hugin and other free 
panoramic software wrote:
> Hi all,
> 
> 
> I am working on a 360 degree panorama. All but the last photo are taken using 
> a panorama head on a tripod. The largest control point distances all involve 
> this last photo.
> 
> How do I tell Hugin to optimise TrX/TrY/TrZ only for this specific photo? 
> Currently I use Hugin 2014.

I haven't been using Hugin for a while. So I've forgotten where
everything is exactly.

In the advanced settings for "optimization", you can manually select
what to optimize.

The workflow I'd recommend would be to optimize normally (maybe even
with the assistant: no special stuff necessary), and only then add the
last picture to the project.

Next, in the advanced settings, you optimize nothing except the
roll/pitch and fov of the last picture, and the TrX/TrY/TrZ that you
mentioned. That should make that last picture "fit right in".

Roger. 

-- 
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
- Datarecovery Services Nederland B.V. Delft. KVK: 30160549 -
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20150528064107.GE16445%40bitwizard.nl.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mosiac model - convergence, accuracy?

[Terry Duell]

Hello Paul,

On Wed, 27 May 2015 19:45:54 +1000, bugbear   
wrote:


[snip]

I did use the new 'EditCP' tool in hugin-2015.0.0, which made finding  
and removing the worst of the CPs an easy task.


How did you do this? Each image on the preview is tiny (since I have 30   
images), so I don't

see how you got benefit from the tool.



I do use a large screen which probably helps, and just increase the FOV as  
much as I can while still keeping the bad points in view.


[snip]



Adding just one vertical line, in the one image, is all that is needed   
to fix it.

Mean error 0.5, max 2.9.


Perfect!

The result is also surprisingly square, given the lack of all but 1  
vertical and horizontal CPs.


Well, except it's upside down...



Yes, but not unexpected as most of the images in the project I received  
were shot in that orientation. The simplest solution would be to stitch  
and then do a 180 rotation in an image viewer.



Cheers,
--
Regards,
Terry Duell

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/op.xzbhauxirs0ygh%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] wxWidgets Debug Alert popup in Hugin, how can I sort this out?

[Mike Mackinven]

Here's the screenshot that plagues me every time I want to use Hugin. 

How can I fix this?




-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dcb48b40-38a3-4a12-a297-78560e4a296a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] One photo taken without tripod

['boomslang' via hugin and other free panoramic software]

Hi all,


I am working on a 360 degree panorama. All but the last photo are taken using a 
panorama head on a tripod. The largest control point distances all involve this 
last photo.

How do I tell Hugin to optimise TrX/TrY/TrZ only for this specific photo? 
Currently I use Hugin 2014.

Thanks in advance!

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1432766131.97419.YahooMailBasic%40web171306.mail.ir2.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mosiac model - convergence, accuracy?

[Roger Broadie]

Hello Paul,

I thought your panorama was pretty good, but I don’t think you have 
fully overcome the problems of parallax resulting from creases and 
folds.  The main cause, I suspect, is the camera tilt of 6 deg plus or 
minus from the vertical that the pitch values of the optimiser imply.


So while I would not normally expect to include the Plane Yaw and Pitch 
parameters in a truly planar photomosaic, it did seem worth trying them 
here.  They do seem to help.


I attach panoa.pto, based on your file, which takes that approach and 
also includes some tuning of the control points and fuller lens 
optimisation.  But I hung on to the h and v points, because I think they 
are one of Hugin’s strengths.  I have resolved some remaining glitches, 
either with added control points – automatic control point finders seem 
to find otherwise featureless areas of grid-lines difficult to deal with 
– or with masking, but have not tried fully to resolve problems with the 
grid-square P25, where the different shapes of the square as captured in 
e.g. images 17 and 23 illustrate graphically the problems of the 
parallax present in places in your images.  The end result yields an 
average error of 1.2 pixels and a maximum of 3.2, for a panorama 
matching that of pano.pto in size.


Broadly, I agree with Terry Duell (Wed, 27 May 2015 at 10:13:42 +1000) 
that the mosaic mode is working OK.  He has given us a pto file (Wed, 27 
May 2015 at 12:34:56 +1000) that does not use the Plane Yaw and Pitch 
parameters.  It has an error of 0.5 average and 2.9 maximum, but is for 
a panorama of only about half the width of yours.  Still pretty good, 
though, even at the full size.


Roger Broadie


-Original Message-
From: paul womack 
To: hugin-ptx@googlegroups.com
Sent: Tue 26 May 2015 12:36:00
Subject:  [hugin-ptx] Mosiac model - convergence, accuracy?

The convergence behaviour of the mosaic model is really quite poor.

I have recently completed shooting a very careful trial, using
a cantilevered tripod (Benbo) over a map on my dining table.
(I shot at less than maximum resolution, at 3 Mp to cut down
the data size)

All the shots (30 in all) are accurately focused and sharp.

I found that for this large image set, it is neccessary
to perform step-wise addition and optimisation
of the images (initially just X and Y).

Simple hoping that the optimiser will just "sort it all out"
doesn't work, at least with the kind of control point
set found by automation. it works OK with "nigh-perfect"
control point sets (I just found ;-)

In practise I found that
as I proceeded, I needed to hand edit a "fairly good"
position of X and Y to get the optimisation to converge at all.

This is doable (since my images form a simple matrix)
but more work than I'd like.

(I also regret that the ctrl-T short cut for "optimise"
is not available on the preview window)

My more significant concern is that my "final" optimisation,
has a disappointingly large error, and (indeed)
shows stitching glitches on final output.

Since my map is nigh 2 dimensional, and I went to considerable
pains to shoot a narrow FOV from a good distance above the
map, I believe that the mosaic model should be able to get
VERY close to perfect on this image set, and yet it doesn't.

I am aware that I may be one of the more extreme users
of the mosaic model; is it believed to be bug free?

I would be able to test this by synthesizing scaled and YPR skewed
sub-images from a high res original (e.g. a giga-pan) and then attempting
to stitch them using mosaic mode.

I would rather not go to this effort unless forced.

I have uploaded the images and project file at

https://www.hightail.com/download/bXBhZEV5VnNreEJEZU1UQw

They will be there for a week. Note that I believe the
map test subject to be in copyright.

  BugBear


--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/55663C15.90809%40ogea.freeserve.co.uk.
For more options, visit https://groups.google.com/d/optout.


panoa.pto
Description: application/ptoptimizer-script

Re: [hugin-ptx] Re: Hugin 2015.0 beta2

[Thomas Pryds]

2015-05-27 19:09 GMT+02:00 T. Modes :

> But there are many language files which needs an update. So all
> translators, please contribute your updated files. Thanks.
>
> The current status is:
> da.po
> 1489 translated messages, 8 fuzzy translations, 3 untranslated messages.
>

Just pushed da.po which should now be at 100% again.

Thomas.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAOC2i35t7pWOUVBdAANGK5bw2_fr%3Dk85W75%3DinVwMDhy3mp9kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2015.0 beta2

[T. Modes]

Am Samstag, 9. Mai 2015 10:27:42 UTC+2 schrieb T. Modes:
>
> Hi all,
>
> after the release of beta 1 of Hugin 2015.0 two weeks ago some bugs have 
> been found and have been fixed.
> So today we are release beta 2
>
> That's a reminder for all translators. Since the release of beta2 only 4 
language files are completed:
de.po 
hu.po 
pt_BR.po 
sk.po
1500 translated messages.

But there are many language files which needs an update. So all 
translators, please contribute your updated files. Thanks.

The current status is:
da.po 
1489 translated messages, 8 fuzzy translations, 3 untranslated messages.
ca_ES.po 
1409 translated messages, 60 fuzzy translations, 31 untranslated messages.
ca...@valencia.po 
1409 translated messages, 60 fuzzy translations, 31 untranslated messages.
cs_CZ.po 
1377 translated messages, 75 fuzzy translations, 48 untranslated messages.
en_GB.po 
76 translated messages, 11 fuzzy translations, 1413 untranslated messages.
fr.po 
1305 translated messages, 118 fuzzy translations, 77 untranslated messages.
it.po 
1433 translated messages, 39 fuzzy translations, 28 untranslated messages.
pl.po 
1310 translated messages, 112 fuzzy translations, 78 untranslated messages.
ru.po 
1311 translated messages, 112 fuzzy translations, 77 untranslated messages.
zh_CN.po 
1346 translated messages, 92 fuzzy translations, 62 untranslated messages.
zh_TW.po 
1300 translated messages, 117 fuzzy translations, 83 untranslated messages.
nl.po 
1337 translated messages, 100 fuzzy translations, 63 untranslated messages.


es.po 
1204 translated messages, 174 fuzzy translations, 122 untranslated messages.
eu.po 
994 translated messages, 262 fuzzy translations, 244 untranslated messages.
fi.po 
783 translated messages, 391 fuzzy translations, 326 untranslated messages.
ja.po 
1094 translated messages, 259 fuzzy translations, 147 untranslated messages.
ro.po 
647 translated messages, 479 fuzzy translations, 374 untranslated messages.
sv.po 
1065 translated messages, 285 fuzzy translations, 150 untranslated messages.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/96b62187-7d0d-410b-b0e2-6f085566ead8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: control point editing/review - feature request

[John Muccigrosso]

+1

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/58a5cbad-840d-4689-b715-efacbd41ead8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] control point editing/review - feature request

[Carlos Eduardo G. Carvalho (Cartola)]

2015-05-26 17:23 GMT-03:00 Paul Womack :

> But if I'm just moving through the list of points I don't want the mouse
> to be in *either* window; I want the focus to be in the list of control
> points. I can then move down through the list of control points with a
> single cursor down key.
>
> As it is I have to click in the CP window, to select a pair, and then
> wiggle the mouse in  the other two windows, and this for every pair, as
> opposed to a single press of cursor down.
>
> The current way is too slow to effectively "batch review" a large set of
> CPs.
>
> I know.
>
> I've tried.
>
> Hence the request.
>
>  BugBear
>

Ok, must agree.


Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CALW1f7j_CGL_7WL8uQR9mfZceY_8boTq9AKzM5yZx%3DJx91PBbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2015.0 beta2

[Frederic Da Vitoria]

2015-05-25 20:17 GMT+02:00 Harry van der Wolf :

*Windows binaries* for the Hugin 2015.0.0 beta2 version are now available.
>
>
> Thanks to Thomas Modes who helped me a lot to get going with the windows
> builds, I have now built 64bit Windows versions.
> The python versions require a pre-installed python 3.4.
>
> Note that these builds will not run on Windows XP 64bit (and neither on
> 32bits windows versions of course).
>
> 64bit installer:
>
> http://sourceforge.net/projects/hugin/files/hugin/hugin-2015.0/HuginSetup_2015.0.0-beta2_64bit.exe/download
>
> 64bit installer with python support:
>
> http://sourceforge.net/projects/hugin/files/hugin/hugin-2015.0/HuginSetup_2015.0.0-beta2_64bit-python.exe/download
>
> 64bit 7z file (simply un7zip to some location and use from there):
>
> http://sourceforge.net/projects/hugin/files/hugin/hugin-2015.0/Hugin_2015.0.0-beta2_64bit.7z/download
>
> 64bit 7z file with python support  (simply un7zip to some location and use
> from there):
>
> http://sourceforge.net/projects/hugin/files/hugin/hugin-2015.0/Hugin_2015.0.0-beta2_64bit-python.7z/download
>
> I have currently no intentions to build 32bit versions.
> (7zip instead of zip as it gives a 23 MB file versus a 33 MB zip)
>
> Please test and give your feedback via this mailing list and this mail
> thread.
>
> (And for those who know me and wonder why I build on windows: Since 2
> months I switched back to windows for the only reason that a (non open
> source) program I wanted and needed is not on Linux. For everything else I
> could use anything on both linux and windows.)
>
> Hoi,
> Harry
>

Thank you. Reading the news about what was introduced without being able to
play with it was frustrating :-)

-- 
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CANe_y9TLgTxuzbzQOAvNnpmU9YKQTO_6Ogphc%3DBKUxQqLA4NWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mosiac model - convergence, accuracy?

[bugbear]

Terry Duell wrote:

Hello Paul,

On Wed, 27 May 2015 08:40:18 +1000, Terry Duell  wrote:



I'll have a look at your project.


I think it all boils down to 'good' and 'less good' control points.
I did a little editing of control points, and removed the vertical and 
horizontal CPs, and the optimisation now looks pretty good. I did have to 
correct roll using 'move/drag' in the fast preview window. My project file is 
attached.
Automatically finding good CPs on maps can be a bit problematic. For some 
projects it can end up being less work manually adding the CPs.
I did use the new 'EditCP' tool in hugin-2015.0.0, which made finding and 
removing the worst of the CPs an easy task.


How did you do this? Each image on the preview is tiny (since I have 30 
images), so I don't
see how you got benefit from the tool.

You clearly know something I don't.

Teach me, oh master!

(in general I suspect people don't use the CP editor much; on my laptop,
with a 1366x768 display, the image windows are only 669x381 pixels
in full screen mode.

(and see my other request for a "don't show the contrast enhanced square in this 
window") option.


This result would suggest to me that the mosaic mode is working OK.

Cheers,


>


Adding just one vertical line, in the one image, is all that is needed to fix 
it.
Mean error 0.5, max 2.9.


Perfect!

The result is also surprisingly square, given the lack of all but 1 vertical 
and horizontal CPs.

Well, except it's upside down...

For purely cosmetic reasons, I gave it a 180 degree rotate (in move/drag),
and centred it (in move/drag via X/Y edit)

Anyway - I tried to center the pano, using mosaic move/drag to alter the X Y.

I just though I'd do an optimise, just to be sure this "finished" pano was 
stable.

And after 213 iterations, it converged again, upside down, pretty much back 
where it started.
There is "some kind" of optimisation attractor which I don't understand, such
that X Y are interacting with Y P R.

I had thought (till now) that X Y Z only really had meaning realtive
to each other (so that the position of the anchor was entirely arbitrary),
but given the existence of such an attractor, it seemed there must
be a "best position" for the anchor (which implies that X Y coordinates
are not just relative to each other), so I added X and Y for the anchor
to the optimisation variables and let the optimiser loose.

It converged:
avg: 0.008403
std: 0006875
max: 0.0617

with (anchor) X=-85, Y=0.7

which sounds suspiciously similar to the sort of optimisation
that results in a tiny FOV (massive focal length). It just puts all the images
in a tiny dot.

It looks like the mosaic model makes the mapped images smaller (and hence CP 
pixel
distances smaller) as X and Y are further from the origin. I believe this is 
the driver of
the bogus attractor I'm seeing.

   BugBear

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/55659252.7030705%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2015.0 beta2

[dex Otaku]

Thank you [both]

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/69963551-f8d2-4eb5-81ce-aa7aecf3671f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Alignment and exposure stacks, feeling like a noob

[brandan34 via hugin and other free panoramic software]

What version are you using? Might want to double check that only one image 
from each stack is being linked to images from other stacks. When I first 
started I was getting control points from every image in a stack to other 
stacks and that is a very good way to cause what you are describing.

As far as how hugin works, I am pretty sure if you have the correct 
settings on the control point detector it should work as I described.(I had 
enough problems in 2013 version that I made a bat that does all of the 
control points for me so I do not need to stress about it and have since 
lost touch with how hugin currently does it.)


-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cd8f3f30-defd-4586-bb58-44525e5d2ed6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.