On 13 Okt., 18:36, Bernd Hohmann hohm...@harddiskcafe.de wrote:
On 13.10.2010 11:54, kfj wrote:
Reverting to full frame fisheye and reoptimizing v+a,b,c created fine
output.
If you just use 6 around and sky, you cannot expect to generate
reliable a, b and c data. They will depend on your
On 11 Okt., 22:21, Bernd Hohmann hohm...@harddiskcafe.de wrote:
Hi,
is there any switch to force autopano-sift-c to create a buch broader
distriubution of the control points?
Probably not, but why use autopano-sift-c?
I reckon I am using the same lens as you (mine is called Walimex pro
On 13.10.2010 01:27, Bruno Postle wrote:
It isn't in the 2.0 release branch, neither I found the sources for
it elsewhere. Can you help here?
cpfind is in the HG 'tip', i.e. you need a recent 2010.3.0 snapshot.
The 2010.2.0 release doesn't have it.
Ok. cpfind Pre-Release
On 13.10.2010 11:54, kfj wrote:
is there any switch to force autopano-sift-c to create a buch broader
distriubution of the control points?
Probably not, but why use autopano-sift-c?
Because cpfind crashes on some images (see my last posting).
I gave cpfind a try on a scenery with a sea,
On Wed 13-Oct-2010 at 15:42 +0200, Bernd Hohmann wrote:
Ok. cpfind Pre-Release 2010.3.0.294c413a5883 crashes here (Ubuntu
8.10 with latest libtiff* from Debian testing, cpfind selfcompiled)
with Segmention Fault when processing LZW compressed tif files.
Is this only with LZW tif files?
On 13.10.2010 22:45, Bruno Postle wrote:
Ok. cpfind Pre-Release 2010.3.0.294c413a5883 crashes here (Ubuntu
8.10 with latest libtiff* from Debian testing, cpfind selfcompiled)
with Segmention Fault when processing LZW compressed tif files.
Is this only with LZW tif files?
In this testcase:
On Wed 13-Oct-2010 at 23:13 +0200, Bernd Hohmann wrote:
Where to send the error report?
We have a bug tracker on sourceforge:
http://sourceforge.net/tracker/?group_id=77506atid=550441
I hate bugtrackers. Will do my very best.
We need to use the tracker because there is enough traffic on
On 12.10.2010 17:48, Jeffrey Martin wrote:
as far as i can tell, autopano-sift-c is too slow, too inaccurate, and
no one wants to work on it because some barbarians decided it was a
good idea to patent it.
Beside the patent issue: if a new controlpoint generator would need 6
hours to create
Pablo's CPFind (or whatever it's currently called) works well. I've got
mixed signals from devs. Not sure if it's in the current hugin branch
or if it still needs to be built separately.
If you want a Patent free ACPD I'd suggest using it, or building it from
source. I've been using it
I have 8 image around and a fisheye for the Zenith.
cpfind hardly finds any controlpoints at all, while autopano-sift-c finds
lots between the 8 images and some to the fisheye.
Suggestions?
Jan
On Tue, Oct 12, 2010 at 10:07 AM, Dale Beams drbe...@hotmail.com wrote:
Pablo's CPFind (or
Dale Beams schrieb am 12.10.10 18:07:
Pablo's CPFind (or whatever it's currently called) works well. I've got
mixed signals from devs. Not sure if it's in the current hugin branch
or if it still needs to be built separately.
cpfind is already in Harry's 2010.3.0 build for Mac. If it's not
On 12.10.2010 18:07, Dale Beams wrote:
Pablo's CPFind (or whatever it's currently called) works well. I've got
mixed signals from devs. Not sure if it's in the current hugin branch
or if it still needs to be built separately.
It isn't in the 2.0 release branch, neither I found the sources
On Tue 12-Oct-2010 at 19:59 +0200, Bernd Hohmann wrote:
On 12.10.2010 18:07, Dale Beams wrote:
Pablo's CPFind (or whatever it's currently called) works well. I've got
mixed signals from devs. Not sure if it's in the current hugin branch
or if it still needs to be built separately.
It isn't
13 matches
Mail list logo
