On 27 Dez., 10:45, "Bruno Postle" <[email protected]> wrote: > It seems that this is a common problem, users of older versions became > accustomed to using the 'optimize everything' preset, but this is almost > always the wrong thing to do now we have XYZ parameters. > > We should simply remove the 'everything' preset, it shouldn't exist.
I think it shows yet again that doing panoramas and mosaics are quite different processes. Since the introduction of mosaic mode, the options in the optimizer tab have multiplied in an attempt to cater for every possible combination. I have had very limited success with translation changes in panoramas, it seems to sometimes work if the CP situation is very good and the panorama doesn't have a very large fov, but I reckon it's generally best not to touch X,Y and Z for panoramas and maybe only try in the last run when everything else is already well settled (luckily wo de have undo now!). Translation adds yet another set of degrees of fredom to the optimization problem - often that's plain too much and the whole thing fails. Even in mosaics I have rarely succeeded optimizing 'everything' - often I do a cyclical thing where I optimize, like, two parameters at a time (like, X,Y Y,Z Z,Y ...) Anyway, removing the 'everything' preset is possibly a good idea for now. How about making the presets customizable, like the presets for the CPGs? If there was a reasonable selection of untemperamental standard presets, less experienced users wouldn't be tempted straight away to optimize 'everything' and get nothing for it. Kay -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
