You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using rtspclientsink in a custom pipeline resulted in a hang in GstPipelineHandler::Stop(). The function would get called twice for the pipeline, and hang the second time through the call awaiting the READY to PAUSE state change.
Stack trace showed it down in gstrtspclientsink.c, waiting for a connection to be started again.
To fix, I added a single line after the mutex lock checking to see if the pipeline was already paused and not playing, and if so, don't do anymore state changes.
if (m_data->paused == true && m_data->playing == false) return;
The text was updated successfully, but these errors were encountered:
andbro-ep
added a commit
to andbro-ep/mrayGStreamerUnity
that referenced
this issue
Jun 9, 2023
This is a fix for the same problem as XPav had and it is the solution provided in the comment:
mrayy#48
Also fixed that the VS solution could be built, by removing flag and files from the build.
Using rtspclientsink in a custom pipeline resulted in a hang in
GstPipelineHandler::Stop()
. The function would get called twice for the pipeline, and hang the second time through the call awaiting the READY to PAUSE state change.Stack trace showed it down in
gstrtspclientsink.c
, waiting for a connection to be started again.To fix, I added a single line after the mutex lock checking to see if the pipeline was already paused and not playing, and if so, don't do anymore state changes.
The text was updated successfully, but these errors were encountered: