Wim Taymans 060d0e1761 Revert "loop: don't call the hooks around blocking wait" ... This reverts commit 46dfa69f26. We do actually need to release the locks for now. The reason is that pipewire core will at various points do a blocking invoke into the thread-loop (which is the data-loop when using non-rt/async processing) to synchronize state. Because these functions are called with the thread-loop lock and from some other thread (like gstreamer) it causes a deadlock because the thread-loop is locked and can't run and the caller is waiting for the thread-loop to complete. See #4472		2025-06-26 12:45:29 +02:00
..
buffer	spa: inline some metadata functions	2024-11-26 12:46:58 +01:00
control	ump: fix program change 2.0 to 1.0 conversion	2025-05-09 11:51:20 +02:00
debug	spa: debug: pod: print unsigned numbers as unsigned	2025-01-05 21:33:03 +01:00
filter-graph	filter-graph: separate data and size for filter graph	2025-01-07 10:38:32 +01:00
graph	add per type API defines	2024-11-26 11:58:51 +01:00
interfaces/audio	add per type API defines	2024-11-26 11:58:51 +01:00
monitor	spa: fix device.profile key	2025-03-06 13:11:38 +01:00
node	audioconvert: add delay_frac to spa_io_rate_match	2025-01-19 17:11:13 +02:00
param	spa: add volume_ramp_scale enum type info	2025-06-13 11:53:42 +02:00
pod	pod: declare offset as unused in spa_pod_builder_bytes_end()	2025-05-29 09:08:40 +02:00
support	Revert "loop: don't call the hooks around blocking wait"	2025-06-26 12:45:29 +02:00
utils	spa: Add default: statements	2025-05-09 11:58:55 +02:00