Sorry, two typo... It was Bruno who told me that autopano-sift-c could
not create ctrl point if hdof 225 degree if I remember correctly.
2010/1/28, Wolfgang Lin wolfgang@gmail.com:
I did not get any ctrl point if I shot Circular in landscape. Berno
told me that it was because of the bug
Thanks Tim
On Sat, Dec 5, 2009 at 8:58 PM, Tim Nugent timnug...@gmail.com wrote:
I wrote a stereographic projection tutorial here:
http://ultrawide.wordpress.com/2008/11/20/how-to-create-a-little-planet-using-hugin/
2009/12/5 slaterson campbell.christop...@gmail.com
On Dec 4, 3:31 pm,
It is a known fact that Panomatic does not give good results for fisheye
lenses. The algoritms do not work correctly with fisheye lenses. Please
don't ask me why as I don't know. Sometimes you're lucky, sometimes you're
not like now. You should better stick to autopano-sift-c for (Full
yes, Bruno is correct as usual. and it will work, i'm doing that right
now.
Wolfgang, you can certainly shoot with your 15mm handheld. Just
practice :)
if you want 3 shot panos, get a shaved nikkor or samyang. MUCH higher
resolution final panos, still in 3 shots.
On Jan 28, 10:56 am,
On Jan 28, 8:07 pm, dmg d...@uvic.ca wrote:
Sorry, i guess I just have to click one more time.
So from what I see, PTmender is not outputing correctly the entire
image? but what it outputs is accurate?
Well, I just rendered another test, and yes the outputs are the same
as Nona minus the
On Jan 28, 8:07 pm, dmg d...@uvic.ca wrote:
But I want to fix the problems. So if we can find a good test case
that shows the bug, I'll take care of it.
I made a simple one. Here's the rar:
http://lemur.dreamhosters.com/hugin/ptMenderTest.rar
It contains my low pano and pto + ptstitcher
Thanks Zoran.
PTmender is significantly faster than Nona. that is true.
--dmg
On Thu, Jan 28, 2010 at 12:02 PM, Zoran Zorkic zo...@gmx.net wrote:
On Jan 28, 8:07 pm, dmg d...@uvic.ca wrote:
But I want to fix the problems. So if we can find a good test case
that shows the bug, I'll take care
Does anyone know of any tool or method to automatically determine the values
to use for cropping a circular fisheye, on the command line? I'm pretty
sure the answer is no but just want to make sure...
--
View this message in context:
On Thu 28-Jan-2010 at 08:36 -0800, Zoran Zorkic wrote:
On Jan 28, 10:35 am, Bart van Andel bavanan...@gmail.com wrote:
The '=' signs are used to refer
to images loaded earlier, e.g. 'v=0' means: 'take the v-value from
image 0'.
So it's crashing cause it's expecting an image before the first
On Jan 29, 12:01 am, Bruno Postle br...@postle.net wrote:
On Thu 28-Jan-2010 at 08:36 -0800, Zoran Zorkic wrote:
On Jan 28, 10:35 am, Bart van Andel bavanan...@gmail.com wrote:
The '=' signs are used to refer
to images loaded earlier, e.g. 'v=0' means: 'take the v-value from
image 0'.
Harry,
Would you expect this version to run on my old PPC G5 that is STILL
running 10.4.11?
I ask because I tried to open an existing project file with this
version of Hugin and it crashed almost immediately.
It was a simple project with a single Equirectangular that was getting
transformed into
But isnt it easy to just use crop tool. Its so easy and takes a minute only.
On Fri, Jan 29, 2010 at 1:53 AM, hdrpano rfc...@gmail.com wrote:
Does anyone know of any tool or method to automatically determine the
values
to use for cropping a circular fisheye, on the command line? I'm
Zoran Zorkic wrote:
On Jan 29, 12:01 am, Bruno Postle br...@postle.net wrote:
In practice Hugin doesn't cope with any of these '=' references
pointing to an image with a later number, so image 0 should never
have any. This sounds like a bug, do you only see this with the
trunk?
Only with
Hi George,
2010.1.0-svn4933 definitely works on my PPC G5 when started from the
10.4.11 HD. I just tested with two projects, one from 2009-12-30, the
other one from 2009-08-29. Both open nicely, also using the fast preview
window. Oh, and it also works with projects (dating back to 2009-12-30
and
14 matches
Mail list logo
