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.
Hello,
Here I go again, trying to do a mosaic of 3.5 gb data, 10 frames. APP suggests to downsize as seen here, using 31 gb RAM.
How can I realize that APP works with more data, as other programs do like (very old versions of) PTGUI?
stefan
I’ve asked Mabula to respond as he know the specific reasons for this.
@vincent-mod
Hello Vincent,
that would be nice. Maybe he can have a look at this old issue from last year (...) as well:
remember? These are lightpollution and starcolor calibrated single panels (stacks) which end up with a strange color gradient which APP causes (Nikon dslr), doing mosaics. I have not found a way to influence the outcome when it appears.
Also I have encountered this:
where APP cannot register correctly two panels within a mosaic (only), as seen. This is also from a milkyway mosaic similar to the above. On serveral occasions this appears with different data. I have tried a lot to get rid of this but failed always. Maybe this has sth to do that I did a workaround saved the stacks as 16bit integer fit-files so that APP can work without this error from my first post here...
stefan
