From 0785d3d7bc68437f5601c5be37d5a348498193ff Mon Sep 17 00:00:00 2001 From: Etienne Dechamps Date: Sat, 15 Jun 2024 17:50:12 +0100 Subject: [PATCH] Document KS buffer size vs WASAPI Exclusive --- BACKENDS.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/BACKENDS.md b/BACKENDS.md index 41ed237..00f5579 100644 --- a/BACKENDS.md +++ b/BACKENDS.md @@ -268,9 +268,11 @@ settings. In principle, similar results should be obtained when using WASAPI Exclusive and Kernel Streaming, since they both offer exclusive access to the hardware. WASAPI is simpler and less likely to cause problems, but Kernel Streaming is -more direct and more flexible. Furthermore, their internal implementation in -PortAudio are very different. Therefore, the WASAPI Exclusive and WDM-KS -PortAudio backends might behave somewhat differently depending on the situation. +more direct and more flexible. For example, Kernel Streaming will typically +provide access to underlying hardware buffer sizes that WASAPI Exclusive would +not use internally. Furthermore, the PortAudio implementation is very different. +Therefore, the WASAPI Exclusive and WDM-KS PortAudio backends might behave +somewhat differently depending on the situation. The WDM-KS backend cannot redirect the stream if the default Windows audio device changes while streaming.