Problem
Gource playback is time-based (--seconds-per-day). If several commits share the same day (or close timestamps), they appear as a cluster with no clear separation. There’s no built-in way to enforce a fixed delay between commits.
For demos/presentations, I often want “N seconds per commit”, regardless of real commit dates.
Proposal
Add an option to advance playback by a fixed interval per commit:
gource --commit-interval 4
Expected behavior:
- Commits remain ordered chronologically.
- Each commit advances animation time by exactly N seconds.
- File events within the same commit stay grouped.
- Should conflict with --seconds-per-day (error or ignore one consistently).
- --auto-skip-seconds likely irrelevant/disabled in this mode.
Use case
Demo/storytelling visualizations where clarity between commits matters more than historical time accuracy. Today this requires rewriting timestamps in a custom log.
Problem
Gource playback is time-based (--seconds-per-day). If several commits share the same day (or close timestamps), they appear as a cluster with no clear separation. There’s no built-in way to enforce a fixed delay between commits.
For demos/presentations, I often want “N seconds per commit”, regardless of real commit dates.
Proposal
Add an option to advance playback by a fixed interval per commit:
gource --commit-interval 4Expected behavior:
Use case
Demo/storytelling visualizations where clarity between commits matters more than historical time accuracy. Today this requires rewriting timestamps in a custom log.