Why xvimagesink uses more cpu than ximagesink in this case?
msmith at xiph.org
Sun Jul 24 09:32:27 PDT 2011
On Sun, Jul 24, 2011 at 7:55 AM, Yogesh Marwaha <yogeshm.007 at gmail.com> wrote:
> 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.
More information about the gstreamer-devel