LADI
/
spa
1
Fork 0
Code

impl-node: fix timing for client-nodes using trigger 

For client-nodes that use trigger, set the signal and wakeup time when
they start the server node. Also set finish time before we resume the
peers on the server.

Client-nodes should really resume the peers directly without going
through the server but this is something to improve later.
This commit is contained in:
Wim Taymans 2023-05-01 13:37:44 +02:00
parent c23c27b566
commit adb7559359
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/modules/module-client-node/remote-node.c
View File

@ -1193,6 +1193,7 @@ static int node_ready(void *d, int status)
a->state[0].status = status;
spa_system_clock_gettime(data_system, CLOCK_MONOTONIC, &ts);
a->signal_time = SPA_TIMESPEC_TO_NSEC(&ts);
a->awake_time = a->signal_time;
if (SPA_UNLIKELY(spa_system_eventfd_write(data_system, data->rtwritefd, 1) < 0))
pw_log_warn("node %p: write failed %m", node);

5
src/pipewire/impl-node.c
View File

@ -1775,6 +1775,11 @@ again:
if (SPA_UNLIKELY(node->driver && !node->driving))
return 0;
if (!node->driver) {
a->status = PW_NODE_ACTIVATION_FINISHED;
a->finish_time = nsec;
}
if (status & SPA_STATUS_HAVE_DATA) {
spa_list_for_each(p, &node->rt.output_mix, rt.node_link)
spa_node_process(p->mix);