Only very old releases of PTmender allow to remap pictures directly to a 
equirectangular panorama, say to output directly to a single Tiff file.
There is no reason for this, if the source files need no furter blending, 
smooth seam, vignetting etc, but just the remapping, PTmender should be 
able to export a single Tiff file.

Recent versions of PTmender force the intermediate step of creating several 
temporary Tiff_m files, that can be stitched together with further tools.

The problem with this is that the border of the remapped temporary Tiff 
files is not clean, but there are semitransparent pixles at the border.

With no hard edge between the remapped pictures and the alpha layer 
background, when using PTroller for stitching panoramas, there is a visible 
seam from the multiple Tiff files.

Alternatives to these PTmender and PTroller can be used to evade this 
issue, but they are way slower!

Nona could be used to output panoramas as a single Tiff file (and it also 
creates Tiff_m wihtout semitransparent border).
Enblend does not use the pixles at the very border of Tiff_m files to 
stitch panoramas, so it can handle the semitransparent Tiff_m files from 
PTmender, but causes errors with very big panoramas (stripes in gigapixle 
panoramas).
And as said, both are very slow compared to PTmender + PTroller.

Summarizing:
PTmender:
- please bring back single Tiff output
- please fix semitransparent border for Tiff_m output

-- 
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/7c128213-73fa-40bd-a778-0b88102d7658%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to