<div dir="auto"><div>Hi,<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 18 avr. 2023, 10 h 45, cfd new via gstreamer-devel <<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div></div>
<div dir="ltr">Thank you for your reply, Will. It is a good idea. It would be nice to have an element or event to handle this scenario.</div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Interesting project. I haven't used fallback sex either, for sure you can insert an IDR anywhere you want. So if you have a 5s prerecorded sequence, you can always use the and switch to your pre-recorded sequence until the rtsp part is restored. You can probably do that yourself too. The least painful method imho would be to use seperate pipeline. One for rtsp, one for file fallack, and one for the recording. Then with appsrc (2) and appsink (recording) you can multiplex in your app.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div dir="ltr"><br></div><div dir="ltr"> Joe<br></div><div><br></div>
</div><div id="m_7234967704003303646yahoo_quoted_2353926273">
<div style="font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a">
<div>
On Tuesday, April 18, 2023, 07:59:33 a.m. EDT, <a href="http://wm-gstreamer.switchd.net" target="_blank" rel="noreferrer">wm-gstreamer.switchd.net</a> via gstreamer-devel <<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">gstreamer-devel@lists.freedesktop.org</a>> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="m_7234967704003303646yiv5495979631"><div>
<p>Hi Joe,</p>
<p><br clear="none">
</p>
<p>Not a direct answer to your question, but an idea for a
workaround I used that may help you:<br clear="none">
</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 terminate!</p>
<p><br clear="none">
</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 clear="none">
</p>
<p><br clear="none">
</p>
<p>I'd not be surprised if there is a standard pipeline element that
does something similar...</p>
<p><br clear="none">
</p>
<p>Will.<br clear="none">
</p>
<p><br clear="none">
</p>
<div id="m_7234967704003303646yiv5495979631yqt99215"><div>On 17/04/2023 19:01, cfd new via
gstreamer-devel wrote:<br clear="none">
</div>
<blockquote type="cite">
</blockquote></div></div><div id="m_7234967704003303646yiv5495979631yqt46593"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px">
<div dir="ltr">how does the receiver(client
side) know quickly if the camera is unplugged or simply stops
for whatever reasons.</div>
<div dir="ltr">I tried to check EOS or ERROR
messages from the bus. However, it will take more than 30s to
see these messages <br clear="none">
</div>
<div dir="ltr">after the camera is
unplugged. This is kind of too long.<br clear="none">
</div>
<div dir="ltr"><br clear="none">
</div>
<div dir="ltr"> Joe<br clear="none">
</div>
</div>
</div></div></div></div>
</div>
</div></div></blockquote></div></div></div>