Does the period cap exist on Windows?
https://learn.microsoft.com/en-us/windows-hardware/drivers/audio/low-latency...
It's not exactly what I would call a "cap", `AudioClient::Initialize()` simply ignores the `period` parameter when opening a stream in shared mode. The article states:
Before Windows 10, the buffer was always set to ~10 ms.
Starting with Windows 10, the buffer size is defined by the audio driver (more details on the buffer are described later in this article).
Later on, the article proceeds to describe `IAudioClient3`'s functionality:
Allow an application to discover the range of buffer sizes (that is, periodicity values) that are supported by the audio driver of a given audio device. This makes it possible for an application to choose between the default buffer size (10 ms) or a small buffer (less than 10 ms) when opening a stream in shared mode. If an application doesn't specify a buffer size, then it will use the default buffer size.
I'm assuming they kept 10 ms as the default even for this new interface in fear of potential glitches that could arise with lower latencies, especially when dealing with multiple devices and/or streams.
If yes, can you add tests for that?
https://gitlab.winehq.org/wine/wine/-/blob/7eb72b7bb3d3ea771efddcb5273e8a694...