Fwd: Vsicorp: Problems with GstShark - RidgeRun
nicolas at ndufresne.ca
Fri May 31 12:18:45 UTC 2019
Le jeudi 30 mai 2019 à 22:30 -0400, John Hanks a écrit :
> In case others are having similar problems. gst-shark is not providing the output it should.
> Has anyone else had similar issues?
> -------- Forwarded Message --------
> Subject: Vsicorp: Problems with GstShark - RidgeRun
> Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
> From: Carlos Rodriguez <carlos.rodriguez at ridgerun.com>
> To: John Hanks <jhanks at vsicorp.com>, support <support at ridgerun.com>
> CC: Miguel Angel Taylor López <miguel.taylor at ridgerun.com>
> Hi John,
> Thanks for your interest in our products and services. RidgeRun is a company with over a decade of embedded Linux experience supporting NVIDIA, Xilinx, Freescale/NXP, and Texas Instruments SoC. RidgeRun focuses on embedded Linux and GStreamer. Many, but not all, of our customers are doing some sort of audio / video streaming ( https://shop.ridgerun.com/collections/all).
> Miguel (CC'ed) will help you with this GstShark problem. He will provide support shortly.
> - Carlos R.
> Ticket Name: Problems with GSTShark
> Ticket Description:
> I've been working with gstreamer for about a year and wanted to use your tools to profile my working pipelines (actually, programs) so I could debug future problems. I followed the instructions to 'git', make and install the code but I must have done something wrong. The only time it seems to do anything is when I set GST_TRACERS=latency. It then displays the latency in the running window like this:
> 0:00:01.739608128 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1558941909, ts=(guint64)1739572905;
> 0:00:01.773075049 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1588456647, ts=(guint64)1773053449;
> 0:00:01.806234476 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1617668782, ts=(guint64)1806211230;
> This output is odd because what I read says the it should create a new subdirectory and dump the information in a file. Even when I set that directory (GST_SHARK_LOCATION), it still dumps latency o the screen and and never creates a file.
I missed that question. The tracers output to the standard debug
facility in GStreamer. To dump to a file, you need to GST_DEBUG_FILE= .
I am looking forward adding trace override specific to tracers in the
future. This is so that someone could eventually implement a transform
function that output into another trace format, could be CTF, SysProf,
or simply to stream this over the network to implement an external
> If I try any of the other tracers (cpuusage,framerate, etc) it just hangs after starting the pipeline - and that is your example pipelines from the wiki.
I haven't analyzed these tracers yet. For cpuusage, that sounds very
similar to upstream rusage tracer. Could be nice if someone tells me
the difference. For framerate, upstream offsets fpsdisplaysink, which
can be used with text-overlay=0 and the -v option of gst-launch-1.0, it
can't give you the rate in the middle of a pipeline though (e.g.
Overlall, just remember that these are downstream tracers, so the
upstream folks on the gstreamer-devel may not be able to help, or fix
any bugs in these.
> I'm guessing I must have done something wrong with the installation but cannot figure out what.
> I'm running Ubuntu 16.04.6.
> Any ideas what I am doing wrong?
> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <jhanks at vsicorp.com>:
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
More information about the gstreamer-devel