Bruno, I like this idea: > http://wiki.panotools.org/SoC_2009_idea#Simple_mask_editing > i.e. put a mask editor in the hugin Crop tab, save the masks as > vector/polygons in the .pto project file and apply the mask at the > nona rendering stage (i.e. this wouldn't involve modifying enblend).
It sounds like it would simplify my workflow and reduce the scope for user-error. For example avoiding the problems I created for myself in my first stumbling efforts with Alpha Channel Masks when I tried to make them grey-scale rather than black. Anything that reduces the scope for user-error has got to be good. If it is also straightforward to store and process then it seems like the unstoppable choice. all the best George On May 7, 9:14 pm, Bruno Postle <[email protected]> wrote: > On Thu 07-May-2009 at 04:54 -0700, grow wrote: > > >> I think grow's project should be tested using Bruno's elegant technique > >> to store masks in external files. > > >Could you give me any pointers to where I would find an explanation of > >"Bruno's Elegant technique". > > I've done a lot of testing to try and figure out the best way to > modify the alpha masks that are fed to enblend. My current > preferred solution would be to implement the proposal here: > > http://wiki.panotools.org/SoC_2009_idea#Simple_mask_editing > > i.e. put a mask editor in the hugin Crop tab, save the masks as > vector/polygons in the .pto project file and apply the mask at the > nona rendering stage (i.e. this wouldn't involve modifying enblend). > > Though one of my test tools is enblend-mask: > > http://search.cpan.org/dist/Panotools-Script/bin/enblend-mask > > This is a wrapper that allows you to have an external bitmap mask > for any enblend input file, the idea is that you manually edit masks > in these external easily compressed files and the two masks get > merged before blending. This is useful because you never want to > keep the enblend input files afterwards, so editing them manually is > bad. > > I think it would be trivial to add this as an option to enblend and > it would also be useful. > > The other test tool is tiff2svg/enblend-svg: > > http://search.cpan.org/dist/Panotools-Script/bin/enblend-svg > > This is another wrapper, it uses a multilayer SVG file to specify > enblend input, this is useful because SVG supports polygon masks. > > This is currently the only 'nice' visual way to easily do masking, > but it doesn't scale because none of the SVG tools deal with cropped > TIFF or 16bit images properly. Hence my preference for doing > masking in hugin eventually. > > -- > 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 [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 -~----------~----~----~----~------~----~------~--~---
