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.
Hi, in my actual image I get strange mosaicing effects in the RGB combination tool. It produces tiles in the upper part of the image that show parts of the image below. I have an example attached.
Is there an idea what happens?
Best regards
Pete
Â
Oh that is a new one. Can you tell me what exactly you did before getting this result (your processing steps) and what kind of data you're combining? Is everything behaving normally otherwise?
@vincent-modÂ
Thanks for your response, Vincent. I am APP user from its first hour. Never experienced this behaviour before. With these data it apperared repeatedly. So I finally combined the channels in PS. I combined 4 stacked files of L, R, G and B data of this frame: https://astrob.in/full/abifgz/0/ . All other functions of APP behave normal.
Peter
Â
Edit: I just tried it once more and this time is was Ok (after it had been wrong at least 10 times before in different editing sessions). So if my issue is singular and nobody else has experienced it yet maybe is better to wait if and when and how often it will reappear or not.
That is interesting. I'm almost thinking you may have an issue with your system maybe, you aren't using an external disk to work on?
The system is stable since many versions of APP 🙂 I have a 2048GB internal SSD that is 1/3 filled as a workspace for APP and another 1024GB SSD for the other "hungry" programs like PS and LR. So the system should not be the culprit. I will try to reproduce the fault and come back to you with maybe more information. I was able to finish the image with SNR 110.3 +11.3 VdB 152 and DeHt-5 last weekend and in my eyes it is another proof for APP's phenomenal ability to produce superflat, gradientfree and well calibrated masters that allow a very deep processing:
Full Res.:> https://astrob.in/full/abifgz/0/
Pffff, that is a very very nice result. Maybe you ran into some memory hickup somehow.. hope it'll stay away.
@vincent-mod
Hope so too. Memory hickup while combining the channels is not on my list to be honest. We'll see, I'll keep you updated. Thank you once more for the support, Vincent.
Â
CS Pete
Yeah, not really on my list either, just guessing out load. 🙂 Seems weird it only pops up that time, that's why my mind was going there. Anyway, thanks for reporting and continuing to look out for it! If it happens again, I'll ask for the data, maybe we can then replicate it.
