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.
I have lots and lots of subs as my setup is limited to 20s subs (defaulting to 10s). In order to reduce the overall integration time when I have hundreds (even close to 2000) of files, I do what was recommended here and process them in batches of roughly 200.
So now I have a small number of integration files. Easy enough to load them again as lights. My question is are there any parameters I should be setting apart from the defaults to maximize the results given I’m starting from files that have already been integrated (with defaults)?
For example, should I use average rather than median when integrating? Should I be removing light pollution, calibrating, etc the individual super subs (the integrated ~200 files) before loading them as lights for the final integration?
Thanks!
I would not ! post-process the 200subs stacks before integrating them into the superStack of all data.
I would make the individual 200sub stacks with automatic integration so average is used with optimal outlier rejection filters. I would enable Multi-Band-Blending on 10% to reduce stacking artefacts.
Then the superStack: also use automatic integration (depending on the amount of frames APP will use median or average automatically), advanced normalization in 5) and enable MBB again 😉
Mabula
Sounds like I'm on the right track then. Is there any benefit to changing the dynamic correction from same camera to distorted then on the super stack? Since these would be on multiple days as well as multiple sets on the same day. All are taken with the same setup, though.
Hi, I have successfully intergated stacks of 400 to 600 lights on my late2015 i7-6700 imac if you don't mind overnight processing this works fine. You can save time by skipping Local Normalization Correction and try adjusting parameters. Also it helps to do steps 0-4 (up to registration) first, then deselect worst subs and resume with Normalization & Integration. Overall the biggest bang for the buck would be a decent mount so your 20s limitation would be gone and you'd reach reasonable integration times. Second best would be to crank up amplification/ISO a step or two - with 400 subs you should be able to reduce noise by two steps: I used to work with a Sony A7II and ISO 3200 and 20 to 30 s subs.
cheers,
jochen
I've done overnight processing before as well. In my case I'm not able to change out the mount but I appreciate your suggestion 🙂 I usually blink my subs to remove the worst before I go into APP. The quality measurement tends to be very similar across all the files.
