Re: [hugin-ptx] Vertical line detector
T. Modes wrote: @brian_ims Kornel is on the right way. Maybe autooptimiser is still running. Check taskmanager and kill autooptimiser.exe or reboot your system. Hi Thomas Got it in one - built ok last night now rebuilding with latest update Cheers -- View this message in context: http://old.nabble.com/Vertical-line-detector-tp32443091p32454353.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
[hugin-ptx] Re: Hugin saving blank EXR files
I'm having the same problem. I tried the 2011.0 32bit windows version with no success. HDR output is always blank. If I export to ldr it seems to work just fine. Has anyone successfully output hdr (.tif or .exr) panoramas from .hdr input files? Should I use another input format? -Kiran On Jul 31, 12:13 pm, Mitch mitchgate...@gmail.com wrote: I just downloaded 2011.2 beta rc2 64bit and have the exact same problem. Then I tried 2011.0 32bit version and the EXR output works! Has anyone else been able to output hdr EXRs from any of the 2011 64bit Windows builds? That said, there are a couple of issues with the resulting EXRs they way Hugin output/merged them. First of all, the alpha is inverted. This causes all kinds of havoc with how Photoshop opens EXRs (forces black alpha pixels as transparent). Ideally I would like to force the alpha of the EXR output to be SOLID WHITE or simply save NO alpha channel at all. Secondly, the merged hdr EXR is way over exposed by default. Is there some way to control the merged Eevby an offset or something? Thanks, Mitch On Jul 30, 11:45 am, Mitch mitchgate...@gmail.com wrote: I'm using Hugin 2011.0.0.0f9fdaf56720 64bit for Windows and running into an issue with bad EXR output. I'm outputting true HDR panos (no fusion) using built-in hdr_merge during stitch process, but the resulting image file is only about 720kb for a 8604x4302 image. If I open it in Photoshop, the resolution is correct but there is no image data (blank) in either rgb or alpha channels. The ldr jpeg from same stitch looks fine and is around 40mb. None of the other checkboxes are on to save intermediate remapped images, etc. (only exposure corrected, low dynamic range and High dynamic range). If choose TIFF as my output format for the HDR image I get the same problem (small file size, all black pixels). My project uses 35 source jpegs - 5 stacks of 7 exposures each. Any ideas what's going wrong here? Thanks, Mitch -- 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
[hugin-ptx] Re: Vertical line detector
On 11 Sep., 19:41, T. Modes thomas.mo...@gmx.de wrote: Hi group, the default branch contains now a vertical line detector. It tries to generate vertical control points for levelling of the pano. I have another slight issue with linefind. When I use it from hugin, sometimes I want it to look only at a single image. If I activate just one image in the images tab and run any CPG, the CPG is fed all images instead of just the single one. With most CPGs it is of course futile to only look at a single image, because, after all, one wants CPS between several images - the only reason to apply a CPG to a single image would be for side-effects, like to generate a key file. With vertical line CPs, it's perfectly sensible to just process one image from the set, though. So my issue is with hugins's interaction with this specific CPG rather than with the CPG itself. I wonder if this wouldn't be easy to fix for someone who's inside the code? 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 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
[hugin-ptx] Re: Vertical line detector
Hi Kay, So my issue is with hugins's interaction with this specific CPG rather than with the CPG itself. I wonder if this wouldn't be easy to fix for someone who's inside the code? added special handling for linefind to work with single image. (It's more like a hack, it works only for cpg which have linefind in the program name) Thomas -- 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
[hugin-ptx] Re: Vertical line detector
On 13 Sep., 19:43, T. Modes thomas.mo...@gmx.de wrote: Hi Kay, So my issue is with hugins's interaction with this specific CPG rather than with the CPG itself. I wonder if this wouldn't be easy to fix for someone who's inside the code? added special handling for linefind to work with single image. (It's more like a hack, it works only for cpg which have linefind in the program name) I suppose new CPGs needing this special treatment won't suddenly turn up out of the blue in large numbers, so a hack should be perfectly adequate ;) It works here. Thanks! 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 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
Re: [hugin-ptx] Re: Vertical line detector
Hi Thomas, Just built the 5551. Did 2 panos and linefind works fine on OSX as well. Will do some more tests. Harry -- 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
[hugin-ptx] Re: New primary seam generator in Enblend
On 1 Sep., 13:17, Rosomack leszczynski.miko...@gmail.com wrote: Hello all, I'm happy to announce a new primary seam generator that was recently integrated into the Enblend mainline. It was developed as part of the Google Summer of Code 2011 program. I'm just doing a handheld panorama taken from the top of a reservoir dam. The banister gave me grief as there were visible blending artifacts. So I remembered having read of the new algorithm here and got the latest code from the repo and built it, resulting in enblend 4.1-101796703d73. When stitching my pano, first thing I noticed was that it was really slow. When I looked at the output, there was a gaping black hole, where enblend had simply forgotten one image. I couldn't quite believe it and reran the stitch to the same effect. When I switched back to the old algorithm using --primary-seam-generator=nearest-feature- transform, it was still slow but at least it included all images. Am I missing something - like, does the new algorithm need the images in a particular sequence? Does anyone else have this problem? In the parts where the new algorithm did place seams (so, between the images it used rather than ignored, it's a 6+1+2), the seam placement was a great deal better than that of the old algorithm. This makes me want to have the new one working very much, never mind it's slow! If needed, I can try and reduce the problem to a simple test case, compress the images and file a bug report. 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 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
