[gst-devel] Pipeline profiling.
ensonic at hora-obscura.de
Tue Apr 27 16:18:28 CEST 2010
> wl2776 wrote:
>> Debug output contains timestamps.
>> Are there any scripts, that can parse them and estimate, for example, the
>> time, required for seeking, for each element, or something else?
> Ok, I'll try to be more specific.
> I have compiled the seeking example
> $GStreamer_source/gst-plugins-base/tests/examples/seek/seek.c both in linux
> and in windows.
> I had to change it a little to compile in windows:
> replace GDK_WINDOW_XID with GDK_WINDOW_HWND in realize_cb
> and add
> #define VSINK "directdrawsink"
> The problem is that seeking on the same file is much slower in windows than
> in linux.
> I use playbin2 in both cases, and the same media file (MPEG2).
> Now I'd like to estimate what causes the delay.
> However, I'm not very familiar with all gstreamer debug categories and don't
> know which ones to switch on. This is important, because simple GST_DEBUG=5
> brakes everything and distorts the picture.
> Another problem, I'm not very familiar with playbin2 internals (have read
> about seeking and pipeline seeking in the design docs, hold its print right
> There is no problem in capturing the debug output and parsing it with some
> perl or python script.
> I just need to know what to capture and parse.
I recommend to log to a file (GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:5") and
then use gst-debug-viewer afterwards (its on git.freedesktop.org). If
its still too slow, try *:4 or maybe "*:4,*mpeg*:5".
More information about the gstreamer-devel