From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Zahari Doychev <zahari.doychev@linux.com>,
Fabio Estevam <festevam@gmail.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jean-Michel Hautbois <jhautbois@gmail.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: Using the coda driver with Gstreamer
Date: Wed, 18 Feb 2015 08:34:43 -0500 [thread overview]
Message-ID: <54E494F3.6030302@collabora.com> (raw)
In-Reply-To: <20150218084245.GB30358@riot.fritz.box>
Le 2015-02-18 03:42, Zahari Doychev a écrit :
>> gst-launch-1.0 filesrc
>> >location=/home/H264_test1_Talkinghead_mp4_480x360.mp4 ! qtdemux !
>> >h264parse ! v4l2video1dec ! videoconvert ! fbdevsink
> I am using this pipeline with gstreamer 1.4.5 and current media branch but I am
> getting very poor performance 1-2 fps when playing 800x400 video. Is it possible
> that fbdevsink is too slow for that? Does anyone know what is going wrong?
In this context, you most likely have a conversion happening in
videoconvert followed by a copy at fbdevsink. Framebuffer device is not
a very good solution if performance matter (no possible zero-copy).
Specially if the selected framebuffer color format does not match the
decoded format.
Nicolas
next prev parent reply other threads:[~2015-02-18 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 17:29 Using the coda driver with Gstreamer Fabio Estevam
2014-11-17 17:45 ` Nicolas Dufresne
2014-11-17 18:20 ` Fabio Estevam
2014-11-17 17:48 ` Andrey Utkin
2014-11-17 18:23 ` Fabio Estevam
2014-11-17 18:55 ` Robert Schwebel
2014-11-17 19:58 ` Fabio Estevam
2014-11-18 18:08 ` Fabio Estevam
2014-11-18 18:41 ` Nicolas Dufresne
2014-12-01 19:17 ` Fabio Estevam
2015-02-18 8:42 ` Zahari Doychev
2015-02-18 13:34 ` Nicolas Dufresne [this message]
2015-02-19 7:24 ` Zahari Doychev
2015-02-19 13:30 ` Nicolas Dufresne
-- strict thread matches above, loose matches on Subject: below --
2014-11-18 21:51 Peter Seiderer
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=54E494F3.6030302@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=festevam@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=jhautbois@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
--cc=slongerbeam@gmail.com \
--cc=zahari.doychev@linux.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).