2013/11/4 T. Modes <[email protected]> > Hi Frederic, > > Am Montag, 4. November 2013 15:19:15 UTC+1 schrieb Frederic Da Vitoria: > >> I have been wondering: why not use Hugin_stitch_project as default? How >> often do Hugin users really need to batch assemble several panoramas at the >> same time or shut off their computer when the panorama is finished >> assembling? >> >> That is a disagreement inside itself. How should the issues fixed, if > nobody tests it and help so to improve it. > > You have often advised new users to use hugin_stitch_project instead. That > is not helpful at all. This should be the last step, if all other solutions > don't work. > I advised the users some steps to try to solve the issue (because I think > in most cases it is a special configuration or the issue is behind the > keyboard.) > But with your advise to use hugin_stitch_project there was never a > substantial feedback to improve the behaviour of PTBatcherGUI. >
OK, I'll refrain from advising this from now on. But you realize that similar problems have been going on for several months (more than a year?), that it generates frustrated Windows users (I have a hunch this is a Windows-specific issue) and that in the Windows world, the general user behavior is: "if the software doesn't work, then use another one"? Windows users who know what a bug tracker is (I am not even saying "who know how to use a bug tracker") are few. So that letting users get hit by PTBatcherGUI problems might achieve getting less Hugin users instead of solving the PTBatcherGUI issue. > You never used PTBatcherGUI and have therefore not contributed active to > its improvement as you always demand. > > Thomas > > PS: If you reduce PTBatcherGUI to a batch stitcher you have not leashed > its full power. It contains a lot more functions. > You are right, I had never looked at all it could do. Checking the documentation... Sorry, I just checked, it still does not contain any option I would use. And I don't expect this to change because: - I never do panoramas with more than a dozen pictures (usual number is 3 - 4), so that the assembly time is usually much lower than my patience, and I don't have the time to start a new panorama during the batch phase, - I do many panoramas in mosaic mode, often also "time lapse", and a little exposure or focus blending, while PTBatcherGUI seems to make most sense if you use the assistant, - I always shoot hand held (I don't even own a tripod) so that automatic assembling is often hopeless, while post-processing individual images generated with Hugin allows me to get acceptable results. I don't expect any software, even one which I would have paid big sums of money for, to be smart enough to make something usable out images with parallax errors. I know, I should change my methods, but I don't even want to buy a SLR because of the weight, so a tripod is completely out of my scope. I understand that other users can find PTBatcher useful. But this is simply currently not true for me. All that PTBatcher would do for me is add an unnecessary and useless step, with all the risks of something going wrong and the added complexity of finding if that problem would come from Hugin or from PTBatcherGUI. If it helps you to find what is going on, I can do a test, though. I can even file a bug, provided I can reproduce the issue, of course. -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CANe_y9RtaGXYjMdZDrA42F59A265WG%2BWEY-b5zWRPVmNLjH_dA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
