Measure element latency

[Nicolas Dufresne]

Le mercredi 12 juin 2019 à 15:21 -0500, clubberlang a écrit :
> Is there a way to sample the tracers -- I would like the latency tracers to
> not write to disk as on a per-buffer basis. Also, is it the right approach
> to build our own custom version of latency on top of GstTracer?

There is already a fork at RidgeRun. My opinion is that it is best to
help improve the current upstream latency tracer instead of forking.
The forks tends to carry bugs that inaccuracies that we have worked
hard to fix upstream.

Now about pacing the output of the latency, this is best done outside
of the tracer. Trace points are not bound to a large data structure, so
to page the output of the latency tracer. So best is if we get these
tracer output hooks upstream, and then you can implement something on
top, rather then inside of it.

> 
> 
> 
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190612/29ebc211/attachment.sig>