W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2018

Raw audio access (Re: Raw data API - 4 - direct RTP access)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 31 May 2018 09:49:01 +0200
To: public-webrtc@w3.org
Message-ID: <0bcb535c-083d-7c5c-5d24-6cc4555cf863@alvestrand.no>
Den 31. mai 2018 08:47, skrev westhawk:
> I think I must have missed something - what Audio use-cases are we
> addressing - that can’t be done with
> the existing (or slightly extended) WebAudio API?

Changing subject, since this is not about the RTP API:

For raw audio, the use cases are the ones where the overhead of
converting the samples to Float32Array at 44.1k sample rate is
unreasonable, but the overhead of converting to (for example) int16
arrays at the incoming sample rate isn't.

(WebAudio's sample rate is adjustable, but it's set for a whole
AudioContext, not on each individual audio media flow).


This is a pretty small set of applications, I think, so it may mean that
raw audio API is pretty far down the list of APIs we feel like working on.

I'm trying to make sure we have all the pieces that people have been
discussing up on the dartboard. I'd guess that after the Stockholm
meeting, we'd decide that one or two of them is going to be chewed on
first, a couple of others may be shelved for good, and a few more are
going to be left in limbo (together with mediacapture-depth, for
instance) until someone picks them back up.
Received on Thursday, 31 May 2018 07:49:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:41 UTC