Hi Yuv, We had a major change of plan here because of the weather, so I can only answer you short.
I can understand. Your short answer is enough for first step. Thanks. You were complaining about cpfind and autopano-sift-c hanging indefinitely. But the screenshot you sent me tells me that the problem lies somewhere else. Yes, They hang or you can say keep working indefinitely. Please! View pdf file I also attached as a reference. I manually stopped APSC process and it however added lots of CPs. Than I optimized it with YPRVB parameters and sent screenshot. So there are two issues indefinite CP generator working and allignment. I have started Command line CP generation with CPfind. It's 01-01-2011 and 10:06 A.M. now. I normally take bracketed images for very bright areas. I have followed your previous advice to put pre Enfused images. Manually fused images with enfuse allign droplet. Enfuse GUI is a good option but it does not have allign feature so I preferred droplet. I will post files as soon as they are finished. Thanks, Emaad On Fri, Dec 31, 2010 at 7:55 PM, Yuval Levy <goo...@levy.ch> wrote: > Hi Emaad, > > We had a major change of plan here because of the weather, so I can only > answer you short. > > You were complaining about cpfind and autopano-sift-c hanging indefinitely. > But the screenshot you sent me tells me that the problem lies somewhere > else. > > Also, I see in your taskbar that there are three Hugin windows open. One > is > the fast preview (screenshot). One is the main window. And the third one? > > The screenshot you send shows an optimization issue, not a CP generation > issue. Optimization is a garbage-in garbage-out process, and bad CPs may > well > be the 'garbage-in'. > > Let's try to go at this one step at a time, together. OK? > > I want you to start an empty instance of Hugin. > > Go into the Images Tab and hit on the "Add individual images" tab. > > Add all of your images. > > Save this project as step1.pto. > > Start a command line in the same folder where you saved step1.pto and issue > the command: > > cpfind -o step2.pto step1.pto > > Post step1.pto and step2.pto to this mailing list. > > Thanks > Yuv > > > > > > > > On December 30, 2010 04:02:43 am Emad ud din Btt wrote: > > hi yuv, > > > > it is impossible to help you / come to a conclusion from what you > describe > > above. If I understand correctly: cpfind and autopano-sift-c work for the > > same large set of images and don't work for a smaller set of images? can > > you make the smaller set of images available? > > > > No, Problem is same for large or smaller set of images. I have attached a > > pdf file with screenshots of Autopano Sift-c (multirow stacked) > > cpgeneration process. This screenshot was taken after 16 hours approx. > > There are 290 images in set.Than I manually interrupted process. It > > howerver added CPs and thats good about autopano sift c. Cpfind does not > > single CP if manually stopped. Autopano Sift-c (multirow stacked) added > > CPs to set of 217 images. This quite similar to CPfind process. It keeps > > iterating, strategies and repeating process again n again. > > > > > > also: did you try cpfind and autopano-sift-c from the command line? just > to > > exclude an unrelated GUI freeze/problem, I'd run the tests from the > command > > line > > > > Dont know how to do it from command line. Is it going to folder, placing > > CPG there and than run it with parameter. Little assistance required so > > that baby do not loose path :) I am not an expert on command line or > > scripting. But ready to learn how to walk in this two way street :) > > > > panorama creation is a _workflow_ not a _software_. > > > > There is more than one workflow to create panoramas, and while CP > > generation is 'essential' to _your_ workflow, it was not to the workflow > > underlying the creation of [0]; and it is certainly not essential part of > > any software. > > > > Yuv, I here for solution and advice. I am ready to follow your advice. > Not > > here for wasting time on arguments. Can you please tell me what workflow > is > > best for doing it right. > > > > The performance and bugs of third-party tools is not the responsibility > of > > those developing, building, packaging or distributing Hugin. Feel free to > > discuss them, but don't expect them to be part of Hugin, nor for Hugin > > developers to take responsibility for them. > > > > Ok thanks for allowing to discuss it. > > > > I have attached two files. One file is CP generation screenshots. Other > > picture contains fast preview of one my project. Autopano sift c mutlirow > > stacked added (30 CPs per image set) and than optimized it with YPRVB > > parameters. Allignment is not right. > > > > On Tue, Dec 28, 2010 at 10:08 PM, Yuval Levy <goo...@levy.ch> wrote: > > > Hi Emaad, > > > > > > On December 27, 2010 04:24:02 am Emad ud din Btt wrote: > > > > Yuv, I have reported CPfind experience in my last email. > > > > > > > > "I have tried CPfind. It worked great for two projects. It added CPs > > > > for 217 images in 1008 seconds. I used default 10 cp settings. It > even > > > > added its max 50 cps per image to these 217 images in very short > time. > > > > But I dont know why its not working like that now for even smaller > > > > number of images. It goes on iterating again and again. Than keep > > > > displaying strategies and than back to iteration process. My previous > > > > experience > > > > > > with > > > > > > > autopano sift c is somewhat same. It also keeps iterating even if you > > > > leave it for 24 hours. I have tested > > > > > > it is impossible to help you / come to a conclusion from what you > > > describe above. If I understand correctly: cpfind and autopano-sift-c > > > work for the same large set of images and don't work for a smaller set > > > of images? can you > > > make the smaller set of images available? > > > > > > if two cp generators fail the same images set, an issue with the input > > > images > > > should be considered/tested. you could try other CP generators on the > > > same, > > > failing set of images. > > > > > > also: did you try cpfind and autopano-sift-c from the command line? > just > > > to > > > exclude an unrelated GUI freeze/problem, I'd run the tests from the > > > command line. > > > > > > > Can anyone, explain how CPfind works. > > > > > > http://wiki.panotools.org/Cpfind > > > > > > > Please! Read my email and help me. > > > > > > It's a two way street. Can't help you without your help. > > > > > > > My second question is....Control point generation is most important > > > > part > > > > > > of > > > > > > > panorama creation. So Why we cant work or discuss over it? > > > > > > Is CP generation really the most important part of panorama creation? > I > > > don't > > > think so. Image alignment is certainly crucial, but there are other > ways > > > to > > > align images than by generating CPs (manual or generated) and > optimizing > > > CPs. > > > > > > > When we talk about PTgui, Autopano or other commercial softwares, we > > > > > > assume > > > > > > > its a full package and CP generation is part of it.I am not into > > > > comparisons here but you will admit CP generation is essential part > of > > > > Panorama creation softwares. > > > > > > Panorama creation is a _workflow_ not a _software_. > > > > > > There is more than one workflow to create panoramas, and while CP > > > generation > > > is 'essential' to _your_ workflow, it was not to the workflow > underlying > > > the > > > creation of [0]; and it is certainly not essential part of any > software. > > > > > > It is wrong to assume that CP generation _must_ be part of any software > > > just > > > because there are software that you deem to be 'full packages'. What > is > > > the > > > definition of 'full package' anyway? > > > > > > Following your logic, you will admit that blending is 'essential part > of > > > Panorama reation softwares'. And yet Enblend is not part of Hugin. > > > Those are > > > two separate distinct packages. Hugin must redistribute Enblend with > the > > > Windows installer to palliate a major design fault in the Windows > > > operating system: it does not have a package manager. In systems with > > > package manager, > > > all Hugin has to do is 'tell' the package manager that it needs > Enblend. > > > > > > Applying the same logic to the CP generation, it would make sense for > the > > > Hugin Windows installer to distribute a CP generator because it can't > > > simply > > > 'tell' the package manager that it needs one. Unfortunately the > > > (re)distribution of most CP generators is encumbered by patents. Blame > > > it on > > > the patent holders and on the legal system in which we operate > > > (SourceForge is > > > located in the United States). > > > > > > Even if one or many software packages do cover what you think is > > > essential to > > > your workflow, it is wrong to expect any other software package to do > the > > > same. Your workflow is your responsibility, not the responsibility of > > > the software package or its authors. > > > > > > The performance and bugs of third-party tools is not the responsibility > > > of those developing, building, packaging or distributing Hugin. Feel > > > free to discuss them, but don't expect them to be part of Hugin, nor > for > > > Hugin developers to take responsibility for them. > > > > > > Yuv > > > > > > [0] <http://www.seamlesscity.com/purchase.html> > -- *Emaad* www.flickr.com/emaad -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
