Skip to content

docs: compress demo video (100MB → 6MB)#72

Open
827652549 wants to merge 10 commits into
joshuayoes:mainfrom
827652549:compress-demo-video
Open

docs: compress demo video (100MB → 6MB)#72
827652549 wants to merge 10 commits into
joshuayoes:mainfrom
827652549:compress-demo-video

Conversation

@827652549
Copy link
Copy Markdown

@827652549 827652549 commented May 19, 2026

The demo video in the README is a ~100MB uncompressed MOV file, which causes slow page loads for everyone who visits the repo.

Changes

  • Converted MOV → MP4 with -movflags faststart (moov atom at file start, enables playback before full download)
  • Stripped empty audio track (original had no audio data)
  • ~100MB → 6MB, no visible quality loss

Note on video hosting

The compressed video is referenced via a GitHub user-attachments URL — the same approach as the original. If the embedded player appears flaky on your end, I can switch to committing the file directly to the repo (demo.mp4, 6MB). Left a comment below with more detail.

827652549 added 10 commits May 20, 2026 00:23
Replace the uncompressed MOV attachment with a compressed MP4 committed
directly to the repository.

Why commit to repo instead of GitHub CDN attachment:
- GitHub user-attachments URLs (uploaded via issue/PR drag-drop) have
  known rendering issues in markdown — the video loads fine when opened
  directly but fails to embed in README or PR comments
- Uploading to a stable CDN (e.g. GitHub Releases assets) requires
  write access to the upstream repo, which external contributors don't have
- At 6MB the file is small enough to commit without meaningfully impacting
  clone size

Changes to the video:
- Convert MOV to MP4 with faststart flag (moov atom at file start,
  enables playback before full download)
- Strip empty audio track (original had no audio data)
- Result: ~100MB → 6MB with no visible quality loss
@827652549
Copy link
Copy Markdown
Author

827652549 commented May 19, 2026

Hey @joshuayoes 👋 — could you check whether the demo video in the README renders correctly on your end?

We noticed that GitHub user-attachments URLs can be flaky when embedded in markdown — the video is reachable directly but occasionally fails to show the inline player (seems related to short-lived S3 presigned URLs). It worked on some page loads but not others.

If you see the same issue, I can switch to committing demo.mp4 (6MB) directly to the repo instead — more reliable but adds a binary file to git history. Happy to go either way, just let me know your preference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant