Version of ScreenToGif
v2.43.2
Description of the Issue
When attempting long-duration screen time-lapse recordings (e.g., capturing 1 frame every 4 seconds for 8-9 hours), raw frame footage after a certain timestamp is frequently missing upon opening the editor.
Through multiple tests, I have categorized this issue into two distinct scenarios:
Scenario 1: Interruption caused by System Sleep (Reproducible)
- Behavior: When Windows automatically enters sleep mode during a recording session, frame capturing stops and fails to resume after the PC wakes up. All screen content after the computer went to sleep is lost.
- UI State: In this scenario, the recording timer/duration displayed on the software UI is noticeably shorter than the actual elapsed time (reflecting only the time before sleep).
Scenario 2: Sporadic silent failure during 8–9 hour recordings (Unexplained)
- Behavior: During long sessions (8-9 hours) without system sleep, the recorder silently stops capturing/saving frames after a certain point. When opening the editor, all frames beyond a specific timestamp are missing.
- UI State: Unlike Scenario 1, the recording timer on the UI incorrectly displays the full normal duration (e.g., 8–9 hours), giving the false impression that the entire session was recorded successfully.
Settings Used
- Capture Rate: 1 frame every 4 seconds (0.25 FPS)
- Storage Mode: Save to disk enabled
- Total Duration: ~8 to 9 hours (~8,000–10,000 frames)
Expected Behavior
- The software should gracefully handle system sleep (either pausing/resuming or preventing sleep).
- The background capture/file-writing thread should remain stable over long sessions, or alert the user if frame capturing/writing fails, rather than silently dropping frames while the timer keeps running.
Version of ScreenToGif
v2.43.2
Description of the Issue
When attempting long-duration screen time-lapse recordings (e.g., capturing 1 frame every 4 seconds for 8-9 hours), raw frame footage after a certain timestamp is frequently missing upon opening the editor.
Through multiple tests, I have categorized this issue into two distinct scenarios:
Scenario 1: Interruption caused by System Sleep (Reproducible)
Scenario 2: Sporadic silent failure during 8–9 hour recordings (Unexplained)
Settings Used
Expected Behavior