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,
As the subject says: are there recommended settings in the integration tab, when you have frames with slightly diffrent spike positions (resulting from different sessions - and let's say these frames are about equal in number)?
Kind regards, Stephan
Good question, but I'm not aware of a specific workflow for that. APP registers star positions and usually spikes don't move between sessions, did your setup change a bit in between?
Well, this happens, when you have to take away your cam from the scope or switch from landscape to portrait orientation. When bringing back the cam the positioning can differ slightly, only 1 or 2 degrees, thats the accuracy you ususally achieve, but unfortunatly it's visible in the spikes...
They can differ in that sense yes, but alignment should take care of getting the exact same orientation again right? I must say I never take photo's in portrait and then landscape, I tend to try and use a similar orientation always for a target. I never saw an issue with my spikes if I did that. But I do think that if you do, it's something that needs to be solved on the hardware side.
