UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Using my CMOS cameras, I often go for lots of high gain, relatively short exposures - this results in really really large image sets (my last one was 1500+ 16Mpixel exposures - see https://flic.kr/p/24WfXDM ) which take a really long time to process - I don't mind the latter so much, since we don't have all that many clear nights there's plenty of time for processing - but I do occasionally want to use the PC for other things. Right now, if I interrupt the process, I often lose hours of processing. Being able to pause processing (or dare I think it, even "save" the current state and close APP, reloading state at a later time and continuing) would allow me to interrupt APP for other stuff whenever I want, while allowing it to continue processing when I don't need the PC anymore.
Getting a faster machine isn't an option, I'm already using a Threadripper 1950x (and yes, 16-core/32 thread processing on a fast SSD is lovely) and this kind of processing can still take many hours to finish. Once my process is optimized, I fully expect to be processing many thousands of images in a "lucky imaging" type scenario, which can increase total processing time to days, making the ability to spread the task across sessions even more useful...
Hi Bart @bdeclerc,
Wow 1500+ frames, amazing, my record with APP is about 500 hundred frames I believe.
Yes, the request for project saving/loading has been mentioned and I am actually thinking about how to implement this. It's an important feature for the mentioned reasons, I agree.
Internally APP stores all data about star analysis, registration, normalization. I will need to convert that information in project files to be able to make this work properly, so I think it should be perfectly possible.
(working on a Threadrippper 1950X myself with a M2 SSD, it's pretty nice 😉 )
The RFC is on my list ToDo !
Mabula
Any update on this RFC? I lost several hourswoth of processing because APP ran out of memory when I tried to use LNC.I had to increase the memory and restarted APP to find that I had to start afresh.Â
Not yet unfortunately, I do know that 1.085 is a version which will address settings etc. So by then we should also check if this is possible.
