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.
Hello from Austria!
I'm having a problem calibrating my data. On my last project I shot lights with a Canon Ra connected to an ASIair. The data was saved as FITS. I was only able to record the calibration data in the camera's CR3 format.
In APP I can create the masters without any problems, but they don't correct the lights.
If I switch from "raw" to "calibrated" in the window, nothing changes even though I have assigned the masters to the lights!?
Can't FITS be calibrated with CR3?
CS Gernot
Hi Gernot @skanker,
That is a problem yes that has to do with image dimensions in both the FITS and CR3 format. They will probably be different and this is because AsiAir is cutting of the raw border of the CR3 data and putting that in the FITS files for capture. And the resulting FITS files will have smaller dimensions then the CR3 raws which still contain the raw border. Without knowing the cropping offsets that asiair does internally, we can not solve nor fix this. If you know the offsets, then we can fix this with the batch crop tool to make the images compatible and have calibration working on the correct pixels in the lights.
As a general rule it is good to keep in mind : always shoot calibration data in the same file format with the same software and same software version as your lights to prevent unexpected results.
Mabula
Hi Mabula!
Thanks for the explanation. I was able to immediately identify the problem with the image sizes in the APP. Unfortunately, due to a technical glitch, I was unable to record the calibration files after the session. I will now try to create the data retrospectively with the ASIair. Please keep your fingers crossed for me 🙂
Greetings from Austria
Gernot
