GStreamer-devel

Fwd: Vsicorp: Problems with GstShark - RidgeRun

Classic

List

Threaded

10 messages Options

jhanksv

Fwd: Vsicorp: Problems with GstShark - RidgeRun

In case others are having similar problems. gst-shark is not providing the output it should.

Has anyone else had similar issues?

John

-------- Forwarded Message --------

Subject:	Vsicorp: Problems with GstShark - RidgeRun
Date:	Wed, 29 May 2019 14:50:45 +0000 (GMT)
From:	Carlos Rodriguez [hidden email]
To:	John Hanks [hidden email], support [hidden email]
CC:	Miguel Angel Taylor López [hidden email]

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.

Regards,

- 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.

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'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?

John

Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:

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

Nicolas Dufresne-5

Re: Fwd: Vsicorp: Problems with GstShark - RidgeRun

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?

The latency and interlatency tracers in GstShark are no longer useful
in my opinion. Julian and I (Collabora) have fixed many issues and came
up with a completely upstream solution for this.

Since 1.16, you can now use the upstream latency tracer to get three
type of information:

- Complete pipeline latency
- Per element latency (not the cumulative like interlatency did)
- Per element reported latency

To enable all of these:

GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...

The initial issue we had with the RidgeRun implementation was a bug
inherited from the original upstream tracer. The time spent in the the
wait function of the sink was included. We also found that the
cumulative latency wasn't so nice to debug the reported latency. The
reported latency tracing is completely new. That being said, thanks to
RidgeRun for the proof of concept.

Nicolas

> John
>
>
> -------- Forwarded Message --------
> Subject: Vsicorp: Problems with GstShark - RidgeRun
> Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
> From: Carlos Rodriguez <[hidden email]>
> To: John Hanks <[hidden email]>, support <[hidden email]>
> CC: Miguel Angel Taylor López <[hidden email]>
>
>
> 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.
>
> Regards,
> - 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.
>
> 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'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?
>
> John
>
>
>
> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
> _______________________________________________
> 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

Nicolas Dufresne-5

Re: Fwd: Vsicorp: Problems with GstShark - RidgeRun

In reply to this post by jhanksv

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?
> John
>
>
> -------- Forwarded Message --------
> Subject: Vsicorp: Problems with GstShark - RidgeRun
> Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
> From: Carlos Rodriguez <[hidden email]>
> To: John Hanks <[hidden email]>, support <[hidden email]>
> CC: Miguel Angel Taylor López <[hidden email]>
>
>
> 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.
>
> Regards,
> - 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
monitor.

>
> 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.
transacoding rate).

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?
>
> John
>
>
>
> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
> _______________________________________________
> 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

jhanksv

Re: Fwd: Vsicorp: Problems with GstShark - RidgeRun

In reply to this post by Nicolas Dufresne-5

This seems to work with the command line example but when I try it from
my C-program using these lines in the code:

setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);

I get no 'trace' output. Any idea what am I doing wrong?

John

On 5/31/19 08:11, Nicolas Dufresne wrote:

> 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?
> The latency and interlatency tracers in GstShark are no longer useful
> in my opinion. Julian and I (Collabora) have fixed many issues and came
> up with a completely upstream solution for this.
>
> Since 1.16, you can now use the upstream latency tracer to get three
> type of information:
>
> - Complete pipeline latency
> - Per element latency (not the cumulative like interlatency did)
> - Per element reported latency
>
> To enable all of these:
>
> GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...
>
>
> The initial issue we had with the RidgeRun implementation was a bug
> inherited from the original upstream tracer. The time spent in the the
> wait function of the sink was included. We also found that the
> cumulative latency wasn't so nice to debug the reported latency. The
> reported latency tracing is completely new. That being said, thanks to
> RidgeRun for the proof of concept.
>
> Nicolas
>
>> John
>>
>>
>> -------- Forwarded Message --------
>> Subject: Vsicorp: Problems with GstShark - RidgeRun
>> Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
>> From: Carlos Rodriguez <[hidden email]>
>> To: John Hanks <[hidden email]>, support <[hidden email]>
>> CC: Miguel Angel Taylor López <[hidden email]>
>>
>>
>> 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.
>>
>> Regards,
>> - 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.
>>
>> 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'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?
>>
>> John
>>
>>
>>
>> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
>> _______________________________________________
>> 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

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

