Thanks for the thanks :-). Glad it was useful!
On Sun, Mar 7, 2021 at 8:54 AM Thomas Käfer wrote:
> Thanks for publishing this. I've used what I've learned from your script
> to make this much simpler much more rigid script for a panorama poor in
> features that I'm currently trying to stich
in). Then I let Hugin
> find control points and at last I do the same (reversed order) with the
> lower line. At the end I add my ground pictures.
>
> Hope this helps you.
>
> Gerhard
>
> Am Samstag, 21. April 2018 18:56:41 UTC+2 schrieb Mike Cowlishaw:
>>
>>
>>
a good testcase!
On Sat, Apr 21, 2018 at 6:36 PM, T. Modes <thomas.mo...@gmx.de> wrote:
>
>
> Am Samstag, 21. April 2018 18:56:41 UTC+2 schrieb Mike Cowlishaw:
>>
>> To date, I have not been able to get Hugin to make sense of them -- I've
>> tried Assistant and als
I've been using Hugin for some years now, with excellent results -- and now
I almost always use the Assistant; perhaps I have become lazy :-).
Recently, I have been taking panoramas with the Mavic Pro (this takes 34
images that covers a downwards hemisphere plus up to about 20° above the
>
>
> The errors are of the form:
>>
>> i7 : Analyzing image...
>> An error happened while loading image : caught exception: bad allocation
>>
>
> You are using the 64 bit version? (If you are using the 32 bit version,
> try the 64 bit version.)
>
I believe so -- I only have the 64-bit
: caught exception: bad allocation
Mike
On Fri, Nov 6, 2015 at 10:19 PM, Terry Duell <tdu...@iinet.net.au> wrote:
> Hello Mike,
>
> On Sat, 07 Nov 2015 02:24:32 +1100, Mike Cowlishaw <mfc.spe...@gmail.com>
> wrote:
>
> [Last post had wrong command copy ..
Just tried running my script for just the pto_gen and pto_var commands,
then opening the .pto with Hugin, running Align, saving, running the
geocpset command, opening the .pto again, and stitching.
This runs without errors, but the result is truly awful -- even 'easy' bits
such as the car is
On Saturday, 7 November 2015 18:37:19 UTC, T. Modes wrote:
>
>
>
> Am Samstag, 7. November 2015 13:45:39 UTC+1 schrieb Mike Cowlishaw:
>>
>>
>>
>
>
>> -- add missing control points using geometry
>> 'geocpset --output='profile profile
&g
On Saturday, 7 November 2015 18:51:56 UTC, Gerald wrote:
>
> Is it the same Rex as the one under OS/2?
>
There are several implementations (all support the ANSI Standard Rexx, I
think). The open object Rexx (ooRexx) that is the current open source/free
version is, indeed, based on the OS/2
>
>
> see http://wiki.panotools.org/Panorama_scripting_in_a_nutshell
> This file is also contained in Hugins help file.
>
Perfect -- thanks.
As mentioned, I didn't find anything like that when searching; maybe worth
'highlighting' in some way?
--
A list of frequently asked questions is
On Saturday, 7 November 2015 17:29:10 UTC, bugbear wrote:
>
> What (on earth) is your Hugin installed on, such that Rex
> is your scripting language of choice?!
>
Windows. But it is also my scripting language of choice on Linux. After
all, I created Rex[x] :-).
Mike
--
A list of
>
>
> Many thanks for that. Making progress :-). My script generates the
> correct commands, I think:
>
pto_gen -o project.pto p*.jpg
pto_var "--set=y=(i%6)*92.9654310-232.413578,p=0-(floor(i/6)*88.1947662)"
--output=project.pto project.pto
cpfind --output=project.pto --prealigned
[Last post had wrong command copy .. retry...]
Many thanks for that. Making progress :-). My script generates the
correct commands, I think:
pto_gen -o project.pto p*.jpg
pto_var
"--set=y=(floor(i/6)*13.5719189)-20.3578783,p=25.5922968-(i%6)*10.2369187"
--output=project.pto
for the
positions is bottom-left.
Mike
On Tue, Nov 3, 2015 at 7:40 PM, T. Modes <thomas.mo...@gmx.de> wrote:
>
> Am Dienstag, 3. November 2015 16:09:07 UTC+1 schrieb Mike Cowlishaw:
>>
>> It should be able to cope with up-down patterns just as well as
>> left-right, and zi
Bruno, thanks for the quick reply! Two separate questions here, I now
think.
> >I wonder whether the order of the images makes a difference (these are
> >top-to-bottom, a column at a time, whereas before I've always done
> >left-to-right, a row at a time)?
>
> Hugin does assume rows by
I've been using Hugin for some time and have always got excellent results
with panoramas from up to 4 x 6 images. However I recently tried a much
larger set (6 x 12) and the align step failed badly with messages about
many unconnected images. If I take a subset (e.g., the first 12 images)
16 matches
Mail list logo
