#895: Web Audio API: User-Selectable Render Quantum Size
Discussions
2023-10-23
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
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.
OpenedSep 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.
Further details:
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