Post

How to capture device audio on the web today? 🎵🔊 getUserMedia() is not for audio only and forces users to go through a screen sharing option. Not great for audio use cases (notetaking, music, ...) We want to fix this. We have a proposal and would love your input ♥️

patrickbrosset.comPatrick - Help us shape device audio capture on the webCapturing device audio only on the web today isn't great. getDisplayMedia doesn't only share audio, and forces users to select a screen to share. We want to improve this experience, and we have a prop...

7/10/26, 4:15 pm3 reposts11 likes

Patrick Brosset

@patrickbrosset.com

Of course I meant getDisplayMedia, not getUserMedia, which is for live mic and webcam media. Sorry about the typo.

Paul Kinlan

@paul.kinlan.me

My hunch is just iterate on what exists. It seems perfectly fine for the browser to do a different picker.

Philipp Hancke

@hcornflower.bsky.social

or a different AEC? :-p

ScrollFlow

@scrollflow.bsky.social

From the extension side: chrome.tabCapture gets tab audio with no picker, but it's off-limits to regular web pages - getDisplayMedia is the only door there and its picker is built for screens, not audio. A dedicated audio surface in the existing picker feels more pragmatic than a new API.

Kaiido

@tristan-f.bsky.social

Reading through the link, you actually meant getDisplayMedia(), not getUserMedia(). And I'd say having one more API doing relatively the same thing will just add to the existing confusion...

Patrick Brosset

@patrickbrosset.com

Oh yes, of course getDisplayMedia. Sorry about that.