Why xvimagesink uses more cpu than ximagesink in this case?

Kevin Hawkins khawkins at hawkinscomputer.com
Sun Jul 24 13:35:07 PDT 2011

Should that be videotestsrc not audiotestsrc?

-----Original Message-----
gstreamer-devel-bounces+khawkins=hawkinscomputer.com at lists.freedesktop.org
[mailto:gstreamer-devel-bounces+khawkins=hawkinscomputer.com at lists.freedeskt
op.org] On Behalf Of Yogesh Marwaha
Sent: Sunday, July 24, 2011 1:16 PM
To: Discussion of the development of and with GStreamer
Subject: Re: Why xvimagesink uses more cpu than ximagesink in this case?

On 24 July 2011 22:02, Michael Smith <msmith at xiph.org> wrote:
> On Sun, Jul 24, 2011 at 7:55 AM, Yogesh Marwaha <yogeshm.007 at gmail.com>
>> Hi,
>> Just consider these simple pipelines:-
>> gst-launch -v audiotestsrc ! goom ! ffmpegcolorspace ! ximagesink
>> gst-launch -v audiotestsrc ! goom ! ffmpegcolorspace ! xvimagesink
>> 2nd uses more cpu than first; though one would think xvimagesink would be
>> better. Any explanation?
> goom produces RGB video. ximagesink can directly render that;
> xvimagesink (usually) cannot, so ffmpegcolorspace has to convert to a
> different video format. That takes a significant amount of cpu time.

Sounds like a valid explanation. Thanks.

Yogesh Marwaha
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org

More information about the gstreamer-devel mailing list