From 03274a5b95146675c05b5b6a0340f45a7b122c50 Mon Sep 17 00:00:00 2001
From: Chris Robinson <chris.kcat@gmail.com>
Date: Fri, 2 Mar 2018 12:46:31 -0800
Subject: Ensure at least the specified ringbuffer size is writable
Previously, all but one of the specified size could be written (so for a size
of n, only n-1 was guaranteed writable). All users pretty much compensated for
this, but it makes more sense to fix it at the source.
---
Alc/backends/mmdevapi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
(limited to 'Alc/backends/mmdevapi.c')
diff --git a/Alc/backends/mmdevapi.c b/Alc/backends/mmdevapi.c
index 34dcf468..961cba52 100644
--- a/Alc/backends/mmdevapi.c
+++ b/Alc/backends/mmdevapi.c
@@ -1810,7 +1810,7 @@ static HRESULT ALCmmdevCapture_resetProxy(ALCmmdevCapture *self)
return hr;
}
- buffer_len = maxu(device->UpdateSize*device->NumUpdates + 1, buffer_len);
+ buffer_len = maxu(device->UpdateSize*device->NumUpdates, buffer_len);
ll_ringbuffer_free(self->Ring);
self->Ring = ll_ringbuffer_create(buffer_len,
FrameSizeFromDevFmt(device->FmtChans, device->FmtType, device->AmbiOrder),
--
cgit v1.2.3