irudisca 52f880f0f2 fix(telegram): use seekable file path for thumbnail & metadata extraction (#225) ...

extractFrameAt() and getVideoMetadata() piped the media into ffmpeg/ffprobe
via pipe:0. A pipe is not seekable, so ffmpeg cannot decode non-faststart MP4s
whose moov atom sits at the END of the file (very common for yt-dlp / HLS-merged
downloads): the frame grab and probe silently fail, and the video is uploaded
with no thumbnail (and, for non-mp4 containers, no dimensions).

Hand ffmpeg/ffprobe a seekable file path instead. When the reader already is an
*os.File we use it directly; otherwise we spool to a temp file and clean it up.

Verified with an A/B upload of a 56 MB non-faststart clip: stock build produced
no thumbnail, patched build produced a correct thumbnail.

Co-authored-by: pennyucloud <valentino@pennyu.co.id>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-23 18:28:03 +08:00

..

.gitignore

feat: auto generate thumbnail for video uploaded to telegram storage

2025-11-28 10:24:15 +08:00

split_test.go

feat: add support for splitting large files into parts for Telegram storage, #156

2025-12-15 10:25:50 +08:00

split.go

feat: support import files from storages to telegram (#183)

2026-01-19 17:39:47 +08:00

telegram.go

refactor: simplify storage path handling across various tasks and storage implementations

2026-01-19 21:27:53 +08:00

util_test.go

feat: auto generate thumbnail for video uploaded to telegram storage

2025-11-28 10:24:15 +08:00

util.go

fix(telegram): use seekable file path for thumbnail & metadata extraction (#225)

2026-07-23 18:28:03 +08:00