<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Joe,</p>
<p><br>
</p>
<p>Not a direct answer to your question, but an idea for a
workaround I used that may help you:<br>
</p>
<p>I used identity with a hand-off function that simply counts
updates, then use a periodic timer to ensure updates keep coming
through.</p>
<p>When no buffers have come through, time to take action!</p>
<p><br>
</p>
<p>In my use-case I placed this after the mp4mux as it was refusing
to pass data on after some unusual data was received, but it's a
flexible approach.<br>
</p>
<p><br>
</p>
<p>I'd not be surprised if there is a standard pipeline element that
does something similar...</p>
<p><br>
</p>
Will.
<div class="moz-cite-prefix">On 17/04/2023 19:01, cfd new via
gstreamer-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:636351547.2467261.1681754516206@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="yahoo-style-wrap" style="font-family:Helvetica Neue,
Helvetica, Arial, sans-serif;font-size:13px;">
<div dir="ltr" data-setdir="false">how does the receiver(client
side) know quickly if the camera is unplugged or simply stops
for whatever reasons.</div>
<div dir="ltr" data-setdir="false">I tried to check EOS or ERROR
messages from the bus. However, it will take more than 30s to
see these messages <br>
</div>
<div dir="ltr" data-setdir="false">after the camera is
unplugged. This is kind of too long.<br>
</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false"> Joe<br>
</div>
</div>
</blockquote>
</body>
</html>