Jump to: navigation, search

Current development

If you do not feel confident, please download and use the last stable 1.4.0 version available here: http://www.autopano.net/download

1.9.7 RC 2

This is the second release candidate for Autopano Pro / Autopano Giga.

Download Links

Release Date : 17 April 2009

Notes :

  • For MacOS, there are 2 packages now. One for 32bits version that works on MacOS 10.4 and 10.5, but in 32bits only. It uses carbon. The second package is leopard only, uses cocoa and is in 64bits.
  • For Linux, you'll need proprietary video drivers from your distribution.

Autopano Giga 1.9.7 RC 2

Autopano Pro 1.9.7 RC 2

It doesn't contains Autopano Tour which is only includes in Giga version. Workspace don't exists and Clauss Rodeon head is not supported.

Translator package

If you are willing to help for the translation of Autopano Pro / Giga 2, here's the package.

Development Notes


What inside this release ? Bug fix, bug fix and ... bug fix !
And some little UI adjustment everywhere.
And linux 32 bits !


On some hardware, the gpu mode was not working. After having checked them directly with
user having such hardware, we added a new test to prevent the use of that mode without
a specific OGL extension that was in fact needed too ( ARB_IMAGING ).
There are still some case that we didn't solve yet with the GPU support. 
We'll release a new version of our OpenGL testing freeware. Everyone should test it even
people for which GPU code was already working. 
As we have changed the way it is working we except that it will fix issue for people having
presently issue, but at the same time, it could break GPU mode for other people.
To resume : It's really complicated. For the final release, we'll keep the current code.
The GPU will then be broken on some hardware even on final version.

--- GPU ISSUE on linux

This is a special case. We regularly get crash because we use GPU code on Linux. It's inside
the libxcb. We try many trick available on the web without any luck yet.
We don't have any idea how to fix that. Moreover, it will really depend on the distribution
and drivers / lib used. 
On one hand my opinion is to block the use of GPU for the moment on that platform to prevent 
crash but on the other hand, I'm sure there are some platform where this crash will never
occurs. Again, it's complicated.


- A cache issue that introduces in RC1 a lot of new crash during
either gigapan detection, raw decoding or rendering. This is the cause
of many crash in fact.
- A multithreading issue that has been solved. This was the cause of crashes
during edition of the panorama ( while using move panorama for example ).
This one was hard to catch but it explains at lot of previously unexplained crashes.

* Bug  72 Resolved (Fixed)  : Move Image mode that was popping 
* Bug  98 Resolved (Fixed)  : Bad Layer selection when having hidden images
* Bug 123 Fermé (Fixed)     : Zoom Fit (100%). The panorama was partially hidden by the scroll bar
* Bug 125 Resolved (Fixed)  : new contextual menu in Layer mode to delete image
* Bug 132 Fermé (Fixed)     : Wrong image numeration in control point editor
* Bug 133 Resolved (Fixed)  : BKT crash
* Bug 134 Resolved (Fixed)  : MAC OS - auto crop / auto color / auto save hang 	 
* Bug 135 Fermé (Fixed)     : Close ALL issue in pano view 	 
* Bug 136 Fermé (Fixed)     : crash when using APW and raw format 	 
* Bug 140 Resolved (Fixed)  : Gigapan, crash during detection 	 
* Bug 142 Resolved (Fixed)  : Image settings problem 	 
* Bug 144 Fermé (Fixed)     : About dialog box, only the first time 	 
* Bug 145 Resolved (Fixed)  : TIF 32 bits Rendering failure 	 
* Bug 146 Resolved (Fixed)  : Papywizard Import problem 	 
* Bug 147 Fermé (Fixed)     : imagedef mailto repport
* Bug 148 Resolved (Fixed)  : Decimale in grid label 	 
* Bug 149 Resolved (Fixed)  : Quality fisheye stitching 	 
* Bug 152 Resolved (Fixed)  : Odd display bug, cannot reproduce
* Bug 160 Resolved (Fixed)  : Rendering stop / crash 	 
* Bug 164 Resolved (Fixed)  : Eyedropper don't work 	 
* Bug 165 Resolved (Fixed)  : HDR rendering
* Bug 166 Resolved (Fixed)  : Snapshot crash
* Bug 168 Resolved (Fixed)  : crash prevLayer en mode GPU

* Bug 141 : GPU Fisheye preview doesn't go to zenith / nadir exactly => this one won't be fixed for final
because it's just a small visual glich during edition.
* Bug 130 : GPU preview in pano column can be too low resolution => this one will be fixed for final because 
it's really not nice to see just 3 pixels there.

Qt 64 bits issue : Not really blocking but annoying

* bug 80  : Mac 64 bits : windows are not opened at the right coordinates on the screen. It's a Qt bug that has
 been reported back. Waiting for Qt 4.5.1 release      
* bug 129 : Mac 64 bits : accents on folder prevent from using them. It's a Qt bug that has been reported back. 
Waiting for Qt 4.5.1 release


We have some test cases generated with papywizard and we achieved 100% good stitch directly. That's the aim I 
was expecting and we get it ! Long live to papywizard, that's an awesome project.

Same story for GIGAPAN : 15 complicated panoramas from 50 to 1500 images. All good directly.


Some work on this part were done too.

--- Mode standard

* We changed the design of hotspot displaying. It was not really well designed and now it should be more easy to understand
that there are 4 types of hotspots and for each what parameters is relevant.
* Changed a little the panorama image parameters display. We changed the way cube face influence the result. Should be more easy to
get either.
-> the multiresolution drop-down has been removed. Now, it's the cube face size that say if we should use it or not.
-> added button that calculate the optimum cube size according to the spherical image used. 
* added autorotation flag to enable / disable that in output flash
* added fullscreen button
* shortcut in all windows to fit content are now consistent with APP/APG
* when selecting an object ( panorama or hotspot ), the property panel directly display itself.

--- Mode KRPano licensed

Nothing really new here.

--- still open bugs

Same bug as for autopano with the mac 64 bits port. 
The good news is that we don't really need a 64 bits mac version of Autopano Tour, so people that have issue here can use
the tiger version to prevent these issues.

   Release Date and Deployment

We are stil on schedule for compiling the final version for the 24 April.
But opening the website and webshop a Friday is not a good idea but if some issue are present there, we could hardly cope
with then during the weekend. So we'll release everything the Monday after ( 27 April ).

Note 1 :

This RC2 uses another type of registration keys ( same as in beta1 and RC1 ), so currently registered customers won't be able to use it. You can still use it in trial mode. If you really want to use it registered, contact us through this form, we have a solution : http://www.autopano.net/contact-kolor/write-to-us.html

Note 2 :

Reminder for Autopano Tour : Flash security. If you cannot execute a local flash :

1.9.6 RC 1

This is the first release candidate for Autopano Pro / Autopano Giga.

Download Links

Release Date : 3 April 2009

Notes :

  • For MacOS, there are 2 packages now. One for 32bits version that works on MacOS 10.4 and 10.5, but in 32bits only. It uses carbon. The second package is leopard only, uses cocoa and is in 64bits.
  • For Linux, you'll need proprietary video drivers from your distribution.

Autopano Giga 1.9.6 RC 1

Autopano Pro 1.9.6 RC 1

It doesn't contains Autopano Tour which is only includes in Giga version. Workspace don't exists and Clauss Rodeon head is not supported.

Translator package

If you are willing to help for the translation of Autopano Pro / Giga 2, here's the package.

Development Notes


What has been fixed. We used our internal tool to make a small report.
A lot of bugs have been fixed :
- Raw support that was buggy is many part even in GPU texture loading code
- Gigapan and papywizard
- Drag'n'drop issue
- Threading in rendering
- Linux GPU code
- HDR workflow was broken
- Dialog box size : on small screen, you have scroller now inside rendering dialog box for example.

The full list is here.

* Bug  10 : Resolved (Fixed) : No Panotools import possible 	 
* Bug  19 : Fermé (Fixed)    : BKT on images to check
* Bug  66 : Fermé (Fixed)    : Choisir une taille de fenêtre des préférences mieux adaptée 	 
* Bug  69 : Resolved (Fixed) : GPU mode, sometimes, textures can start flickering in an infinite loop
* Bug  73 : Resolved (Fixed) : Gigapan plugin improvement 	 
* Bug  74 : Resolved (Fixed) : crash si Temp folder on another disk 	 
* Bug  76 : Resolved (Fixed) : Drag'n'drop image / .pano dans APP/APG 	 
* Bug  77 : Resolved (Fixed) : RAW files issue 	 
* Bug  78 : Fermé (Fixed)    : RMS and history 	 
* Bug  79 : Resolved (Fixed) : Circular crop gpu still activated 	 
* Bug  81 : Fermé (Fixed)    : Fisheye Detection, initial view 	 
* Bug  82 : Resolved (Fixed) : UI Grid settings not saved between session 	 
* Bug  83 : Resolved (Fixed) : Rendering : threading is hanging 	 
* Bug  84 : Resolved (Fixed) : Color correction buggy 	 
* Bug  85 : Fermé (Fixed)    : Papywizard crash on folder browse 	 
* Bug  86 : Resolved (Fixed) : Linux : x windows / GPU issue 	 
* Bug  88 : Fermé (Fixed)    : Initial view estimator 	 
* Bug  89 : Resolved (Fixed) : Render UI 	 
* Bug  90 : Resolved (Fixed) : OSX 10.5 rendering issue 	 
* Bug  91 : Resolved (Fixed) : GPU texture issue 	 
* Bug  92 : Fermé (Fixed)    : UI dialog box trop petites 	 
* Bug  93 : Resolved (Fixed) : Gerard, crash rendu 	 
* Bug  96 : Fermé (Fixed)    : Papywizard optimization bug 	 
* Bug 100 : Resolved (Fixed) : HDR workflow broken 	 
* Bug 101 : Resolved (Fixed) : Vertical line not working 	 
* Bug 107 : Fermé (Fixed)    : Fisheyes images coupées en deux 	 
* Bug 111 : Resolved (Fixed) : pano %g not serialized 	 
* Bug 112 : Fermé (Fixed)    : no panorama found 	 
* Bug 113 : Fermé (Fixed)    : Image properties avec BKT bug 	 
* Bug 119 : Resolved (Fixed) : Bug GPU and raw, with low cache 	 
* Bug 121 : Resolved (Fixed) : Ordre images dans le group 	 
* Bug 127 : Resolved (Fixed) : Gigapan and brackets

