Hi,
Am Mittwoch, 26. Februar 2014 18:32:15 UTC+1 schrieb Cartola:
Well, I don't know if the problem is me, but I don't remember of making a
good auto set of CPs ever. I've always wanted to be able to make it find
more spread ones.
Some samples of mine are available at the links below.
Tks Thomas,
I'll try to change distance and do some tests.
Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/
2014-02-27 14:14 GMT-03:00 T. Modes thomas.mo...@gmx.de:
Hi,
Am Mittwoch, 26. Februar 2014 18:32:15 UTC+1 schrieb Cartola:
Well, I don't know if
Hi,
Am Mittwoch, 26. Februar 2014 02:46:49 UTC+1 schrieb Cartola:
I really liked the result. It is a shell script (sh) and surely has many
more things to be improved. I can share it but it is maybe a little
specific for a tokina 10-17 at 13mm,
Maybe sharing the images could help. There
Well, I don't know if the problem is me, but I don't remember of making a
good auto set of CPs ever. I've always wanted to be able to make it find
more spread ones.
Some samples of mine are available at the links below. They are not the
ones used at this last time, which are for a job and I guess
Hi all,
just to give some feedback:
the script is working quite well IMHO. It tries to find CPs in specific
parts of the image and almost always (or something like 9/10 times) works
standalone. When it really fails it gives me the file to add a specific CP
between a specific image pair, so I do
On Feb 20, 2014 12:46 AM, Carlos Eduardo G. Carvalho wrote:
I was thinking about trying autopano-sift-c, but would have to install it
and it's requisites, like mono, so I didn't do it yet.
autopano-sift-c doesn't depend on mono, in fact it is very straightforward
to build. The original
Why is nobody reading the help?
2) What is the option --link?
I haven't used this, but think it is used to create stacks.
It links image variables, like hfov, image distortion a, b, c,.. - as one
the Photos tab (or the old lens tab).
See http://wiki.panotools.org/Pto_var
For creating
Thanks a lot Terry. I still have some questions.
1) Why use !v0? I mean, usually I use only one lens and optimize v and
!v0 sounds strange. Is it for more than one lens?
2) What is the option --link?
3) I am also trying to find a way to spread the control points. Usually
cpfind is not finding
Hello Carlos,
On Wed, 19 Feb 2014 22:12:53 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
Thanks a lot Terry. I still have some questions.
1) Why use !v0? I mean, usually I use only one lens and optimize v and
!v0 sounds strange. Is it for more than one lens?
I
2014-02-19 19:53 GMT-03:00 Terry Duell tdu...@iinet.net.au:
Hello Carlos,
On Wed, 19 Feb 2014 22:12:53 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
Thanks a lot Terry. I still have some questions.
1) Why use !v0? I mean, usually I use only one lens and
Hello Carlos,
On Thu, 20 Feb 2014 10:38:38 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
[snip]
3) I am also trying to find a way to spread the control points. Usually
cpfind is not finding points in the bottom of the images. They are wide
fish-eye lens, don't
2014-02-19 20:51 GMT-03:00 Terry Duell tdu...@iinet.net.au:
I have seen your later post, and I'm pondering on it.
I don't expect I'll see any more success that you have had, but it is a
worthy challenge.
In my few experiments thus far I have had Autopano-Sift-C find about 10
points, but some
Hello Carlos,
On Thu, 20 Feb 2014 10:38:38 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
[snip]
Yes, I've read the man and played a lot with many options, those
mentioned
as more effective with fish eye lens, like sieve1size, sieve1width,
sieve1height,
Hello Carlos,
On Thu, 20 Feb 2014 13:14:12 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
[snip]
Maybe there can be some parallax, but I really believe it is very small,
based on what I've seen in another set of images with the same equipment,
where I specifically
On Thu, 20 Feb 2014 13:36:08 +1100, Terry Duell tdu...@iinet.net.au
wrote:
It might be useful to try a couple of test sets, one set with a
similarly spare set of features near the edges, and one set which has a
Sorry, I meant to trypewirt 'sparse' not 'spare' :-)
Cheers,
--
Regards,
On Thu, 20 Feb 2014 13:14:12 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
Also will maybe try with other set of images produced with a very well
calibrated equipment to see if the problem of detecting at the bottom
will also happen.
Just came across this
Hi,
I am trying to make an optimization script to do as I do in the GUI. When I
use Hugin in general I optimize little by little, like:
(y, p, r)
(y, p, r, v)
(y, p, r, v, b)
Everything without translation
I tried to find how to script this and found autooptimizer, but it doesn't
have options
Hello Carlos,
On Wed, 19 Feb 2014 13:27:21 +1100, Carlos Eduardo G. Carvalho (Cartola)
cartol...@gmail.com wrote:
Hi,
I am trying to make an optimization script to do as I do in the GUI.
When I
use Hugin in general I optimize little by little, like:
(y, p, r)
(y, p, r, v)
(y, p, r, v,
18 matches
Mail list logo