Hi! Am Sonntag, 26. Mai 2019 16:20:43 UTC+2 schrieb Roberto ornelas orozco: > > Try using enblend 3.2 instead of 4. You can download ir from their page un > sourceforge
The current enblend version 4.2 that ships with Hugin 2019.0.0 actually works. No need to use old versions. Just check Hugin's preferences for the default enblend arguments (used for new projects), they changed from version 3.2 to 4.x and need to be adapted if you still use old settings. If you work with old .pto files you might want to check the enblend arguments for this project. The documentation is available from http://enblend.sourceforge.net/index.htm or directly here: http://enblend.sourceforge.net/enblend.doc/enblend_4.2.pdf Some notes: - Basic enblend arguments for Hugin In Hugin you can add commandline arguments either by entering directly to the 'options' dialog for your current project or as a default for new projects in the Preferences. If it works for you without options just leave this line empty. - There are basically to points to look up in the documentation when - enblend's output shows artefacts or you'd like to improve the way the seam is generated -> current enblend features - enblend fails to run on the complete set of your images -> problem solving Since enblend is a work in progress each version can show certain changes in how it processes your images with certain arguments. That's why you need to first of all determine the enblend version your current installation of Hugin is using: - stitch a simple panorama (to save some time you can deactivate all but two overlapping images in the preview window) and keep an eye on the stitching log. Search the first dozen lines for a line starting with 'Blender:' - If that log closes too fast make sure (that in Hugin Preferences the 'Stitching' tab uses (in the third paragraph 'Processor') PTBatcherGUI with option 'Verbose Output' activated). Now while stitching your panorama switch to PTBatcherGUI and make sure that both options 'Verbose output' (shows a separate window describing step by step what's happening while PTBatcherGUI processes your project file) and 'Always save log' are activated. The latter saves a .log file in the same directory as your .pto project file. The .log file can be opened in a basic text editor like Notepad++ (Windows) or BBEdit (OS X). The verbosity level can be increased in Hugin's Preferences and for enblend in the stitching tab (add '-v' once or even up to 6 times to make it a real chatter box) Here are the current enblend arguments I use: --preassemble --primary-seam-generator=nft --blend-colorspace=identity -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/0ba94f55-f010-4a5e-8e58-fd6d6de583de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
