Add support for Chrome-based browsers
Open
bug
help wanted
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Chrome-based browsers don't appear to respect the presentation time of media files added to SourceBuffer, although they work fine with Firefox.
We currently pass `-ss ... -t ... -i ... -movflags frag_keyframe+delay_moov+default_base_moof` to ffmpeg.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the SourceBuffer media path and the ffmpeg invocation that uses `-ss`, `-t`, `-i`, and the listed movflags. Compare the resulting presentation-time behavior in Chrome-based browsers with Firefox, then verify that media duration and playback timing are respected in both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100