I come back to the topic after testing pano with your suggestions. The tests were done on raw files.
I would like to share my observations - it may be helpful for someone.
Erik's solution - full spherical (360 ° x180 °) and PS -> AWA -> Full sphericalThis method works and can apply it to align edges.
This is a fairly quick fix. However, it has a disadvantage of generating a full panorama and thus the resulting file is huge. When working with files from the ~ 47Mpix matrix, a flattened PS file with a size of ~ 4.4GB is generated. If PSB had individual layers it would be even bigger.
Perhaps it is influenced by the fact that so far I only have a trial version, which adds watermarks to the entire panorama. In the case of the full version, there will be no watermarks, so there will be real transparency for the unfilled panorama. However, I think that it will not be too big reduction of the resulting file size.
It is also impossible to crop (resize with ratio 1:2) this panorama because then AWA will not work.
The second and bigger problem for me is the preview of the panorama after loading it into AWA. It is difficult to work with on details, as AWA allows only 150% magnification. And most of the panorama is empty space.
The two above-mentioned difficulties can only be solved in hardware (a larger monitor and a different resolution and a more efficient computer), which, unfortunately, is not a cheap solution.
In addition, if someone replace the camera with another one with a larger matrix or switch to the medium format at all, unfortunately this solution cannot be used without major investments in equipment.
John's solution - fake "perfect" camera imagesI admit that I rejected this solution at the beginning as too time-consuming. However, I decided to try them out anyway. Unfortunately, I haven't been able to make as good fake images from raw files as you do. @John - I'd love to see you do it :) By "fov" you meant Field of View?
So I ran tests on files generated by you (compressed jpg) but for a workflow it doesn't matter. Just like the size of the generated files does not matter, because it is similar to the output files.
After uploading these fake files to PS, aligning and creating a panorama, AWA had no problem with correcting the straight lines.
There is also no unnecessary transparent space that would take up the working space in the AWA preview.
Overall, the Erika solution will be faster and more effective for large panoramas with 8 or more combined images.
John's solution may be more effective with smaller panoramas, especially when working with large raw files.
A few more notes:1. Panorama 180x360 gave me a file with 23K x 11.6K pixels. After aligning the lines, the image had a useful 7600 x 5250 pixels (horizontal position). That is less than one output file which has 5500 x 8200 pixels (vertical position). Of course, this is the result of a correction that causes the frame to be shrinked.
I would like to add that the solution with false images gives a slightly larger usable image (about 10%) than the 180x360 panorama. Here, I made the comparison for both cases on jpg files.
2. While reading the forum, in one of the threads someone asked when the version 13 of PTGui will be. And he got a counter-question: what do you need because version 12 offers a lot?. And here is what comes to my mind, what should be in PTGui in the next version. This is lens / edge correction similar to what is in PS -> AWA. I think it would be a great addition to PTGui, making it easier to work on panoramas. Everything in one place. This is my dream;)
@Erik, @John - how do you think it is possible to implement and put on the roadmap?
Thanks again for Erik and John help. This is called a real support!
@John - if you had a moment I would love to see you generating these fake images.