From: Gary Thomas <gary@mlbassoc.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: New gst-player
Date: Thu, 05 Mar 2015 07:10:51 -0700 [thread overview]
Message-ID: <54F863EB.3030604@mlbassoc.com> (raw)
In-Reply-To: <CAP71WjxLNWnEcGtbFDkm6af1MK5LkpPZhujcZ5mN49jRf=MkYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
On 2015-03-05 06:47, Nicolas Dechesne wrote:
> On Thu, Mar 5, 2015 at 2:44 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2015-03-05 06:40, Nicolas Dechesne wrote:
>>>
>>> On Thu, Mar 5, 2015 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>
>>>> Sadly, it doesn't build with the libav we have in OE-core :-(
>>>>
>>>> BTW, I measured the current used by my board (i.MX6Q)
>>>> mplayer2 => 1.8A
>>>> gst-play => 2.1A
>>>> Given that I normally run my board with a 2.0A wall brick,
>>>> it's no wonder that it dies when I run gst-play.
>>>
>>>
>>> ouch. that's quite a difference. when you play video this is no just
>>> about the decoders, but also how video is rendered. can you
>>> check/compare what's the overall pipeline, including any processing
>>> done on the video buffers (YUV) after the decoder (including up/down
>>> scaling, color conversion, ...).
>>
>>
>> How would I get that info (short of hacking the library)?
>
>
> for Gstreamer you can print/display the actual pipeline by doing:
>
> export GST_DEBUG_DUMP_DOT_DIR=/tmp
>
> and then run your standard Gstreamer application, it will create .dot
> files in /tmp (you can use another folder), at each stage of the
> pipeline, you can print/share the pipeline when transitioning from
> PAUSE to PLAYING. The .dot file can be converted to a nice graph,
> using graphviz tool (e.g. dot -Tpng -O xxx.dot)
>
> that will give you all the information about the multimedia pipeline.
I ran the gst-play-1.0 and it created a single file. It looks pretty
when converted to an image, but I'm not sure what it tells me about
the actual pipeline.
>
> for mplayer, i don't know how to get the same info..
>
Given that it's the same file being played on the same hardware,
shouldn't both programs need to be doing the same conversions, etc?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: 0.00.00.616955667-gst-play.async-done.dot --]
[-- Type: application/msword-template, Size: 29209 bytes --]
[-- Attachment #3: 0.00.00.616955667-gst-play.async-done.dot.png --]
[-- Type: image/png, Size: 1293133 bytes --]
next prev parent reply other threads:[~2015-03-05 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 23:45 New gst-player Gary Thomas
2015-03-05 6:32 ` Burton, Ross
2015-03-05 12:16 ` Gary Thomas
2015-03-05 12:45 ` Burton, Ross
2015-03-05 12:54 ` Gary Thomas
2015-03-05 13:34 ` Gary Thomas
2015-03-05 13:40 ` Nicolas Dechesne
2015-03-05 13:44 ` Gary Thomas
2015-03-05 13:47 ` Nicolas Dechesne
2015-03-05 14:10 ` Gary Thomas [this message]
2015-03-05 14:19 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F863EB.3030604@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=nicolas.dechesne@linaro.org \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.