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.
@ancalime That's hard to say without more info. Which calibration data did you use? Which settings in APP? Which version of APP? Did you try to load the unprocessed PI file into APP and stretch it?
Normally I load my files, ie. 200 120s lights, 30 darks, 30 1s flats and darkflats (or flatdarks) in the 1st tab of APP. I subsequently leave all at tab 2 default, and press tab 3 and analyse the stars. When the stars are analysed, I uncheck the odd looking frames. I then leave tab 4 at defaults, tab 5 at defaults, and in tab 6 I leave intergrate on automatic, No LNC and I leave MBB as is, which is not enabled. When all is finished, I get the very overcorrected stack. APP wersion 1.083. See below the unprocessed PI stack loaded and stretched in APP. Also, I always have this workflow, but never had this kind of overcorrection
Â
hmmmm.... i also just decided to check all the frames... turns out that I have a few pure white frames in it.... guess we all make mistakes sometimes
Â
If I may chime in, I think I see the same in the PI result, just way less of a stretch. Can that be the case as well?
I fished out 10 pure white frames. I guess I forgot to get them out when I did APP, it might explain it. Without those, and in PI, it was a simple DBE and bob was again my uncle... havent tried in APP without those nasty white frames. But I think it's been an error on my side all along
Â


