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.
APP cannot process my data.
Hi. I got some data yesterday that APP cannot process somehow. The final result are smeared stars. The first indication that there is something wrong is in the processing graph. All Stars are at quality 1. I am a beginner but it usually looks very different.
I process with the defaults.
I am about to upload the data, but it's 24GB so maybe someone can make suggestions? Maybe I need to process it like it was a mosaic because it shifted between pictures. But by not much. I also got an exception twice. But I did restart. This inability to process happens with 17 and 20 beta.
Â
Hi Konrad @guglhupf,
Your data is probably a bit noisy and/or you have very small stars (FWHM about 2pixels). Please enable the cosmic ray/noise reducer in star analysis and set it to a value of about 10 and then retry star analysis and continued processing 😉
Do you need cosmetic hot column correction? I will check if there is a problem there.
Finally, are you using calibration frames? Are you using darks and thus a Bad Pixel Map in APP? Chances are likely that if you don't, creating a Bad Pixel Map for your camera's sensor will really help here, because now APP is thinking that the hot pixels of your sensor are stars causing the misalignment in your result.
Mabula
Thank you.Â
Yes, after I tried DSS and then looked into the data in Photshop I realized that's likely what happens. The hot pixels are overwhelmingly brighter. I am a novice. The camera is a QHY268C the Scope FRA500. I also used an Optolong L-Exteme which likely makes things so dim.
The whole train is new to me ( I imaged before with a REDCAT and a ASI1600 ).Â
I did use a Bad Pixel Map and yes also a Master Dark as well.Â
Raw and Intermediately processed and final processed data is here https://drive.google.com/file/d/1YgqBqv1R7mHoNDWEQemdaBDC9-BCBAGW/view?usp=sharing
Master Dark and BPM I used are here https://drive.google.com/file/d/1UgwpUGGTJnkQR5FLezjZtBpVvqkfhwyt/view?usp=sharing
I did try the settings. But it didn't help. Still get all perfect scores.
Thank you!
Â
Ok, 15 seems to have done it
Hi Konrad, Okay I will look at your data for testing to improve this, thank you.
If you need to increase it to 15 even, then I think you are exposing your image way too short when using such a Optolong L-Exteme filter. What exposure time do you have? Your results will probably benefit a lot if you can increase the exposure time per sub.
Mabula
Sorry, I didn't get a notification. Thank you for sharing your experience. Much obliged.Â
You are of course you absolutely right. I saw it when I looked at a photo in PS. Way dark. I used 200s for the set I originally did. I used 600s yesterday. 600s is much better. But I could go even further up from there. Mount is not the best. But I think 600s will do OK. Thank you