We also fixed some reported back bugsplats :
* Detection of image as standard lens, then another detection as fisheye => crash
* Remove images in editor, then color optimization => crash

--- Gigapan support

Quite everything is working. The most problematic issue was to handle isolated images. The solution was
to create artificially one CP between all isolated images on the grid. This way, when we optimize the full
panorama using control point, isolated images following the full grid. It works pretty well. But I found that
really as a working trick and not a really solution. I'm working on a code that will prevent this use.

--- Papywizard support

A lot of work done here too. I hope that all users can now test this part a lot. I confess that I don't have
much sample sets to check the support of this head, just have a deep overview on this plugin.
Thanks to mediavets for the full review of the interface.

--- Still open bugs

* bug 72  : Move mode is behaving strangely on big panorama ( an annoying poping can happen )
* bug 75  : Mac 64 bits : GPU : http://www.autopano.net/forum/t5535-apg-beta-1-osx-x64-gpu-acceleration-on-mac-pro-issue
* bug 80  : Mac 64 bits : windows are not opened at the right coordinates on the screen. It's a Qt bug that has been reported back. We are waiting for the feedback         
* bug 98  : Layer mode, bad selection of images in presence of hidden pictures
* bug 102 : Minors UI fix for the mac platform
* bug 123 : Zoom fit in panorama editor fits the panorama but it is partially hidden by right scroll bar
* bug 124 : Gpu on ati. We didn't found this one : http://www.autopano.net/forum/t5087-apg-1.9.1-alpha-2-strange-behaviour-with-gpu-usage
* bug 128 : Linux and font size. Not really adapted to this platform
* bug 129 : Mac 64 bits : accents on folder prevent from using them. It's a Qt bug that has been reported back. We are waiting for the feedback
* bug 130 : Panorama preview in GPU mode too low resolution but is not when opening the panorama in editor ( panoview column )

The linux 32 bits version has not yet been compiled.


There has been a lot of work on this tool. First, the big integration of KRPano licensing validation
as well as features available only with a KRPano license.
So, we are using now the latest version of KRPano ( 1.0.8 beta 7 )

--- KRPano licensed mode

In about menu, you can now see the KRPano registration. You need to select the KRPano unlimited license to unlock these features.
The features that are available in this mode :
* multiresolution ( see the multiresolution drop-down menu near jpeg quality selector in panorama property )
* drop down menu for direct panorama selection in a virtual tour ( project property, insert panorama list )
* export XML ( project property, export )

--- New features / enhancements

* removed flash 9 / flash 10 selection because the generated flash is now compatible with both version
* hotspots : jpeg / html, you now can select the position and size of them
* hotspots : you can choose to use the moving transition or not when going to a new panorama
* polygone hotspots, lensflare, point hotspots : you can now edit them without deleting them ( select a corner and move )
* new direct icon : save as, close project
* improved navigation in central window ( zooming is possible to have bigger preview of panorama )

--- still open bugs

* Mac : needs some minor fix ( scroll tool that can be buggy, etc ) -> Qt issue
* Mac : buggy menu bar -> Qt issue
* Mac 64 bits : accents on folder prevent from using them. It's a Qt bug that has been reported back. We are waiting for the feedback
  ( same bug in Autopano Pro / Giga ) 
* Mac : some menu are disable and show not ( and revert ) -> Qt issue

Note : a lot of bug are in fact issue coming from the new Qt 4.5 library on mac platform. We hope here that they will get back 
to us before our final release date.

   Release Date : 24 April 2009

That's the date where we would like to ship the new production release, open our new website and launch selling of the new products brand.
It's 3 weeks from now and except the Mac Qt bugs, we don't know of any big blocking bug.

Note 1 :

This beta 1 uses another type of registration keys, so currently registered customers won't be able to use it. You can still use it in trial mode. If you really want to use it registered, contact us through this form, we have a solution : http://www.autopano.net/contact-kolor/write-to-us.html

Note 2 :

Reminder for Autopano Tour : Flash security. If you cannot execute a local flash :

1.9.5 Beta 1

This is first beta version of autopano 2 generation.

Download Links

Release Date : 13 march 2009

Notes :

  • For MacOS, there are 2 packages now. One for 32bits version that works on MacOS 10.4 and 10.5, but in 32bits only. It uses carbon. The second package is leopard only, uses cocoa and is in 64bits.
  • For Linux, you'll need proprietary video drivers from your distribution.

Autopano Giga 1.9.5 Beta 1

Autopano Pro 1.9.5 Beta 1

It doesn't contains Autopano Tour which is only includes in Giga version. Workspace don't exists and Clauss Rodeon head is not supported.

Translator package

If you are willing to help for the translation of Autopano Pro / Giga 2, here's the package.

Development Notes

I really have to say, this beta 1 was hard to release.
It's the most advanced autopano we never did with plenty of changes and improvement.
For you to be able to get the full power of it, I really encourage you to read through the following because many new concept, tools, algorithms are explained.


