webrtcHacks

@webrtcHacks

WebRTC information & experiments for developers

webrtcHacks
@webrtcHacks
Oct 8
webrtcHacks email subscribers: we’ve switched providers. You may notice a new layout or inbox placement. Look for [email protected], and check Spam or Promotions if an update is missing. Get new posts by email:
webrtchacks.com
Subscribe - webrtcHacks
Email notification on new posts Open the signup form in a new tab View previous campaigns. RSS feed
webrtcHacks
@webrtcHacks
Oct 8
New post: Voice agents get confused by echo too. @HCornflower traces phantom turns to browser echo: 21% of Edge sessions vs. 4% in Chrome in his setup. AEC belongs in your voice-agent testing. webrtchacks.com/voice-agents-g…
1
webrtcHacks
@webrtcHacks
Oct 6
New post: Google Chrome downloads a new neural AEC while you are not looking @HCornflower reverse engineers the model, tests it against AEC3, and asks why other browsers don't get the weights. webrtchacks.com/chrome-neural-…
webrtcHacks
@webrtcHacks
Jul 2
New post: Vector Vibing to speed up Opus encode by 20% - @HCornflower describes how he wired up the AVX2 Opus implementation for speed gains webrtchacks.com/vector-vibing-…
Made with AI
webrtcHacks
@webrtcHacks
Jun 2
New post: Vibe-coding #WebRTC by @HCornflower - using AI to tackle long-standing WebRTC issues and ship fixes across libWebRTC, @ChromiumDev , @_pion , and @firefox without handing taste over to the minions
Vibe-coding WebRTC - webrtcHacks
From webrtchacks.com