Nicolas Dufresne-5

Re: Fwd: Vsicorp: Problems with GstShark - RidgeRun

Le mardi 04 juin 2019 à 21:29 -0400, John Hanks a écrit :
> This seems to work with the command line example but when I try it from
> my C-program using these lines in the code:
>
> setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
> setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);
>
> I get no 'trace' output. Any idea what am I doing wrong?

Do you properly set the env before calling gst_init() (or any variant
of this) ?

>
> John
>
> On 5/31/19 08:11, Nicolas Dufresne wrote:
> > 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?
> > The latency and interlatency tracers in GstShark are no longer useful
> > in my opinion. Julian and I (Collabora) have fixed many issues and came
> > up with a completely upstream solution for this.
> >
> > Since 1.16, you can now use the upstream latency tracer to get three
> > type of information:
> >
> > - Complete pipeline latency
> > - Per element latency (not the cumulative like interlatency did)
> > - Per element reported latency
> >
> > To enable all of these:
> >
> > GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...
> >
> >
> > The initial issue we had with the RidgeRun implementation was a bug
> > inherited from the original upstream tracer. The time spent in the the
> > wait function of the sink was included. We also found that the
> > cumulative latency wasn't so nice to debug the reported latency. The
> > reported latency tracing is completely new. That being said, thanks to
> > RidgeRun for the proof of concept.
> >
> > Nicolas
> >
> > > John
> > >
> > >
> > > -------- Forwarded Message --------
> > > Subject: Vsicorp: Problems with GstShark - RidgeRun
> > > Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
> > > From: Carlos Rodriguez <[hidden email]>
> > > To: John Hanks <[hidden email]>, support <[hidden email]>
> > > CC: Miguel Angel Taylor López <[hidden email]>
> > >
> > >
> > > 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.
> > >
> > > Regards,
> > > - 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.
> > >
> > > 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'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?
> > >
> > > John
> > >
> > >
> > >
> > > Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
> > > _______________________________________________
> > > 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
> _______________________________________________
> 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

Michael Gruner

Problems with GstShark - RidgeRun

Hi Nicolas,

Thanks for jumping in. Our goal with GstShark is to provide a tool to developers so they can identify bottlenecks in the pipelines in an easy, visual way. The first step towards that was to add CTF support to the project. Next we wanted to provide a nice visualisation tool to consume this CTF and plot the data, even en real time. We never quite got to the later (yet).

It would be great if we could use your tracers as well, and eventually merge ours into mainline. That would leave GstShark as an independent front-end, and RidgeRun would focus on developing hardware specific tracers. A good starting point for the transition is to add CTF support to your tracers. We can clean up the CTF support and prepare a merge request into GStreamer.

Would that be something someone on your team could review and work with us to merge in mainline?

Regards,

Michael

PD:

For cpuusage, that sounds very similar to upstream rusage tracer. Could be nice if someone tells me

the difference.

The CPU tracers is simply that, prints the CPU usage every N seconds. To do so it parses /proc/stat instead of using getrusage() as you do. There is no reason to keep it if rusage is upstream, it’s there because we weren’t aware of yours back then on 1.7 when tracing first started. We need the CTF output though.

On Jun 4, 2019, at 8:43 PM, Nicolas Dufresne <[hidden email]> wrote:

Le mardi 04 juin 2019 à 21:29 -0400, John Hanks a écrit :
This seems to work with the command line example but when I try it from
my C-program using these lines in the code:

setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
    setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);

I get no 'trace' output. Any idea what am I doing wrong?