--- GPU

It is our flagship feature of this beta 1. The previous alpha has already some part of that, but now, in the editor,
you have all the tools that are compatible with this mode ( except tone mapper ... ).
So, what to say. It's fast, it's fun to use with such a depth zoom on gigapixel panorama !
You can notice some improvements :
- the initial view of the panorama is now centered around the content ( where some pixels are located )
- zoom-in zoom-out is now done by 10% step instead of giant gap. This allows a far more convincing navigation of
the panorama in the editor.
- shortcut : Ctrl+0 => fit the full extend the panorama in the windows
- shortcut : Ctrl+1 => go to 100%
- when switching from one projection mode to another, it's realtime ( took around 20 ms here ). This will allow you to explore
new projections modes that appeared some time ago : panini, vedutismo, generalised stereographic projections, etc

--- Optimization

This is one of the main algorithms in panorama. If this one works great, panorama is easy to do. If it don't, 
making panoramas can be nightmares. So what is exactly this optimization stage ?
You are in the stage where control points have been detected and validated. Using those CP, you should
be able to find all camera positions and lens distortion. That's done by the optimizer which is a fairly
complexe piece of math in fact.
In v1.4.2, you didn't have really access to parameters of this optimizer except in the detection settings :
strong algorithm, optimize lens distortion or not, use advanced lens distortion or not. That was all.
We decided to put the whole optimizer public. This is a concequence of all the new features we added to
support for example motorized panorama head.
So how do it work now ?
For the novice user, you'll have optimizer profiles that will check the right algorithms to use on standard
case : quick optimization, strong optimizer, gigapixels optimizing and fisheyes optimizing.
For the advanced user, you have access to the individual algorithms that correspond to a profile ( and check
uncheck which one ).
I will document all the individual algorithms but not here because it would double this post length :)
Just play a little with it, you'll see, it's fun.

Note 1 : we put the strong algorithm as default. I really encourage you to try the quick too. Because this one
works also 90% pourcent. It only fails when a wrong link is discovered in the panorama ( because of symetry for example ).
Really, it's interesting to look at that aspect ... sift finds so much correspondance.

Note 2 : the optimizer has been speeded up at lot. A multifocal 300 images panorama is now optimized
in 5 to 10 seconds instead of 15 minutes before. And the quality is now better than before. This is expecially
true for big panorama.

--- Panorama Editor

Some feature request have been filled here :
- Improvement in the history pannel. Now, it's dockable, you can put it over the advisor for example.
- Undo / Redo in the menu and as shortcut are available ( Ctrl+Z, Ctrl+R )
- the advisor has a vertical slider if the information are too long to fit in the windows
- zoom-in and zoom-out have changed to have more steps.
- In gpu mode, the crop tool has changed. The crop zone doesn't rotate itself, it's the panorama that rotates, so it gives the
real preview of the scene.

--- Control Point Editor

Some revamp here too. The most noticable is when this tool is enable, it has it's own advisor on the main editor
pannel. This advisor gives informations about the need of optimization for example, but also allows to hide good links for
example. Because when doing big panorama, it's often complicated to find where the problem is located when having 1000 green
boxes displayed and only 2 or 3 reds ...

--- Metadata

New options in general setting / image tab.
For user that commonly do panorama without exif or with false exif, you can now override what you want to setup the default
exif value or even force the value to something else.
This is useful with convertor lens.

EXIF GPS tags are now kept in the rendered panorama ( works on : jpeg, tiff ) 
IPTC field are also kept in the rendered panorama ( works on : jpeg, tiff )
ICC profile should be okay too ( to test on jpeg, tiff )

--- CPU / Multitheading

While working on the GPU code, we found out that some optimization could be done in CPU code too. So we did some.
The editor and the rendering is really faster. We estimate that the final rendering has got a 2x factor just by using
those improvement ( expecially in multiband blending ).
The multithreading in the rendering has also been changed to balance thread in a better way. It improves the speed in
case of 8 or more cores ( not true with smartblend ).
BTW : we changed the limit of cpu number from 8 to 32.

--- Detection options

New options here :
The most interesting is the layout option. You have 2 build-in options here : "free" and "single-row or column".
What does that do ? 
In fact, it tells to CP detector what possible link can exist. In free mode, any image can be linked to any other.
In single row mode, one image can only be linked to previous and next one. It's interesting to see that it can helps
some cases in presence of wrong links, making the strong optimizer profile obsolete.
So we dediced to keep that feature in the build even if most of time, the right choice is the "free" mode.
BTW : templates will be listed in this drop-down too.
Feature request filled : separate auto-save-and-close into 2 individuals flags : auto-save, auto-close.
Improvement : we changed the fisheye circular crop detector. It's brand new and can handle far more cases than before. 
Sometimes, with dark pictures, we could have issues, it has been solved. Now, it also detects the fisheye center and
doesn't suppose it in the middle of the picture.

--- Rendering dialog box

