From ceb3c90497d1a8f8c2a4015d2f2c966573e5d7bc Mon Sep 17 00:00:00 2001 From: Bryan Biedenkapp Date: Fri, 16 Aug 2024 11:40:07 -0400 Subject: [PATCH] I swear some day I'll learn to English well given its my primary language; --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6576ea84..c3ec34d2 100644 --- a/README.md +++ b/README.md @@ -160,7 +160,7 @@ This source repository contains configuration example files within the configs f If using local audio with `dvmbridge`, command line arguments for the input and output device *are* required. (See command line parameters below.) -On Windows, by default `dvmbridge` will default to using the WinMM (Windows Multimedia API), this should work for most uses. If necessary, in some situations (like many instances of `dvmbridge` for example), it may be desirable to use the Windows high-performance audio subsystem, WASAPI (Windows Audio Session API), normally `dvmbridge` will simply default to using WinMM on Windows sysetms, but +On Windows, by default `dvmbridge` will utilize WinMM (Windows Multimedia API), this should work for most uses. If necessary, in some situations (like many instances of `dvmbridge` for example), it may be desirable to use the Windows high-performance audio subsystem, WASAPI (Windows Audio Session API), normally `dvmbridge` will always default to using WinMM on Windows systems (even those with WASAPI support), but using the command line parameter `-wasapi` will force `dvmbridge` to utilize WASAPI instead. (This may help with some cases of where audio is choppy as well.) There is no other real configuration for a `dvmbridge` instance other then setting the appropriate parameters within the configuration files.