Skip to content

Commit 5837204

Browse files
committed
Clarify preferred buffer size explanation
1 parent e25d2bd commit 5837204

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

CONFIGURATION.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -119,11 +119,11 @@ that the QA40x hardware queue is always being drained, and hopefully stays
119119
nearly empty at all times.
120120

121121
At 48 kHz, the best tradeoff between reliability and latency is likely to be
122-
1024 samples; this ensures there is always some data queued on the USB host side
123-
to keep the QA40x hardware output queue nearly filled at all times. Smaller
124-
buffers only make sense if you care about latency. Larger buffers will always
125-
improve reliability and efficiency by relaxing scheduling constraints and
126-
allowing for more data to be preloaded, but come with diminishing returns.
122+
1024 samples; this ensures the QA40x hardware queue is always full (under the
123+
assumption that buffer switches are instant). Smaller buffers only make sense if
124+
you care about latency. Larger buffers will always improve reliability and
125+
efficiency by relaxing scheduling constraints and allowing for more data to be
126+
preloaded, but come with diminishing returns.
127127

128128
At higher sample rates, it is recommended to use a larger buffer size due to the
129129
tigher buffer processing deadlines that could otherwise result in

0 commit comments

Comments
 (0)