Wim Taymans 8748c77451 context: make driver runnable when we add a runnable node ... Explicitly make the driver runnable when we add a runnable node to it. We have to do this because the runnable node might not be directly linked to this driver. In the case of the echo-canceler, for example, a playback stream can be linked to the sink before the echo canceled virtual sink. All echo-cancel nodes are added to a source driver, which would not be activated because there is no direct path from the playback stream to the source river. Fixes #3145		2023-04-11 16:31:44 +02:00
..
daemon	module-link-factory: ignore link.passive by default	2023-03-28 15:19:16 +02:00
examples	core: add bound_props event	2023-03-21 17:22:27 +01:00
gst	gst: deviceprodiver: Sort devices by session priority	2023-03-11 10:55:07 +01:00
modules	filter-chain: fix bq_raw activate	2023-04-07 16:45:28 +02:00
pipewire	context: make driver runnable when we add a runnable node	2023-04-11 16:31:44 +02:00
tests	core: add bound_props event	2023-03-21 17:22:27 +01:00
tools	pw-cli: avoid property leak	2023-03-16 12:55:27 +01:00
meson.build	treewide: meson.build: use feature.allowed()	2022-02-04 00:15:59 +01:00