mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-12-15 08:56:38 -05:00
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
This commit is contained in:
parent
8249fa3cbf
commit
224f1f16f1
1 changed files with 4 additions and 0 deletions
|
|
@ -440,6 +440,10 @@ static void node_event_info(void *data, const struct pw_node_info *info)
|
||||||
case SPA_PARAM_PropInfo:
|
case SPA_PARAM_PropInfo:
|
||||||
case SPA_PARAM_Format:
|
case SPA_PARAM_Format:
|
||||||
case SPA_PARAM_EnumFormat:
|
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++;
|
changed++;
|
||||||
break;
|
break;
|
||||||
default:
|
default:
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue