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.
Dear experts.
I have 7.7 hours (3 sessions), 231x 120sec, ASI2600MC with Askar FRA 500 (no reducer), on M81/M82. Dithered every 3 frames.
My questions:
- Are there best practice parameters for drizzle and droplet size?
- For 1) - 6) I used all standard parameters, except in 6) LNC 4th, 3 it.
- I want to have separate R G B channels.
--> Shall I do lpc/cbg before or after channel split?
--> Or even do csc before the channel split?
In addition I have a 4th session, 2.9 hours with Ha-OIII duoband filter (Altair 6nm), 58x 180sec, dithered every 2nd frame.
I want to use "Ha-OIII extract Ha" and "Ha-OIII extract OIII"
- Shall I use the exact same parameters for 1) - 6), including the same drizzle/droplet?
- And again: shall I do lpc/cbg on the 2 resulting integrated FITS? Â (Before using all the channels in Combine RBG)
Because the framing in all sessions is different, I need to do reg/norm of the channels.
--> Again: before or after lpc/cbg?
The two principal variants seem to be:
- 3 sessions w/o filter: Integrate OSC sessions, lpc/cbg and csc, split channels into R G B
Session with duoband filter: Ha extract from Ha-OIII, lpc/cbg
and then OIII extract from Ha-OIII, lpc/cbg
reg/norm of all 5 channelsorÂ
- Integrate OSC sessions, split channels into R G B
Ha extract from Ha-OIII
OIII extract from Ha-OIII
reg/norm of all 5 channels
lpc/cbg for each of the 5 channels
(Then my question: When do I do csc, if I want?)
Thank you and best regards.
Michael
----- Bonus question 😉
Would you propose any changes, if I do the linear processing and stretching of the 5 channels (R, G, B, Ha, OIII) in PixInsight?
(I would like to try BlurXTerminator.)
I would like to do lpc/cbg here in APP - so variant 1 or 2.
Shall I do reg/norm of the 5 channels here in APP?
PS: Just remembered this post, where Mabula (@mabula-admin) recommended for my Fuji XH2-S (same Sony sensor as ASI2600MC, same 26 megapixel, also APS-C, 600mm lens) to drizzle with scale 1 and droplets 2.0
==> Can I derive correctly to use the same for ASI2600MC with the 500m FRA500 telescope ?!
I integrated the OSC images (7.7 hours have become 7.6 hours, I left out all frame with quality score < 400):
- 0) Adaptive Airy Disc, 5) Neutralise Background: off, 6) LNC 4th, 3 iterations
- Drizzle/Droplet in 3 variants: 1.0/1.0 - 1.5/1.5 - 1.0/2.0
Here the comparison:
1.0/2.0 is quite a bit noisier, (at least) I cannot see more details
1.0/1.0 and 1.5/1.5 are quite similar - but I see a small bit of more details in 1.0,1.0
(Though it's difficult to compare in Mac's preview, as the 2 files have different pixel size.)
I derive from this to go with 1.0,1.0 ...
Hi Michael @michaelacg,
For workflows like this, I think the proof is in the pudding, so you need to experiment for yourself and see what works best for you, or for your data actually. The ideal workflow can actually depend on the object that you shoot.
But I can of course give you some general guidelines / best practices:
- definitely do lpc/cbg before channel split
- csc calibrate star colors can only be done before channel split
- yes, do LPC and CBG on the Ha and O3 channels as well
- But, if you can and want to combine R,G,B,Ha and O3 to 1 composite, you can also simply do LPC/CBG on that composite
- Personally, I would do workflow 2, register and normalize all subs of all channels when making the R,G,B, Ha & O3 stacks. CSC is wouldl do then on making a RGB composite, perform CSC on that to have accurate star color for your final composite.
- Bonus response: yes, still do reg/norm in APP
Regarding all the drizzle options, there is never a best setting that will work on all data. Drizzle performs well or not well depending on many factors, amount of data, quality of data, dithering, undersampling etc... As a guideline, for Bayer Drizzle, you use 2x the droplet size as for mono data. If you drizzle but do not change the scale, so keep it at 1.0x, then use droplets of 0,5-1 for mono and droplets of 1-2 for RGB. Simply said, for Bayer Drizzle, scale 1.0 and droplets of 2.0 are more or less the same as not drizzling, but still debayering the data. The lower you set the droplet size, the more drizzling becomes apparent, but also the noisier the result will be.
So for drizzle in general, you need to experiment really what is a good value for your data and this is very personal I think. Drizzle is always a balance between getting sharpness or noise... so you will get more sharpness with more noise, or less noise with less sharpness and the droplet size controls this. sharper and noisier is with smaller droplets 😉
Hope this helps?
Mabula
Thank you, Mabula.
By coincidence, I just posted a minute earlier the comparison of the 3 drizzle variants.
Re. you advice to do workflow 2, i.e. register and normalise all 5 channels in one run.
- I wanted to do this ... including 6) Integrate ...
- ... and stumbled over the question, which option I shall choose in 0) RAW/FITS:
- for OSC I learned to choose Adaptive Airy Disc
- but for the Ha-OIII filter, there is the option "Ha OIII color", which I interpreted as generating an OSC FITS for my filter frames. - So my conclusion is:
a. Integrate OSC and filter frames separately (using Ha-OIII extract XX)
b. lpc/cbg, maybe csc
c. separate channels
d. reg/norm all channels
e. and finally rotate, crop
Is/where is there a misunderstanding?
