Thanks for the feedback Greg and Thomas. As I suspected, this is a problem only I have, and I have my workarounds. The first is to just export layers, the drag and drop the files into a batch script that calls TuFuse. The second is to adjust the command line parameters to Enfuse so that I get a more pleasing result. Enfuse and TuFuse are based on the same algorithm, but sometimes the default settings for TuFuse produce a slightly more pleasing result to my eye when compared to the default Enfuse settings.
Thanks again, Jeff On Saturday, October 25, 2025 at 1:01:46 AM UTC-7 T. Modes wrote: > Hi Jeff, > > Jeff schrieb am Samstag, 25. Oktober 2025 um 05:13:01 UTC+2: > > In src/hugin1/base_wx/StitchingExecutor.cpp, there are 7 instances of " > --compression=". > > > There are also other parameters which are passed in the --arg= form. > So for consitent behaviour I don't want to change this for a single > parameter for a single extern program not used by default by Hugin. > For using other programs the easiest way would be to use an user defined > output sequence. There you have better control above all switches without > the need to re-compiling. > The format is written in doc/executor_file_format.txt and Hugin come with > an example file for smartblend > (share/hugin/data/output/normal_smartblend.executor) > > The only drawback is that you loose the ability to choose the output > format on the stitcher tab. Instead you would need several user defined > output sequences. > > Thomas > -- 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 visit https://groups.google.com/d/msgid/hugin-ptx/a0d3ab6a-a96c-427e-95e2-c9a79365ad0cn%40googlegroups.com.
