I want to ask a few questions about the automatic assistant stitching: 1. Maximum time difference - is this the maximal interval between two partial photos in a panorama, or two panoramas? 2. How to set crop to "outside"? I tried --crop=Max, but it did not work (normal auto crop) 3. How to optimize exposures, but no colors? By default the optimizer is set to Arguments=-a -m -l -s What do the parameters mean?
On Friday, May 16, 2025 at 6:48:36 AM UTC+2 Abrimaal wrote: > Update > > found Mercator = set projection to 5 in normal.assistant (file in > share\hugin\data\assistant) > > Now searching how to add custom commands in "When Done" menu of batch > processor > The "any other" command could open any batch file, for example: Delete > all .log files, Open folder, Bulk Rename suffixes... > [image: when done.png] > > > On Friday, May 16, 2025 at 3:40:49 AM UTC+2 Abrimaal wrote: > >> In the Batch Processor, there is a button "User defined sequence" >> I would like to modify the initial settings of batch panorama stitcher. >> >> Part 1: >> Where is the original sequence file located? >> That I could make a new file based on the original. >> Now clicking the button does nothing. >> >> I want the batch processor to >> - Use Mercator projection for all panoramas >> - Make two panoramas from each project: with exposure correction and >> without. >> >> ---------- ---------- >> >> Part 2: >> I opened hugin.exe in a text editor, >> replaced "Equirectangular" to "Mercator" (+ 7 spaces to keep the file >> length) >> >> Started batch processor, but it still selects "Equirectangular" for >> panorama projection. >> (I do not want any panoramas in the equirectangular projection, never >> ever) >> >> After the replace, Hugin also starts with Equirectangular, but it should >> start in Mercator. >> Where else should I replace the string "Equirectangular" to "Mercator" to >> make it work? >> There are hundreds of files in Hugin folders. Please help me with this. >> >> ---------- ---------- >> >> Part 2.5 (by the way) >> It resembles the situation when I wanted to replace _blended_fused and >> _fused to _bf and _f >> I replaced all occurences in one file, but I still got panoramas with >> these long (too long) suffixes. >> I found the strings _blended_fused and _fused in many other files. >> Replacing one after one, finally it led to crash, but never saved any >> panorama with _bf or _f suffix. >> >> Sometimes I also leave workfiles (_exposure_layers), shortening them to >> _ex >> >> Now I use Bulk Rename Utility to shorten the suffixes. >> I have to do it right after the panoramas are created (to avoid including >> these files into any other projects.) >> >> ---------- ---------- ---------- ---------- >> >> @ hvd...gmail.com >> I will try Xpano, thanks for recommendation >> >> On Saturday, March 22, 2025 at 1:30:08 AM UTC+1 Abrimaal wrote: >> >>> Thank you for the hints, >>> although I haven't found out how to split (automatically) two panoramas >>> in one .pto file. >>> Manually this is quite simple, to remove images that build the pano 1, >>> save as a new .pto, then the same with the 2nd panorama. >>> Anyway, the images in the new .pto files must be reset: positons, lens >>> and photometrics, then aligned again. >>> >>> After stitching a few hundreds of simple and more complex panoramas in >>> automatic mode, >>> I noticed: >>> Positive aspects: >>> - more free time >>> - better blending of objects, the long linear objects are not broken, >>> the objects close to the camera are also well stitched. (I think the engine >>> has been improved in the new version) - it refers to the manual mode too. >>> Negative aspects: >>> - a random image is selected as the anchor, it refers especially to >>> exposures. (what about automatic selection of the highest exposure?) >>> - incorrect blending of the sky and ground - there are sharp lines when >>> the exposures or colors between two images are significant. In the older >>> versions of Hugin, there were smooth gradients, but the objects usually >>> were broken. >>> - incorrect alignment of 2 image panoramas (see the attached photo). >>> After resetting positions and lens, then optimizing again, the new panorama >>> is ok. >>> >>> Automatic stitching saves a lot of time, but many panoramas must be >>> corrected manually. The weakest point is the vertical line detector. >>> Now the line detector assumes that every straight line is a vertical >>> line. >>> The line detector will not work correctly without an object detector, >>> using Ai to identify objects. >>> Does any freeware object detector exist, that could be included in >>> Hugin? >>> To avoid placing "vertical" lines on signs, trees, human legs etc. and >>> also to find vertical lines in incontinuous objects (for example windows on >>> two floors, or joining bricks in a wall). >>> >>> >>> On Monday, January 6, 2025 at 8:09:30 PM UTC+1 T. Modes wrote: >>> >>>> Abrimaal schrieb am Sonntag, 5. Januar 2025 um 03:09:40 UTC+1: >>>> >>>> Wow, this is a huge step ahead. >>>> >>>> This feature exits since 2010, so nothing new. >>>> >>>> >>>> Unaligned image types >>>> unsuccessful photos (sometimes happen) >>>> >>>> select remove image from the context menu in the find pano dialog. >>>> >>>> >>>> separators (any photo to separate panoramas taken one after one) >>>> >>>> select split from the context menu in the find pano dialog >>>> >>>> This should be done *before* running the assistant, otherwise the >>>> assistant will probably not run successful. Also cpfind does not work >>>> optimal with such wrong images in the pano. >>>> >>> -- 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/8215cfe8-3225-44ee-81f2-7bbba0e94126n%40googlegroups.com.
