Very nice. Thanks for sharing!
Really great captures Mike! That is a heroic effort to process all of those frames,especially in WJ. Would love to see that animation. Great work.
Thank you all very kindly.
. Each stack was made using the number of frames Autostakkert chose for the reference frame,
Can you please elaborate on this?
I've been dropping avi files into AS!4 and doing nothing else that stacking various percentages according to what the quality graph tells me.
What are you doing that I ain't?
In Autostakkert, after you Analyze a video, in the lower left, under Reference Frame, click Manual. Autostakkert will show you the number of frames it was decided to use for the reference frame. I stacked that number of frames for each video. It's different for each video. Make sure that this setting is back on Automatic before you Analyze the next video. This would be SO much easier if Emil would make this an option, to automatically stack the number of frames chosen for the reference frame. I could have literally dragged in all 70 videos of the evening, set the APs, clicked Stack, and come back when it was done.
In any event, after stacking, sharpen your images however you prefer. You need a batch processor, like waveSharp, or BiggSky, or whatever tool you prefer, as long as it can process in batch. Because there is no effin way I am manually processing 70 stacks.
Finally, when you do your derotations in WinJUPOS, weight the individual images by the number of frames in each stack going into the derotation. For example, for the 10 derotations I made for the night (the SEB breakout image and these 9), these were the numbers of frames stacked and the corresponding weights:
Batch 1 Batch 2
14526 0.8 14621 0.7
9862 0.6 17970 0.9
9911 0.6 17842 0.9
17946 1.0 13183 0.6
11152 0.6 17824 0.9
10280 0.6 18428 0.9
15854 0.9 20597 1.0
Batch 3 Batch 4
19878 0.8 13391 0.6
23828 1.0 19419 0.9
13065 0.5 13534 0.6
19459 0.8 13693 0.7
19396 0.8 12478 0.6
17694 0.7 6954 0.3
18430 0.8 20844 1.0
Batch 5 Batch 6
13495 0.5 17656 0.7
18841 0.8 14802 0.6
18631 0.7 7291 0.3
18363 0.7 15555 0.6
14506 0.6 17456 0.7
20225 0.8 24954 1.0
24920 1.0 24654 1.0
Batch 7 Batch 8
21422 0.9 20972 0.8
17471 0.8 19575 0.8
22073 1.0 21682 0.9
23012 1.0 24953 1.0
21606 0.9 24953 1.0
21269 0.9 24601 1.0
17890 0.8 21865 0.9
Batch 9 Batch 10
16618 0.8 19075 0.8
15510 0.8 14644 0.6
17666 0.9 24193 1.0
5704 0.3 21895 0.9
9826 0.5 19845 0.8
19575 1.0 24954 1.0
20103 1.0 21226 0.9
It would be better if WinJUPOS allowed more than a single digit of precision for the weights, but alas, it doesn't. Just 1 more decimal would be much better.
In case it isn't clear, the stack with the most frames gets a weight of 1.0 in the derotation and the rest are scaled linearly by frames stacked relative to the best stack.
The point of all of this is that using the number of frames chosen for the reference frame is a crude but seemingly effective way of stacking fewer frames in poorer videos and more frames in better videos. Weighting the derotation by frames stacked ensures that all the frames that go into the derotation are treated roughly equally, rather than entire stacks. You don't want to weight a stack with 6,000 frames the same as one with 24,000 frames.
Without that one option in Autostakkert, however, this is grueling, and I doubt anyone but me it dumb enough to do it. I've requested that option, by the way, to automatically stack the number of frames chosen for the reference frame. I'm pretty sure it's a one-liner. But so far I have had no response from Emil.
