You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docgen timestamps writes timing.json, but VHS Sleep values stay manual unless users run an external script (see course-builder sync_vhs_sleep_from_timing.py) or issue #11 upstream command.
Proposal
When config enables it (e.g. pipeline.sync_vhs_after_timestamps: true or vhs.sync_from_timing: true):
Respect --skip-vhs / existing skip flags: either still run tape file rewrite only (no VHS render), or gate sync behind a dedicated --skip-tape-sync if you want zero file mutation without an explicit flag.
Acceptance criteria
Documented in README and docgen.yaml example
Opt-in default (do not rewrite tapes unless enabled)
Problem
docgen timestampswritestiming.json, but VHSSleepvalues stay manual unless users run an external script (see course-buildersync_vhs_sleep_from_timing.py) or issue #11 upstream command.Proposal
When config enables it (e.g.
pipeline.sync_vhs_after_timestamps: trueorvhs.sync_from_timing: true):docgen timestampsingenerate-allandrebuild-after-audio, run the same logic as proposed in Feature: sync VHS tape Sleep durations from timing.json (Whisper) #11 (syncSleepin.tapefiles fromtiming.json).--skip-vhs/ existing skip flags: either still run tape file rewrite only (no VHS render), or gate sync behind a dedicated--skip-tape-syncif you want zero file mutation without an explicit flag.Acceptance criteria
docgen.yamlexampleRelated
sync-vhs/ timing-driven Sleeprendered/*.mp4(after sync, users still runvhs→compose)