Echo: Day 3
Today, I watched a few videos to explore how video streaming can be implemented. One option I found is WebRTC, which is the protocol used by Google Meet and many other video conferencing tools. WebRTC enables peer-to-peer live video and audio streaming. However, for Echo’s use case, I only need to stream video from the producer’s device to the backend, where the video can be saved or cached. Multiple consumers can then playback the stream live. For this purpose, using direct WebRTC might not be the best option.
Yesterday, I implemented basic streaming from the frontend to the backend using WebSockets. Another option could be to use WebRTC for transferring the feed from the producer client to the backend. I haven’t tried the WebRTC method yet, but I plan to do so in the coming days.
Get Alwin Sunil’s stories in your inbox
Join Medium for free to get updates from this writer.
Additionally, I need to update the sample app I created yesterday to properly handle both screen and camera feeds. Currently, if both streams are being transmitted, the binary data received by the server is saved into one WebM stream. This causes corrupted video output since the binary data of the two different streams is combined in the order in which it arrives.
Videos referenced:
- WebRTC Tutorial — How does WebRTC work?
- WebRTC in 100 Seconds // Build a Video Chat app from Scratch
- WebSockets in 100 Seconds & Beyond with Socket.io
That’s all for today, thank you for reading.
