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.
When I calibrate my lights (all with gain 111) with darks, flats and darkflats (all of them with gain 111) the '2) Calibrate' process sometimes halts asking to select the correct masterflat for light frames. Version beta-24.
The dialog provides two items to chose from: one is the correct flat (at ISO/gain: 111.0), the other is a weird item: "MF-IG_0.0-E_0.0s-notAvailable-5496x3672.fits".
And searching through the astropixelprocessor directory I found other items like "BPM-notAvailable-5496x3672.fits" next to a proper BPM fits file.
Why is that?
Dear Gilles @museceleste,
that notAvailable indicates that there are flats without an instrument tag in the FITS header. You can fix those frames with the Batch Modify FIts metadata tool 😉 find the problem files and then create new ones with the correct Instrument name, the instrument name is the name of the camera and that name is controlled by your capture software/hardware.
Â
Thank you! Decidedly, APP has answers to almost every thing 😉
Didn't know about this batch tool. Now that I do, I have 3 more questions (sorry):
1. With regards to the APP dialog on the left hand side, I can't find the HDU1 'filter' nor the HDU1 'Session' tags in my flats (even in regular/normal flats created by my ASIxxx camera). Do these header tags exist? What should they contain? Does the tool massively replace only the non-blank (or filled) fields?
2. After opening/selecting several flats with the tool, is there a way to inspect their individual headers sequentially (e.g. by pressing a NEXT button?)
3. Is there a textbox into which I could enter a header tag content and let APP search for the corresponding file(s) that contain it? And would it support wildcards?
Tks
Gil
Hi Gilles @museceleste,
THe Batch Modify FIts tool is made for issue like this. Data created within 1 imaging session where the captured software or hardware did not have correct settings or was misconfigured by mistake.
So the frames that you load into tool should be from the same imaging session, then you will know that the header tags present or not will be the same, right?
The filter tag should be in the FITS HDU normally, most capture software will put that tag into the saved files. The session tag is not standard, APP will enter this in saved images that were loaded in multi-session mode with a session tag applied to those frames.
If you need to alter the instrument, enter a new name in the instrument field and the saved files will have that in the Fits HDU.
Mabula
