<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/28/2015 07:26 PM, Rob wrote:<br>
</div>
<blockquote
cite="mid:CABhifwov+Kt=ZExg7Rbx_v46HS2EGv1YBGPe_WrgNoJVdbzvHg@mail.gmail.com"
type="cite">
<div dir="ltr">On 27 February 2015 at 18:59, Stefan Sauer <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:ensonic@hora-obscura.de" target="_blank">ensonic@hora-obscura.de</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> On 02/27/2015 12:38
AM, Rob wrote:<span class=""><br>
<span style="white-space:pre-wrap">><br>
> On Thursday, 26 February 2015, Stefan Sauer
<<a moz-do-not-send="true"
href="mailto:ensonic@hora-obscura.de"
target="_blank">ensonic@hora-obscura.de</a> <a
moz-do-not-send="true"
href="mailto:ensonic@hora-obscura.de"
target="_blank"><mailto:ensonic@hora-obscura.de></a>>
wrote:<br>
><br>
></span><br>
<blockquote type="cite">On 02/18/2015 12:53 PM,
Sebastian Dröge wrote:<br>
> On Di, 2015-02-17 at 16:59 +0000, Luis de
Bethencourt wrote:<br>
>> Hello everyone,<br>
>><br>
>> GStreamer is going to apply for Google
Summer of Code 2015. But we need<br>
>> your help!<br>
>><br>
>> We would really appreciate if you suggested
proposals, volunteered for<br>
>> mentoring, or added content to the
proposals.<br>
>><br>
>> Current list of proposals is here:<br>
>> <a moz-do-not-send="true"
href="http://gstreamer.freedesktop.org/GSOC/socprojects.html"
target="_blank">http://gstreamer.freedesktop.org/GSOC/socprojects.html</a><br>
<br>
> Does anybody have any other ideas, or would
like to be added as a<br>
> potential mentor for any of these projects?
Would be great to get some<br>
> more ideas and potential mentors so we can
properly handle all<br>
> projects :)<br>
<br>
What about porting gst-debug-viewer to gtk+3 and
improving it?<br>
<br>
</blockquote>
</span> Are you suggesting to make this a web-app? If
done cleverly (e.g. open log from url) could be sweet.</div>
</blockquote>
<div> </div>
<div>Imagine a world where for any GStreamer process, you
can do something like:</div>
<div><br>
</div>
<div>GST_DEBUG_PORT=8080</div>
<div><br>
</div>
<div>and then open <a moz-do-not-send="true"
href="http://localhost:8080/graphs">http://localhost:8080/graphs</a>
for a list of pipelines which you can then open to see
their graphs and see them update dynamically. They're
perhaps SVG pipelines that are interactive and
inspectable. Maybe you can even track buffers through the
paths through the pipeline or get statistics about how
long each element spends processing buffers, see each
element's latency contribution, see where overruns (full
queues) or underruns (empty queues) and a bunch of other
stuff are. I would love something like this.</div>
</div>
</div>
</div>
</blockquote>
We all would love that. With the gst-tracer branch we can expose
such data over a socket. One such consumer could be
gst-debug-viewer.<br>
Running this inprocess + the html rendering would have the benefit
that we could access arbitrary data without that we need to change
the socket protocol. <br>
<br>
But sofar I was under impression that running this in-process would
be less preferable as it could potentially affect performance quite
a bit.<br>
<blockquote
cite="mid:CABhifwov+Kt=ZExg7Rbx_v46HS2EGv1YBGPe_WrgNoJVdbzvHg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Random side-thought: An element knows best how its
input buffers map to output buffers, why not make it an
element's responsibility to indicate that mapping somehow
so that all buffer life cycles are completely mapped? That
plus hooks to get information about a buffer when it is
created / modified / copied / transformed into another
buffer / destroyed should allow some pretty shiny
investigative tools.</div>
</div>
</div>
</div>
</blockquote>
You get such this information in the gst-tracer. The buffer mapping
is more complicated. E.g. imagine buffers read from a file,
processed by demuxer. Should the outputs of the demuxer still be
marked as stemming from the input buffers? Then you do processing,
e.g. audio-resampling and video-rate adaptation. Now mapping
buffer-ids gets tricky for sure. Finally you mux into an output
stream. While there where input buffers containing the information
that also goes into e.g. stream headers, this is practically
unmappable.<br>
<br>
Regarding the tracer: <br>
<a class="moz-txt-link-freetext" href="https://bugzilla.gnome.org/show_bug.cgi?id=733187">https://bugzilla.gnome.org/show_bug.cgi?id=733187</a><br>
<br>
Stefan<br>
<blockquote
cite="mid:CABhifwov+Kt=ZExg7Rbx_v46HS2EGv1YBGPe_WrgNoJVdbzvHg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Rob</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>