Pauli Virtanen e446e3aac5 bluez5: media-source: account for driver clock rate difference in rate match ... The rate matching calculations are done in the system clock domain. If the driver ticks at a different rate, the correction factor needs to be adjusted by the rate_diff. setup_matching() also needs to be before spa_bt_decode_buffer_process(): as follower we should use rate matching value calculated on the *previous* cycle, because this is what driver is doing when it adjusts it tick rate.		2025-09-07 18:26:03 +00:00
..
examples	spa: examples: local-libcamera: pass camera id to the plugin	2025-08-01 15:40:28 +00:00
include	spa: fix typo in raw-types for LLFE	2025-09-05 15:44:22 +02:00
include-private/spa-private	spa: move dbus helpers out of bluez plugin	2024-02-05 13:03:20 +00:00
lib	pod: rework the parser	2025-07-29 15:15:02 +02:00
plugins	bluez5: media-source: account for driver clock rate difference in rate match	2025-09-07 18:26:03 +00:00
tests	pod: check that choices are not empty	2025-07-15 10:13:18 +02:00
tools	meson.build: make spa-json-dump available for subprojects	2025-07-23 12:19:21 +00:00
meson.build	meson: Always use -fno-strict-aliasing and -fno-strict-overflow	2025-07-24 07:30:28 +00:00