Rtpjitterbuffer latency question

[BogdanS]

How latency in rtpjitterbuffer works?

I have sender side that sends h264 over udp and reciever player with d3dvideosink in the end.

Reciever side: udpsrc-rtpjitterbuffer-parse-decode-d3dvideosink.

If I put latency of rtpjitterbuffer to 1000, when I send from sendee with hight rate [x8] (fast playback )   memory usage are growing up to infinity.
If I put latency to 100 , memory is not growing (or growing slow), but  when I want to see 0.25 rate playback its really jitty.
Using 1.6.1 gs.
So my question if latency this is a time that jitterbuffer keeps inside or this is a diff between timestamps?

[Nicolas Dufresne-5]

Le mardi 28 février 2017 à 12:10 -0800, BogdanS a écrit :

> How latency in rtpjitterbuffer works?
>
> I have sender side that sends h264 over udp and reciever player with
> d3dvideosink in the end.
>
> Reciever side: udpsrc-rtpjitterbuffer-parse-decode-d3dvideosink.
>
> If I put latency of rtpjitterbuffer to 1000, when I send from sendee
> with
> hight rate [x8] (fast playback )   memory usage are growing up to
> infinity. 
> If I put latency to 100 , memory is not growing (or growing slow),
> but  when
> I want to see 0.25 rate playback its really jitty.
> Using 1.6.1 gs.
> So my question if latency this is a time that jitterbuffer keeps
> inside or
> this is a diff between timestamps?
>

That latency instruct the sinks to delay the playback. As a side
effect, data arriving on-time, will accumulate. They can accumulate in
the jitter buffer, but also in any queues inside your pipeline.

Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[BogdanS]

Nicolas Dufresne-5 wrote

Le mardi 28 février 2017 à 12:10 -0800, BogdanS a écrit :
> How latency in rtpjitterbuffer works?
>
> I have sender side that sends h264 over udp and reciever player with
> d3dvideosink in the end.
>
> Reciever side: udpsrc-rtpjitterbuffer-parse-decode-d3dvideosink.
>
> If I put latency of rtpjitterbuffer to 1000, when I send from sendee
> with
> hight rate [x8] (fast playback )   memory usage are growing up to
> infinity. 
> If I put latency to 100 , memory is not growing (or growing slow),
> but  when
> I want to see 0.25 rate playback its really jitty.
> Using 1.6.1 gs.
> So my question if latency this is a time that jitterbuffer keeps
> inside or
> this is a diff between timestamps?
>

That latency instruct the sinks to delay the playback. As a side
effect, data arriving on-time, will accumulate. They can accumulate in
the jitter buffer, but also in any queues inside your pipeline.

Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


signature.asc (188 bytes) <http://gstreamer-devel.966125.n4.nabble.com/attachment/4682053/0/signature.asc>

 Thank you, Nicolas.  If there is true, so why rtpjitterbuffer have no max-size-buffer or max-time option?  In that case rtpjitterbuffer will no leak.

[Nicolas Dufresne-5]

Le 28 févr. 2017 4:35 PM, "BogdanS" <[hidden email]> a écrit :

Nicolas Dufresne-5 wrote

> Le mardi 28 février 2017 à 12:10 -0800, BogdanS a écrit :
>> How latency in rtpjitterbuffer works?
>>
>> I have sender side that sends h264 over udp and reciever player with
>> d3dvideosink in the end.
>>
>> Reciever side: udpsrc-rtpjitterbuffer-parse-decode-d3dvideosink.
>>
>> If I put latency of rtpjitterbuffer to 1000, when I send from sendee
>> with
>> hight rate [x8] (fast playback )   memory usage are growing up to
>> infinity. 
>> If I put latency to 100 , memory is not growing (or growing slow),
>> but  when
>> I want to see 0.25 rate playback its really jitty.
>> Using 1.6.1 gs.
>> So my question if latency this is a time that jitterbuffer keeps
>> inside or
>> this is a diff between timestamps?
>>
>
> That latency instruct the sinks to delay the playback. As a side
> effect, data arriving on-time, will accumulate. They can accumulate in
> the jitter buffer, but also in any queues inside your pipeline.
>
> Nicolas

> _______________________________________________
> gstreamer-devel mailing list

> gstreamer-devel@.freedesktop

> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
> signature.asc (188 bytes)
> &lt;http://gstreamer-devel.966125.n4.nabble.com/attachment/4682053/0/signature.asc&gt;

 Thank you, Nicolas.  If there is true, so why rtpjitterbuffer have no
max-size-buffer or max-time option?  In that case rtpjitterbuffer will no
leak.

It does not need one, and it does not leak. It's doing exactly what you have asked.

--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Rtpjitterbuffer-latency-question-tp4682052p4682054.html

Sent from the GStreamer-devel mailing list archive at Nabble.com.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel