chadwallacehart

The #MoQ vs. #WebRTC debate has been missing use case details. See our new post for an analysis of:
1:1 calls
#VoiceAI
Meetings
Streaming
Live streaming
Webinars / Townhalls

https://webrtchacks.com/webrtc-vs-moq-by-use-case/

New post: WebRTC Plumbing with GStreamer by @ystreet00@floss.social - @gstreamer@floss.social 's long relationship with #WebRTC, recent developments, and a review of the many WebRTC-related integrations
https://webrtchacks.com/webrtc-plumbing-with-gstreamer/

New webrtcHacks post on video_replay - a powerful libWebRTC tool for replaying audio and video to help with #WebRTC debugging.
Philipp Hancke gives a nice step-by-step walkthrough of using this with some explanation on all the flag options.
https://webrtchacks.com/capture-and-replay-streams-with-video-replay/

New webrtcHacks post: Is everyone switching to #MoQ? Fippo responds to some FUD about #WebRTC in a recent MoQ launch post with some historical perspective & Chrome Status data
https://webrtchacks.com/is-everyone-switching-to-moq/

New webrtcHacks post on how to measure #OpenAI response latency - Fippo shares a guide on how to use chrome://webrtc-internals and WireShark to precisely measure and analyze OpenAI's response timing with their #WebRTC Realtime API

https://webrtchacks.com/measuring-the-response-latency-of-openais-webrtc-based-real-time-api/

New webrtcHacks: Meta’s Fengdeng Lyu takes us inside NetEQ, libWebRTC’s audio jitter buffer. Learn how #WebRTC ensures smooth audio playback even under network stress. Fengdeng starts with some concepts and then walks through the code’s many algorithms
https://webrtchacks.com/how-webrtcs-neteq-jitter-buffer-provides-smooth-audio

new webrtcHacks post: WebRTC cracks the WHIP on OBS - a review of the official addition of #WebRTC to OBS Studio, the long history behind this, how it compares to #RTMP, and what's next.
https://webrtchacks.com/webrtc-cracks-the-whip-on-obs/

I interviewed Sean DuBois last week about OpenAI’s #WebRTC.

My learnings:
- The Realtime API with WebRTC implementation is more about speed and pragmatism vs. some grand architectural vision
- TURN isn't critical anymore - use ICE TLS
- Many of WebRTC’s audio enhancements are not a priority
- Media over QUIC is not on the horizon there
- WebRTC is about more than LLM↔voice interaction

📺 Watch the lightly edited video and explore the annotated transcript here: https://webrtchacks.com/openai-webrtc-qa-with-sean-dubois/

Interesting to see how Google Meet is experimenting with #AV1 during its pre-call test in this new webrtcHacks post by
@hcornflower@bird.makeup: https://webrtchacks.com/the-hidden-av1-gift-in-google-meet/

I repurposed an old Google #AIY Voice Kit to use @openai@twtr.plus Realtime API with #WebRTC. Vibecoding failed, so I did some old school research+trial&error.

My main learnings:
· Pass all the same WSS messages via Data Channel
· Ephemeral tokens not always needed
· API is a lot like WHIP (no SDK needed)
· Best practices for managing gUM and RTCPeerConnection still apply (not in docs)
· Use speech events for voice functions

Full code walkthrough on webrtcHacks here: https://webrtchacks.com/the-unofficial-guide-to-openai-realtime-webrtc-api

Over the years I have built a methodology on #webrtcHacks for analyzing #WebRTC related repos on GitHub and reviewing other open source resources for trends. I will be presenting my latest analysis live on Tuesday, December 10!
Tsahi Levent-Levi will moderate with his own questions and commentary.

Join us! You can sign-up here: https://events.ringcentral.com/events/webrtchacks-2024-oss-webrtc-stats-review

New webrtcHacks post: Power-up getStats for Client Monitoring
by Balázs Kreith. Useful insights with code for using WebRTC's getStats data for common issues – network congestion, CPU overuse, stuck tracks, and frozen video
https://webrtchacks.com/power-up-getstats-for-client-monitoring/

Bandwidth Estimation is an important but undercovered topic in #WebRTC. It was exciting to have Kaustav Ghosh contribute a post on Bandwidth Probing for #webrtchacks

You will see it is one of the more complex mechanisms in Google Congestion Control (GCC). Other than an explanation and review of the implementation, he also highlights some helpful debug tools.

Read here: https://webrtchacks.com/probing-webrtc-bandwidth-probing-why-and-how-in-gcc/

ok, I signed up for Mastodon. Does this mean I can stop using twitter?

New webrtcHacks post by Philipp Hancke - an update on end-to-end encryption in #WebRTC

I have never seen e2ee get much use and that seems true for everyone according to his usage analysis. Fippo also uncovered what looks to be a Google Meet experiment in this area

https://webrtchacks.com/end-to-end-encryption-in-webrtc-4-years-later/

I found lots of quirks while converting an MP4 to a MediaStream for #WebRTC use. I looked at:
* CDN vs. media server vs. client slide
* #WebCodecs
* captureStream
* Lots of fun getDisplayMedia options

Read about all of this with demos on webrtcHacks: https://webrtchacks.com/all-the-ways-to-send-a-video-file-over-webrtc/

New webrtcHacks post: how OpenAI does #WebRTC in the new gpt-realtime. A look at the new calls endpoint, ICE negotiation improvements, and sending 🎥video to the LLM with a easy to follow single html file demo

The post with demo and links to the repo: https://webrtchacks.com/how-openai-does-webrtc-in-the-new-gpt-realtime/

I am excited to host a livestream on OpenAI’s #WebRTC implementation with lead dev Sean DuBois on Thurs, April 10 -11:00 AM EDT / 17:00 CEST

I’ll ask him about:
- @_pion@beta.birdsite.live there
- their different WebRTC deployments
- architectural decisions
- what's next there

AND we’ll have some audience Q&A

Register here: https://events.ringcentral.com/events/openai-realtime-webrtc-q-a-with-sean-dubois

I posted an edited and annotated transcript to the 2024 WebRTC in Open Source Review: A Quantitative Analysis Livestream I did last month to webrtcHacks: https://webrtchacks.com/2024-webrtc-in-open-source-review-a-quantitative-analysis/

If you watched then this is a refresher with some clarifications. If you missed that, then you can read and follow along, or just read minus the banter 😀