MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
Hi
Last night I took a series of lights and then used my library of darks for processing. However when I examined the file after integrating it seems that the darks and lights were orientated differently.Â
I am using the ASI294MC-Pro camera which has a distinctive 'amp glow'. Normally the darks usually remove this artifact, either totally or largely.
However on this batch it seems as though APP inverted the dark, as the light colour of the glow is still in the upper right and a dark version is on lower right.
I have changed nothing - other than the target - since my last images.
Can anyone help/advise?
Frank
Mmm, that is strange as the sensor will always have the amp-glow on the same side, no matter what orientation the camera would be in. Did you do anything, as insignificant as it may be, to the darks in between (like copying them over or loading them into something else in between)?
Â
Hi Vincent
I think that I have got to the bottom of this.
I have been using darks from a library built up over the past months where the capture was done using ASICap - the ASI natuve software.
However recently I have been using CCDCiel for scope control and capture. It seems as though these two capture methods differ in how they present the image data.
I am currently taking a new set of darks with CCDCiel, and the APP processed image - hopefully - will be OK.
I'll let you know.
Frank
Ah, yes that could very well be the reason. Different software introduced in your workflow may influence some things. Sometimes these packages also change the data a bit, I've seen differences in which 1 package took on row and column op pixels off, probably due to the used image algorithm it uses, which gave a mismatch for APP with the darks and lights that were taken with another package.
