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 am trying to figure out what I am doing wrong. I have run multiple integration session by now an every time I see an annoying grid popping up in PI. I forced RGGB and different integration settings including now a "as is" session without using bias or dark frames.
Integration 4+ hours via 600 sec subs via ZWO ASI071MCÂ
Please help? What am I doing possibly wrong?
I can't provide PI advice unfortunately, but what kind of data did you use and how did you process it in APP?
UHC-S lights (RGB/OSC), Ha (via same OSC) and initially Darks and Bias files.
Initially I started with the defaults for multi-channel / filter processing.
Shown picture was a "St-avg-19800.0s-NR-x_2.0_1.0_dr-hat-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB-Ha_UHC-S_4thLNC_it3" but UHC-S and Ha "as is" have the same grid phenomenon.
Regarding "PI", this was only used to do a quick check via the autostretch function.
AvisFS Fit viewer shows...
JUST TO BE SURE (so I can cancel one issue out), for this ZWO ASI071MC (latest version APP) I should "force debayer" (RGGB in my case) right???
Â
Looks a bit like a mosaic pattern. If you want you can upload a few raw frames (straight from the camera) for me to have a look at?
Can't.
Max upload file size 30MB... my subs are 31MB per sub.
You can upload the data to our server. Log in with appuser as the username and password. Please create a folder with your name on it first. Will that work for you?
Might it be that I didn't use "force RGB" so far. I read that for this grid issue, sometimes the Debayer function might be causing this...
Not sure, I would say APP should recognize this camera so leaving it at default settings should work. MC is color already so if it doesn't do this automatically and comes out gray, you need to enable "force CFA" and select the correct pattern.
@vincent-mod
Done. I have no flats. "D"=Dark / "DARK"=Dark / "B"=Bias, etc
So I downloaded 2 files (as a start), I think you need to give it these settings for the H-alpha;
Then the mosaic pattern vanishes. APP indeed doesn't recognize it as having a bayer pattern.
Thanks. Will do.
The first X runs was indeed on "auto detect debayer mode"
It worked.
I did now a two step process, one for the UHS data via enforced debayer, one for the Ha data with debayer settings as mentioned by you.
Both worked fine now with the ZWO ASI071MC data. Thanks!!!
Now its time to have some fun with it in PixInsight.
Sorry to Piggyback on this thread, but I just wanted to chime in and say that APP also doesn't recognise my Qhy163c properly either. I have to check the 'Force Bayer CFA' box as well, and then choose the BGGR pattern (as supported doesn't work).
It would be great if a future release would fix this, so I don't have to 'forget' to do it every time 😅Â
Vincent can you tag Mabula to add this as a fix please?
Cheers!Â
@xiga Did you verify that the FITS file contains a property for the Bayer matrix to apply? If that property isn't there then APP (or any other application for that matter) cannot know the Bayer matrix to apply.
Â
HTH, Wouter
I think that is indeed the issue. Also for camera's that have MM or MC in their name, if the company doesn't supply APP with an indicator it won't know.
Small correction: MM cameras are mono cameras and their images don't need debayering. But it is true for MC cameras.
Yes, that's what I meant. 😉 APP doesn't know what to do if that name isn't given.
Ahhh OK I understand now 😉
Is it EXIF info APP uses to detect the format (out of curiosity)
I'm not super sure myself, but I think so yes, in the fits header is where this info ends up.
