mafintosh / mafintosh/transcode-stream
Browserify support...
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
...by depending on ffmpeg.js, then projects such as webtorrent will have a huge benefit.
Not sure whether the performance of an Emscriptified version of ffmpeg will make that a realistic approach for the browser, but as concept it would be awesome if reliably possible overall. However, to be able to play e.g. mkv in the browser for supported codecs we only need to change the container to mp4 leaving the audio/video streams as-is, so at least for this it might be worthy.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes Browserify support through ffmpeg.js, with webtorrent as an example consumer. Start by reviewing the project’s current stream-transcoding interface and the linked ffmpeg.js approach. Done would mean a reliable browser-compatible path for the described container conversion and supported codecs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100