2026-10-09 APP 2.0.0-beta48 has been released !
This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
As an APP and PixInsight user
I would like to have the following extra information included into the FITS Header of the integrated file, if possible
so that I can make easier use of this information when performing further processing on the image stack.
Â
The headers are as follows:
FOCALLEN
RA
DEC
DATE-OBS
XPIXSZ
YPIXSZ
Â
As all the sub frames of my stack are produced with the same camera and scope, even in multiple sessions, this information should remain fairly consistent.
What I'm looking for is for the FOXALLEN, XPIXSZ and YPIXSZ to be included provided all the subs were taken at the same settings. If combining multiple sessions, from different cameras, I understand it would not make sense to include this information as it is likely to be inconsistent.
For the RA, DEC and DATE-OBS, the information from any sub frame included in the integration should suffice.
The intention is for this information to be used to platesolve the image, so that it can be properly colour calibrated against Gaia data.
Dear @cjdawson,
Thank you very much for your request.
This issue is on our issue list and we will address it going forward. I have added this topic as well to the issue description so we will report back here if it is done.
Mabula
Â
Hi @cjdawson,
I have fixed everything for the 2.0.0-beta33 release,the FILTER tag, FRAMETYP tag and moving all distinct FITS tags from the reference or source FITS files to the output FITS images that APP produces across the whole application. So all relevant tags for plate-solving like RA and DEC coordinates will remain present now.
This is from the release notes:
- IMPROVED and FIXED, keep FITS HEADER TAGS from reference/source files including RA, DEC, FOCALLEN, XPIXSZ, YPIXSZ, DATE-OBS etc...
As mentioned in several topics like this one https://www.astropixelprocessor.com/community/rfcs-request-for-changes/include-more-fits-header-information-in-the-integration/#post-31871 , whenever APP would make a new FITS file, old FITS tags from the reference or source file would be lost like the RA and DEC coordinates of the object in the image. This is now fixed for the entire application. Calibration masters will still have all the information from the capture software like gain and sensor offset if present, integration files will have all the distinct FITS tags from the reference frame which should make sure that all information is correct like the RA and DEC coordinates. And saving FITS files in all tools will keep the original FITS header tags that APP will not add itself. The FTIS header will have a note that indicates when the transferred tags start from the source/reference file: HDU1 - NOTE-XX = 'Distinct header tags from the original/reference frame follow below'Â
See the below screenshots for the FITS headers that APP will now produce keeping the distinct FITS tags from the reference or source FITS files. Also note the addition of FILTER tag and FRAMETYP tags as described in the release notes below:
I will try to release 2.0.0-beta33 in the coming days for sure 😊 !
Mabula
That was quick.  I'll keep an eye out for the release so that I can give it a try.
Mabula, I was able to generate Extract HA. Extract OIII, and RGB Combine SHO files with the new release yesterday that had the full astrometric solution and worked well in PI, where I was able to use several of their tools which require the full astrometric solution. The RC Astro tools in PI are quite useful. Any prospect of them working in APP? Thanks for the great update.
@mabula-admin Hiya.  I've just downloaded it, and given it a go with a mosaic created using my Seestar S50.
Was able to run the image plate solver and the Spectrophotometric Colour Calibaration using the stack from APP without having to modify the FITS header of the stack.
This is perfect.
Â
Thank you.
