mirotalkbro VS shaka-player

MiroTalk WebRTC Live broadcasting involves the real-time transmission of audio, video, and data streams from a broadcaster to multiple viewers. Instead of relying on a centralized server to distribute the stream to viewers, WebRTC enables a direct connection between the broadcaster and each viewer. This approach offers several advantages, such as lower latency, scalability, and reduced infrastructure costs.

Live demo: https://bro.mirotalk.com

GitHub: https://github.com/miroslavpejic85/mirotalkbro

Self-Hosting: https://github.com/miroslavpejic85/mirotalkbro/blob/main/doc...

Note: Unlimited time, unlimited rooms each having a broadcast and many viewers.

# MiroTalk WebRTC P2P

MiroTalk P2P offers a compelling solution for businesses, remote teams, educational institutions, and anyone seeking a reliable and secure video conferencing experience. Its P2P architecture, coupled with WebRTC technology, ensures efficient and high-quality communication while prioritizing user privacy and data security.

Live demo: https://p2p.mirotalk.com

GitHub: https://github.com/miroslavpejic85/mirotalk

Self-Hosting: https://github.com/miroslavpejic85/mirotalk/blob/master/docs...

Note: Unlimited time, unlimited rooms each having around 5-8 participants.

# MiroTalk WebRTC SFU

MiroTalk SFU is an advanced video conferencing solution that combines the benefits of WebRTC technology with the scalability and flexibility of the SFU architecture. It provides high-quality video and audio, supports large conferences, and offers additional features like multi-stream management, intelligent bandwidth management, and recording capabilities. Whether it's for business meetings, virtual events, or educational purposes, MiroTalk SFU offers a powerful and reliable solution for real-time video communication.

Live demo: https://sfu.mirotalk.com

GitHub: https://github.com/miroslavpejic85/mirotalksfu

Self-Hosting: https://github.com/miroslavpejic85/mirotalksfu/blob/main/doc...

Note: Unlimited time, unlimited rooms each having 8+ participants.

# MiroTalk WebRTC C2C

MiroTalk C2C is a cutting-edge web application that revolutionizes real-time cam-to-cam video conferences using WebRTC technology. This powerful solution empowers users to engage in seamless, secure, and immersive one-on-one video conversations with crystal-clear video and audio quality.

Live demo: https://c2c.mirotalk.com

GitHub: https://github.com/miroslavpejic85/mirotalkc2c

Self-Hosting: https://github.com/miroslavpejic85/mirotalkc2c/blob/main/doc...

Note: Unlimited time, unlimited rooms each having 2 participants.

# MiroTalk WebRTC Rooms scheduler

MiroTalk Rooms Scheduler allow users to schedule and manage real-time video conferencing meetings through the web browsers. They are designed to facilitate the process of setting up and joining video conference calls for multiple participants, without the need for external applications or plugins.

Live demo: https://webrtc.mirotalk.com

GitHub: https://github.com/miroslavpejic85/mirotalkwebrtc

Self-Hosting: https://github.com/miroslavpejic85/mirotalkwebrtc/blob/maste...

# Author

GitHub: https://github.com/miroslavpejic85

Linkedin: https://www.linkedin.com/in/miroslav-pejic-976a07101/

Email: [email protected]

Support: https://github.com/sponsors/miroslavpejic85

# Thank you!

What kind of tutorial do you need? Live demo: https://bro.mirotalk.com Github: https://github.com/miroslavpejic85/mirotalkbro Self Hosting: https://github.com/miroslavpejic85/mirotalkbro/blob/main/docs/self-hosting.md The MiroTalk live broadcasting process typically involves the following steps: 1. Broadcasting Setup: The broadcaster initiates a WebRTC connection by capturing audio and video from their device, encoding the media into a suitable format, and creating a WebRTC stream. This stream is then distributed to the viewers. 2. Viewer Connection: Viewers who want to watch the live broadcast establish a direct connection with the broadcaster using WebRTC. They access the broadcast URL or join a signaling channel that facilitates the exchange of connection details. 3. Peer-to-Peer Connection: Each viewer connects directly to the broadcaster's stream and establishes a P2P connection. This connection allows the viewer to receive the audio and video streams in real-time. 4. Media Streaming: The broadcaster continuously sends the audio and video data to each viewer using the established P2P connections. This data is typically transmitted using the Real-Time Protocol (RTP) over User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). 5. Decoding and Playback: Each viewer's browser receives the audio and video data and decodes it for playback. The decoded media is then rendered on the viewer's device, allowing them to watch the live broadcast. 6. Data Channels: WebRTC also supports data channels, which enable the exchange of additional information between the broadcaster and viewers. This feature can be used for chat functionality, synchronized interactions, or any other application-specific data exchange.

A quick search of 1003 in Shaka issues hints at that being related to a network timeout, and that's consistent with the player requesting a lower quality (it thinks the network can't keep up with the higher bitrate) until it eventually gives up. That could explain why there are so many VAAPI errors, as it's constantly testing new bitrates until it gives up. Super weird.

It uses a video player that was made by Google. It's shaka player: https://github.com/google/shaka-player. You can see a proof of Piped using this video player here: https://github.com/TeamPiped/Piped/blob/master/package.json#L21

https://github.com/google/shaka-player Will this work on react native?

I expect the Shaka player issue for Providers programming has been there forever due to DRM issues. It has always been there since I started using Stremium months ago anyway. I have Sling and Locast. It looks like your adblocker may be interfering with playback. I have disabled the three ad blockers I am using for the Stremium domain. I use a Chromebook to watch news during the day and today I can still watch any channel, including those that use the Shaka Player by moving the progress bar. My CB is touchscreen, but the PC works the same. Like everyone else I believe the video playback needs serious work. The RW/FF is busted too. Reddit is not the place to get support though. You need to contact them directly. They will usually get back to you, at least in my experience. I'm also looking the the Shaka Player github to see what issues they are working on because it is more likely that improvements will come from there, not Stremium. https://github.com/google/shaka-player

I believe that's mistaken. From the article:

> As far as I’m aware, Widevine is the only available DRM for a Chromium-based browser, especially so for Electron.

But according to this [0] the Chromium-based Edge browser supports both Google's WideVine CDM and Microsoft's PlayReady CDM. Not sure if that's really any help, but that's a different question.

[0] https://github.com/google/shaka-player/issues/2492#issuecomm...