fix(export): normalize meeting transcript timestamps for markdown exports (Fixes #1472) - #1473
Conversation
…orts Meeting segments store epoch-millisecond timestamps, but transcript export formatters treated them as seconds-from-zero. Normalize to recording-relative offsets before TXT/SRT/JSON/Markdown export and parse SQLite UTC note timestamps explicitly so header times render in local time. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Merged as #1560 — your fix, unchanged, rebased onto current Why it moved branches rather than being rebased in place: my token can't push to a fork branch when the rebase brings The only conflict was in Worth recording that the blast radius was wider than the title suggests: |
|
Thanks @gabrielste1n — glad the diagnosis held. Appreciate you landing it as #1560 when the fork branch was awkward to push. |
Summary
Root cause
Diarization finalization already subtracts recording start before merge, but export-transcript read raw
ote.transcript JSON and passed epoch-ms values into ormatTimestamp(), which expects seconds from zero. That produced giant hour fields like
496069042:26:40.Verification
\
cd openwhispr-wt/1472-markdown-export-timestamps
node --test test/helpers/transcriptFormatter.test.js
13 pass (includes epoch-ms normalization + UTC created_at parsing)
\\
AI assistance
AI-assisted (Cursor). Stan Shih reviewed the diff.
Fixes #1472
Made with Cursor