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'm new to making calibration frames.
1) I have 4 nights of data I want to calibrate so I can add more later. When adding Lights, I am having it choose the filter but selecting 1 session for all four nights. Is this correct? I had always made each night a session before but was told it wasn't needed.
2) My working directory is in a folder "Stacked". The output of frames goes to a folder "Calibrated 1-4". Is this the best way to do that? What will I get saved to the Stacked folder?
3) When I calibrate the next 4-8 nights, do I load the raw darks and bias files I used this time or will I have "Master" files to use? Does that make a difference?
4) When I am ready to stack to get my final LRGBH files, do I just put the calibrated frames in Lights and nothing else? Thanks!
Steve
There is no 'right' way to organise your data. Whatever works for you, helps you avoid mistakes and reminds you what you did is the 'right' way. I can give you a run down on how I do it, but feel free to disregard what I say and do what makes sense to you. When I was first starting I was pretty haphazard about data management, but over time I developed a more rigid structure that works for me.
Bear in mind that your acquisition software may have rules or capabilities that affect data management. I use NINA, so my workflows will start from there.
I only use sessions to group data by exposure time. In the layout below (which is related to narrowband imaging of a faint target), session 1 has all the 10 min exposures for Ha and Oiii and session 2 has all the 20 min exposures for Sii. I make no distinction for data from different nights. I may add a session 3 to hold 2 min rgb exposures for star colours if I get the chance.
However, if you are setting up your equipment from scratch each night then it may make more sense to use a session for each night so that each session can have its own calibration frames.
Often you may only need one session, even for multiple nights.
Â
I hope this is legible.
The working directory (Work) is where APP stores all the files it creates, unless you tell it differently.
Each Masters folder holds the masterdarks and masterflats that relate to that session. They can be created (in Work) during your first test integration and moved to the masters folder for use in later integrations, assuming your optical setup is unchanged. After they have been created the Flats, Darkflats (Bias) and Darks folders can be deleted.
The Lights, Flats, etc folders are created by NINA (in my setup). Each folder has a subfolder for filter type (again - assuming NINA is set up that way).
Assuming you only use one camera there will be a BPM that can be stored in any masters folder and used for all sessions.
The final integration is pretty simple. For each session load the raw lights from the lights folder, the master calibration frames from the masters folder and you are good to go.
Â
Hope this helps
JC
Â
@connor231 thanks! I am using Nina at StarFront so my scope is always there.
How does NINA save to folders by filter, etc. Currently, all my subs are uploaded to a folder on my cloud drive, all at once. I can sort there by name or date created. It would be nice to go into separate folders.
Steve
In NINA, under Options/Imaging, there is a field called 'Image file pattern'. This can contain details on how NINA is to save its subs.
The pattern I use is:
$$IMAGETYPE$$\$$FILTER$$_$$TARGETNAME$$\$$DATETIME$$_$$GAIN$$_$$EXPOSURETIME$$s_$$OFFSET$$_$$FRAMENR$$
This pattern creates a folder for each imagetype (lights, flats, etc) and a subfolder that concatenates the filter name and target name.
The last part is how it creates the filename for each sub. All this must be entered precisely, but gives a lot of flexibility and control over NINA.
I'm using an older version of NINA, but I think this should work in the latest version.
JC
Â
@connor231 Is the difference that you put a "\" in the format rather than the underscore "_"? That causes the folders for Lights and inside, target and filter?
Steve
Yes that's right.
It works like a typical Windows directory string and file identifier. Each "\" separates a folder from a subfolder, except the last "\" which precedes the filename. The "_" is just a placeholder that is placed into the name to make it easier to read.
Its a format that is familiar to oldies like me, who go back to the days of MSDOS (or even earlier).
JC
I'm new to making calibration frames.
1) I have 4 nights of data I want to calibrate so I can add more later. When adding Lights, I am having it choose the filter but selecting 1 session for all four nights. Is this correct? I had always made each night a session before but was told it wasn't needed.
2) My working directory is in a folder "Stacked". The output of frames goes to a folder "Calibrated 1-4". Is this the best way to do that? What will I get saved to the Stacked folder?
3) When I calibrate the next 4-8 nights, do I load the raw darks and bias files I used this time or will I have "Master" files to use? Does that make a difference?
4) When I am ready to stack to get my final LRGBH files, do I just put the calibrated frames in Lights and nothing else? Thanks!
Hi Steve @stevehookem & John @connor231,
Steve, did all of your questions get answered? Or do you still have more questions about this? I think that John (thanks!) has answered part of it?
1) The separation of data into several sessions is only needed if you will calibration data that is different for the different actual/real life sessions. So if you can can use all darks, bias, flats from the first actual session also for the other subsequent nights. Then you can simply disable the multi-session mode and treat all data as 1 session.
2) That will be fine, in the working directory, a temporary file is created and destroyed while integrating your data. The working directory is also the default location of your integrated files, unless you select that save directory yourself.
3) You will be able to use the previously created masterframes. You can load them directly as masters with the master load buttons in 1) Load. It will not make a difference if you don't load the masters that you already have, and thus recreate the masters, since they should be indentical pixel by pixel and thus give identical calibration results.
4) Yes, if you chose to save the calibrated frames, then you simply load those to make your integrated LRGBHa files.
Please let me know if this answers all of your questions.
Mabula
Â
Great Steve!
