@Hongchan Choi <[email protected]> can I think help with this question.
On Fri, Sep 25, 2026 at 7:58 AM Jan A <[email protected]> wrote: > Hello, > > Could you clarify the expected relationship between renderSizeHint and > physical audio round-trip latency in Chrome on macOS? > > When requesting a smaller render quantum, such as 64 or 32 frames, is it > expected that the actual AudioWorklet block size can decrease without a > corresponding reduction in physical input-to-output latency? > > Specifically: > > - Does renderSizeHint influence the CoreAudio input/output buffer > sizes, or only the processing block size within Web Audio? > - Are capture and output buffering configured independently of the Web > Audio render quantum? > - Is there a public tracking issue or documentation covering this > distinction and any planned work on reducing macOS audio I/O latency? > > We are interested in the expected behavior of a normal supported Chrome > installation, without command-line flags or system-level adjustments. > > Thank you for any clarification. > > Jan A > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/105dab86-11d4-4106-a8ee-a636cf73f332n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/105dab86-11d4-4106-a8ee-a636cf73f332n%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9YAKJox-ZfP1snHfpDUTqZyc%2Bx-F-9CC_MZ39SvzksSQ%40mail.gmail.com.
