Problem Statement
While recording a timelapse, the interface currently shows only the elapsed time (how long the capture process has been running). However, users have no direct feedback on how long their final timelapse video will be once frames are compiled.
This makes it difficult to estimate the resulting video duration during long recording sessions, especially when experimenting with different capture intervals and FPS settings. Having a “Recorded Time” indicator would give a clearer sense of progress and help users plan recordings more efficiently.
Proposed Solution
Add a new “Recorded Time” indicator to the live progress output that estimates the final timelapse duration based on the elapsed recording time, capture interval, and output FPS.
Use Cases
-
Long-duration timelapses (e.g., sunrise to sunset)
A user recording for 8–10 hours with a 10-second interval wants to know how long the final timelapse will last without manually calculating it.
Displaying the “Recorded Time” in real-time helps them gauge progress and storage expectations.
-
Testing different interval/FPS configurations
When experimenting with different intervals or playback speeds, users can instantly see the impact on the final video duration — useful for calibrating artistic or experimental shots.
-
Resource planning for limited storage systems
Users running on laptops or low-storage devices can estimate how many frames (and total output length) will be generated, helping them manage space before and during recording.
-
Live monitoring via TUI dashboards
For users running Chronapse in full-screen terminal sessions or automating it on remote systems (e.g., Raspberry Pi, Linux servers), the “Recorded Time” display provides immediate, intuitive feedback without external calculation.
Alternatives Considered
No response
Feature Type
UI/UX Enhancement
Priority
Medium - Nice to have
Implementation Ideas
No response
Mockups or Examples
No response
Additional Context
No response
Contribution
Pre-submission Checklist
Problem Statement
While recording a timelapse, the interface currently shows only the elapsed time (how long the capture process has been running). However, users have no direct feedback on how long their final timelapse video will be once frames are compiled.
This makes it difficult to estimate the resulting video duration during long recording sessions, especially when experimenting with different capture intervals and FPS settings. Having a “Recorded Time” indicator would give a clearer sense of progress and help users plan recordings more efficiently.
Proposed Solution
Add a new “Recorded Time” indicator to the live progress output that estimates the final timelapse duration based on the elapsed recording time, capture interval, and output FPS.
Use Cases
Long-duration timelapses (e.g., sunrise to sunset)
A user recording for 8–10 hours with a 10-second interval wants to know how long the final timelapse will last without manually calculating it.
Displaying the “Recorded Time” in real-time helps them gauge progress and storage expectations.
Testing different interval/FPS configurations
When experimenting with different intervals or playback speeds, users can instantly see the impact on the final video duration — useful for calibrating artistic or experimental shots.
Resource planning for limited storage systems
Users running on laptops or low-storage devices can estimate how many frames (and total output length) will be generated, helping them manage space before and during recording.
Live monitoring via TUI dashboards
For users running Chronapse in full-screen terminal sessions or automating it on remote systems (e.g., Raspberry Pi, Linux servers), the “Recorded Time” display provides immediate, intuitive feedback without external calculation.
Alternatives Considered
No response
Feature Type
UI/UX Enhancement
Priority
Medium - Nice to have
Implementation Ideas
No response
Mockups or Examples
No response
Additional Context
No response
Contribution
Pre-submission Checklist