Hi folks,
another update this week - version 4.1.13041 has just been uploaded. A couple of significant new features - 'Time Travel Auto Capture' and 'Freeze/Resume'...
Time Travel Auto Capture
This feature is intended to help combine traditional 'Capture an SER and process later' planetary imaging with SharpCap live planetary stacking. When enabled, SharpCap will do two things...
- Continually monitor the stack quality, looking for peaks in quality that indicate that the frames leading up to that point have been particularly high quality
and
- Use memory to store the most recent hundreds or thousands of frames that have contributed to the current state of the stack
That means that when the stack quality *does* peak, SharpCap can make the decision to save those stored frames to SER, knowing that they are of better than average quality. It's like being able to press the 'Start Capture' button *after* a period of good seeing rather than before - that's why the 'Time Travel' name. Once a peak has occurred and a batch of frames saved to SER, SharpCap just goes back to watching the quality and storing frames, waiting for a new, even higher, peak in quality...
To get started with auto capture, get the stack going as normal and then go to the 'Auto Capture' tab in the Planetary Stacking area - once the stack has reached target length, a graph will start to appear showing how the stack quality is changing over time. This is the quality before sharpening/adjustments, so those settings will not affect the graph.

- Screenshot 2025-01-20 154257.jpg (74.39 KiB) Viewed 5137 times
Higher values in the graph indicate a higher quality (more contrasty) stacked image, which in turn means that the frames that have recently been stacked are higher quality (better seeing or focus typically). A peak in the graph occurs after a period of good quality frames that have come to an end, a trough after a period of poor quality frames that have now improved.
Activating Auto Capture and Memory Requirements
You will see the 'Activate' button to turn on auto capture - if this is not available then it almost certainly means that there is not enough memory allocated to 'High Speed Frame Cache' in the memory settings. The number of frames that need to be stored in memory to activate this feature is calculated as:
Code: Select all
Frames contributing to current stack : Target Stack Length * 2 * "Filter Factor"
plus
Decision Buffer : 10 * current camera FPS
The 'Filter Factor' is a factor that corrects for the 'Frame Filtering' option being active - if it is inactive, the filter factor is 1. If it is active and you are selecting the best 50% of frames, the filter factor is 2; for the best 33% it would be 3 and for the best 25% it would be 4.
The decision buffer allows SharpCap 10 seconds extra time to decide if a high quality score is a peak (time to capture) or is just part of a gradual and continuing rise in quality (don't capture just yet - quality is still improving).
If you cannot activate this feature and cannot further increase the memory allocation, then consider turning down the target stack length or disabling frame filtering to reduce the amount of memory required.
How Auto Captures Happen
Once activated, you will first see the stored frame count begin to increase up to the calculated number of frames - the frame gauge will be orange while filling (insufficient frames to capture) and change to green when there are sufficient stored frames.

- Screenshot 2025-01-20 155456.jpg (40.26 KiB) Viewed 5137 times
Once there are enough frames and the gauge turns green, SharpCap will also draw two lines onto the quality graph:
- A horizontal green dashed line - this indicates the quality threshold for capturing - a capture will happen when the stack quality peaks above this level (note - it must be a peak, not just rising above the level)
- A vertical green dashed line leading to a recent measurement - this is the decision point indicator - the measurement that SharpCap is looking at to consider whether to capture. A capture will start when the decision point quality matches the threshold line *and* all the more recent quality measurements than the decision point are lower values than the decision point value

- Screenshot 2025-01-20 155526.jpg (73.09 KiB) Viewed 5137 times
When a capture happens, it will usually happen *very* quickly, since the frames needed are already in memory, and SharpCap just has to save them to file. The frame gauge level will drop when a capture happens and the gauge will also turn pink during capture, but this might be hard to spot if the capture finished rapidly. To make it easy to tell that a capture has happened, SharpCap shades the area of the quality graph red to show the time period of the capture that has been saved.

- Screenshot 2025-01-20 155602.jpg (25.87 KiB) Viewed 5137 times
Over time, more captures will automatically happen each time the stack quality peaks to a new higher level.

- Screenshot 2025-01-20 160601.jpg (38.31 KiB) Viewed 5137 times
Note the adjustment to change how much of the history SharpCap includes in its calculation of the quality threshold level - in the screenshots it is set to 15 minutes, which means that high quality peaks in the stack are ignored after they are more than 15 minutes old. This helps ensure that a high quality peak early in a session does not prevent any more captures at all for the rest of the session.
It's also worth noting that immediately after a capture, the number of stored frames will be depleted, and SharpCap cannot capture again until the store has refilled - that means that a peak followed by a short dip, followed by a higher peak may mean that the second, higher, peak is not captured due to occurring in this 'refill' period.
Please remember that this is the first version of this functionality, so there are probably still some gremlins to be found and resolved - feedback welcome!
Freeze and Resume
This is much simpler... Currently Planetary Live Stacking resets if you close and then reopen it. In most cases that's fine, but if you want to do something else and then come back to the same stack, there was no way to do it. Now the Freeze and Resume feature gives you that ability.
Freezing a Stack
To freeze a stack, just press the 'Freeze and Close' button - this will keep the current state of the stack active (including any timelapse that is running), but close the live planetary stacking tool so that you can use other tools (focus tools to refocus for instance, or other tools to perform a meridian flip).

- Screenshot 2025-01-20 161312.jpg (37.05 KiB) Viewed 5137 times
Resuming after Freezing
When you want to return to planetary stacking, just re-select it, then press the 'Unfreeze and Resume' button to continue stacking (the button has an attention-grabbing yellow/red flashing background and is the only thing you can press at this point apart from 'Reset Stack').

- Screenshot 2025-01-20 161515.jpg (36.81 KiB) Viewed 5137 times
Note that you should make sure that you have returned to the same image size (width/height) of capture area and the same camera mode before resuming, otherwise the stack may immediately reset due to the mismatch. I will look into warning about that situation in a future update.
If you perform a meridian flip, SharpCap will detect that the flip has occurred since the start of the stack (providing your ASCOM mount reports the side of pier to SharpCap) and will automatically rotate all frames captured after the flip by 180 degrees before adding them to the stack, to align with the existing image. I must admit though that I haven't had the clear sky to test this feature yet!
cheers,
Robin