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 been having issues since my latest PC build. Working with a R7 5800x3d 8 core, 32GB RAM, and a 5TB HD, only thing that has changed is the processor. It has happened pretty much with every integration session. I deleted most of the files that said they were corrupted but I have verified that I can open this in kstars so I don't think the file is corrupted, but I sent it to that email address per the instructions. Any hint as to what might be the root cause?
The error that gets output says
"The FITS file:
.. RC10 Atik 383L+ Dec 2023\M82_120s_-20d_2x_b\M82_120s_-20d_2x_b_Light_B_001.fits
seems to be corrupt unfortunately.
The fits kernel can't be read. But, if you can load this FITS file
with other applications, then please share this fits file with us
so we can test it and hopefully fix this problem.
You can send this fits file to support@astropixelprocessor.com so we can test it."
Thanks, Clear skies,
Dalton
Just a quick update. I am getting this error during the calibration phase now. It is saying one of my dark FITs files is corrupted but that one I can also load in kstars. Any settings I should tweak?
The issues seem to be compounding 🙁 Now when I run my normal flow I can't even load the first calibration frame (dark) without getting this message. Sometimes it take several minutes for the error to show up, and during that time it is trying to load a single file, the RAM usage hangs around 550-600MB, out of the available 32GB. Can I provide any logs that might be helpful to get this resolved?
I've just updated my version from beta 14 to to 29.
Analyze Stars went from about a frame per second, to over a minute per frame. No clue why.
And during integration I got an error message about bad .header information. Sorry, didn't screenshot it. Will do if it happens again.
The issues seem to be compounding 🙁 Now when I run my normal flow I can't even load the first calibration frame (dark) without getting this message. Sometimes it take several minutes for the error to show up, and during that time it is trying to load a single file, the RAM usage hangs around 550-600MB, out of the available 32GB. Can I provide any logs that might be helpful to get this resolved?
Hi @daltomagne,
First of all, which APP version are you using? Did you try the latest APP version 2.0.0-beta29? If not, please do and let me know what happens 😉
If you are using the latest APP version, please realize that the file or files can be corrupt although Kstars can read it. If Kstars produced the file, it probably is not following FITS conventions verey well. We use a library from NASA to read/write FITS files, which follows the FITS conventions precisely.
Feel free to upload the problem FITS here, so I can test them myself:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder like : DaltonOrtega-fits-read-issue
and let me know once uploaded 😉
Mabula
I've just updated my version from beta 14 to to 29.
Analyze Stars went from about a frame per second, to over a minute per frame. No clue why.
And during integration I got an error message about bad .header information. Sorry, didn't screenshot it. Will do if it happens again.
Hi @cheetah,
Did you check if data calibration is working as expected with the calibrated image viewer mode? Chances are that calibration has a problem. Or perhaps you have too noisy data, in case you need to enable the cosmic ray/noise reducer, did you try this in 3) analyse stars?
Did you try to analyse the stars without calirbation data? Is it working fast then?
Mabula
@mabula-admin Hi Mabula, I have been running that same version, 2.0.0-beta29. I have uploaded a FITS file to that site under the specified folder. In this stack (285 L frames @ 16MBper frame), around the 80th image under star analysis it slows down tremendously, took another 10 minutes to load and analyze the next few frames, then eventually quits the process with that error posted above.
Hi, just wanted to check and see if you were able to open the FITS file I uploaded. Anything look corrupted?
