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.
I made a mistake in giving a name for a new distortion model. Can I change that name and if so, where do I find the file containing that new name when searching under Windows Explorer?
Thank you for your answer and best regards,
Thierry
I have to say I never used a distortion model myself. It isn't stored in the working directory that you set for APP?
@vincent-mod
I have been searching within the directory C:\Users\...\AppData\Local\ AstroPixelProcessor but couldn’t find any file that has the date stamp corresponding to the date I added the new distortion model.
I’d like to delete one old distortion model as well in the file I’m looking for.
Any other suggestion where to look at?
Is that your work directory? APP asks what directory you want to use for data processing at the start.
@vincent-mod
I have been searching in the working directory first but couldn’t find it there, therefore I have been searching in the installation directory of APP which is the one I mentioned in my earlier post.
Any other idea where to look for?
@vincent-mod
I meanwhile found the file: it sits directly under C:\Users\me as user\ under the name “APP-cameraProfiles.txt”
Oh hey, that is weird. I'll pass this on to Mabula!
@vincent-mod
I modified the file meanwhile: I deleted 1 distortion model within the file and modified the name of the other distortion model. When looking in APP it looks fine.
Ok, got word from Mabula. So the location of the profile is indeed correct, the thing is that a profile isn't dependent on a dataset or project so the profile is stored in the location of the license. It should be used carefully as well, especially when using telescope equipment. A profile works best when you have a regular camera with objective as this doesn't change. A Newtonian telescope for example, there the profile will change depending on things like collimation. It can be used to speed up mosaics for instance, but only when you can be sure of the profile staying exactly the same, so in general the advice is not to use it with telescope data.
@vincent-mod
Thank you for the extra information. It seems indeed logic that a profile for a telescope is less predictable then for a camera with lens. I will see what I will do with one profile, which is a ZWO camera on my Celestron 9.25”.
Best regards,
Thierry
