On 17 Jan., 14:11, George R <[email protected]> wrote: > First odd thing. > At first when I changed the Program Preferences to use MultiBlend it > seemed to not take me seriously! (I also have this problem sometimes > with humans.:-) When I re-ran an existing project it just used > enblend as it always had. After several tries over a couple of days > ...
I've hit upon this. The reason AFAIK is that changing the hugin preferences only affects new projects. It's really fiddly to get an existing project stitched with something different, but as you've found out, being persistent can do the trick ;-) I've forgotten what precisely you have to do to change the setting for an existing project (modifying the relevant line in the pto and restarting hugin before loading the pto might do the trick - the line I mean is "#hugin_blender enblend" towards the end) - and pressing the 'Apply' button in the preferences might also have an effect - opposite to standard GUI behaviour where pressing Okay will apply a setting, I think in hugin it may not override the existing project's settings. > it eventually did seem to use Multiblend and after that I couldn't get > it to go wrong. I have made a wild guess that perhaps if PTBatcher > is open (which I suspect it was in my case) when a preference is > changed in Hugin then PTBatcher needs to be quit and restarted before > it will apply the new preferences? That is reasonable behaviour - but > perhaps it could be mentioned in the instructions somewhere. Indeed the bahaviour is confusing. I think the rationale, if any, is to make sure a given pto will create the same output every time, so if an existing PTO is loaded, it's settings will rule. > Second Odd thing > When I did get Hugin to use Multiblend the resulting panorama had > colours that were quite odd. The blues were sort of copper-coloured > or flesh-tones. Greens were shades of turquoise. Browns were shades > of grey. It was an interesting effect ... it looked a bit like the > scene had been shot on something like infrared film. This time my > guess was that the problem lay with my 16-bit Tiff input files. So I > re-created my input-image-set as 8-bit Tiffs and this time the project > ran to completion producing an acceptable stitch. This is a common problem with multiblend. You need to pass it the -bgr flag. For some reason it sometimes uses BGR instead of RGB. > It would be great if MultiBlend could handle 16-bit Tiffs as the > projects where I have problems with run-time tend to be the ones using > large 16-bit Tiff images. I also use 16bit TIFFs. With the -bgr switch, the colours come out all right. 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
