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, is there a way in APP to convert a BIN1 FITS to BIN2 near the hardware BIN2 CCD? Have already tried using Scale under Integration to 0.5. But don't see any change.
Dear Enrico,
Why would you want to throw away valuable information by reducing it to bin2 before anything ?
Integrating with scale 0.5 should work and give you an integration with half resolution, doesn't it?
Mabula
@mabula-admin My camera has too small a pixel size for my focal length (ASI6200mm with Edge 1100 HD). This brings me into oversampling with bloating stars. I have already tried Scale 0.5 but did not see any improvement as it would be with BIN2.
Okay, I have bin2 code ready, but it is not yet implemented in APP. Perhaps you can send me a couple of lights and I will test it and implement it going forward?
Can you upload some lights here:
https://upload.astropixelprocessor.com/
username and password : upload
Make a folder with your name and let me know once uploaded 😉
Mabula
I'm in the same boat... I shot 5 hours of data I need to convert from BIN1 to BIN2 (because I forgot to set adjust my Oiii data to Bin 2) My flats are in BIN 2. So I'd like to convert each raw image and then I can feed it into APP with my other files and it will compile. When I try to include the data it doubles or upsizes all me other Oiii sessions.
Please let me know.
