On Feb 8, 2015 4:09 PM, "Terry Duell" <[email protected]> wrote: > > Hello Stan, > > > On Mon, 09 Feb 2015 12:03:45 +1100, Stan Green <[email protected]> wrote: > >> I always wait at least one year before I download the next version. Today I went from 2012.0.0 to 2014.0.0 and tried to generate a pano on a set of Raw images that I had stored in Light Room. No, I did not try to use Raw images, I first converted them to TIFFs and moved them to the desk top. > > > What OS, and where did you get your copy of hugin-2014.0.0? > > >> >> The first problem I encountered is shown on the following screen shot. I was not sure what to do so I chose “Cancel”. BTW, it did not suppress further warnings, I received the alert several more times. >> > > I have not seen this before. > I am guessing that this means you have a hugin built with debugging 'on', and that there is some problem with WxWidgets. > Others may know better.
If using Debian Linux, there seems to be some issue between WxWidgets 3 and Hugin. I just click "Don't show this again, followed by Continue, and everything works. This is using the Hugin currently available in Debian Sid repository. >> The second problem was that I was forced to manually select the control points. I was testing the 2015.0.0 on a set of TIFFs that I had previously used to create a pano under 2012.0 where I had not encountered any problems. It was not a great pano but it ran with no problems. > > > Can you elaborate on "...forced to manually select control points"? > Did CPFind not return any control points, or did something else happen? > > >> >> The third problem (I gave up at this point) was that when I selected “Create panorama” I saw the following screen: >> > > OK, that's expected, > >> >> Followed by: >> > > This screen suggests that hugin hasn't been able to read the metadata it needs from your input images, i.e. it doesn't seem to know about the hfov, which probably affected the finding of control points. At this point you could enter a hfov= 50 (say) each time you are asked, and see what happens. Another choice IIRC is to click either OK or Cancel. I forget which. Happens sometimes when using images from my cheap phone. Hugin proceeds to bring in the images & give each the correct hfov. > I would have expected hugin to pop up a dialog box when you first loaded your images, asking for the hfov, if it wasn't able to figure it from the image metadata. > Can you try conversion from RAW to JPEG and pass the JPEGs to hugin and see if this makes any difference. > You might also try the "Advanced" or 'expert" interface and see if you get asked for the hfov for each image when you use "Add images". But he said these were TIFFs that worked fine in Hugin 2012.0.0. >> What happened to the idiot proof interface? > > Probably just trying to proof against a new set of idiots :-) > Changes to the hugin gui interface were adopted in hugin-2013.0.0 and briefly described in the tutorial here < http://hugin.sourceforge.net/tutorials/new-gui/en.shtml>. I don't think the intent was "idiot-proofing." (Sometimes I think the 2013+ UI is a bit idiotic itself, such as the split between the Preview & Panorama editing screens.) But it's a work in progress, as they say. > Cheers, > -- > Regards, > Terry Duell -- 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/CAHuCaafSV-qXQFFJ%3DZDuHYiq2P0RWvka%3DwND-9tA4v9P_-cbFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
