autooptimiser -n -o project_ypXYZ.pto project_ypXYZ.pto
pano_modify --projection=0 --fov=AUTO -o finished.pto project_ypXYZ.pto
On Friday, 29 April 2022 at 13:05:52 UTC+1 Michael Perry wrote:
> Thank you, that works simply and perfectly
>
>
> On Thursday, 28 April 2022 at 16:30:21 UTC+1 T.
Thank you Florian; I can see a logic in your statement. However, I still
think there is something odd with this. It may be a particular result of
working with mosaic stitching in very controlled conditions; the images
making up my panoramas are laid out on a regular grid and my control points
a
Is there not a bias in the way Hugin optimises; that control points at the
intersection of four images will be weighted three more times than those at
the intersection of the pair of images above or below? The larger error in
control points always tend to be the furthest from the centre.
Withou
Thank you, that works simply and perfectly
On Thursday, 28 April 2022 at 16:30:21 UTC+1 T. Modes wrote:
> michae...@mac.com schrieb am Donnerstag, 28. April 2022 um 12:23:49 UTC+2:
>
>> pto_var: can anyone tell me whether there is a way to specify, for
>> example, optimising yaw of all images i
pto_var: can anyone tell me whether there is a way to specify, for example,
optimising yaw of all images including the anchor without having to specify
each image?
Thus, some sort of:
--opt=yALL
rather than
--opt=y0,y1,y2,y3,y4…
On Thursday, 28 April 2022 at 10:39:12 UTC+1 Michael Perry wrote
this on the
> command-line.
>
> --
> Bruno
>
> On Wed, 27 Apr 2022 at 19:30, 'Michael Perry' wrote:
>
> > I am converting my workflow to the command line. I have a problem with
> pto_var and a question about pano_modify, I wonder if you can advise me.
> &
/Drag tab and the
Overview Mode to Mosaic Plane. Is there some code that might effect this?
Hoping you will find these interesting problems.
Michael
On Tuesday, 26 April 2022 at 15:34:22 UTC+1 Michael Perry wrote:
> Oh! How exciting. I had not come across this Executor system - I w
"I seem to remember that you can select more than one photo and it will
generate points just for that set"
Yes, this is also a useful way of adding a bias to an optimisation I think
- by adding in extra links for the less well correlated images, countering
the success of the better matches.
ugh I wasn't referring to the python API, the 'Executor' system is used
> by Hugin when aligning and stitching using the Assistant. It is
> configurable by editing these INI files.
>
> --
> Bruno
>
> On Fri, 15 Apr 2022, 13:54 'Michael Perry' via hug
couraged to modify, create and
> share. I haven't played with them since they were first introduced, it
> would be really useful if you could try this method and describe your
> success or failure here, as they are an underused resource that more people
> would use if they were
Is there a way to get the Hugin 2019.2.0 to use Rectilinear Projection as
its default projection rather than Equirectangular?
On Thursday, 25 February 2021 at 13:00:58 UTC Michael Perry wrote:
> I wonder if there is anyone in the forum who has a view about this?
>
>
> On Saturda
I wonder if there is anyone in the forum who has a view about this?
On Saturday, 22 August 2020 at 15:31:54 UTC+1 Michael Perry wrote:
> Can anyone advise me how to change the default settings for y, p, r, X, Y,
> projection (to and move/drag (to mosaic)
> Also, is there some way t
ntrol points per overlap than 25 control points
thank you
On Sunday, 18 November 2018 at 09:46:51 UTC Michael Perry wrote:
> I use Hugin to stitch mosaics. I find the best procedure is to optimise
> for X and Y before y, p and r. I have to select Custom parameters to be
> able to do th
I use Hugin to stitch mosaics. I find the best procedure is to optimise for
X and Y before y, p and r. I have to select Custom parameters to be able to
do this, then after de-selecting yaw, pitch and roll in the Optimiser tab,
I select the X and Y variables columns in their place.
Is there a w
Me too on OSX 10.7.5. Quite irregular, though I will pay more attention
next time
On Thursday, November 6, 2014 5:55:42 PM UTC, Frederic Da Vitoria wrote:
>
> 2014-11-06 18:34 GMT+01:00 John Muccigrosso >:
>
>> Hugin 2014 RC4 on a MacBook Pro running OS X 10.9.5 with Intel HD
>> Graphics 3000 5
PM UTC+1, Tduell wrote:
>
> Hello Michael,
>
> On Fri, 17 Oct 2014 04:35:46 +1100, Michael Perry >
> wrote:
>
> > I stitch mosaics using Hugin. My camera is mounted to a copy stand and
> > can slide in both X and Y and uses a (calibrated) Macro lens about 4
I stitch mosaics using Hugin. My camera is mounted to a copy stand and can
slide in both X and Y and uses a (calibrated) Macro lens about 40cm above
the artwork.
I am convinced that I am not using the right optimisation processes in
Hugin. The workflow is:
• Optimise in x and y to get all th
I stitch mosaics using Hugin. My camera is mounted to a copy stand and can
slide in both X and Y and uses a (calibrated) Macro lens about 40cm above
the copy artwork.
I am convinced that I am not using the right optimisation processes in
Hugin. The workflow is:
• optimise in x and y to get a
errors were huge.
thanks again though
Michael
On Friday, December 6, 2013 1:44:15 AM UTC, Tduell wrote:
>
> Hello Michael,
>
> On Fri, 06 Dec 2013 12:07:15 +1100, Michael Perry
> >
>
> wrote:
>
> > For me, cpfind is incredibly accurate at identifying contr
On Friday, December 6, 2013 1:44:15 AM UTC, Tduell wrote:
>
> Hello Michael,
>
> On Fri, 06 Dec 2013 12:07:15 +1100, Michael Perry
> >
>
> wrote:
>
> > For me, cpfind is incredibly accurate at identifying control points with
> > paintings and ph
For me, cpfind is incredibly accurate at identifying control points with
paintings and photographs. Today I have tried to stitch some maps. The
control point selection was not at all accurate. Worse, when I manually
chose control points, hugin informed me that my point were not correlated.
Has
> On Tue 05-Nov-2013 at 09:11 +1100, Terry Duell wrote:
> >> On Tue, 05 Nov 2013 02:35:05 +1100, Michael Perry
> >> >
> wrote:
> >>
> >>> Why does the flat-scanned stitching tutorial state that "You need to
> stop
> >>> H
Why does the flat-scanned stitching tutorial state that "You need to stop
Hugin from assuming that all the pictures were taken with the same camera"?
What is the reason for that - it can take a long time changing the notional
lens on each image
http://hugin.sourceforge.net/tutorials/scans/en.sh
23 matches
Mail list logo
