[gstreamer-bugs] [Bug 605594] relatively high cpu usage compared to other players

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=605594
  GStreamer | gstreamer (core) | 0.10.x

--- Comment #1 from Olaf Leidinger <leidola at web.de> 2009-12-28 11:53:45 UTC ---
Forgot to mention: gstreamer is 0.10.24
Same measurement for mp3 file:

FN=somefile.mp3
time mplayer  "$FN"; time gst-launch-0.10 playbin uri=file:///"`pwd`/$FN"; time
mpg123 "$FN"
MPlayer SVN-r29463-4.3.4 (C) 2000-2009 MPlayer Team
[cut]
==========================================================================
Öffne Audiodecoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 44100 Hz, 2 ch, s16le, 192.0 kbit/13.61% (ratio: 24000->176400)
Ausgewählter Audiocodec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
[cut]
real    7m8.355s
user    0m10.949s
sys    0m2.488s

(gst-launch-0.10:3415): GLib-WARNING **: g_set_prgname() called multiple times
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock
Got EOS from element "playbin0".
Execution ended after 428212510743 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

real    7m9.236s
user    0m25.162s
sys    0m2.296s
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
    version 1.9.2; written and copyright by Michael Hipp and others
    free software (LGPL/GPL) without any warranty but with best wishes
[cut]
MPEG 1.0 layer III, 192 kbit/s, 44100 Hz joint-stereo
Note: Illegal Audio-MPEG-Header 0x41504554 at offset 0x9cd6f1.
Note: Trying to resync...
Note: Hit end of (available) data during resync.
[cut]
real    7m8.331s
user    0m12.433s
sys    0m1.532s

In this case I get:

app:    relative cpu usage:
mplayer    1.0
gstreamer  2.3
mpg123     1.1

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.