<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">Le 28 févr. 2017 4:35 PM, "BogdanS" <<a href="mailto:bodyaf@gmail.com">bodyaf@gmail.com</a>> a écrit :<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nicolas Dufresne-5 wrote<br>
<div class="elided-text">> Le mardi 28 février 2017 à 12:10 -0800, BogdanS a écrit :<br>
>> How latency in rtpjitterbuffer works?<br>
>><br>
>> I have sender side that sends h264 over udp and reciever player with<br>
>> d3dvideosink in the end.<br>
>><br>
>> Reciever side: udpsrc-rtpjitterbuffer-parse-<wbr>decode-d3dvideosink.<br>
>><br>
>> If I put latency of rtpjitterbuffer to 1000, when I send from sendee<br>
>> with<br>
>> hight rate [x8] (fast playback ) memory usage are growing up to<br>
>> infinity. <br>
>> If I put latency to 100 , memory is not growing (or growing slow),<br>
>> but when<br>
>> I want to see 0.25 rate playback its really jitty.<br>
>> Using 1.6.1 gs.<br>
>> So my question if latency this is a time that jitterbuffer keeps<br>
>> inside or<br>
>> this is a diff between timestamps?<br>
>><br>
><br>
> That latency instruct the sinks to delay the playback. As a side<br>
> effect, data arriving on-time, will accumulate. They can accumulate in<br>
> the jitter buffer, but also in any queues inside your pipeline.<br>
><br>
> Nicolas<br>
</div>> ______________________________<wbr>_________________<br>
> gstreamer-devel mailing list<br>
<br>
> gstreamer-devel@.freedesktop<br>
<br>
> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/gstreamer-<wbr>devel</a><br>
><br>
><br>
> signature.asc (188 bytes)<br>
> <<a href="http://gstreamer-devel.966125.n4.nabble.com/attachment/4682053/0/signature.asc>" rel="noreferrer" target="_blank">http://gstreamer-devel.<wbr>966125.n4.nabble.com/<wbr>attachment/4682053/0/<wbr>signature.asc></a>;<br>
<br>
Thank you, Nicolas. If there is true, so why rtpjitterbuffer have no<br>
max-size-buffer or max-time option? In that case rtpjitterbuffer will no<br>
leak.<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">It does not need one, and it does not leak. It's doing exactly what you have asked.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/Rtpjitterbuffer-latency-question-tp4682052p4682054.html" rel="noreferrer" target="_blank">http://gstreamer-devel.966125.<wbr>n4.nabble.com/Rtpjitterbuffer-<wbr>latency-question-<wbr>tp4682052p4682054.html</a><br>
<div class="elided-text">Sent from the GStreamer-devel mailing list archive at Nabble.com.<br>
______________________________<wbr>_________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.<wbr>freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/gstreamer-<wbr>devel</a><br>
</div></blockquote></div><br></div></div></div>