June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
I have one of the new ASI6200mm cameras. I gathered a bunch of darks and bias when I first got it. Later, I changed the gain and offset to experiment with read noise, well depth and offset amount. I was reusing the darks and bias while gathering new flats for test images. All of a sudden I could not get my flats to remove dust donuts and calibration was really causing strange "bright" vignetting. I tried changing APP setting and calibration was still not working. Then I realized I had changed gain and offset from the initial darks and bias. I redid my darks and bias with the new gain and offset. Now APP works great again.Â
Â
Thanks for explaining your workflow and solution! Yes indeed, changing the gain will change the noise profile which causes a mismatch for calibrating the flats.
I am not so sure that the gain and offset were my calibration problem. Did that make sense, Vince?
I had the same problem again even with the correct gain/offset for lights and calibration frames. I was also getting an error about "Corrupted Image" randomly on all types of files. Then I noticed that there were both upper and lowercase filter names. My setup uses filter names that are all lower case - lum, red, green, blue etc. The load dialog shows my lower case names along with Luminance, Red, Green....etc
Once I assigned my frames to the correct filter name (my name variations were listed at the top of the channel assignments), calibration worked fine. I also no longer got the "Corrupted image" errors.
I will rename my filters in my capture software (SKYX) to match APP names. That should keep me from making the wrong assignments. Maybe APP should check for name variations to prevent this? I'm sure others have made the same mistake without even realizing it.Â
Randall
PS - using the image viewer and switching between linear/l-calibrated makes checking the calibration results easy. Best to check this before continuing in case calibration didn't work well. That is really a great feature of APP.
