<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
Hi Michael,<br>
<br>
AppSrc ignores max-buffers and max-time, it just issues a warning
and continues buffering. Maybe it is intentional, or perhaps it is
because gst_base_src_loop is blocked, waiting for a reply from
gst_pad_peer_query. Leaky-type leads to a jerky, stuttering video.
is_live is already set to true.<br>
<br>
The scenario of events looks fundamentally wrong. So, I want to
understand what is going on.<br>
<br>
Andrey.<br>
<br>
<div class="moz-cite-prefix">25.08.2023 16:37, Michael Gruner пишет:<br>
</div>
<blockquote type="cite"
cite="mid:9F8936C3-DBDE-4D2F-892A-38204C227C0E@ridgerun.com">
<pre class="moz-quote-pre" wrap="">Hi Andrey,
You can use the max-bytes, max-buffers or max-time along with the leaky-type properties in the appsrc to avoid queueing data. For example `appsrc max-buffers=3 leaky-type=downstream` will only keep the latest 3 camera buffers and discard older ones. Also, if your buffers come from a camera set the `is-live=true` property as well. If I recall correctly, that'll let the pipeline know you're pushing data from a live source and will not perform this delay (don't quote me on that :) ). An initial PTS of 1000 hours is expected in video encoders, and is to allow reordering of frames where the first DTS can be lower than the first PTS.
Michael
</pre>
</blockquote>
</body>
<lt-container></lt-container>
</html>