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 to
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 togetether:
#!/bin/bash
pto_gen -o scripting_step1_images.pto IMG_*.JPG
# https://wiki.panotools.org/Pano
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 Ob
>
>
> 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 ava
Am Samstag, 7. November 2015 19:44:47 UTC+1 schrieb Mike Cowlishaw:
>
> OK .. many thanks; will try those soon (not tomorrow). Is there an
> overview of hugin commands, like those, somewhere? I googled and browsed
> for some time and did not come across 'hugin_executor',as far as I recall.
Is it the same Rex as the one under OS/2?
Le 2015-11-07 13:01, Mike Cowlishaw a écrit :
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 l
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
>>
>> -- done
>> say
>> say 'Starting Hugin. Open' profile
Am Samstag, 7. November 2015 13:45:39 UTC+1 schrieb Mike Cowlishaw:
>
>
>
> -- add missing control points using geometry
> 'geocpset --output='profile profile
>
> -- done
> say
> say 'Starting Hugin. Open' profile', Align,
>
this can also be achieved from the command line: hugin_executor -
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 frequen
What (on earth) is your Hugin installed on, such that Rex
is your scripting language of choice?!
BugBear
On 7 November 2015 at 12:45, Mike Cowlishaw wrote:
>> Ah!! That works perfectly! Very many thanks. Presumably I can add
>> that step to the script by calling cpfind again (with --pre
Am Samstag, 7. November 2015 12:01:00 UTC+1 schrieb Mike Cowlishaw:
>
> 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
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 no
>
>
> 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 insta
Am Samstag, 7. November 2015 09:58:36 UTC+1 schrieb Mike Cowlishaw:
>
> 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
Hi, yes, the commands look good -- it is the errors that seem to be causing
the problems. Sometimes (with the same set of images) there are only one
or two error messages, and the result then is OK.
The errors are of the form:
i7 : Analyzing image...
An error happened while loading image : c
Hello Mike,
On Sat, 07 Nov 2015 02:24:32 +1100, Mike Cowlishaw
wrote:
[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)
[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 project.pto
>
>
> 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 proj
Am Mittwoch, 4. November 2015 16:15:22 UTC+1 schrieb Mike Cowlishaw:
>
> OK, many thanks .. working through the documentation on those and building
> a script; will report in due course.
>
That would be nice. There is no much feedback for this workflow/tools.
> The documentation for pto_va
OK, many thanks .. working through the documentation on those and building
a script; will report in due course. The documentation for pto_var is
especially skimpy. Are the constants you suggest (13, 27, 9) in degrees?
The functions seem to work in radians. Also I assume the origin for the
pos
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 zig-zag arrangements should work as well.
>
>>
>> Unless there are gaps or featureless areas, like blue sky, it's difficult
>> to say what t
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 defa
On 2 November 2015 12:07:06 GMT+00:00, Mike Cowlishaw wrote:
>
>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 default (you can change this in
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)
al
24 matches
Mail list logo