Do you properly set the env before calling gst_init() (or any variant
of this) ?

John

On 5/31/19 08:11, Nicolas Dufresne wrote:
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?
The latency and interlatency tracers in GstShark are no longer useful
in my opinion. Julian and I (Collabora) have fixed many issues and came
up with a completely upstream solution for this.

Since 1.16, you can now use the upstream latency tracer to get three
type of information:

  - Complete pipeline latency
  - Per element latency (not the cumulative like interlatency did)
  - Per element reported latency

To enable all of these:

GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...

The initial issue we had with the RidgeRun implementation was a bug
inherited from the original upstream tracer. The time spent in the the
wait function of the sink was included. We also found that the
cumulative latency wasn't so nice to debug the reported latency. The
reported latency tracing is completely new. That being said, thanks to
RidgeRun for the proof of concept.

Nicolas

John

-------- Forwarded Message --------
Subject: Vsicorp: Problems with GstShark - RidgeRun
Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
From: Carlos Rodriguez <[hidden email]>
To: John Hanks <[hidden email]>, support <[hidden email]>
CC: Miguel Angel Taylor López <[hidden email]>

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.

Regards,
- 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.

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'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?

John

Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
_______________________________________________
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
_______________________________________________
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

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

Michael Gruner

Problems with GstShark - RidgeRun

In reply to this post by jhanksv

Hi John

Just tested a fresh clone on a Ubuntu 16.04 box running gst 1.14.1 and worked. It looks like GstShark tracers are not being properly installed. Latency is not part of our installation, but upstream. Can you double check that you configured the project as the following:

./autogen.sh --libdir /usr/lib/x86_64-linux-gnu/ --prefix /usr

Otherwise GStreamer won’t be able to find them. Additionally, can you provide the output of the following:

gst-inspect-1.0 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsharktracers.so

Thanks!

Michael

www.ridgerun.com

GST_TRACERS="framerate;bitrate" GST_DEBUG=GST_TRACER:7 gst-launch-1.0 videotestsrc is-live=true ! fakesink

0:00:00.020323481 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d89c0 (cpuusage)

0:00:00.020358658 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8a80 (graphic)

0:00:00.020387450 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8b40 (proctime)

0:00:00.020426883 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8c00 (interlatency)

0:00:00.020447822 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8cc0 (scheduletime)

0:00:00.020460864 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8d80 (framerate)

0:00:00.020471561 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8e40 (queuelevel)

0:00:00.020482140 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8f00 (bitrate)

0:00:00.020531668 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x555757311810 (buffer)

0:00:00.020732953 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: framerate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", fps=(structure)"value\,\ type\=\(type\)guint\,\ description\=\(string\)\"Frames\\\ per\\\ second\"\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(uint\)0\,\ max\=\(uint\)4294967295\;";

0:00:00.020747257 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: framerate, pad=(string)%s, fps=(uint)%u;

0:00:00.020817151 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: bitrate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", bitrate=(structure)"value\,\ type\=\(type\)guint64\,\ description\=\(string\)Bitrate\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(guint64\)0\,\ max\=\(guint64\)18446744073709551615\;";

0:00:00.020827605 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: bitrate, pad=(string)%s, bitrate=(guint64)%lu;

Setting pipeline to PAUSED ...

Pipeline is live and does not need PREROLL ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

0:00:00.787144028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)20275200;

0:00:00.787207946 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)22;

0:00:01.788378328 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:01.788449999 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

0:00:02.787562028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:02.787620822 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

On May 30, 2019, at 8:30 PM, John Hanks <[hidden email]> wrote:

In case others are having similar problems. gst-shark is not providing the output it should.
Has anyone else had similar issues?

John

-------- Forwarded Message --------

Subject: Vsicorp: Problems with GstShark - RidgeRun

Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)

From: Carlos Rodriguez [hidden email]

To: John Hanks [hidden email], support [hidden email]

CC: Miguel Angel Taylor López [hidden email]

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.

Regards,

- 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.

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'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?

John

Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:

_______________________________________________
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

jhanksv

Re: Fwd: Vsicorp: Problems with GstShark - RidgeRun

In reply to this post by Nicolas Dufresne-5

I think so. This is my exact code:

setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
     setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);

   /* Initialize GStreamer */
   gst_init (&argc, &argv);

-----------

I have aslo tried settign the environment variable in the shell and then
running the program.

John

On 6/4/19 22:43, Nicolas Dufresne wrote:

> Le mardi 04 juin 2019 à 21:29 -0400, John Hanks a écrit :
>> This seems to work with the command line example but when I try it from
>> my C-program using these lines in the code:
>>
>> setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
>> setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);
>>
>> I get no 'trace' output. Any idea what am I doing wrong?
> Do you properly set the env before calling gst_init() (or any variant
> of this) ?
>
>> John
>>
>> On 5/31/19 08:11, Nicolas Dufresne wrote:
>>> 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?
>>> The latency and interlatency tracers in GstShark are no longer useful
>>> in my opinion. Julian and I (Collabora) have fixed many issues and came
>>> up with a completely upstream solution for this.
>>>
>>> Since 1.16, you can now use the upstream latency tracer to get three
>>> type of information:
>>>
>>> - Complete pipeline latency
>>> - Per element latency (not the cumulative like interlatency did)
>>> - Per element reported latency
>>>
>>> To enable all of these:
>>>
>>> GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...
>>>
>>>
>>> The initial issue we had with the RidgeRun implementation was a bug
>>> inherited from the original upstream tracer. The time spent in the the
>>> wait function of the sink was included. We also found that the
>>> cumulative latency wasn't so nice to debug the reported latency. The
>>> reported latency tracing is completely new. That being said, thanks to
>>> RidgeRun for the proof of concept.
>>>
>>> Nicolas
>>>
>>>> John
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: Vsicorp: Problems with GstShark - RidgeRun
>>>> Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)
>>>> From: Carlos Rodriguez <[hidden email]>
>>>> To: John Hanks <[hidden email]>, support <[hidden email]>
>>>> CC: Miguel Angel Taylor López <[hidden email]>
>>>>
>>>>
>>>> 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.
>>>>
>>>> Regards,
>>>> - 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.
>>>>
>>>> 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'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?
>>>>
>>>> John
>>>>
>>>>
>>>>
>>>> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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

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

jhanksv

Re: Problems with GstShark - RidgeRun

In reply to this post by Michael Gruner

Yes, this appears to be what I used in a slightly different order from your website:

Ubuntu 64 bits	--prefix /usr/ --libdir /usr/lib/x86_64-linux-gnu/

I copied and pasted it in.

The output from gst-inspect is:

Plugin Details:
Name                     sharktracers
Description              GstShark tracers
Filename                 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsharktracers.so
Version                  0.6.1.1
License                  LGPL
Source module            gst-shark
Source release date      2019-05-24 02:22 (UTC)
Binary package           GstShark
Origin URL               https://github.com/RidgeRun/gst-shark

cpuusage (GstTracerFactory)
graphic (GstTracerFactory)
proctime (GstTracerFactory)
interlatency (GstTracerFactory)
scheduletime (GstTracerFactory)
framerate (GstTracerFactory)
queuelevel (GstTracerFactory)
bitrate (GstTracerFactory)
buffer (GstTracerFactory)

9 features:
+-- 9 tracers

As I type this, I am in the process of upgrading from 1.15.0 to what looks like 1.16.0. I thought I had already done that before. Let me see if that helps.

Will I need to re-install gst-shark after I do that?

John

On 6/5/19 18:44, Michael Gruner wrote:

Hi John

Just tested a fresh clone on a Ubuntu 16.04 box running gst 1.14.1 and worked. It looks like GstShark tracers are not being properly installed. Latency is not part of our installation, but upstream. Can you double check that you configured the project as the following:

./autogen.sh --libdir /usr/lib/x86_64-linux-gnu/ --prefix /usr

Otherwise GStreamer won’t be able to find them. Additionally, can you provide the output of the following:

gst-inspect-1.0 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsharktracers.so

Thanks!

Michael

www.ridgerun.com

GST_TRACERS="framerate;bitrate" GST_DEBUG=GST_TRACER:7 gst-launch-1.0 videotestsrc is-live=true ! fakesink

0:00:00.020323481 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d89c0 (cpuusage)

0:00:00.020358658 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8a80 (graphic)

0:00:00.020387450 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8b40 (proctime)

0:00:00.020426883 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8c00 (interlatency)

0:00:00.020447822 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8cc0 (scheduletime)

0:00:00.020460864 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8d80 (framerate)

0:00:00.020471561 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8e40 (queuelevel)

0:00:00.020482140 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8f00 (bitrate)

0:00:00.020531668 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x555757311810 (buffer)

0:00:00.020732953 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: framerate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", fps=(structure)"value\,\ type\=\(type\)guint\,\ description\=\(string\)\"Frames\\\ per\\\ second\"\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(uint\)0\,\ max\=\(uint\)4294967295\;";

0:00:00.020747257 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: framerate, pad=(string)%s, fps=(uint)%u;

0:00:00.020817151 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: bitrate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", bitrate=(structure)"value\,\ type\=\(type\)guint64\,\ description\=\(string\)Bitrate\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(guint64\)0\,\ max\=\(guint64\)18446744073709551615\;";

0:00:00.020827605 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: bitrate, pad=(string)%s, bitrate=(guint64)%lu;

Setting pipeline to PAUSED ...

Pipeline is live and does not need PREROLL ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

0:00:00.787144028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)20275200;

0:00:00.787207946 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)22;

0:00:01.788378328 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:01.788449999 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

0:00:02.787562028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:02.787620822 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

On May 30, 2019, at 8:30 PM, John Hanks <[hidden email]> wrote:

In case others are having similar problems. gst-shark is not providing the output it should.

Has anyone else had similar issues?

John

-------- Forwarded Message --------

Subject: Vsicorp: Problems with GstShark - RidgeRun

Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)

From: Carlos Rodriguez [hidden email]

To: John Hanks [hidden email], support [hidden email]

CC: Miguel Angel Taylor López [hidden email]

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.

Regards,

- 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.

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'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?

John

Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:

_______________________________________________
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

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

jhanksv

Re: Problems with GstShark - RidgeRun

I have upgrades gstreamer to 1.17.0. I have done a new git and autogen/make/make install and still seem to have the same issues.

Some output does come on the screen when looking for latency but not for anything else. IF I try to have it saved to disk, it does not. My code starts with:

setenv("GST_SHARK_LOCATION","/tmp/profile",TRUE);
setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);

/* Initialize GStreamer */
gst_init (&argc, &argv);

--------

At some point during testing today, it did create a directory on disk but I cannot tell what command I was using at the time - I found the directory while I was upgrading gstreamer - and I have not been able to recreate it now that I am on 1.17.0.

John

On 6/6/19 19:45, John Hanks wrote:

Yes, this appears to be what I used in a slightly different order from your website:

Ubuntu 64 bits --prefix /usr/ --libdir /usr/lib/x86_64-linux-gnu/

I copied and pasted it in.

The output from gst-inspect is:

Plugin Details:
Name                     sharktracers
Description              GstShark tracers
Filename                 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsharktracers.so
Version                  0.6.1.1
License                  LGPL
Source module            gst-shark
Source release date      2019-05-24 02:22 (UTC)
Binary package           GstShark
Origin URL               https://github.com/RidgeRun/gst-shark

cpuusage (GstTracerFactory)
graphic (GstTracerFactory)
proctime (GstTracerFactory)
interlatency (GstTracerFactory)
scheduletime (GstTracerFactory)
framerate (GstTracerFactory)
queuelevel (GstTracerFactory)
bitrate (GstTracerFactory)
buffer (GstTracerFactory)

9 features:
+-- 9 tracers

As I type this, I am in the process of upgrading from 1.15.0 to what looks like 1.16.0. I thought I had already done that before. Let me see if that helps.

Will I need to re-install gst-shark after I do that?

John

On 6/5/19 18:44, Michael Gruner wrote:
Hi John

Just tested a fresh clone on a Ubuntu 16.04 box running gst 1.14.1 and worked. It looks like GstShark tracers are not being properly installed. Latency is not part of our installation, but upstream. Can you double check that you configured the project as the following:

./autogen.sh --libdir /usr/lib/x86_64-linux-gnu/ --prefix /usr

Otherwise GStreamer won’t be able to find them. Additionally, can you provide the output of the following:

gst-inspect-1.0 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsharktracers.so

Thanks!

Michael

www.ridgerun.com

GST_TRACERS="framerate;bitrate" GST_DEBUG=GST_TRACER:7 gst-launch-1.0 videotestsrc is-live=true ! fakesink

0:00:00.020323481 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d89c0 (cpuusage)

0:00:00.020358658 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8a80 (graphic)

0:00:00.020387450 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8b40 (proctime)

0:00:00.020426883 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8c00 (interlatency)

0:00:00.020447822 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8cc0 (scheduletime)

0:00:00.020460864 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8d80 (framerate)

0:00:00.020471561 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8e40 (queuelevel)

0:00:00.020482140 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x5557571d8f00 (bitrate)

0:00:00.020531668 1559 0x555757287a40 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register:<registry0> update existing feature 0x555757311810 (buffer)

0:00:00.020732953 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: framerate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", fps=(structure)"value\,\ type\=\(type\)guint\,\ description\=\(string\)\"Frames\\\ per\\\ second\"\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(uint\)0\,\ max\=\(uint\)4294967295\;";

0:00:00.020747257 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: framerate, pad=(string)%s, fps=(uint)%u;

0:00:00.020817151 1559 0x555757287a40 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: bitrate.class, pad=(structure)"scope\,\ type\=\(type\)gchararray\,\ related-to\=\(GstTracerValueScope\)GST_TRACER_VALUE_SCOPE_PAD\;", bitrate=(structure)"value\,\ type\=\(type\)guint64\,\ description\=\(string\)Bitrate\,\ flags\=\(GstTracerValueFlags\)GST_TRACER_VALUE_FLAGS_AGGREGATED\,\ min\=\(guint64\)0\,\ max\=\(guint64\)18446744073709551615\;";

0:00:00.020827605 1559 0x555757287a40 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: bitrate, pad=(string)%s, bitrate=(guint64)%lu;

Setting pipeline to PAUSED ...

Pipeline is live and does not need PREROLL ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

0:00:00.787144028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)20275200;

0:00:00.787207946 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)22;

0:00:01.788378328 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:01.788449999 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

0:00:02.787562028 1559 0x555757287a40 TRACE GST_TRACER :0:: bitrate, pad=(string)videotestsrc0_src, bitrate=(guint64)27648000;

0:00:02.787620822 1559 0x555757287a40 TRACE GST_TRACER :0:: framerate, pad=(string)videotestsrc0_src, fps=(uint)30;

On May 30, 2019, at 8:30 PM, John Hanks <[hidden email]> wrote:

In case others are having similar problems. gst-shark is not providing the output it should.

Has anyone else had similar issues?

John

-------- Forwarded Message --------

Subject: Vsicorp: Problems with GstShark - RidgeRun

Date: Wed, 29 May 2019 14:50:45 +0000 (GMT)

From: Carlos Rodriguez [hidden email]

To: John Hanks [hidden email], support [hidden email]

CC: Miguel Angel Taylor López [hidden email]

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.

Regards,

- 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.

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'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?

John

Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <[hidden email]>:

_______________________________________________
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
_______________________________________________
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