ggsoli.blogg.se

1. #WEBTORRENT LIVE STREAMING INSTALL#
2. #WEBTORRENT LIVE STREAMING SERIES#
3. #WEBTORRENT LIVE STREAMING TORRENT#

#WEBTORRENT LIVE STREAMING INSTALL#

Install the broadcaster and the viewer in a local http server (xampp recommended),Įnter to the broadcaster.html pres start to start streaming, every minute the app will send a transaction to metamask, this transaction will have the magnet of 1 minute segment.Įnter the viewer.html and press start. Warning don´t use main network only use test network Rinkeby, every minute it will ask for a transaction using ether, you need to have ether and active metamask in the broadcaster and viewer. Need to install Metamask and use the test network Rinkeby Webtorrent-live-stream-on-Ethereum-BlockchainĪlpha test using Blockchain Technology and Webtorrent for live streaming Nile.js is Derek Miranda, Kevin Qiu, and Justin Pierson.

Come check us out at our website, GitHub and npm. ConclusionĪs a proof of concept, we would like other developers to try our library and leave feedback on how we can improve the project or even build upon it. If anyone in the open source community is able to provide some insight, please make a pull request on our GitHub repo. If using Chrome Canary to test the library, it seems to run indefinitely. One solution that we have found, is browser specific.

We’ve checked the CPU and memory usage but have found no error messages or anomalies. ProblemsĪs we rack up the number WebTorrent seeds on the broadcaster side, there seems to be a client side memory leak which eventually causes the browser to crash. From this experience, we further acknowledge the effectiveness of combining peer-to-peer delivery with a CDN, a la Peer5, to handle the spectrum of low to high numbers of viewers. To offset this poor initial performance, we allowed the broadcaster enough time to send each peer enough data to view without missing a second. If there are only a few peers viewing the stream, initial upload speed is highly dependent on the broadcaster’s bandwidth and network speed, creating a major bottleneck. The disconnected webRTC peer will open a WebSocket connection with server, where it will be reassigned to a new WebSocket peer. Our library is designed to automatically reconnect on service disruptions. After receiving the magnet, each viewer client will begin to leech (download) and seed (upload) the stream.ĭistributed Video Streaming via WebTorrent Considerationsīecause of the linked list structure of our WebSocket to WebRTC connection, if a peer disconnects, the chain would be broken. The server emits the magnet to the initial WebSocket connections which pass the magnet along through WebRTC peers in a linked list structure. The magnet is first passed to a Node/Express server which is connected to a limited number of WebSockets.

#WEBTORRENT LIVE STREAMING SERIES#

We propagate the magnet to the viewing peers through a series of WebSocket and WebRTC connections. Once the WebTorrent client begins to seed, a magnet link (an identifier in the form of a string) is generated.

#WEBTORRENT LIVE STREAMING TORRENT#

To emulate streaming, we take the video stream and split it into clips that are distributed to viewers through their own generated torrent files. How we use WebTorrent to streamįirst, torrent files used by WebTorrent are immutable, making it less than ideal for live streaming. This also makes it a better fit than implementing typical WebRTC peer connections due to the approximately 10 to 20 connection limit per peer that WebTorrent has been able to mitigate. We chose WebTorrent as our means of broadcasting the stream because video streams can get progressively stronger as more peers join the stream. Our library uses WebTorrent, a distributed file delivery protocol inspired by BitTorrent and built with WebRTC. We built Nile.js, a peer-to-peer live video streaming library designed to handle scaling. A Peer-to-Peer Live Video Streaming Library built on WebTorrent Intro