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.
Getting this error in Normalize that essentially halts process with multiple error windows saying that same thing. Never seen this before but it has happened last few workflows. Nothing else has changed in terms of camera or image acquisition (FITS via SharpCap). It is a non-recoverable error. Help!
Â
I have also encountered this srror... any ideas?
Ross
I posted the error in this forum and in a Face Book group. Got no help. I did the following to address the issue:
- Noticed on my Windows 11 laptop that Java was not installed so went ahead and did that (I suspect a Java error is involved). This helped on one processing run and not the other where more frames involved.
- Installed APP on a MAC desktop unit (you can do multiple installs). I bring all the image files over on a Samsung portable drive and APP so far has run perfectly on the MAC. Not the most convenient solution but it works.
I suppose we could also go back to a much earlier version but then lose any "improvements" in version 2. Too bad the author did not reply to help - we cannot be alone with this bug.
This error continues to plague my processing.. I can go weeks and everything is ok and then it strikes again.. After many years of using APP and the lack of response it is about time I made the move to stacking in Pixinsight..Â
I am having the same ongoing experience. Often a restart and rerunning of APP works ok. I still think it's an external Java issue as that module has to be ended in Task Manager to clear the errors. Frustrating......
I usually process in Pixinsight and have decided to bite the bullet and learn WBPP for stacking and this has solved my problems. As I shoot Hyperstar the number of subs often exceed 200 by 50mb and neither APP or PI can do this quickly and my stacking runs are usually batched overnight. A failure in a big overnight run becomes a real set back.
Ross
