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 list members,
Over the last half year I have collected some 1750 subs in LRGB and Ha. L was recorded in 60s and 120s subs. Today I decided that it was enough data and started to run them through APP 1.078, but encountered a problem in assigning the calibration masters to the subs. There are two sets of masters, the first 6 sessions use master set 1, the other 5 sessions use master set 2.
When I load the lights I can assign them to session 1 - 11, the first 5 by clicking on "session 1" etc, the last 6 by entering a custom session name, which I called "session 6" etc.
So far all goes well and I have all subs assigned to these 11 sessions. Now, when loading the masters I run into trouble as the dialogue "To which session do we need to assign the frame(s)?" only shows the last 8 session names, so sessions 4 - 11. I can provide a custom session name and tried "session 1", which works, but then I need to assign the same master to session 2 as well, which then cancels the first assignment. I also tried assigning them to a custom session "session 1 session 2 session 3 session 4 session 5 session 6", but that does not seem to work either.
Obviously it is due to something I am oblivious of, so could someone on this forum please give me some directions on how to proceed?
Thanks in advance!
Nicolàs
bump
Woops, my apologies I seem to have missed your post.
I'll ask Mabula for this one, but just as an aside.. could you split the data up? I usually try to avoid sessions with >500 frames and decide to split those up.
Hi Vincent,
thanks for coming back on this, glad my 'bump' helped... 😉
I managed to process the data by using only three sessions, the result of which is here, but I think it is better to process them in 11 sessions, am I right?
Splitting up into separate sessions creates another problem. I have noticed in the past that if you do so, all integrations should have the same size and origin if you wish to combine them to one RGB. The problem is of course, that I then need to incorporate one of the 1731 frames (which comes from one of the 11 sessions) into all sessions and use that as reference. Or is there a better way to split up the processing?
I prefer NOT to split the processing, as that makes the whole process quicker. Now I start the processing on my observatory computer and some 12 hours later (I believe it was 10 minutes shorter than that) the job is done. When I split the job, I need to start each job, which needs my attention (sorry for my want of being lazy, but that is what computers are for... ;-)).
Furthermore I noticed that creating the NB masters in 1.078 I could not automatically apply them to the NB lights, instead they were loaded as 'MONO', despite having loaded them as 'user header tag'. So I removed them from the list and loaded them again, now assigning them manually to the NB lights. Perhaps I should start a new topic for that?
Nicolàs
I've asked Mabula to check your problem out, I've never worked with 11 sessions before. 😉 Please notify me again if he didn't within a few days (he's a busy man).
Hi Vincent,
thanks for coming back on this, glad my 'bump' helped... 😉
I managed to process the data by using only three sessions, the result of which is here, but I think it is better to process them in 11 sessions, am I right?
Splitting up into separate sessions creates another problem. I have noticed in the past that if you do so, all integrations should have the same size and origin if you wish to combine them to one RGB. The problem is of course, that I then need to incorporate one of the 1731 frames (which comes from one of the 11 sessions) into all sessions and use that as reference. Or is there a better way to split up the processing?
I prefer NOT to split the processing, as that makes the whole process quicker. Now I start the processing on my observatory computer and some 12 hours later (I believe it was 10 minutes shorter than that) the job is done. When I split the job, I need to start each job, which needs my attention (sorry for my want of being lazy, but that is what computers are for... ;-)).
Furthermore I noticed that creating the NB masters in 1.078 I could not automatically apply them to the NB lights, instead they were loaded as 'MONO', despite having loaded them as 'user header tag'. So I removed them from the list and loaded them again, now assigning them manually to the NB lights. Perhaps I should start a new topic for that?
Nicolàs
Dear Nicolàs @infinnity-deck, & @vincent-mod,
Thank you for sharing this issue. I understand what is happening, the session (and filter) selection dialogue is not prepared for so many sessions (or filters).... which creates the issue clearly. I will fix this this afternoon.
Furthermore I noticed that creating the NB masters in 1.078 I could not automatically apply them to the NB lights, instead they were loaded as 'MONO', despite having loaded them as 'user header tag'. So I removed them from the list and loaded them again, now assigning them manually to the NB lights. Perhaps I should start a new topic for that?
I have fixed this already for the APP 1.079 release 😉 so no need to create new topic for this. (The issue was caused by a change in the FILTER header tagt to allow for more than 10 filters and/or sessions.)
I will release APP 1.079 once I have your issue fixed.
Mabula
Hi Mabula,
thanks for joining in and for your answer and upcoming solution, will download the newest version as soon as it becomes available.
Nicolàs
PS: I love the new RGB-combine, get much better results with it in an easier way!
