15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
Running 1.077 on Windows 10 and noticing the Construct Frame Details step is very slow (several minutes) when I have a lot of light frames and cancel a process (or have an error). Also have the same delay when I remove items from the list to correct the problem (not enough stars etc). I have about 1200 light frames across LRGBHa but this will be pretty common for me on broadband targets in a light polluted area. Any recommendations on how to avoid this delay? Put some of the logs below if helpful...
Thanks, Mathew
11:18:32 - FRAME DETAILS UPDATER: updated succesfully
11:18:32 - CONSTRUCT FRAME DETAILS LIST: starting...
11:18:32 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
11:18:32 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
11:18:32 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
11:18:32 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
11:19:41 - CONSTRUCT FRAME DETAILS LIST: finished
11:19:42 - 5) NORMALIZE:: REGISTER was stopped, cancelling normalization task as well
11:19:42 - 5) NORMALIZE: was cancelled...
11:19:42 - FRAME DETAILS UPDATER: starting...
11:19:42 - FRAME DETAILS UPDATER: no new frames to add
11:19:42 - FRAME DETAILS UPDATER: rebuilding all frame details...
11:19:42 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
11:19:42 - FRAME DETAILS UPDATER: updated succesfully
11:19:42 - CONSTRUCT FRAME DETAILS LIST: starting...
11:19:42 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
11:19:42 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
11:19:42 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
11:19:43 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
11:20:51 - CONSTRUCT FRAME DETAILS LIST: finished
11:20:52 - 6) INTEGRATE: normalization was broken down, so cancelling integration as well.
11:20:52 - FRAME DETAILS UPDATER: starting...
11:20:52 - FRAME DETAILS UPDATER: no new frames to add
11:20:52 - FRAME DETAILS UPDATER: rebuilding all frame details...
11:20:52 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
11:20:52 - FRAME DETAILS UPDATER: updated succesfully
11:20:52 - CONSTRUCT FRAME DETAILS LIST: starting...
11:20:52 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
11:20:52 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
11:20:52 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
11:20:53 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
11:22:01 - CONSTRUCT FRAME DETAILS LIST: finished
Mmm, well 1200 frames at the same time is a lot I have to say. Can't you split those up into, say, 400 at a time?
I could probably do each channel independently, but I still have over 600 frames of luminance. Not sure how easy it would be to break the same channel into two integrations and effectively recombine it later and still retain the same quality. I am going to try the latest version and see if that helps at all - never noticed these delays until the last update to v1.077 though.
If you have enough memory, 600 should work as well. It depends a little on the size per frame and such. But I would try to chop it up a little at least. Let me know how it goes and good luck!
