Hi, Date: Fri, 15 Oct 2010 08:38:45 +0200 From: Brendan Le Foll <[email protected]> To: jms yang <[email protected]> Cc: [email protected] Subject: Re: [MeeGo-dev] gstremaer message gone Message-ID: <[email protected]<[email protected]> > Content-Type: text/plain; charset=ISO-8859-1
On 15 October 2010 04:50, jms yang <[email protected]> wrote: > so, you mean either setting the "GST_DEBUG" and "--gst-debug-level" are not > able to enable the message dump. > It is VERY VERY important for multimedia debugging and?development. > anyone knows why they did it? Yep that's exactly what it means. And i'm guessing to make it that tiny tiny bit faster? It's not just a tiny improvement, as there checks like (for instance) class casting for each pad_push occurring. You'll maybe not realise this if you're playing a 25fps video clip (where you don't care about latencies and thus you can afford big buffers), but the overhead is quite high with a low-latency voip call, where there are around 100 buffers to be processed per second and more than 20 elements (=> more than 40 pads) processing them. In my experience the only way to have GStreamer with debug log is to install it through separate packages, not to be installed on the "production" images. At least as long as we care about performances.. P.S. sorry for replying with a different message id, but it appears there are no ways to use the fine digests to have barely sensible way to reply to a single message.. and I don't like to be spammed with a 100+ messages a day to which I'm not interested. Regards
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
