Wim Taymans 1084cc24b6 alsa: handle the case where the driver is destroyed ... When the driver node is destroyed (like when unplugging the cable) it will drop/pause all of the follower ALSA nodes. This is something that happens internally because of how the ALSA nodes work together, on the PipeWire level, the nodes are still running and they will just be moved to another driver. The problem is that nothing will then start the nodes again after moving it to the new driver. Fix this by keeping track of the desired target state of the ALSA node and restoring that state when we detect that we are paused when moved to a new driver. Fixes #4401		2024-11-15 16:09:36 +01:00
..
examples
include	filter-chain: update channels from filter-graph	2024-11-15 10:53:45 +01:00
include-private/spa-private
plugins	alsa: handle the case where the driver is destroyed	2024-11-15 16:09:36 +01:00
tests
tools	spa: add spa_json_object_next	2024-09-16 09:50:36 +02:00
meson.build	require newer alsa 1.2.10 for UMP support	2024-07-30 10:06:41 +02:00