- From: Paul Adenot <notifications@github.com>
- Date: Tue, 24 Oct 2023 02:38:39 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 October 2023 09:38:45 UTC
No more than implementations have decided to make running an `AudioContext ` affect other web applications (or any application) running on the same device today. Creating and starting an `AudioContext`, in the overwhelming majority of cases (the exception being if the `AudioContextLatencyCategory` is [`"playback"`](https://webaudio.github.io/web-audio-api/#dom-audiocontextlatencycategory-playback)), will start a low-latency real-time audio stream on the device. This in turns _can_, depending on the OS and various other factors, lower the global latency and/or buffer size of all apps on the machine, or at least the programs that are using the same audio device. This is the case for any program that make use of low-latency audio. Allowing authors to pick a buffer size, or asking the OS for the best buffer size to use, isn't going to negatively change the impact of a web application on the rest of the system, because the default always has been something quite impactful already. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/895#issuecomment-1776866623 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/895/1776866623@github.com>
Received on Tuesday, 24 October 2023 09:38:45 UTC