Hi,

sorry for getting very late on this very important issue.

On December 6, 2010 03:34:59 am namklim wrote:
> According to the release notes "For the first time Hugin can be
> considered feature-complete.  A third-party control points generator
> is no longer necessary. This release delivers some major new features,
> integrates some projects from the 2010 Google Summer of Code, and
> includes many general improvements."
> 
> I was highlighting an issue which I thought might mean that statement
> was not correct and new users of Hugin could well be disappointed
> because of the out-of-the-box performance.

downloading your files was a pain.  next time before using one of these so 
called "free" download services that throw consumer-hostile code at everybody 
and waste my time (and yours), ask here if you need to share a large file.

I have uploaded your file to my server at 
<http://www.photopla.net/hugin/namklim.zip> and strongly encourage developers 
to have a look / use it as a test case.

This is the result of my testing on these files.  cpfind was run on an empty 
pto file that is just listing the images (attached).  panomatic was run on the 
images themselves.  I only ran three tests.

1. REFERENCE: `time panomatic -o panomatic.default.pto *.jpg`

real    1m17.629s
user    2m20.150s
sys     0m2.980s

detected CPs: 158


2. DEFAULT `time cpfind -o cpfind.default.pto imgonly.pto`

real    0m58.063s
user    1m40.830s
sys     0m2.890s

detected CPs: 4


3. FULLSCALE `time cpfind fullscale time cpfind --fullscale -o 
cpfind.fullscale.pto imgonly.pto`

real    3m0.262s
user    5m17.250s
sys     0m7.640s

detected CPs: ZERO

these results are puzzling.  they require more confirmation to see if this is 
an exceptional case, or if the issue affects more cases and we can only find 
this out if the code is out in real world use.

In terms of speed, cpfind (default) is almost 20% faster than panomatic 
(default), but what is speed if the quality is not there?

What surprises me is that cpfind's results are worse at full scale than 
resized.

Is this a show stopper?  I don't think so - shipping without cpfind is worse 
than shipping with cpfind as-is.  But we definitely need more information to 
understand under which circumstances this problem happens.

I have started a tracker ticket: 
<https://bugs.launchpad.net/hugin/+bug/694329>

Please continue discussion and testing there.

Yuv





# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360  E10.4804 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v89.8515443244759 Ra0 Rb0 Rc0 Rd0 Re0 Eev10.4803573889675 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 u10 n"20101109_IMGP1456_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev10.4803573889675 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1457_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev11.4918530613957 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1458_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev10.9657842161378 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1459_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev11.4918530613957 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1460_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev11.4918530613957 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1461_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev12.4512111272839 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1462_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev12.4512111272839 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1463_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev9.96578421613775 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1464_KX.jpg"
#-hugin  cropFactor=1.5
i w2848 h4288 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev10.4803573889675 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 u10 n"20101109_IMGP1465_KX.jpg"


# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v r8
v p8
v y8
v r9
v p9
v y9
v


# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions 
#hugin_enfuseOptions 
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType tif
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to