Apr 9 2026 APP 2.0.0-beta40 has been released !
It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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.
Hi Folks,
When I run APP with adaptive pedestal enabled, I often (always?) get the adaptive pedestal warning window as well as messages like the following regarding clipping:
08:06:45 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
08:06:45 - 2) CALIBRATE: performing calibration in 32bits normalized floats...
08:06:45 - 2) CALIBRATE: converting data to 32bits normalized floats...
08:06:46 - 2) CALIBRATE: Adaptive Data Pedestal set at: 1.755E-02
08:06:46 - 2) CALIBRATE: 193 pixels are clipping to 0.
How serious is this? How do I diagnose and fix whatever is causing this? I do have some shadowing from my OAG prism that appears to be well corrected by the flats, but maybe it's too severe?
I'm using an unmodified Canon 6D, images and darks are 150 sec, using flats + flat darks (no bias frames).
Thanks,
-Bret
@bstott_98 Hi Bret,
The warning shows that less than 200 pixels are clipping so that's not very bad. The clipping happens when the sky background in the lights is at a similar level as the darks and this can be prevented by taking longer exposures. Do you use a filter while imaging and, if yes, which one?
HTH, Wouter
Hi Wouter,
Thanks for getting back to me. I am not using any filters.
-Bret
Hi Wouter,
I’m imaging at f/10. My scope is an EdgeHD 11”.
-Bret
@bstott_98 So that may explain the clipping of the pixels. You may want to up your exposure time to 200 sec or more. Still, less than 200 clipping pixels is not very serious and may be ignored if you prefer.
Hi Wouter,
Ill give that a try. Sounds like I can safely ignore though too. Thanks for the suggestions!
-Bret
I get this as well then get some weird results which look Green or blue and nothing else, when I open these files in either siril, pixinsight or Nebulosity they look normal
If I don'tuse multiply scale but only add scale in normalization it seems all fine
I use the L-extreme and now the L-ultimate and the exposures are 10 minutes long, proper darks etc.
It's something that occurs at times with this version and the previous beta version, Windows 11
@nicholas64 Nick, can you post a screenshot of the green or blue image that you get? Do you make any changes to the settings in APP or do you simply load the lights and calibration data in tab 1 and then go to tab 6 and hit the Integrate button?
It's only after using add scale in normalization it actually works but the warning still appears.
The original image looks blue or mono colored when using multi scale in normalization
Yet when using that same image in the other apps it appears normal.
No idea why
Here is the stacked image using the default settings in APP
Yet if you put that image in say, Nebulosity it appears normal
Just stretched ans auto colour balance
@nicholas64 Does it help if you click the openGL button to the top of the APP screen such that it changes to CPU?
No difference
I might reshoot my darks with this batch as they are over a year old and see how that goes but I have to say this is puzzling.
