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.
Good afternoon,
  After processing my data at default settings I am getting this strange tiled/striped result. I am using Dark, Flat, and Dark Flat calibration frames. I have selected to only use the best 80 out of 91 frames. Any ideas what may be going on? Any insights would be greatly appreciated!
Thanks much, cheers and clears,
Bill
Bill (@canofbill)
I certainly don't have a definitive answer - so what follows is guesswork.
It does not look like an optical issue or a processing issue. It looks to me like a hardware issue, somewhere between the camera sensor and the AsiAir. The first thing that comes to mind is failed hardware in the camera itself. But that's probably best left as the last thing to consider.
It could just be a cable issue (I'm assuming you are using a standalone AsiAir - rather than one of those "built into the camera" units). I used to be sceptical when the Cloudy Nights guys suggested cable failure - until it happened to me twice. There are some truly terrible cables out there, and ZWO used to supply some of the worst (but I think they have gotten better). Now I only buy premium cables (from Lindy Electronics) and they have never failed me.
The AsiAir appears to be based on a Raspberry Pi. Its a neat little unit (I have one myself) but I've heard they can be subject to failure by corrosion - especially if you live by the sea.
Lastly, I think that an exposure time of 0.2 sec (for flats and darkflats) is too short for the sensor used in the 533. I would increase it to 1-2 sec. I don't believe that's the cause of this issue, its just general advice.
JC
I figured it out!
By decreasing the interpolation from 1.0 to 0.8 it effectively "downsampled" enough to register and integrate properly!
Thanks for the input JC, much appreciated!
