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. Since downloading the latest version of APP, I am consistently having problems with the results (as per the image attached). The Amp Glow from my 183CProTec is obvious from the right (despite using 50 dark files, all at the same temp etc) and the vigneting appearance is pretty awful. I have changed nothing in the way I process the files, I dither when capturing to reduce noise etc, and have great difficulty then trying to process this out to make the image acceptable.
Â
Would appreciate any advice - this has only happened since upgrading to 1.083 and then 1.083.2.
Â
Thanks in anticipation.
Â
In this regard not much changed in APP itself I think. Are you taking flats? How old are your darks?
I use Flats, Dark Flats, Darks and Bias. All of them are a day old... Since losing patience with this, I reprocessed using a library of calibration frame from 30 months ago, and the image came out absolutely fine! Settings for new Calibration frames were identical to the old ones, so I remain absolutely baffled...
That would indicate something went wrong with the new ones, you can maybe check the various calibration file headers in APP to see if you see any issues there (like different offset or offsets of 0 etc)
