Nirbheek Chauhan 05a37d3791 wasapi: Clarify usage of low-latency property, add myself as author ... The low-latency property is *always* safe to enable, so applications that do realtime communication should set it, and the elements will automatically configure WASAPI to use the lowest possible device period, and the audioringbuffer in audiobasesink will also be configured accordingly. Applications can also use exclusive mode during capture and playback for the lowest possible latency if they know that the device will not be used by any other application. In this mode, the latency-time and buffer-time properties will be completely ignored.		2018-02-26 16:23:11 +05:30
..
gstaudioclient3.h	wasapi: Use IAudioClient3 interface when available	2018-02-26 16:23:11 +05:30
gstwasapi.c	wasapi: Set a default category for util functions	2018-02-26 16:23:11 +05:30
gstwasapidevice.c	wasapi: Fix indentation issues missed by the commit hook	2018-02-08 11:46:01 +05:30
gstwasapidevice.h	wasapi: Fix indentation issues missed by the commit hook	2018-02-08 11:46:01 +05:30
gstwasapisink.c	wasapi: Clarify usage of low-latency property, add myself as author	2018-02-26 16:23:11 +05:30
gstwasapisink.h	wasapi: Add a property for trying the AudioClient3 API	2018-02-26 16:23:11 +05:30
gstwasapisrc.c	wasapi: Clarify usage of low-latency property, add myself as author	2018-02-26 16:23:11 +05:30
gstwasapisrc.h	wasapi: Add a property for trying the AudioClient3 API	2018-02-26 16:23:11 +05:30
gstwasapiutil.c	wasapi: Set realtime thread priority at runtime	2018-02-26 16:23:11 +05:30
gstwasapiutil.h	wasapi: Set realtime thread priority at runtime	2018-02-26 16:23:11 +05:30
Makefile.am	wasapi: Implement a device provider for probing	2018-01-31 14:58:21 +05:30
meson.build	meson: Fix wasapi build on Windows	2018-02-08 14:41:33 +05:30