From 264383cdd41d7ce1eff5bf8a064c21609b18148a Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Thu, 7 Mar 2019 18:34:39 +0100 Subject: [PATCH] remote-node: first run the tee and then signal ready We first need to run the tee so that all the io areas are ready before we can start the driver on the daemon. --- src/modules/module-client-node/remote-node.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/modules/module-client-node/remote-node.c b/src/modules/module-client-node/remote-node.c index 2bc8194b0..d1813a5f1 100644 --- a/src/modules/module-client-node/remote-node.c +++ b/src/modules/module-client-node/remote-node.c @@ -1176,11 +1176,15 @@ static int node_ready(void *d, int status) { struct node_data *data = d; struct pw_node *node = data->node; + struct pw_port *p; uint64_t cmd = 1; pw_log_trace("node %p: ready driver:%d exported:%d status:%d", node, node->driver, node->exported, status); + spa_list_for_each(p, &node->rt.output_mix, rt.node_link) + spa_node_process(p->mix); + if (write(data->rtwritefd, &cmd, sizeof(cmd)) != sizeof(cmd)) pw_log_warn("node %p: write failed %m", node);