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.
Hi all,
I am using a dual setup with a ZWO294mc (which needs to force the RGGB pattern under 0 raw/fits) and a QHY294MM (which doesn't need that),
What do I have to use under 0 raw/fits to integrate both cam's frames together?
TIA and CS
Mike
In that case I would process them separately and then save the calibrated frames. Those calibrated frames can then be loaded in together. If that doesn't work, please let me know.
Adding to what Vincent wrote: force bayer only is needed if APP cannot determine itself that the OSC frames need debayering. APP will determine that based on the FITS header so if the bayer pattern is in there then you do no need to force bayer.
Note that if you load both OSC and mono frames then force bayer should not be enabled since then APP will think that the mono frames are OSC as well. So if you load all frames and process them and you see that APP cannot determine that the OSC lights need debayering, then you need to process them separated from the mono frames and force bayer on the OSC data.
@wvreeven
Thanks, that was my thought, too.
Not sure if the FITS header work, but I will try it.
Regards
Mike
@vincent-mod
Thank you Vincent. That also answers my following question about registration 😉 If I use all the different but calibrated files, they will register during the processing!
Regards
Mike
