Share:
Notifications
Clear all

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.

Combine images like HDR: short and long exposure

8 Posts
3 Users
3 Reactions
4,878 Views
(@ippiu)
Neutron Star
Joined: 8 years ago
Posts: 147
Topic starter  

Hi @vincent-mod and @mabula-admin

I was looking for a way to combine or integrate images from different exposures: i'd like to image M13.

I usually use this approach with different sessions and/or different filters.

But I came across this @mabula-admin's message and it seems different from using above method: https://www.astropixelprocessor.com/community/gallery/m42-hdr-cropped-my-dusty-first-attempt/#post-5479

Any explanation about which method mabula is referring to? 

(I don't think he is referring to different sessions)

Thanks



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

I don't think you linked the other method you're referring to.
Combining data with different exposures is no problem, you can all load it in as 1 session or multiple sessions if you have calibration data for each separate session. however it's not going to produce a HDR result, this option is not available (yet). If your target is a cluster, you might want to set the weights in tab 6 to "star shape" (and if you're integrating > 20 frames, integrate set to average). This will prioritize the frames with the best star-shapes and thus result in an integration with rounder and smaller stars. You can always experiment with these weights to see what the result will be.



   
ippiu reacted
ReplyQuote
(@ippiu)
Neutron Star
Joined: 8 years ago
Posts: 147
Topic starter  
Posted by: @vincent-mod

I don't think you linked the other method you're referring to.

Sorry, i explained myself very bad.

The "other method" i was referring to, it was supposed to be an alternative method Mabula was referring to in his reply: i don't know which method.

I was interested in Mabula's sentence highlighted in red:  

Posted by: @vincent-mod

 If your target is a cluster, you might want to set the weights in tab 6 to "star shape" (and if you're integrating > 20 frames, integrate set to average). This will prioritize the frames with the best star-shapes and thus result in an integration with rounder and smaller stars. You can always experiment with these weights to see what the result will be.

Probably this is the same method Mabula was referring to in his old reply and you are explaining to me now: right?

For instance: i have a set of 20s 50 images of globular core well exposed. 120s 50 images of the same core blown out all white. I integrate in 1 session: prioritize star shape. Using this method and playing with its settings can i achieve a well expose globular core, even if half of the images have burnt white core?

Basing on this red highlighted sentence it should be the right method i'm looking for (try avoid HDR photoshop layers):

I haven't imaged the globular cluster yet, but i'm already looking for a good way of process all session of images. 

Thanks a lot as usual for your support 



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Yes, it's the method he mentioned and indeed that's the tooltip for the weights I explained. So, these weights will be purely focused on the stars and their shapes, APP won't make a nice HDR result where the core will be nicely exposed and the rest as well, this still needs to be performed in other software.



   
ippiu reacted
ReplyQuote
(@turfpit)
Red Giant
Joined: 7 years ago
Posts: 24
 

@ippiu

https://www.astropixelprocessor.com/community/gallery/m42-running-man-multi-exposure/#post-9256

I just loaded all the frames (lights and calibration) for the 5 different exposures and processed as though it was a single set of exposures.  Seemed to come out OK with little effort.

Dave

 

 



   
ReplyQuote
(@ippiu)
Neutron Star
Joined: 8 years ago
Posts: 147
Topic starter  
Posted by: @turfpit

I just loaded all the frames (lights and calibration) for the 5 different exposures and processed as though it was a single set of exposures. 

So, Dave, do you mean just 1 session with all exposures together?

Or 5 different sessions as it seemed from your sentence in the original post, where you wrote "I loaded the multi exposures into APP as a multi-session and here is the result."

 Which integration method did you choose? All automatic? Or average and then which weight?

Thanks



   
ReplyQuote
(@turfpit)
Red Giant
Joined: 7 years ago
Posts: 24
 

@ippiu

Looking back in my processing folders - I loaded each set of exposures into its own session (5 in all).  That ended up with 5 stacks which APP transparently dealt with.  For integration I used 'automatic' plus the defaults as offered.  I always use the defaults as they seem sensible and always give me decent results.   I was surprised at the outcome for so little effort - I like fast and easy. 

Next time I try this technique will be on M31 when it comes around - maybe 120s or 90s and then some 10s for the core.

For the M27 I just posted in the Gallery, I had several frames with meteor/satellite streaks but APP dealt with them using the settings it offered.  

Dave

 



   
ippiu reacted
ReplyQuote
(@ippiu)
Neutron Star
Joined: 8 years ago
Posts: 147
Topic starter  

Thanks, Dave



   
ReplyQuote
Share: