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.
Hello,
Recently bought the owners licence and now doing my first stacking after getting some new data and installing the owners licence.
When i try to save the image with or without stretch and in JPEG or in TIFF i get the following message:
Encountered error in module:
TiffImageSaver
Error message:
java.lang.IllegalStateException: output == null!
Cause:
output == null!
it.geosolutions.imageioimpl.plugins.tiff.TIFFImageWriter.write(TIFFImageWriter.java:2654)
it.geosolutions.imageioimpl.plugins.tiff.TIFFImageWriter.write(TIFFImageWriter.java:2614)
javax.imageio.ImageWriter.write(ImageWriter.java:597)
qc.a(Unknown Source)
Â
Could you please help with what i should do?
Thanks!
Rick
Hi Rick and thank you for the purchase!
Sorry for the inconvenience here, could you check if the location you are saving to is able to be written to? On what system is this?
Hi Vincent,
No problem of course.
The odd things is that the FITS files save without any problem (the automatic ones and the ones with the save button) but when trying to save manually as JPEG or TIFF it gives the error.
I have since tried to copy the data elseware and try it again, but this gives the same error.
The loading bar goes to 11%, 35%, back to 11% and then pops the error.
Would be great to know what i can try to do about this as i do not have software able to process the FITS files.
Thanks,
Rick
Â
Ah, interesting, what APP version is this on? If you're not using 1.083-beta, please try that one first. I'm wondering why the output in those cases causes a nullpointer, you indeed are pointing it to your working directory right? And any weird characters in the name perhaps (not that it should matter I think)? Is this on an external drive?
Version 1.082, this was the download that was linked in the purchase email. I have just downloaded the beta files, and will try after this process is done. I have moved all the files to a different location and doing the whole stacking process again, to see if it somehow has something to do with the files it was located in. I am pointing at the working directory yes, i did not change this. No weird characters, and not an external drive. I will let you know if 1.083 does work, should you think of anything please let me know so i can avoid installing the beta 🙂Â
The beta is fully working without any major issues so that will be fine to have as your regular build. Please keep me updated and if all else fails I'll inform Mabula for more suggestions. Again, I do apologize as it would be nice to have a smoother start. 😉
Thanks, Will do. The odd thing is that i did not have this issue with the trial version a few days ago. Will keep you posted.
That is interesting as they should be the same, which might point to something going on on your system perhaps? Anyway, let's wait for your tests.
I have just tried again from the new location an had the same issue, only after it popped up i also received a notification from my AVG Antivirus software if i wanted to allow APP to write to this "protected" location. I allowed this, and then i could save as usual, and also tried again from the original location and that also seems to be working. Somehow it had something to do with it, even though the AVG message did not pop up earlier. Thanks for the help!
Ah, antivirus protection. Yes, that's indeed something that can cause issues, they are not always responding correctly to system activities. Nice to have found out! I'll keep it in mind as well if people experience this.
@jjones Yeah looks like the same issue. I guess i was lucky to get a notification from the antivirus after many tries. Hope it works out!
