Wim Taymans 2ff62641b9 context: when forcing rate/quantum don't limit latency ... Usually, the max-latency is calculated by the device when it is configured based on the maximum buffer size and limits the latency change that can be done. When we are forcing a rate/quantum and we are going to reconfigure the device, this limit should not apply because the current buffer settings and latency are going to change because of the reconfigure. See #3613		2023-10-30 11:18:55 +01:00
..
daemon	conf: fix videotestsrc example configuration	2023-10-26 16:35:30 +02:00
examples	example: fix invalid free() operation in bluez-session	2023-10-22 14:48:44 +00:00
gst	pipewiresink: use maximum size of buffers to configure pool	2023-10-27 18:01:37 +02:00
modules	module-rtp-sap/sink: try to bind sockets to an explicit interface	2023-10-24 07:17:21 +00:00
pipewire	context: when forcing rate/quantum don't limit latency	2023-10-30 11:18:55 +01:00
tests	core: add bound_props event	2023-03-21 17:22:27 +01:00
tools	tools: make pw-dump/mon/top try to connect to the default manager socket	2023-10-24 07:08:07 +00:00
meson.build	treewide: meson.build: use feature.allowed()	2022-02-04 00:15:59 +01:00