Skip to content

Commit

Permalink
Document KS buffer size vs WASAPI Exclusive
Browse files Browse the repository at this point in the history
  • Loading branch information
dechamps committed Jun 15, 2024
1 parent b2e16cc commit 0785d3d
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions BACKENDS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 0785d3d

Please sign in to comment.