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.
I'm getting this Java error in recent days with either 1.082 or 1.083-beta1. It doesn't seem to matter what settings I use for the TIFF. 8-bit, 16-bit, 32-bit float, different ICC pallets. All the same. Any input welcome.
Â
Ok, I'm getting the same sort of error with JPEG as well.
@tschuh Do you get the error as well when saving to FITS? Is your working folder on the internal hard drive or an external one? If external, what type is it? Normal HD or SSD?
@tschuh So you probably get this error after processing a FITS file in APP, correct? Can you explain exactly what steps you do to get to this error and upload the FITS file that was used to
https://upload.astropixelprocessor.com/
using upload1 as both username and password? Please create a folder called tschuh_tiff_error and put the FITS file in there. Then we will have a look.
@wvreeven I was about to upload my FITS when I figured out what the problem was. My A/V software (Avast) was *silently* blocking not the fwrite() but the APP application itself. A recent update made that block more vocal and it was highlighted as a blocked application, false positive for ransomware of all things. I've whitelisted the app and all appears to be working correctly again.
