Why xvimagesink uses more cpu than ximagesink in this case?

[Yogesh Marwaha]

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> wrote:
>> 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