From 224f1f16f1987d8be38126cc3e0b3a3c669e7522 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Thu, 21 Sep 2023 16:42:08 +0200 Subject: [PATCH] pulse-server: emit stream changed after Latency param change Piggy back on the Latency param change to emit a stream changed event because we now might have a link between the stream and a device. We should really watch for new links and emit change events for the streams that it links to. Fixes #3522 --- src/modules/module-protocol-pulse/manager.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/modules/module-protocol-pulse/manager.c b/src/modules/module-protocol-pulse/manager.c index c298ab8d7..35a8be14b 100644 --- a/src/modules/module-protocol-pulse/manager.c +++ b/src/modules/module-protocol-pulse/manager.c @@ -440,6 +440,10 @@ static void node_event_info(void *data, const struct pw_node_info *info) case SPA_PARAM_PropInfo: case SPA_PARAM_Format: case SPA_PARAM_EnumFormat: + /* also emit changed for the Latency param because the stream might + * now be linked. FIXME, we should check if a new link is made for + * a stream and only emit a changed event in that case. */ + case SPA_PARAM_Latency: changed++; break; default: