mediacapture-record
awesome-pion
Our great sponsors
| mediacapture-record | awesome-pion | |
|---|---|---|
| 3 | 4 | |
| 101 | 680 | |
| - | 2.6% | |
| 2.6 | 1.0 | |
| 12 months ago | 12 days ago | |
| Bikeshed | Shell | |
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mediacapture-record
-
How do I Effectively Capture Video playing in Canvas?
Courtesy of this GitHub thread, my currently working, but very inconvenient strategy to capture the video is to use mediaCapture(0) on the canvas element with MediaStreamTrackProcessor to pipe frames into WebM muxer from a package called webm-muxer.
-
How to create a seamless loop for a looping video?
WebRTC's RTCRtpSender.replaceTrack() method achieves "seamless" replacement of a MediaStreamTrack. I proposed the same be added to MediaRecorder, see Add replaceTrack method to MediaRecorder., Add replaceStream to MediaRecorder.
-
FFmpeg for browser and node, powered by WebAssembly
I guess this could be used to remux the broken files that are spitted by the MediaRecorder API, which have missing metadata that prevents from seeking and thus far has been ignored / sweeped away in Chrome [1], Firefox [2], and even the standard itself [3], which ignored in its design the basic fact that encoding any file should include a "closing" stage (where metadata is written) before yielding it as a finished file.
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=642012
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1283464
[3]: https://github.com/w3c/mediacapture-record/issues/119
awesome-pion
-
Chromium based browsers leak users' local IP via WebRTC's foundation attribute
I see a lot of WebRTC usage just in the LAN. WebRTC sees a lot of usage outside of conferencing!
* Controlling Robots (formant.io)
* Security Cameras
* File Sharing
* Game Streaming/VNC
I keep a list of interesting open source WebRTC projects at https://github.com/pion/awesome-pion
-
Ask HN: Why is there no enterprise grade open-source zoom alternative?
For more interesting related projects, you may also want to checkout https://github.com/pion/awesome-pion
I'm fiddling now and then on an alternative conferencing frontend(Pyrite - https://github.com/garage44/pyrite) for Galene(https://galene.org), which is a SFU that uses Pion.
-
Show HN: AV1 and WebRTC
AV1 support is already available in libwebrtc!
So when I started building Pion the target use case was to make it easier to build scalable servers. Instead of interacting with a WebRTC servers REST API to query information/load balance I wanted to have it all in one code base. It also is really useful to have Media+Transport decoupled. Lots of use cases I didn't realize grew out of that.
* Teleoperation/robotics (https://github.com/Ragnar-H/TelloGo)
* Control remote software (https://github.com/m1k1o/neko)
* Cross platform file sharing (https://github.com/saljam/webwormhole)
* Sending pre-recorded media (RTMP/HLS/RTSP -> WebRTC)
* Custom DataChannel servers/bridges (https://snowflake.torproject.org/)
Lots of other cool ones in https://github.com/pion/awesome-pion I need to update it. It has been a bit since I have looked through https://pkg.go.dev/github.com/pion/webrtc/v3?tab=importedby
-
Pion WebRTC v3.0.0 Released
Pion WebRTC is a Go implementation of WebRTC. If you haven't used it before check out awesome-pion or example-webrtc-applications for what people are doing. We maintain a feature list and other helpful resources in our README.md