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 a trial license and after integrating half of my final image was blocked by a grey area. Is this due to it being a trial license? If so how can I fix it.Â
Meaning if this is caused by something other than it being a trial license, what could it be and how can I fix it.Â
Hi Robert @hank-bobo,
Thank you very much for posting your issue and welcome to the APP forum !
The Trial license provides a 100% working APP version, so everything works the same as with a paid license. Your issue must be caused be 1 or more bad frames that actually have no data but show that grey area. I recently saw this with several frames of the Celestron Origin telescope actually. You need to browse through your images and find the problem frames and delete them.
After 3) Analyse stars, you can probably see from the frame list, which are the bad frame or frames. They will have a low star count or very different values than the other frames. With the right mouse button over the frame list, you can delete the problem frames.
Let me know if this helps.
Mabula
@mabula-admin would this issue only be caused by the light frames?
I noticed my dark flat frames are oriented differently than the rest of my frames. They are 4000x6000 instead of the other way around like all my other frames.Â
@mabula-admin would this issue only be caused by the light frames?
I think it can be caused by any frame actually, so also by your calibration frames. I would first check your lights though.
I noticed my dark flat frames are oriented differently than the rest of my frames. They are 4000x6000 instead of the other way around like all my other frames.
That is weird yes, what capture software or hardware are you using to make your images? It could be an orientation setting in the software or hardware that captures your frames.
Â
@mabula-admin I took out the dark flat frames from the integration and the problem was fixed. I used the same hardware as my other frames. A Nikon d3300 with a coma corrector on a skywatcher 300p on an alt-az mount. I will look into getting the dark flat frames oriented in the correct way and try again. Thanks for your help!
Does the camera have some sort of auto-rotate feature? I think I have heard of that before being an issue sometimes.
@vincent-mod while taking the dark flat frames I think camera may have been angled in such a way that it automatically rotated the images.
Hi Robert @hank-bobo,
Okay, thank you for the feedback. So the problem was solved with leaving out the flatdarks, right? This must mean that that artifact is in one or more of your flat darks. The camera probably made an error while saving the frame in the camera. That can occur and it would like your issue in fact.
The rotation of the images is not the cause at all. The orientation is metadata that APP will ignore when loading those frames to create calibration masters and to calibrate the light frames. That orientation tag on the frame causes it to show oriented differently in normal photography software and you can see it in APP as well if you enable orientation above the image viewer, but it has zero effect on how the images are processed 😉 So my advice is to double check each of those flat darks and then you will fine one with this banding artifact. Delete it, and then reprocess with all the flat darks left and all should be okay.
Mabula
