[ptx] Autopano 1.03 Beta

[Claudio Soprano]

Hi,

The /noclean doesn't work at the end i can find the files .pto .pts .ptp 
(using /hugin /pta /ptgui) but not the .key files

that i usually got in the same dir where i launched autopano (i usually 
copy it where i have the photo to stitch)

anyway thanks for ur work

P.S. i use ur autopano from 1st version and lately i got problems with 
some photos not recognize but splitted in 2
(that i fixed changing ransac mode)

Claudio Soprano

alexandre jenny wrote:

>Hi,
>
>Integration into PtGui, Hugin or PtAssembler is surely broken as the new
>version
>doesn't create the project files in a sub folder but in the folder directly.
>So just use it standalone.
>
>Many flags have changed signification so if no point were detected just
>remove 
>Every flags. You can keep /keys (for the number of keys) and /size for the
>detection size. 
>
>For enhanced results, use /keys:100 /size:800 (or more).
>Results must be really better than previous version.
>(My testing shows that the 1.02 version for size 1024 gets same quality of
>result
>As the 1.03 for size 512 : that's more than twice in accurary).
>
>Bye
>   Alexandre Jenny
>
>  
>
>>-----Message d'origine-----
>>De : ptx-bounces at email-lists.org 
>>[mailto:ptx-bounces at email-lists.org] De la part de Jim Watters
>>Envoyé : mardi 13 juillet 2004 22:48
>>À : ptx at email-lists.org
>>Objet : Re: [ptx] Autopano 1.03 Beta
>>
>>
>>I found problems with PTGui too.  But I did find a project 
>>file in the 
>>autopano directory.  I was able to open the new project in 
>>Notepad and 
>>copy and past the control points to the original file.  But because 
>>there was 1 file excluded and the order of the files were 
>>different,  I 
>>had to first open the file in PTGui add the missing file and 
>>rearrange 
>>to the same order as the original, then save.  Nothing like like 
>>selecting a menu item as with 1.02
>>I used /size:800 /sift:1 /keys:40 /search:3 /validation:0 /noclean
>>
>>/sift:0  would crash autopano
>>
>>running a second time with the /noclean, still had to make 
>>key file I have only tried so for on the one project of 
>>fisheye lens.  I was able 
>>to get control points with this project with old version.  Will keep 
>>trying some other project that did not work before.
>>
>> Jim Watters
>>
>> Graphic Software Developer  http://members.rogers.com/jimwatters
>>
>>
>>
>>rolfo wrote:
>>
>>    
>>
>>>Hi Alexandre,
>>>i love autopano but this update don't work for me! In a quick
>>>comparasion (i use PTGui) the old autopano 1.02 found 
>>>      
>>>
>>32Controlpoints 
>>    
>>
>>>same project 1.03 couldn't find any controlpoints ( i used these 
>>>settings: /verbose /search:1 /ransac:1 /keys:30 /size:1000). Also i 
>>>tried other Projects (all with Fisheyes either 10D with Sigma8mm or 
>>>NikonCoolpix4500 with FE-8) with the new autopano it never 
>>>      
>>>
>>found any 
>>    
>>
>>>controlpoint. So it is possible that the new autopano don't 
>>>      
>>>
>>work with 
>>    
>>
>>>Fisheyes or PTGui anymore or do i something completly wrong?
>>>Best Regards
>>>rolfo
>>>
>>>alexandre jenny schrieb:
>>>
>>>      
>>>
>>>>Hi,
>>>>       
>>>>I'm busy, but I still got some times to look after autopano.
>>>>
>>>>What is already done and working :
>>>>- really improved quality of detection (huge, really)
>>>>- great speed up of kdtree detection
>>>>- 16 bits tolerant
>>>>- new spatial test for removal of wrong key pairs
>>>>- remove of warning for tiff files
>>>>- all in one executable (no sift_keypoints.exe anymore)
>>>>- many new flags, just list them by launching autopano /h
>>>>
>>>>What's coming in the final version :
>>>>- the enhanced sift detection system : PCA-sift.
>>>>- automatic position calculation
>>>>
>>>>??? Any other idea ???
>>>>
>>>>I uploaded a beta working version for testing purpose here :
>>>>
>>>>http://www.le-geo.com/kolor/autopano/autopano_v103beta.zip
>>>>
>>>>Bye
>>>> Alexandre
>>>>
>>>>
>>>> 
>>>>
>>>>        
>>>>
>>>      
>>>
>
>  
>