- a new format ".kro". Kolor Raw Format. We introduced this to overcome limitations on file formats for giant panorama.
Our Paris-20-gigapixels will be over 300000 pixel in width, so PSB couldn't be used. This format will be documentated and
integrated in all our tools to support giant format in 8, 16 or 32 bits formats. BTW : next build of XNView supports it,
that's a good sideeffect of a great collaboration with Pierre, xnview Author.
- We fixed a know crash bug when selecting / unselecting layers in mode "one per file".

--- Main Windows

When you detect a lot of panorama, you don't see any new panorama being calculated when there are more than 3 or 4 panoramas displayed
on the right column. So we changed that and now this column set it's focus to the currently activated.
With Autopano Giga, you can also see 2 new icones : save / load workspace. Easy to guess what it does ...
saves all groups and all panos, reopen everything.
Note : Individual settings of groups are not kept. That's by design. It will allow to patch them all by way :
save the workspace, change default value in general menu, load workspace => groups will have the new settings.

--- Motorized panorama head support

Easy. Click the browse button, select all images and the papywizard xml file and press ok.
You'll get a preview of the panorama.
2 options :
- auto detection : launch directly the detection ( enabled by default ). Uncheck if you need for example to patch exif before detection.
- skip optimization : it will still create control point but won't optimize them. You need to hit on optimize to use them.
That's nice to get a panorama build only with coordinates from the xml file.

Clauss rodeon support is quite the same except we added a button to inverse Y coordinates. With that head, it can happen that you
hang the lens in the wrong direction ( shoot rear instead of front ). So Y can be reversed. This support is APG only.

Gigapan support. It was complicated to create a strong system. It now works except if you are in presence of strong symetric structure.
I have a nightmare case from Richard ... :) BTW. I will create a video to learn how to edit and patch gigapan panoramas.
New feature : support of the new shooting sequences

--- What's missing ?

We didn't achieve to put everything we have planned for the final version. For example, the plugin system that would allow to 
integrate the new HDR engine. So we'll postpone that for v2.2. I apologize for that.
The version 2.1 will be dedicated to some minor enhancement and fixes, version 2.2 for real strong new features.

Our next big thing is a new smartblend. This algorithm is acutally pretty old now and moreover it doesn't scale well.
So since 5 months we are working in parallel on a new algorithm, we called it smartblend2, but the name could change.
Our first results are really good and the speed has nothing to compare with this old technic. It's something that will come out
for 3rd trimester.

The second big thing is orthographic model. That's a real revamp of math concept. We tried to make that happen but didn't work in fact.
In 2 months, we'll have a major math study on that. We'll have more news about that at this time.

--- Notes about bugs still presents in APP/APG beta 1

