cowprod at gmail.com
Thu Apr 7 13:49:59 UTC 2016
May I post here gst-player debug ? or a link to the debug ?
2016-04-04 9:27 GMT+02:00 Sebastian Dröge-3 [via GStreamer-devel] <
ml-node+s966125n4676722h65 at n4.nabble.com>:
> On Fr, 2016-04-01 at 07:08 -0700, cowprod wrote:
> > Hi Sebastian,
> > I'm trying to retrieve information about the decoder use to play the
> > RTSP stream.
> The easiest would be to just take a look at the debug logs. The second
> easiest would be to use the GstBin API to iterate through playbin once
> it started playback, i.e. gst_bin_iterate() and
> gst_bin_iterate_recurse() could be useful here.
> Basically, if there is no audio in your pipeline anymore, the only
> latency you will observe from GStreamer is a) the video decoder latency
> and b) the rtpjitterbuffer latency.
> a) is most likely using vtdec here, Apple VideoToolbox based decoder.
> Unfortunately that API does not provide proper latency information so
> we're doing guesses here, and those guesses are better if you use
> baseline profile.
> You could alternatively try the libav software decoder, avdec_h264.
> b) is what you configure on rtspsrc.
> Sebastian Dröge, Centricular Ltd · http://www.centricular.com
> gstreamer-devel mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4676722&i=0>
> *signature.asc* (968 bytes) Download Attachment
> If you reply to this email, your message will be added to the discussion
> To unsubscribe from RTSP Latency, click here
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/RTSP-Latency-tp4676606p4676794.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel