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 am having problems in 2.0 39 beta with the alignment of stars within my triple imaging rig, it seems like the individual channels (one shot by each scope) are not correctly aligned once registered and stacked. I can literally make it better by tweaking alignment in PS between the channels and that just never happened in 1.083.4. Its like something is going wrong with the sub pixel alignment between each of the three filters. Giving me rainbow stars. Its not lateral chromatic aberration either as its like they are out left to right across the entire image.Â
Anyone know anything about this?
Could you indicate what settings you used? A good idea in some cases is to do a reset of the settings first as they are being saved after closing APP.
@supernov I have changed no settings from the original ones. There used to be all sorts that you could tick, tune dynamic distortion correction etc.Â
Could you try it with disabling the dynamic distortion correction?
@supernov possibly but as of right now i know 1.083.4 worked for me and so i am trying to work out how to grab a copy and try that with this data. The problem is that you get small variations between the optics (and even small difference in focal length) on each scope so you so need to do some field correction to get it all to match up with each other, not sure how turning dynamic distortion correction off would help with that, in the past its been better to have it on under 1.083.4.
Ah yes, sorry I glossed over the multiple telescopes part. I think Mabula may ask for some data to check, I do know there have been improvements in the registration engine between 1.083 and now, but if there's a situation where something doesn't work properly he'd love some data. Pinging Mabula @mabula-admin It may still be interesting to know the RMS values of registration without the correction, just to see if that is indeed definitely needed.
Hi Adam @adamj,
Thank you very much for sharing your issue. The new registration engine of 2.0.0-beta39 is by far superior to 1.083.4, so if bet39 is not working, something weird is going on and I need to see it.
What do you mean by a triple imaging rig? Simply shooting R,G,B ? If so, are you registering all filters at the same time? If not, try that.
Please upload your data here so I can investigate myself:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
please make a folder with your name and issue like : Adam-RainbowStars
and upload your data there and let me know once done, thanks !
Mabula
