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.
Hello,
Â
please have a look. I calibrated as usual, cmos 6200mm same temp, same gain, same offset for all calibration frames and get ok for Ha, but not for red:
uncalibrated:
calibrated:
Ha looks normal, Red absolutlely not, easily seen.
any ideas?
this is how the flats look like:
the stretch on red seem very strong...
the exposure times on the flats are for red 0,2 secs, Ha ca. 3 sec (done by autoflat aid in APT)
could this cause that?Â
Â
stefan
22 hours and no ideas here, ok...
since I had 2 days lost due to this before I continue, since pixinsight worked on it with all calibrationframes without any problem!
I suppose the "again - error" in APT claimming my mono files are RGGB written in the files header could have caused this, for this was the only thing I set in the WBP scripts in PI to mono my hand. If this is so, someone should have a look into it in APP, for a hint in the header should not be able to destroy the entire stack, should it?
Â
e.
APP does look at the header to determine what the files are, if the header provides the wrong information then APP will do the wrong thing, this then should be fixed at the data acquisition stage indeed.
APP does look at the header to determine what the files are, if the header provides the wrong information then APP will do the wrong thing, this then should be fixed at the data acquisition stage indeed.
That is one option, yet not the most customer friendly. Taking a look at Pixinsight's Weighted Batch Preprocessing
tool shows that there are better options for cases where a lot of data like this happens to exist. Instead of having to convert each single frame - and with the Masters it even did not work- and wasting lots of time and nerves one just pushes a buttom and it works in WBPP. Your response does not help here at all, does it only state the plain obvious
Well the issue originates from somewhere else, so of course it doesn't help in APP itself. We can try to accommodate that, but usually we try to contact the other developer that can issue a fix. I will discuss this with Mabula though.
Well the issue originates from somewhere else, so of course it doesn't help in APP itself. We can try to accommodate that, but usually we try to contact the other developer that can issue a fix. I will discuss this with Mabula though.
That will not change anything. Note what I said above and the cause is also not clear, since an old version of APT was used for certain reasons on an old pc for other reasons. I bet there is a reason why in Pixinsight you can easily set it. For transparency. So that you see if someting is wrong, no matter why (!). You seem to be a bit selfreferential. Try to see the needs of the customer first and maybe a bit faster - and not that point of view of APP-developers...Â
