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 all,
I am busy trying to process old sessions from my harddrive using the
latest version of APP 1.070.
As already posted some time ago, when doing Bayer Drizzle, in many
data sets things go wrong, showing areas ( triangleshapes ) with green
background etc.
Now today I tried to process a session from M106 of last year and no way
it wants to integrate correctly, either normal or with bayer drizzle, there seems
to be some faulty image that shifts a bit ( stacked with DSS or PixInsight all stacks
normal )
I just reinstalled version 1.068 and now all problems seem to have gone
( at least it stacks normal again )!!
Could it be a faulty instalation of V1.070 maybe and should I try again
to install V1.070 to see if the fault has gone away?
Attached an image I posted earlier ( M27 ) showing the effect when things go wrong.
Thanks for any hint(s)!
Lammertus
PD: Could this be a graphics card problem??
Alas, now just finished the whole workflow through APP and whenÂ
stretching the image other areas show up that shouldn't be there.
Evenso, the integration is correct, not as in V1.070
Any clues?? ( On the left Bayer Drizzled, on the right without drizzleÂ
shown in PixInsight with only Screentransfer )
Thanks, Mert
Can this error be caused by using droplet size 0.5 and scale 2.0 ( so image will be
2x as big on both axis )???
Any help on drizzling would be apreciated!!
I have read that data should be undersampled, in my case I am not sure,
setup 1 uses TS APO 102/700 with reducer, is this setup oversampled?
setup 2 uses a Maksutov 150/1900mm, same question. ( ok just checked, thisÂ
should be ok with good seeing 1" - 2" )
Both setups use ASI1600MCC as the imaging camera.
This is likely another user error from me!!
Regards,
Mert
Ok, just one more time since there is no feedback, maybe this
can be helpful for someone else.
I just tried again on the very same image set of M27 and used
Drizzle instead of Bayerdrizzle, now the result is fine so for as
far as I am concerned this can be considered as a user error or
simple a user without enough experience 🙂
