Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

Multi session DLSR - best practice

6 Posts
4 Users
0 Reactions
3,085 Views
 Mark
(@gilgm)
Main Sequence Star
Joined: 5 years ago
Posts: 18
Topic starter  

New to APP , and watching and reading as much tutorials / faqs as I can.

Cant seem to find a specific way to get the best output from Multiple sessions in my Bortle 8 area , of the same target over a period of months. At the basic level If I use the same Focal length , exposure , ISO settings over multiple nights am I better to combine either :

1. Integrate all in one go using the multi session option.

2. Integrate each night separately as 1 session. Then combine the integrated final non stretched fits produced at the end of each session together. Will it treat the final integrated Fits from each session as ‘Light’ files that have been fully processed . So in effect I’m stacking the final files from each night together?

Tia.

 

 

 



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

You can create integrations of a few nights together (ideally over 40 subs at least). This will not stress your system as much as combining everything (which requires a big system ususally). Those integrations can then be combined again when you have them all, the result should be quite nice doing it that way and yes, you can load integrations as lights. No calibration frames then of course as they should've been used already for the integrations.



   
ReplyQuote
(@igor_cheb)
White Dwarf
Joined: 5 years ago
Posts: 13
 

@vincent-mod

Will there be a difference between the two ways (i.e. a) stack everything in one go and (b)stack each session separately and then stack results) ? If so which should give better result? 



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

Hi Igor,

Sorry I was on the move for a few weeks. So, theoretically stacking the subs would give a slightly better result. However, in practice, I never really saw that and it's not always handy either as a lot of subs can give memory issues. You can try both approaches to see if you see a difference, but I tend to combine integrations I corrected fully etc.



   
ReplyQuote
 Deep
(@app3sashimi)
White Dwarf
Joined: 3 years ago
Posts: 13
 

Hello

I recently started using APP and started to experiment with multi session approach. If I produce integrated fits (non-stretched) from individual sessions what is the process to combine them? Do I load them up as light frames and run integrate ? I noticed pulling them as "processed" files and trying to integrate complains that there are no light frames. 

Thank you



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

You indeed just load them in as lights.



   
ReplyQuote
Share: