On Tue, Jan 21, 2020 at 8:10 PM Boris Zbarsky <bzbar...@mit.edu> wrote:

> On 1/16/20 11:21 PM, Karl Tomlinson wrote:
> > Would it be appropriate to state that we don't intend to implement
> > the Audio Device Client API in Gecko because we don't see a need
> > for this additional/parallel audio API?
>
> Does anyone other than Google want the Audio Device Client API?
>

The current status is that there were people that wanted it, but recently
stated they'd rather use a regular AudioContext, because changing the
buffer size [0] and changing the audio output device [1] are now
considered, as new features of the AudioContext.


> > * Something that might arguably be harder to implement in Web
> >    Audio than to implement in a new smaller API is the configurable
> >    `callbackBufferSize`.
>
> The explainer for the new thing claims that the WG considered adding
> this and rejected it, right?  Should we push harder for them to consider
> it more seriously?
>

This is outdated it seems, I'll look into updating it. The current position
of the WG is to support changing the buffer size [0]. It's not particularly
easy, but it's necessary to have good performances for a very large portion
of users (more or less people using Windows that don't have the most recent
drivers, and all Android users, those two platforms commonly have a native
audio buffer size that is not a multiple of 128, the github issues explains
the problem).

Additionally, the reason it's not easy to implement is because the
`AudioContext` supports features that are easier to implement with
non-power-of-two buffer sizes (anything that requires computing Fast
Fourier Transforms), but those features are also very commonly used and
useful. Authors that need to use those features and use an Audio Device
Client will face the same problem implementers are going to face, so this
is not a strong argument in favor of not doing variable buffer size on the
AudioContext.

As such, neither the AudioWG nor the Audio CG has found a reason why Audio
Device Client would perform better or have more features than an
AudioContext with the two additions [0] [1] mentioned.

Paul.

[0]: https://github.com/WebAudio/web-audio-api-v2/issues/13
[1]:
https://github.com/WebAudio/web-audio-api-v2/issues/10#issuecomment-531648915


>
> -Boris
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to