UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
I have about 460 pictures of 360x180 panorama. Many overlaps at zenith. Actually I have several tries of the same panorama taken on different nights, so I have about 2000 pictures which can be used.
Is there a chance to stich them all together in APP? I'm getting warnings about downscaling and technical limits after trying to stich about 20-30 of the images.
I'm used to stich gigapixel panoramas in Autopano Giga but stiching dark skies has proven to be challenging. Transition between dark sky at zenith and light polution at horizon seems very difficult. Manipulation of such transitions gives easy visible bands between top/bottom of the images.
Is there a way in APP to solve this problem and prepare images somehow for stiching in Autopano?
Is it possible to batch save streched images with neutralized bg + saturation as tiff after registration?
Thanks for any tips!
You can try to do that, but it would require a hefty specced machine. When landscape is included, this is not something APP is made to do well yet. I would try to do it step-by-step, so smaller parts first and then try the bigger one. Before pressing the integrate button, you can always check where the panels end up after registration by choosing the "l-c-registered" preview mode on top of the preview window. This is faster than having to wait for the entire integration to finish and only then seeing it failed or succeeded. Do use the "calibrated projection" model in tab 4.
It is rather challenging though, just so you know, it may be that APP needs some more fine tuning to get that to work easier.
Looks like the 700 mpixel limit is a problem for me. My columns are 16 images high (from Canon EOS 550D) and I cannot even process one column at once. Am I doing something wrong?
How can I save images to .tiff after registration? I see there is a "save registered frames" button. It saves to .fits. Are those the calibrated images? How to convert from .fits to tiff? When I use convert on Linux I'm getting only bw images. What am I doing wrong?
Thanks!
Mmm, it might be too big of a project in the sense you do need loads of memory for tasks like that, and I haven't seen such a huge project with APP before either, so it might not be the best of experiences yet. What happens if you chop it up even more, half a column at a time? You likely also have to make it smaller in the end by quite a bit, just to be able to process it.
@vincent-mod Is it any real file size limit for APP? Because I have 130 panels of Milky Way multiply by 2 the same cameras(in final it will be around 260 panels). Of course I will first integrate separate panels and then try to integrate into final panorama, I would like also interpolate result by 1,5-2,0(based on two cameras data). So I wonder if I will use a supercomputer I will be able to calculate it, or APP does have some kind build in limit that it won't work? I expect result of around 4-5 GigaPixels.
Thank you in advance for your answer.
@mostaszewski Hi. There is no hard coded limit in APP. But I hope that you realize that you will need a LOT of CPU, memory and disk space.
@wvreeven Thank You for your answer. Yes, I am aware of this, but I will find this computing power fot this project I really believe that it is worth it 🙂 I just was worry that there is some kind of limit directly in APP.
