MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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 am running into a problem performing 1-star comet registration on two different image sets from the same night.
I use a barn door tracker. It can track for about 30 - 45 minutes. After that I have to reset/rewind, resume tracking, and recenter the camera on the comet field. The delay is only a few minutes of time, but the second image set is offset (and slightly rotated) compared to the first image set.
If I try to register all images in APP, the resulting integration stack will have a double comet nucleus, and the double star trails show that there is also a slight angular misalignment. Somehow the software does not appear to be properly keeping track of the registration changes in the second set of images.
As a workaround I am performing normal (multi-star) registration on all images, saving those registered (and normalized) images, then registering again using comet/1-star mode, then performing final integration.
Am I using an incorrect workflow? Am I asking APP to try to do too much at once?
(First attached image shows final integration result after using the workflow method I described above. You can see the shift/rotation difference between the two image sets. Second image is a final integration of about 175 frames of comet 104P Kowal from last night.)
Thank you in advance,
Tom Krajci
New Mexico
I did a quick double check of my comet image workflow on a small sample of images.
 This shows the integrated result after using comet/1-star registration on three different image sets from the same evening. You can see there are differences in positioning and rotation of the camera frame.
But a close look at the final stack/integration shows:
...the comet images are not accurately registered, so the nucleus is triple. Also, the stars do not show motion in a straight line between the three image sets, so there is also a problem with keeping track of the necessary rotation for proper registration.
At the present moment my workflow is to calibrate and register all frames using normal registration...save these registered (and normalized) frames...clear/reset/restart APP and then register all these frames using comet/1-star registration.
I think we can do the same question with the data I already asked for you to upload. 🙂
