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 tried integrating a few times now with exposures of different lengths. Â I have done this as single session and multi-session. Â Last night I loaded subs of 10, 30, 60, 120 and 300 seconds of M42, using multisession, to perform an HDR composition. Â
The 10 second batch went fine, but the other groups all had low #s of stars in a some subs, like 7 stars. Â Some groups, for example the 120 batch was mostly bad, and some, for example, 300 only had a few like that. Â Of course, registration went on to fail for those subs. The subs that fail are virtually identical to neighboring subs that went fine. Â I looked at the star maps for the bad subs, and all that showed was core of M42, blobs that made up 7 or so 'stars,' but none of the real stars showed. Â The star map for the good subs showed a generous amount of stars, as you'd expect.Â
I don't understand why the different exposures can't be analyzed and registered together, this has happened several times trying to do this.Â
I'm restacking now, one group at a time. Â If all goes as it has before, they'll all register/integrate with no problem. (Will update if not!)
Â
Â
Â
Â
I restacked each set individually, and they all registered/integrated with no problems..Â
So why not all together?
Hi @davloose,
On which APP version is this happening? Is it one of the beta versions, or is it happening on the latest 1.083 release?
I am assuming that star analysis is giving high star counts but that registration is failing?
It definitely should work all together.
Mabula
I believe it was 1.083 beta2. I have just upgraded to 1.083 release. Â It gives a very low count for the bad frames, between 7 and 15 for example, and high counts for the good ones, upwards of 500. The star map is telling, looks as expected for the good frames, lots of stars, but for the bad, it shows only the core of Orion Nebula and a couple surrounding regions, hence few "stars."Â
H David, okay, do you want me to have a look at the data so we can determine what exactly is happening here and why star analysis is difficult on your data? Are the stars very small or very big for example?
Mabula
That would be great, I'm uploading right now. Â As far as I know, they are quite ordinary subs of M42.
I did stack them separately, so star analysis has no trouble like that...Â
Will advise when they are up in the cloud.
Files are here, all subs, and masters for flats/darks/bias and bad pixel map:
https://www.icloud.com/iclouddrive/06f1NV105IqXi7y8RJezjjqfQ#Orion_Nebula_-_Sub_Frames_and_Masters
@mabula-admin Did you have a  chance to look into this yet?  Thanks.
Hi David @davloose,
Apologies for the delay.
Can you please upload your data here:
https://upload.astropixelprocessor.com/
Use username and password: upload
and make a folder name in which you upload your data, lile: DavidLoose-analyseStarsIssue
Let me know once uploaded and I will check it 😉
I can't and won't use iCloud so I can't access the data there.
Mabula
They are uploaded, finally! Â Dark skies == slow internet, out here! Â Thanks for having a look, @mabula-adminÂ
Hi David @davloose, thank you very much for uploading the data directly to us 😉
The first thing I tested was running all the lights without any calibration frames to exclude the possibility that there is something wrong with the calibration data. As it turns out, all frames give good star counts and registration is flawless. 10 sec frames give starcounts of about 200-300... the higher exposures have star counts of 500 so maxing out with the default max star count of 3) analyse stars.
I will now investigate your calibration data to see if we can explain what happens there and where the problem might be...
Mabula
Thank you so much!
Â
Hi David @davloose,
Could it be the case that you were running into this issue with one of the beta releases of 1.083 ?
With the latest 1.083 stable release, all works perfectly with and without calibration data. All frames show good star counts and registration is flawless on the whole dataset.
Your calibration data seems to be okay as well.
With the beta releases there was an issue in 3)analyse stars which does explain the problem that you had 😉
Download links for the latest 1.083 stable release are at the top of the forum.
Mabula
Yes, it was a beta. Â I'll try it again, I have since upgraded to latest. THANKS!!!
