[w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843)

I'm requesting a TAG review of RenderCapacity API.

Generally, the Web Audio renderer’s performance is affected by the machine speed and the computational load of an audio graph. However, Web Audio API does not expose a way to monitor the computational load, and it leaves developers no options to detect glitches that are the essential part of UX in audio applications. Providing developers with a “glitch indicator” is getting more important because the scale of audio applications grows larger and more complex. (Developers have been asking for this feature [since 2018](https://github.com/WebAudio/web-audio-api-v2/issues/40#issue-494445229).)

  - Explainer: [bit.ly/render-capacity-explainer](https://bit.ly/render-capacity-explainer) (will be moved to a markdown doc soon)
  - Specification URL: https://webaudio.github.io/web-audio-api/#AudioRenderCapacity (Editor's Draft)
  - Tests: N/A
  - User research: N/A
  - Security and Privacy self-review²: See the Privacy Concern section in the explainer.
  - Primary contacts:
      - 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
  - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/WebAudio/web-audio-api/issues/2444
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5180333360676864

Further details:

  - [v] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: 2023 Q2~Q3
  - The group where the work on this specification is currently being done: W3C Audio WG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): N/A
  - Major unresolved issues with or opposition to this specification: 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


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/843
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/843@github.com>