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.
I am new to both iTelescope and to APP. My first imaging session with iTelescope was using T18 on M81. Some of the calibrated files I received automatically from iTelescope appeared to be damaged when loaded them into APP. The 'damaged' ones where always images taken when the scope did a meridian flip. The images from the East side appeared fine, while the images from the West side appeared damaged. Below are some screen shots: Â
This is an image using red filter from the east side. Looks good.
This next image is from the same session using the same filter from the W side. Looks damaged with no data in the histogram.
Thinking that this was a problem with iTelescope, I contacted their support, and they sent me a screen shot of the rendering of the same image on their computer, which follows, and looks fine.
Clearly there is something strange going on on my end. This strange behavior happens with all W images. I had a session on T24 and the same thing is happening. The W images are all green.
Can anyone help me? I can upload the files if needed.
Thanks.
Thanks Wouter, however Mladen Dugec from iTelescope checked the image and he said the issue was with APP and not with iTelescope. Any chance you can take a look into this? I can upload the two files. Thanks.
Hi Sikander @alexdaryan,
Thank you very much for reporting this. I am aware of the issue and it will be fixed in the next APP release. The issue is in the iTelescope FITS header where maximDL is doing something that is not standard which confuses APP at the moment.
In some frames a BAYERPAT tag will be provided allthough it is no Bayer data at all.
There is an easy work around at the moment so you can still properly process your iTelescope data.
in menu 0) RAW/FITS on the left side, set the Bayer / X-Trans algortihm to no interpolation and all should be okay 😉
Mabula
Â
Thank you so much Mabula! That worked. I am glad that you are aware of the issue and that there will be a fix in the next release. I am enjoying both iTelescope and APP! I will let Mladen over at iTelescope know about this. Thanks again.
