Specify the buffer size as itself instead of the period count

Certain backends don't need a buffer size to be a strict multiple of the period
count, which allows a little more flexibility. The period/update size simply
acts as the minimum request, which helps control CPU load by determining how
often parameter and other pre-mixing updates are processed.

1 files changed, 1 insertions, 1 deletions

diff --git a/Alc/backends/base.cpp b/Alc/backends/base.cpp
index ba5e5486..5239ae5b 100644
--- a/Alc/backends/base.cpp
+++ b/Alc/backends/base.cpp
@@ -51,7 +51,7 @@ ClockLatency BackendBase::getClockLatency()
      * any given time during playback. Without a more accurate measurement from
      * the output, this is an okay approximation.
      */
-    ret.Latency  = std::chrono::seconds{mDevice->UpdateSize*maxi(mDevice->NumUpdates-1, 0)};
+    ret.Latency  = std::chrono::seconds{maxi(mDevice->BufferSize-mDevice->UpdateSize, 0)};
     ret.Latency /= mDevice->Frequency;
 
     return ret;