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.
Hi! I’m having a strange problem with OSC images I debayer, stack,integrate, remove LP and color calibrate in APP, then load into PI for access to BlurXterminator. I want to bring back into APP for more sharpening and stretching as I prefer those tools. The image is linear FITS the whole time. However when I load back into APP the color appears to be gone. Even setting saturation at max.
I did not have this problem with RGB images taken with a mono camera. Im wondering if it has to do with Bayer matrix or the particular FITS format I use when saving from PI. It has a lot of options for bit depth and signed/unsigned integer etc. Any ideas?
Wayne
Mmm, can you save at a 32-bit depth at least?
@whixson, best will be to save it in 32bits floats since the data would still be linear. Maybe the BlurXterminator tool does something which affect the color info?
Do you want me to check the result that you load into APP?
@mabula-admin thanks Mabula. Actually I tried saving in APP, opening in PI and immediately re-saving with no processing in PI and still have the problem. I’m not sure if I used 32 bit float? I’ll try again
Did you ever figure this out? There "shouldn't" be but I wonder if this is related to the ROWORDER and the XISF format. There are some interesting debates/arguments about PixInsights handling of ROWORDER. I have some strange color behavior between APP and PI. If you are still trying to use BlurX I suggest using DBE in PixInsight then BlurX, then come back to APP. BlurX works best before color calibration. There is also a program now that works like BlurX called AstroSharp and you can run it at the end of image processing. Search Github for it.
Hi @whixson, I tried myself, I opened a color FITS integration file created by APP in Pixinsight, saved as 32bits float and the image looked exactly the same as the original in APP when stretched in APP.If the image would look different, then by all means, it is a Pixinsight problem I would think?
Did you try? All okay now? I know that an older version of APP had a bug with 32 bits integer files, so I double checked that as well, saved as 32bits integer in Pixinsight and then loaded it into APP. The file again looked exactly the same in detail and color which it should.
Mabula
Did you ever figure this out? There "shouldn't" be but I wonder if this is related to the ROWORDER and the XISF format. There are some interesting debates/arguments about PixInsights handling of ROWORDER. I have some strange color behavior between APP and PI. If you are still trying to use BlurX I suggest using DBE in PixInsight then BlurX, then come back to APP. BlurX works best before color calibration. There is also a program now that works like BlurX called AstroSharp and you can run it at the end of image processing. Search Github for it.
@dheyergmail-com ROWORDER should never influence this problem. ROWORDER applied to raw images that still need to be demosaiced. The problem reported here deals with already demosaiced data 😉