We changed the way to release a version and normally, the stability of the release should be better ( I hope you'll confirm that ).
Nevertheless, there are still some open bugs :
* Panotools import is broken
* Some gigapan panorama on architecture still fails to stitch directly. It happens when 2 neighboring images are too similar due to similarity.
A new algorithm will be added to patch such case. A big thanks to Richard for providing me the most nightmare gigapan cases in the world :)
* Gpu on linux is really unstable ( commonly it's crashes because of X beeing unable to cope with threading )
* Move tool doesn't work always as expected => seems an index issue
* In GPU mode, panoramas with fisheye is not previewing accurately expecially on poles ( distorted preview but panorama still good )

* Project view
- zooming with wheel mouse
- panning with scroll bars, arrow keys or mouse right button click
- drag and drop of pictures or projects files 

* Hotspot edition view
- zooming with wheel mouse (even while drawing a polygon)
- translating with arrow keys (even while drawing a polygon)

* Hotspot properties
- can be used to display graphical object (an image or swf)
- panorama transition settings (entry position)

* 3D view
- When one hotspot connected to another panorama is selected, the contextual menu enables to set the entry position to linked panorama

* Metadatas
- when using a partial panorama rendered by Autopano Pro/Giga, the field of view is read back from exif value, so you don't need to cope with that.

* KRPano full license integration ( still inactive in this release )
- If you have an unlimited KRPano license, you can unlock advanced feature in Autopano Tour. Many feature have been developed but this feature 
is still inactive because we are waiting for the next 1.0.8 krpano release that has all the features we need to propose that to you
- Multiresolution has been integrated ( still some work to do for partial giant panorama )
- Export of the KRPano xml has been coded too
- Manual location of html or images on the flash viewport has been coded but will be activated with 1.0.8 only ( example to say logo in upper / left corner ).
This feature is available in both mode : standard or advanced.

Note 1 :

This beta 1 uses another type of registration keys, so currently registered customers won't be able to use it. You can still use it in trial mode.

If you really want to use it registered, contact us through this form, we have a solution : http://www.autopano.net/contact-kolor/write-to-us.html

Note 2 :

Reminder for Autopano Tour : Flash security. If you cannot execute a local flash :

1.9.1 Alpha 2

This is the second alpha serie of autopano 2 generation. It contains many new feature as well as the first release of Autopano Tour.

Download Links

Release Date : 23 December 2008


There is a lot to say about this alpha2. First, we'll make separate the talk with autopano tour. If you are interested into that one, see our announcement about it here : http://www.autopano.net/forum/t5015-announcing-autopano-tour

So let's concentrate on Autopano Giga.

Real Time Editor

The first big new feature is the editor that was changed totally. Before, everything was done using the CPU, so the preview could only be of a really small size. You still have this mode, but now, you also have a GPU mode.

  General windows, Edit, Settings, General tab, you'll see something new : GPU ( enabled or not ). 

You have to enable it and restart autopano to be able to use that feature.

WARNING : if you use the check button and your hardware is not good enough for GPGPU, it will crash. To test compatibility with GPU mode, proceed this way :

 check the enable button, click OK, if the hardware is not good enough, you'll get the message why.


So, why not have a look at it directly ? http://www.autopano.net/data/blog/kolor-giga-alpha2/02.html

The fact that you have now a real time editor allows you for example to interact with the panorama directly. You can pan, rotate a panorama directly. You can see it morph itself according to the projection law. It's always funny to see.

A small notice on the slider new the zoom drop down button. This slider change the way the panorama is displayed. When having look back to the cpu mode, you can just see what is inside the panorama ( after the crop has been applied ).

Outside that, nothing exist. It's not the case in the GPU mode. The editor works always with the whole panorama even part that are outside the crop zone. So this slider switch between the cpu mode to the full extend view. This forces me to talk about the view. We need to clarify that. There is 3 zones now.

  • zone 1 : outside the projection mode. For example for spherical, everything below theta -180 or over +180. It just doesn't exist. that plain standard grey. You can see nothing here.
  • zone 2 : in the projection extend but not part of the crop zone. Here, you can see some part of the panorama but really dark.
  • zone 3 : in the crop zone. That's where you work in fact, where the usefull pixel are located. Those pixel are displayed in the good color here.

Checkerboard : in zone 2 or zone 3, everywhere you have alpha, you'll see a dynamic checker board that adjusts dynamically with the zoom.


What's cool with that real time editor is that quite every tools are now real time too, because the tool itself doesn't cost a lot to do, it's the refresh that was costly. So when rotating or making an automatic horizon, it's just free.

BTW : DrSlony did have a great idea with color correction. Why not have an automatic yellow anchor fly over mode ? You just fly over the panorama and you can see where to put the yellow anchor. Good idea and it will work with small panorama below 15 images. For bigger images, you still need to optimize the panorama. Anyway, we'll do it.

Last consequence of the real time editor : the move mode. It was not so usable without that feature, but now, it's just awesome. Click on an image, drag it around and drop where you want. Everything is visible directly and to place manually an image, it's so easy now. Click on the image, move it approximately to the right position, zoom in, move a little, zoom to 100%, done.

There is two new move mode there : global panorama move and panorama rotation. It's straightforward to understand.

WARNING : not everything is working in the GPU mode

  • color correction can be broken at edge ( bug : coming from the color constraints calculation )
  • we disabled the level tool because we need some extra work to support it in GPU

Panorama head support

A lot of work done here too. I apologize to people that were waiting this feature for so long, but in fact, it's not straightforward to do. Anyway. Now, it works in 95% for 3 kind of projects already :

  • papywizard project based ( for the merlin head for example ). You provide the .xml file and the pictures and done.
  • clauss rodeon panorama head : same principle. Provide the clauss log file and the pictures.
  • last but the harder to code : gigapan. Just browse for some images and autopano giga tries to guess everything.

See it in action here :


It's already working quite perfectly in many case. But not all. I found some tricky gigapan case that did get a good panorama at the end. But you can tweak the result by hand with the control point editor. One point : with such big panorama, I found out that optimization can be really really slow. And to patch just a small area of the panorama, you don't need to reoptimize everything. So I spend some time on the local optimizer again. It was present since a long time in autopano but not really used. Now, it's better and working (on big panorama, on small one, just use standard optimization ). So how does it work : While having the control point editor open, right click on a picture, you'll see a contextual menu with optimization.

In live here : http://www.autopano.net/data/blog/kolor-giga-alpha2/05.html

BTW : this local optimize feature is not totally finished and won't work well with hightly distorted lenses. But on big panorama, without lens distortion, it's just perfect to fix small area without reoptimizing everything.


There were many revamp in other part of the software that are not totally visible now. For example, in group properties, there is a new drop down menu called template. Yes, that's the first part of template stitching. How does that work ?

  • when you have a good panorama for example done with your Nikon D300+10.5 fisheye 6 shots + 1 zenith. You found that one really good and should be always the base of such kind of work. Let's use the save as template feature near the save as button in panorama view and name this template "D300,10.5,6+1 images". Save.
  • Then open a serie of image that has been done the same way. Go on the property of this group and select the template that now appears there. Everything should go better with less stitching error.


Many part of the software has also been corrected and improved.

  • new cameras support ( 50D, 450D, D700, etc )
  • new raw format support
  • many improvement in the lens distortion code

Okay, that's already a lot for you to test.

What's next ?

  • Finishing GPU mode in the editor
  • A big pass on the plugin system to integrate everything related to HDR. That is the last big part we still need to do.

That's for alpha3.

Then we are in beta stage and not far from release.

1.9.0 Alpha 1 Rev 3

This is the second alpha serie of autopano 2 generation. We decided to release a Giga version that everyone could use with their actual serial number for 1.4.2 Autopano Pro version. So every beta tester have a free Autopano Giga, ain't that cool :)

Download Links

BTW : we may drop support of G4/G5 processors on Mac. It's really a nightmare to support and we won't be able to use every optimization trick we are using now on them. So for the moment, we won't release any Mac compilation for G4, G5 processors.

Release Date : 10 September 2008

Fixes between Alpha 1 Rev 1

  • NEW - group properties, now, you have access to all settings for the group ( including rendering settings )
  • FIX - BUG control point editor that didn't work
  • FIX - BUG flash export : missing logo
  • FIX - BUG extended save as
  • FIX - BUG with exif default value
  • FIX - BUG main progress bar
  • FIX - BUG Raw didn't work with new cache system
  • FIX - Many fixes in detection process
  • FIX - Crash during rendering ( new cache system issues )
  • FIX - a lot of refresh issue in the interface are fixed with qt 4.4.1
  • IMPROVED - shell extension to manage new projection mode and vista far better



This wasn't really clear in the previous version. In fact, we were mixing 2 kind of settings together and it made the interface not clear and straightforward. I had a lot of discussion about how to make a good documentation of autopano and it highlights me that in fact a design issue was done that prevent to make a really good documentation.

So here's the clean up : we now have 2 kinds of settings :

- panorama related settings : settings that are associated to single panorama
example : defaut render size=100%, defaut color anchor, detection quality, etc
- software related settings : related to the software so it's the same for all panorama
example : cache path, grid in the editor, separate group by focale, etc.

Having cleaned that, it's now more obvious were you will found any settings.
In general setting menu, you'll get one menu (general) for the software, and the other are all
default value for panorama :
Images -> NEW : how should images be handled : default exif, raw decoding setting, etc
Detection -> classique default detection settings
Panorama -> NEW : panorama layout default value, anchor type, etc
Render -> classique default rendering value
Those 4 dialog boxes set everything you need to describe a panorama.

So when creating a group, a copy of those settings is done to the group. It will use them to generate panorama during detection. One question remains : The group option dialog box is in fact the detection setting tab. It allows to override on the concerned group the default setting. In fact, we should add the same 4 tabs there too because you surely want sometimes to override some other settings like for example 100% in rendering on that single group, right ? I was wondering if we should do that or not. I'm open to discussion on this topic.

Every other menu in panorama editor, settings, are now software only setting. If you need to change something which is related to the panorama, there should be a tool to do that, not a setting ( example, color anchor editor, render dialog box to change rendering options, etc ). There will be no more panorama related option in other settings dialog box.

Status of this job : everything has been done on this work except settings related to optimizer and control point editor. So you don't need to check those, there are not fixed yet. But everything related to detection / panorama layout / rendering should work.


That was also something we need to revamp. There are some thread in bug report which talks about crash when switching to planar projection. It has a strong theorical issue. So we had to change everything and that has been done. The projection code is now clear and far more optimized than before. You won't get that crash anymore even with big planar panorama. In fact, it allows a lot of new possibilities : - new projection modes. We checked that with the mercartor projection and it was integrated in less than 2 hours. We will add more projection to the software : if you have any good suggestion ... ( to GURL : we'll do your idea, it's just a kickass idea ! ) - new possibility. In general settings, you can see, automatic projection mode ! Yes, easy to implement, it will determine the best projection according to the panorama layout : rectilinear for small fov, 360 x small vertical fov will be cylindrical, full sphere will be spherical. This works great. You don't have yet editable switch limits, but that's planned.

Test this feature, I really enjoy this better planar mode.


This feature was something I really wanted for v2. It seems easy, but it is not because we need to change the design of the detection algorithm. When using panorama head, you either have access to a file which gives you location of each picture ( merlin head for example ), or at least you know that the panorama has some structure : one image has some neightboor, not all image are neightboors : it's a template of shooting in fact : 8 rows, 6 columns. So the software needs to know about this structure to work better : faster detection, no false link, singleton images should be well located directly.

Panorama head support gives us also the opportunity to work differently in the software and use plugin based on wizard. Just look at the File, Import, menu to check this feature. The gigapan support has been largely debugged, but not the clauss rodeon yet. BTW : you can try gigapan on large panorama ( we did 800 pictures ), but it's not perfect for the moment, because the algorithm used to cope with unlinked picture is not finished yet.


What is a stack ? Easy, 2 to n pictures that are in fact to be threated together. The most common case is a bracket stack. We introduces this notion to be able to use this structure notion in each part of the software to optimize it. Like with panohead, a images bracket serie has a structure that APP should know about. If it does know about, it can do many things better like for example detection. How does it works ? Easy : if you used bracket, pictures in the group view will be regrouped logically together into a stack with a BKT icon. If there is a stack in the group, the detection will use this structure notion to make a better detection. In fact you have 2 options to control that : Detect links in ()one stack level, ()all stack level. Let me illustrate that with a 3 bracket 5 positions panorama.

  POS.1  POS.2  POS.3  POS.4  POS.5               POS.1  POS.2  POS.3  POS.4  POS.5    
0 eV   IM01 - IM04 - IM07 - IM10 - IM13         0 eV   IM01 - IM04 - IM07 - IM10 - IM13     
       |      |      |      |      |                   |      |      |      |      |            
-2 eV  IM02   IM05   IM08   IM11   IM14         -2 eV  IM02 - IM05 - IM08 - IM11 - IM14     
       |      |      |      |      |                   |      |      |      |      |           
+2 eV  IM03   IM06   IM09   IM12   IM15         +2 eV  IM03 - IM06 - IM09 - IM12 - IM15     

         One stack : only the ev0 links                All stack level : every stack level will be
         will be detected                              analysed to find link

The links within a stack are always detected. We could imagine to add an option to prevent that too, because if you were accurate during shooting, they should match perfectly.

We did some testing of this stack feature. Panoramas with 9 bracket level or 11 bracket are now better supported than in previous version. But that's not the only reason to add this new notion. It will be the background for 'N to 1 plugin'. An 'N to 1 plugin' is easy to understand, it uses N images in input and creates one in output. When thinking back to bracket, what is the more obvious 'N to 1 plugin' ? Merge to HDR. From N LDR plugins, we get a HDR picture. Those plugins will be introduces in alpha 2 or alpha 3. So that's the second and but main reason to support stack.


We talked a little about that already when defining the panohead support. Yes, detection has been totally changed. The main change was to use the structure notion of the group. If we have stack, we need to use this new information. If images comes from a panorama head, we need to use this information too.

Another topic that often arise when talking of detection is raw support. Many users don't understand why detection is so quick when using jpeg and so long when using raw. In fact, it's the raw decoding that is really long, the detection is fast.

So here's what has been done in detection :

  • we now use the structure notion of stack and panorama head
  • when detecting raw, you can see in the progress bar a step that wasn't before there : raw decoding. So you are now informed it doesn't do the detection, but raw decoding
  • last but not least, the detection is now fully multithreaded, 1 core => 20s, 4 cores => 5 seconds. We did a lot of work on that it scales perfectly. It's so amazing that now I'm using 100 images panorama when debugging rather than some of my old 15 images panorama before.

Really, if you had to remind only one fact in this first alpha, it should be multithreading in detection :)

