summaryrefslogtreecommitdiffstats
path: root/meta-pipewire/recipes-multimedia/pipewire/pipewire/0005-gst-pwaudioringbuffer-wait-only-for-STREAM_STATE_CON.patch
blob: eef08af809ab34ba348a9a10b5b85b2a5fe09791 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
From df47442f5396897f8bdba5a37699d21f0e4da85f Mon Sep 17 00:00:00 2001
From: George Kiagiadakis <george.kiagiadakis@collabora.com>
Date: Thu, 11 Jul 2019 16:34:35 +0300
Subject: [PATCH] gst/pwaudioringbuffer: wait only for STREAM_STATE_CONFIGURE
 when starting

The CONFIGURE state is reached when the pw_client_node is exported,
while the READY state requires the session manager to try and link
the stream. If the SM does not want to link the stream due to policy,
the client should not hang there forever.

Upstream-Status: Submitted [https://github.com/PipeWire/pipewire/pull/140]
---
 src/gst/gstpwaudioringbuffer.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/gst/gstpwaudioringbuffer.c b/src/gst/gstpwaudioringbuffer.c
index 97350f38..3efec6ec 100644
--- a/src/gst/gstpwaudioringbuffer.c
+++ b/src/gst/gstpwaudioringbuffer.c
@@ -442,9 +442,9 @@ gst_pw_audio_ring_buffer_acquire (GstAudioRingBuffer *buf,
           params, 1) < 0)
     goto start_error;
 
-  GST_DEBUG_OBJECT (self->elem, "waiting for stream READY");
+  GST_DEBUG_OBJECT (self->elem, "waiting for stream CONFIGURE");
 
-  if (!wait_for_stream_state (self, PW_STREAM_STATE_READY))
+  if (!wait_for_stream_state (self, PW_STREAM_STATE_CONFIGURE))
     goto start_error;
 
   pw_thread_loop_unlock (self->main_loop);
-- 
2.23.0