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 hope someone can help with my problem.
I have a data set which, after loading lights, darks, bias and flats, runs the calibration tab and I can look at the maste results on screen and all look fine.
I press callibrate stars and get a screen pop up and that is as far as it will go.
Is this a data set problem or the programme ?
Regards
Steve
Might be an issue in the calibration data, what happens when you integrate without any calibration frames?
I am just trying the same data on another computer.
When thats done I will try without calibration frames.
S
OK so it turns out the bias files are the problem. Leave them out and all goes to plan.
The only difference I can see is the colour space. lights are 16b RGB and NO in CFA column
Bias frames are 16b Grey and RGGB in the CFA column.
I think I read something about APT doing its Bias frames in grey because thats what it does for CCD mono. I think I will have to find out how to do colour bias frames as that seems to be the problem.
Regards
S
That might be of influence (not 100% sure), at least we narrowed it down now. 🙂
So, as far as I can tell ticking the force CFA in the 0 tab has cured the problem. All files went through the complete process with no issues.
Found this by reading similar problem by another member and just trying it out. The file set was created in APT if that makes any difference.
S
Ah, yes that could be the issue. Some capture software don’t add proper FITS keywords in the resulting subs and APP then can’t know what the type of data is.
