Re: [hugin-ptx] Re: Remapped images and bracketed exposures
2010/1/26 Rick Workman ridgewo...@mac.com b) If the tools ever become part of the bundle, it would be helpful if the directory containing them was included in the PATH prior to calling any external script (like an automatic set_environment), so the script wouldn't have to deal with this. Alternatively, a pattern could be defined which contained the tools' directory path. I'm planning to make the tools part of the bundle within a month. The issue is not including the tools inside the bundle. I can have that arranged in 15 minutes. The issue is to make the tools available in a user friendly way. I'm thinking about that one. I set myself a month. I can already create a bundle right now with the tools in it and I have already a script to accompany the bundle. The isue would only be that the user has to modify the script once to include the/path/to/Hugin.app. Leaving that to the user is not user friendly. On the other hand: users willing and capable to use command line tools will have no problem editing a text file once to include that path. 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
Re: [hugin-ptx] Re: Remapped images and bracketed exposures
Nice, but what does final file format section give you then? Wouldn't you like to have a check box there to disable making the final panorama stitch in the case you would like to process the intermediate files or layered tiff in another work flow and don't care about a final file? Cheers O 2010/1/26 Bruno Postle br...@postle.net On Mon 25-Jan-2010 at 20:55 +0100, Harry van der Wolf wrote: 2010/1/25 Rick Workman ridgewo...@mac.com Just to close this topic, I've submitted a feature request (#2939561) to support this capability inside Hugin (no standalone tools required). Text follows. I see that you want to close this topic. Until now I remained at distance as Bruno is the expert on this topic, not me. I'd like to see all the options for 'remapped images' removed and a single checkbox for 'keep intermediate files': http://www.flickr.com/photos/36383...@n00/3855865677/ Enabling this would disable the 'clean' step and keep _everything_, users who use it would be expected to be able to cope with the additional files. Though I'm not going to be able to make these changes, so whatever happens is up to whoever does the work. -- Bruno -- 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.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- /O -- 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: Remapped images and bracketed exposures
Just to close this topic, I've submitted a feature request (#2939561) to support this capability inside Hugin (no standalone tools required). Text follows. Rick The Problem: Small stitcher errors caused by nodal point errors, poor choice of control points, and/or motion can often be corrected in Photoshop using layers and masks if the exposure corrected, remapped source images are available. For Normal output, these are kept if the Remapped images option is enabled. However, for Exposure fusion:Fused and blended panorama, the Remapped images option only keeps the uncorrected remapped images, i.e., the input to the enfuse process. The corrected images (i.e., projectName_stack_ldr_N files ) are designated temporary and erased when the blending process is complete. This precludes fixing the seam errors in Photoshop. WorkAround: The desired files are actually produced as part of the stitching process. Using a standalone copy of the Hugin_tools (I got mine from Harry van der Wolf's website), the project file can be run through a pto2mk and make all process to generate the desired files. (I created a scriptlet that you can drag and drop a project file on to automate this process.) Any unnecessary temporary files must then be removed manually. The disadvantages of the workaround are obvious: additional manual steps and downloading of the standalone tools which wouldn't otherwise be necessary. Feature Request: Add support to the GUI stitcher tab so that the projectName_stack_ldr_N files are retained. Some possibilities: a) Add additional Exposure fusion checkbox to retain exposure corrected, remapped images when Fused and blended panorama is selected. b) Extend semantics of current Exposure fusion:Remapped images checkbox to also save projectName_stack_ldr_N files when Fused and blended panorama is selected. c) Use Normal:Remapped Images checkbox to enable saving of projectName_stack_ldr_N files when Exposure fusion:Fused and blended panorama is selected. (This is my least favourite option due to potential user confusion and should probably only be done in the context of a redesign of the Output GUI.) On Jan 20, 5:50 pm, Rick Workman ridgewo...@mac.com wrote: OK, I think I've sorted this out. I've installed Hugin_tools from Harry's web site so I can run pto2mk on the project file and then run make on the result as suggested. Not particularly user friendly but I'll try and put a wrapper around it to make it easier. I'd still like to see this supported through the GUI somehow, but this will work for now. Rick On Jan 20, 4:29 pm, Rick Workman ridgewo...@mac.com wrote: On Jan 19, 5:19 pm, Bruno Postle br...@postle.net wrote: On Tue 19-Jan-2010 at 08:26 -0800, Rick Workman wrote: Maybe I'm not communicating this well, but they appear to exist temporarily as *_stack_ldr_* files, e.g., test_stack_ldr_.tiff, during the process, but the cleanup throws them away. So I'd just like an option (or parameter setting) that doesn't delete them. Selecting 'remapped images' should keep these files, but it doesn't keep everything. So my conclusion is that it doesn't currently keep the files I want, and there's no way to configure Hugin to do so.. If you stitch on the command-line with 'make', nothing is deleted: make -f project.pto.mk all Running 'make clean' will then delete all intermediate files: make -f project.pto.mk clean Can you point me at what I need, in addition to the Hugin Mac binary I have have already installed? Also is there any doc/tutorial that will tell me how to do this? My terminal skills are a bit rusty. Rick -- 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: Remapped images and bracketed exposures
Maybe I'm not communicating this well, but they appear to exist temporarily as *_stack_ldr_* files, e.g., test_stack_ldr_.tiff, during the process, but the cleanup throws them away. So I'd just like an option (or parameter setting) that doesn't delete them. This is consistent with my understanding, i.e., Fused and blended panorama exposure fuses the bracketed stacks into one set of images that are then blended just like a single set (non-stacked) of images. Rick On Jan 18, 6:36 pm, Bruno Postle br...@postle.net wrote: On Mon 18-Jan-2010 at 15:07 -0800, Rick Workman wrote: Not sure I understand. I choose Fused and Blended panorama as output. Now whether I select Normal:Remapped images or Exposure fusion:Remapped images I get remapped versions of the 18 images prior to fusing, rather than 6, exposure corrected, fused images, which is what I'm looking for. An exposure-corrected, exposure-fused image doesn't really exist, adjusting exposure before fusing doesn't improve the results. Actually, both options appear to produce the same set of remapped images. They will produce similar images if Hugin thinks they all have the same EV. If Hugin can't read the EV from the EXIF data, you will have to run exposure optimisation. Sorry if that sounds complex, what you are trying to achieve will probably work, but it isn't a typical workflow. -- Bruno -- 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: Remapped images and bracketed exposures
On Tue 19-Jan-2010 at 08:26 -0800, Rick Workman wrote: Maybe I'm not communicating this well, but they appear to exist temporarily as *_stack_ldr_* files, e.g., test_stack_ldr_.tiff, during the process, but the cleanup throws them away. So I'd just like an option (or parameter setting) that doesn't delete them. Selecting 'remapped images' should keep these files, but it doesn't keep everything. If you stitch on the command-line with 'make', nothing is deleted: make -f project.pto.mk all Running 'make clean' will then delete all intermediate files: make -f project.pto.mk clean -- Bruno -- 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: Remapped images and bracketed exposures
I have tried that option (and a few others) but it produces remapped but uncorrected versions of the original 18 images, rather than a set of 6 corrected fused images. I'm using Harry van der Wolf's recent build (2010.1.0, svn level 4892). Rick On Jan 18, 5:17 pm, Bruno Postle br...@postle.net wrote: On Mon 18-Jan-2010 at 14:12 -0800, Rick Workman wrote: However, when I have a bracketed exposure set of images and output a Fused and blended panorama with Remapped images, the remapped images do not have exposure correction applied. They appear to be the remapped original exposure images prior to fusing, and therefore aren't much help in the patching process. Is there any way to retain (I'm sure they're being generated) the set of exposure corrected images (like the set for Blended panorama) produced just before the final output? Sure, just select the 'Normal - Remapped images' checkbox in addition to the 'Exposure fusion' option. -- Bruno -- 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: Remapped images and bracketed exposures
Not sure I understand. I choose Fused and Blended panorama as output. Now whether I select Normal:Remapped images or Exposure fusion:Remapped images I get remapped versions of the 18 images prior to fusing, rather than 6, exposure corrected, fused images, which is what I'm looking for. Actually, both options appear to produce the same set of remapped images. Based on the tooltip for Exposure fusion:Remapped images, I'm getting the expected result for that option. It would be nice if Normal:Remapped images produced the desired result, but it doesn't appear to do so. Am I missing something? Rick On Jan 18, 5:46 pm, Bruno Postle br...@postle.net wrote: On Mon 18-Jan-2010 at 14:40 -0800, Rick Workman wrote: I have tried that option (and a few others) but it produces remapped but uncorrected versions of the original 18 images, rather than a set of 6 corrected fused images. This should work, though you can always stitch everything twice, saving 'remapped images' for both 'Normal' and 'Exposure fused' output. -- Bruno -- 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: Remapped images and bracketed exposures
On Mon 18-Jan-2010 at 15:07 -0800, Rick Workman wrote: Not sure I understand. I choose Fused and Blended panorama as output. Now whether I select Normal:Remapped images or Exposure fusion:Remapped images I get remapped versions of the 18 images prior to fusing, rather than 6, exposure corrected, fused images, which is what I'm looking for. An exposure-corrected, exposure-fused image doesn't really exist, adjusting exposure before fusing doesn't improve the results. Actually, both options appear to produce the same set of remapped images. They will produce similar images if Hugin thinks they all have the same EV. If Hugin can't read the EV from the EXIF data, you will have to run exposure optimisation. Sorry if that sounds complex, what you are trying to achieve will probably work, but it isn't a typical workflow. -- Bruno -- 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