BTW : didn't I notice that this full revamp has improved a lot detectivity ? Now panorama that weren't detected well before are good with standard detection quality. I checked on old nightmare cases which are now often directly perfect.


For autopano engine 2, our way to work on the code was pretty clear : follow the images ! First detection, then control point validation, optimizing, rendering, etc ... As you can see, this alpha 1 has done some major breakthrough in the detection and point validation.

The next step is the optimizer. That's for alpha 2. I really want to step into this huge hidden part of the software. Some jobs have already been done. You could find that if you do big panoramas. The optimizer is faster, far more faster. But that's the first improvement only. BTW : to get better quality, ie RMS, for big panorama, it's now good to use robust algorithm. It really stabilize the layout and RMS drops a lot.

Warning : current version of optimizer is not totally finished, so as always with alph, save before if you can. Second note : it uses far less memory now ! So for crazy people, optimizing a 2000 images panorama on 32bits is possible. I didn't make an estimation of the new top limit, but it should be far bigger than 2000 images ... let's shoot guy :)

Another next step is the rendering. We dig up a lot of stuff already. In fact, we were forced to because we did GPU processing. Yes, we managed to do full GPU rendering :) Pretty nice. This technical achievement raised a lot of questionning in our rendering pipeline. How can we do a clever CPU core usage, how can GPU be integrated into that, could we use both together, etc. A lot of work still has to be done so that's why we disabled any GPU rendering in the current alpha, even if it's present.


