Bruno Postle wrote: > > No idea, maybe you need to calculate the camera response of your > sensor for reuse in your template project. > > Can you run the same project through photometric optimisation? i.e. > calculate vignetting and camera response, and see if you have the > artefacts in HDR projects created by Hugin itself? > > -- > Bruno >
Thanks for the reply. I tried that (I think) using the Exposure tab and it made the problem even worse. For the moment I'm using Hugin to write out a stitching template, nona/enblend to create the panos, and Luminance to create the hdr. I'd like to figure out what's wrong with using Hugin exclusively. Will take a look again next week. Before that, I need to get the reverse process to work. Using Luminance to create the hdr from each fisheye and then using the same stitching template (with the filenames changed) to stitch the 3 hdr. But the output from stitching is all black. I wonder if nona/enblend are supposed to be able to stitch hdr? -- View this message in context: http://old.nabble.com/Automating-creation-of-HDR-pano-tp26621718p26740289.html Sent from the hugin ptx mailing list archive at Nabble.com. -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
