Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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.
Topic starter
August 27, 2020 17:45
Over the last couple years I have imaged a target using iTelescope. I completed my run last night and went to process them today -- I use the calibrated images that iTelescope provides. I noticed that when I opened the images in Astro Pixel Processor that the images from this summer are 32 bit gray, but the images from previous runs are 16 bit gray. Wondering what I need to do next, do they all have to be the same or can I integrate/stack them all together in each channel as is?
August 27, 2020 18:08
If I'm not mistaken that should be fine, usually 16-bit is enough anyway. But I'm not 100% sure, you'd have to test that by just combining them in a run.
