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.
Hi,
Tonight I processed 400 Canon 5d MKIV RAW light frames of M31 in APP with ~ 84 darks, 33 bias, and 33 flat frames. While processing I watched the "Available HDD" drop from 294GB to ~164GB.
In the APP folder there was a .dat file that was a HUGE 128GB.
Just wanted to ask if this is normal?
As soon as processing finished the file disappeared and available HDD went back up to 294GB
I have 32GB ram, 16GB allocated to APP but my RAM usage went from 27% to 87% during processing which I thought was odd.
Is there a tool or calculation I can use to make sure I have enough free HDD space for processing if using lots of frames, per the above?
Many thanks,
Stephen
Â
Â
Usually APP tells you if you have enough space left for processing, but it does use quite a bit for processing especially with higher resolutions etc. You can divide the data up in smaller chunks if you want to limit the resources more, like doing 4x100 frames at a time and combining those 4 later.
