On January 2, 2011 06:35:02 pm Bruno Postle wrote:
> On Sat 01-Jan-2011 at 17:11 -0500, Yuval Levy wrote:
> >On December 26, 2010 07:07:29 pm Bruno Postle wrote:
> >> Hugin doesn't have a usable way to share lens and camera information
> >> between users, you basically have to recalculate this every time you
> >> create a project.
> >
> >A user can record his lens.ini file.  This is the first thing Pablo taught
> >me when I met him in 2007.
> 
> We still don't have any way of collecting and sharing this
> information

I see little value in sharing information that is anyway affected by variation 
in production runs.  I had three Sigma 8mm here and each of them had different 
parameters but reported the same lens according to EXIF data.  They were also 
different models.  I rather calibrate my lenses myself than rely on third 
party data.


> >There has been recently a suggestion by Tom Sharpless, which I strongly
> >support, that the serious panorama photographer has a shooting
> >pattern/grid and that this grid should be part of the input to the
> >stitching process (he specifically mentioned the CP generators, but this
> >can be even more useful for the optimizer).
> 
> I've shot lots of multirow panoramas and I each time I've gone to
> stitch them I had no idea how many rows or columns there were.
> 
> Unless you have a click-stop panorama head you will always have a
> different number of photos in each row.

even with a click-stop panorama head it happens.  Only with the motorized it 
does not.


> I see very little value in a wizard that asks you a number of rows
> and columns, this will only add complication to the GUI and won't
> help a significant proportion of people who do seriously large
> panoramas.

and yet there is demand for that?

 
> http://bugs.launchpad.net/hugin/+bug/696636

thanks.


> Though really I was only trying to illustrate how having a 'product
> vision' written down can help indicate weaknesses in the application
> itself.

yes, it always help to have a vision written down; and derive from it written 
specs; and use it to prioritize the specs.

So far we have not had the luxury of prioritizing specs - whoever is available 
and whatever they want to improve to Hugin, they are welcome.

Yuv

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to