Version: (using KDE KDE 3.3.1) Installed from: Mandrake RPMs OS: Linux In the linux's world there is no easy stitcher. I think I should be feasible to do it because it exists on Win world (I've tested one provided by my Canon Camera). So it's probably the fist step to do one. See http://rbpark.ath.cx/articles.html that provides the easyest solution (I looking for such tools for long) by using : autopano-sift : http://user.cs.tu-berlin.de/~nowozin/autopano-sift/, hugin : http://hugin.sf.net/, and enblend : http://enblend.sourceforge.net/. It's seems easier with that tutorial but you always need 3 programs, for me it's not an easy task. It's should be an idea for a new digikam image plugin (even if it use more than one images ?) to create easily panoramic picture.
Addition by Maxime Delorme: > ------------start---------- > a new plugin for gimp appears for that ... > see http://stitchpanorama.sourceforge.net/ > ------------end------------
*** This bug has been confirmed by popular vote. ***
This probably would be better done as a kipi-plugin instead of a digikamimageplugin. Kipi tends to be more batch oriented, while d-i-p is focused on one image at a time.
While this bug has more than 400 votes by now, I am pretty much against it. There is special software for this and hugin has improved a lot since then. Panorama software is a complicated issue and there are 3 Google summer of code projects relevant for hugin this year. Integrating something as big as this into digikam or image-plugins sounds like re-inventing the wheel. From my point of view it would be better to think about a good way of how to invoke hugin from digikam with the relevant images. One possible approach for this could be the proposed service menus, http://bugs.kde.org/show_bug.cgi?id=88932
Arnd, Not sure than you re-invent _all_ the wheel. Hugin use a shared lib to perform all complex operation on image : libpano. It's include all algorithm require to process panorama. To have tried to use hugin in the pass, I can said than it's wrong approach for me, especailly about the interface. It's too complicated (like gimp for ex.) Hugin is at the oppposite of digiKam. Processing panorama must be simple. I have tried the Win32 Olympus interface provided with my old camera C3000Z to perform panorama. The workflow is really simple to use. This is what i would to see in digiKam. I will try to take screenshot of the tool in action... Gilles
Gilles, of course you don't re-invent _all_ the wheel, because hugin uses the panotools internally. But still one has to get the whole GUI right, and that is a lot of work. If you have tried recent svn versions of hugin you will see that its user interface has gotten much better and several cool algorithms were integrated, in particular the one to adjust white-balance and exposure between images (This was the first time I could stitch all my old panos where I did not know that WB and exposure is better fixed ;-) Hugin 0.7.beta 5 has as first visible TAB a three step process: 1. Load 2. Align 3. Create Panorama. (Personally I don't use this, but people seem to be happy with it!)
> I have tried the Win32 Olympus interface provided with my old camera > C3000Z to perform panorama. The workflow is really simple to use. This > is what i would to see in digiKam. I will try to take screenshot of the > tool in action... AFAIK Olympus tool is hardware supported by camera and special data on Olympus xD cards. Doing it on your own maybe more sophisticated. Some kind of simple interface for calling Hugin would be probably the best thing.
*** Bug 151471 has been marked as a duplicate of this bug. ***
I'd realy like to have the panorama tool as a native plugin to digikam. I hate having to switch to multiple programs in order to achieve a single goal: manage my photos as to speak about digikam. I don't like the idea to call hugins from digikam. why should we call an external program for panormama and not for simple edition. Why not call the gimp or krita for simple edition (if you extend the idea of calling an external program). To go forward with this idea, why no creating a specific profile for konqueror to browse photos with specific service menus that would call some gimp scrips or the like. More over, if you start depending on external software, you're at the risk that: 1) a digikam equivalent includes the feature and becomes more attractive 2) the external program can become incompatible with digikam 3) the program can be abandoned or integrated in a digikam alternative More over, having multiple GUI behaviour is realy a bad experience (ok/cancel button inverted, not the same dialog boxes, once the image is edited, do I save it and overwrite or is the program aware that I'm editing a picture and clicking save replaces the original without prompting. Many usability problems in perspective IMHO. (of course, I admit that it's not an easy task and as I'm not a developper, thus I can't complain ;-) . Those words are only here in the hope it can highlight some trouble not creating a native panorama tool.)
I'm totally agree with Olivier. If something must be done, it must be a new plugin as well, with a simple interface to perform panorama, not a very complex interface outside... Gilles
I think a kipi plugin would be really nice, too. I just downloaded my images from my canon, and really thought, such a tool might already had been implented. After searching around in the menus of digikam, I just realised, I have to download another software for this, which I was not very happy about. So you can see, from the users perspective, having a native plugin is the better choice - but besides *not* having a plugin at all, of course external use of another app might be a solution, but not a good one. If hugin uses libraries (including some dependency to autopano-sift on my ubuntu machine), it may be possible to use this piece of softwarelibrary to create a front end as kipi plugin if the user wants more perfect solutions, not just an easy tool, he can use hugin - like he can use krita or gimp to manipulate his photos in more ways, than he does with digikam. So the kipi plugin just needs to adress the most likely scenario: put some images together as a panorama.
product digikamplugins -> kipiplugins
Git commit 014ef1a5ebdd38f4ac2498f51f5a36363912ab9a by Gilles Caulier. Committed on 15/08/2011 at 17:58. Pushed by cgilles into branch 'master'. New Panorama kipi-plugin is now ready to use for next release 2.1.0 BUGS: 98693 BUGS: 235766 M +0 -2 CMakeLists.txt http://commits.kde.org/kipi-plugins/014ef1a5ebdd38f4ac2498f51f5a36363912ab9a