Wim Taymans 02c332bb78 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-18 10:54:30 +01:00
..
examples	examples: fix mapoffset in examples	2024-06-13 10:11:29 +02:00
include	keys: add lazy scheduling flags and docs	2024-11-11 15:03:43 +01:00
include-private/spa-private	spa: move dbus helpers out of bluez plugin	2024-02-05 13:03:20 +00:00
plugins	alsa: handle the case where the driver is destroyed	2024-11-18 10:54:30 +01:00
tests	Add GNU/Hurd support	2023-09-24 15:11:52 +00:00
tools	spa: improve JSON error reporting in spa-json-dump	2024-03-27 15:57:39 +01:00
meson.build	meson: fix conflicting use of feature-based dependency lookups	2024-07-12 10:28:29 +02:00