I really enjoy to work with klaus on this topic. He's a really good man and the KRPano viewer is fantastic. To show you that, we decided to make a quick and 'a bit dirty' output in flash directly in this alpha ( alpha means work in progress, so don't ask for the full perfect swf output yet ! ). Two ways to access this feature :

  • rendering dialog box, swf format
  • main menu, tools : dialog box to convert a picture into swf

Nothing really fancy, but you can already start playing with flash VR with that.


In several part of the software, we made some minor changes. I cannot list them all here, but here's the principals :

  • we removed the popup progress bar that show and hide when detecting groups. It's an idea that came up many time in the future thread to have a global progress bar clearly visible. So we did this behavior and put a global progress bar in the main window ( it's not yet totally bug less ).
  • The browse folder dialog box has been revamped. It's a bit bigger but has new feature like the "group by focal" option. It creates one group per focal, easy and useful.
  • The cache. This is typically a hidden feature but so useful in the software. We rewrote it from scratch. It's faster and works now with multithreading.
  • Default exif : you can set default exif value ( lens type ) for pictures which don't have exif. For people working with HDR pictures for example,

that's a great feature to put automatically the right focal / lens type.


There are still some big feature to code and improve in alpha 2 :

  • The optimizer. That will be my first topic when getting back from holiday
  • GPU. Lionel will continue to work on this part to get the best out of it
  • Real Time preview. This is a sidework related to GPU
  • Continue flash integration
  • "N to 1 plugin" interface to prepare HDR integration

Alpha 3 will be targetted on HDR only

I think that when those features are stable and working great, we'll have a good v2.0