tennevin yves wrote: > I've been using Hugin to created enfused or exr HDR files from sets of > image that are not a panorama.
is there a reason why you don't use Qtpfsgui or other HDR tools? > 1- By default the projection is set to equirectilinear with an angle of > 360x180. because this is the most panorama of all panoramas and hugin is a panorama stitching tool. > Such images needs a rectilinear projection, so I need to change the > projection and calculate the field of view. > 1 click on Assembling tab. > 2 click on rectilinear projection. > 1 click on Field of view calc. > 1 click on optimal size calc. > =>5 clicks consuming the user time. probably Hugin could be marginally improved if it would automatically calculate FoV and optimal Size after images are added/moved around. Does not take much, and it could be set as a preference. Same thing for the projection. Many people are not doing full sphericals and so the equirectangular projection is not optimal for them. Some logic could be developed to determine an ideal projection (rectilinear -> pannini -> cylindrical -> equirect) based on FoV and user preferences. Both of the above are probably less than one hour of work to an experiencd coder, and IMO would make sense. Writing patches for these would be a good exercise for GSoC student applications. > 2- I need to create control points to realign the images, this is easily > done, but there is an issue: > Is there a way to only alignate images versus the first one and not all > together. > eg: 7 images for panomatic, currently it does: > (1-2) (1-3) (1-4) (1-5) (1-6) (1-7) (2-3) (2-4) (2-5) (2-6) (2-7) (3-4) > (3-5) (3-6) (3-7) (4-5) (4-6) (4-7) (5-6) (5-7) (6-7) > meaning 21 comparisons while it could do > (1-2) (2-3) (3-4) (4-5) (5-6) (6-7) > meaning 6 comparisons assuming the exposures are classed in this order. > Is there a way to pass the control point creator the informtion to > handles images in this way, so the complexity is not dependant of F(n+1) > but of (n-1) (F = Fibonacci Function here.) > It also costs: > 1 click on control point tab. > 1 click on create control points. > 1 click once the controls points were added... > => 3 clicks. This is a major weakness of Hugin, as pointed out by Bruno. Hugin does not have provisions for brackets. It will require a change in the underlying model so that brackets can be recognized. Then images in a bracket can simply be assumed to be aligned (because of tripod shooting), or CPs can be generated respective to a reference image in the stack. This would be helpful for panorama making too, but is quite complex. I think Tom Sharpless has developed some thoughts in this direction. Could become a GSoC project Added to GSoC 2009 potential projects. *Anybody* can add their ideas there, and students may pick them up. <http://wiki.panotools.org/SoC_2009_idea#bracketing_pano_model> Tim has published a patch that can be helpful in some pano HDR situations, but I don't think they will help you. <http://ultrawide.wordpress.com/2008/11/16/hacking-hugin-part-1/> > 3- Alignements: > We need to optimize the image shift... > optimizing positions usually works, but it still needs: > 1 click on Optimize tabs. > 1 click on optimize (assuming we use the default one). > 1 click to confirm. > => 3 Clicks I don't understand how you would want to avoid this step? if your images are tripod-aligned, you don't need 2 and 3, just use Tim's patch. If they are not tripod-aligned, optimization is inevitable? or am I missing something in your feedback? > 4- Color optimization has to be done without vignetting optimization... > The issue is that there is no option to perform it, it's not hard, it > only requires to optimize the last paramter and not the others but... > 1 click to click on exposure tab, > 2 click on custom parameter, > 1 click on 'photometric response' > 1click on Optimize... > 1click on 'I confirm it is right...' > => 6 clicks consuming the user time. Special case, but why not accomodate it if we can? I think that this point to a preference. I have similar situations when I have to change in the Optimizer tab what lens parameters are optimized. I think it would be relatively easy to add an Optimize preset "Camera Response only" and add a preference tab for the default Photometric Optimization (and for the default Lens geometry optimization too). > Could we get a button in first tab probably not because the first tab is for the simple panoramas, but your feedback is helpful to improve the special functionalities that make Hugin the Swiss Army Knife of panorama making and beyond. Thank you for taking your time to describe your user experience. Yuv --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
