Is 686 images too m...
 
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.

 

Is 686 images too many for APP?

8 Posts
3 Users
0 Reactions
2,303 Views
(@chuck666)
Brown Dwarf
Joined: 4 years ago
Posts: 4
Topic starter  

I am integrating 686 images that are 39.4mb ea. APP is using 336.3 GB of free SDD. I have 11 threads set as available and 28 gb of Ram available. Using trail version 1.082. After 5.5 hours, I'm just at 37% completed and running integrating pixels as I write.

Is this correct? Another 11 hours to complete? DSS would take about 2 hours and AsiDeepStack about the same. Siri would be about 20 hours. 

Chuck

 

 



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@chuck666 Can you tell us more about the configuration used in APP? Did you simply load the lights and calibration files, go to tab 6 and hit the integrate button or did you modify any of the settings in tabs 2 to 6? Are all images of the same framing or did you load a mosaic? What stage of processing in APP is taking so long?



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

Also, keep in mind that DSS internally uses way simpler algorithms than APP. APP has chosen to have quality up-front, resulting in tricky data to be processed nicely. But this does come at the cost of it taking longer. With that many frames, creating sub-integrations first is preferred.



   
ReplyQuote
(@chuck666)
Brown Dwarf
Joined: 4 years ago
Posts: 4
Topic starter  

@wouter

@vincent

Thanks for replying. I basically did the full default settings per the Charles Bracken pdf. I Changed MBB to 5 %..

Two image sets. One of group of 480 and another of 206. Same 30 ea of darks, flats and dark flats. Stages 2-5 have taken 1h 16min. Stage 6 started at 19:12 last night. As I type at 06:23; it's says 69% complete.

This is my first try to see if I like the SW. I really like the interface; but not this processing time.

"With that many frames, creating sub-integrations first is preferred." Don't know what that means??

Thank you.

Chuck



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 
Posted by: @chuck666

"With that many frames, creating sub-integrations first is preferred." Don't know what that means??

It means to split up the data set into smaller sets of, say, 100 frames per set and integrate those 100 frames of each sub-set separately. You can then load those sub-integrations again as lights (don't load any calibration files) and integrate those sub-integrations into a new integration which will be your final result.



   
ReplyQuote
(@chuck666)
Brown Dwarf
Joined: 4 years ago
Posts: 4
Topic starter  

Thank you on the sub answer. It just finished integrating the 686 images. @09:10. About 12.2 hours total. 

Is that typical?

I want to save as 16bit; not 32 bit? Is that possible in this SW? I am now going to try Post using APP. Again, using the basic defaults from the Bracken pdf.

Last question for now. Will 1.083 Beta 2 be faster?

Again, thanks for supporting me. During this quest.

Chuck



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

Not by a lot no, we constantly are improving the speed and in the future will have gpu support as well etc. Dividing the work in sub-sets makes it a lot faster as well.

Saving as 16-bit is also possible, when you have the final integration and stretch as you want, you press the save button on the top right. There you can choose some formats.



   
ReplyQuote
(@chuck666)
Brown Dwarf
Joined: 4 years ago
Posts: 4
Topic starter  

@vincent-mod

Actually, that just allows file type changes. Tiff, JPEG and FITS. You have to go into "batch modify" and you can change the bittedness. But I found it. Thanks

I have a speed issue and it's probably me. I still have all the files loaded from when I first ran the integrate sequence. I switched to the tool menu and went to rotate the image and it takes nearly 2 minutes for the update. That just doesn't make sense?? One must have to close and restart the APP app to do "TOOLS"??

Chuck

Edit. Closing and restarting APP improved the speed to and acceptable level. Also, I stand corrected, you can change bittedness of the TIFF file type.


This post was modified 4 years ago 2 times by Charles Willford

   
ReplyQuote
Share: