#895: Web Audio API: User-Selectable Render Quantum Size

Visit on Github.

Opened Sep 11, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of User-Selectable Render Quantum Size.

Historically, WebAudio has always rendered the graph in chunks of 128 frames, called a render quantum in the specification. This was a trade-off between function-call overhead and latency. A smaller number would reduce latency, but the function call overhead would increase. With a larger value, the overhead is reduced, but the latency increases because any change takes more audio frames to reach the output.

  • Explainer¹ (minimally containing user needs and example code): User-Selectable Render Quantum
  • User research: N/A
  • Security and Privacy self-review²: See the Security/Privacy section in the explainer.
  • GitHub repo (if you prefer feedback filed there): https://github.com/WebAudio/web-audio-api
  • Primary contacts (and their relationship to the specification):
    • Hongchan Choi ([hoch]), W3C Audio Working Group Co-chair
    • Paul Adenot ([@padenot]), Web Audio API specification editor
  • Organization(s)/project(s) driving the specification: W3C Audio Working Group
  • External status/issue trackers for this feature: N/A

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • The group where the incubation/design work on this is being done (or is intended to be done in the future): N/A
  • The group where standardization of this work is intended to be done ("unknown" if not known): W3 Audio WG
  • Existing major pieces of multi-stakeholder review or discussion of this design: N/A
  • Major unresolved issues with or opposition to this design: N/A
  • This work is being funded by: N/A

We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a comment in this issue and @hoch @padenot

Discussions

2023-10-16

Minutes

bumped

2023-10-23

Minutes

Max: not sure whether this api.. it's used by one particular web application, to set the rendering frequency of the device. Wondering whether this will apply to other applications. Is it per application? Should not have any influence to other applications running on the devices, one particular application wants to use it. [will leave comment]

2024-01-london

Minutes

Yves: it looks like it makes sense... I looked at it before and felt it looked OK.

Sangwhan: there is a user need. This is well thought-through.

Yves: It's mostly hints so there is an implicit graceful degredation....

Sangwhan: agreed... the application should have a right to request... I'm an LGTM.

Yves: Same.