Sharing knowledge around Autopano
You are not logged in.
APP-1.9.0-a1-r3_64 testing results on Gentoo x86_64 (Intel Core 2 Duo 2.4GHz, 4GB RAM, 100GB temp)
I ran APP using this command:
drslony@localhost ~/app_190a1r3 $ ./AutopanoGiga
The first screenshot shows what my APP looked like when I run it this way.
1- "View Image" takes much longer to open than any other raw image viewer I use. Left/Right buttons, don't work, but everything else seems correct. Choosing "Fit picture" made my whole system hang for about 20 seconds, I couldn't move the mouse, switch virtual desktops with the keyboard or anything, but the music form Amarok didn't stop playing. When image was at 100% things like the EXIF button displayed after about 0.1s, but when the image is set to "Fit picture" then the exif button takes about half a second to work.
2- This bug always happens when I run APP using "./AutopanoGiga". It always crashes when I click on "Detect" with this error in the terminal when using raw files:
./AutopanoGiga: symbol lookup error: ./AutopanoGiga: undefined symbol: _ZN12QtConcurrent16ThreadEngineBaseC2Ev
I tried using different locations of the raw files, different names of the raw files, and different raw file formats, always got this crash.
When I try using jpg files, it always crashes with this error:
./AutopanoGiga: symbol lookup error: ./AutopanoGiga: undefined symbol: _ZN20QFutureInterfaceBaseC2ENS_5StateE
When I start APP using "sh AutopanoGiga.sh" then it adapts my KDE color scheme differently than when I start it the other way, the open file dialog looks different, and it doesn't crash when I run "Detect".
The second screenshot shows what my APP looked like when I run it this way.
The rest of these points concern APP when I ran it using
drslony@localhost ~/app_190a1r3 $ sh AutopanoGiga.sh
3- The "Add Images" dialog's "Files of type" list only has one entry, "All files (*.*)"
4- 1 CPU is used when I select some images to add and hit "Open", or at least conky reports 50% CPU usage.
However when I hit "Detect", then both CPUs are used properly.
5- I tried stitching a bracketed panorama, the result was terrible. I used "Detect links in" - "one stack level". See last screenshot. I assume its terrible because APP chose the wrong image in the stack - it probably chose the +2EV ones, and some of them are too overexposed to stitch well.
6- The image in the Panorama Editor window is set to "Fit Picture", and when I resize the window it seems to work faster then previous APP versions, good.
7- When I try moving the "Info" panel in the Panorama Editor window from the bottom to the left, the window gets stretched vertically to about 2500px (see third screenshot). Resizing it normally is impossible, I had to use the "force" feature in KDE to make the second fourth and fifth screenshots. It seems to push the "Info" panel above the pano instead of floating it to the left and the pano to the right.
8- I tried detecting the pano again using "Detect links in" - "All stack levels". The detect process has been on "SIFT Key extraction" for about 15 minutes in the same spot, so I killed it and retried on a smaller set of images (now 12, then 84). On the smaller set it worked very quickly, and they were correctly detected.
9- I changed color correction to HDR and enabled RH2, it updated the preview but it was very dark, so I moved up the Key value and now it seemed to be stuck in a loop, it kept saying "Blending" in the pano status, and every several seconds it disappeared and reappeared. My system was almost frozen, but after several attempts I managed to close the rh2 window and the pano editor.
10- Images in the "Group" in the main APP window when added are not sorted alphanumerically, they seem unordered, random.
11- I tried detecting the pano again using "Detect links in" - "All stack levels". This time it took only about 15 minutes to do the whole thing and the result is much better, but there are still some rather big errors. Also the point of a stack is to keep the bracketed images identically aligned, but I see no difference between APP-1.9.0-a1r3 and 1.4.2 - some bracketed sets are still not aligned. Also I cannot move a 'stack', it just moves the individual image, same as in 1.4.2. Is the stack functionality implemented yet? Can I check somehow if there are in fact any stacks detected?
12- I tried to render a pano, but then I decided to stop rendering so I hit stop (several times by now) and it didnt stop yet, 20 minutes later, APP is still frozen.
Offline
Alexandre could you please tell us whether there is anything we need to do to:
1- make sure stacks exist and that bracketed images are perfectly aligned
2- move whole stacks using the move tool.
Or are stacks not yet fully implemented?
Offline
DrSlony wrote:
5- I tried stitching a bracketed panorama, the result was terrible. I used "Detect links in" - "one stack level". See last screenshot. I assume its terrible because APP chose the wrong image in the stack - it probably chose the +2EV ones, and some of them are too overexposed to stitch well.
I just found a horrible bug that creates a lot of mess in many stitching that were good directly with 1.4.2 and bad now. It's a general bug that explains a lot of stitching issue with 1.9
Offline
AlexandreJ wrote:
DrSlony wrote:
5- I tried stitching a bracketed panorama, the result was terrible. I used "Detect links in" - "one stack level". See last screenshot. I assume its terrible because APP chose the wrong image in the stack - it probably chose the +2EV ones, and some of them are too overexposed to stitch well.
I just found a horrible bug that creates a lot of mess in many stitching that were good directly with 1.4.2 and bad now. It's a general bug that explains a lot of stitching issue with 1.9
That's good news - I hope it's easy to fix and that perhaps we'll see a v4 release real soon?
Offline
mediavets wrote:
That's good news - I hope it's easy to fix and that perhaps we'll see a v4 release real soon?
Hum, complicated. We're working fast on alpha 2, so not a good timing to release anything.
Offline
Hmm well in my opinion wasting time on compiling another set of alpha1 revisions doesnt make much sens since we already discovered many bugs, so I would let Kolor fix them and add new features (alpha2) and then we cab alphatest that... and this way we might see the final version sooner... Remember alpha and betas are just for testing, not for production use...
Offline
DrSlony wrote:
Hmm well in my opinion wasting time on compiling another set of alpha1 revisions doesnt make much sens since we already discovered many bugs, so I would let Kolor fix them and add new features (alpha2) and then we cab alphatest that... and this way we might see the final version sooner... Remember alpha and betas are just for testing, not for production use...
Yes, that makes sense. The latest Alpha is unusable because of that 'horrible' detection bug so there's little point in doing any more testing with it at this stage anyway, so I'm happy to wait for Alpha 2.
Last edited by mediavets (2008-09-16 10:51:01)
Offline
Clicking on "New Group" should make APP jump to that newly created group... Currently if I already have several groups and I create a new one, its created off-screen so I have to scroll to it manually to add images to it.
Offline