Red Hat Bugzilla – Bug 508470
playing music takes too much CPU (gstreamer pulsesink inefficiencies)
Last modified: 2010-06-28 09:20:02 EDT
Description of problem:
When playing music on an older machine, the music player and pulseaudio processes take together about 40% of CPU. I've tried rhythmbox, exaile and gst-launch, all seem to have the same problem.
Music players not using gstreamer work fine, the usage is about 10%. Also, when redirecting the output to alsasink (with pulseaudio plugin enabled) instead of pulsesink, the usage is a bit lower, but still not good.
I'd suspect there is a bad interaction with pulseaudio or an unnecessary resampling in the audio path.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. gst-launch filesrc location=foo.flac \! flacdec \! pulsesink
2. watch CPU usage
I'm experiencing pretty high CPU usage on my C2D as well - currently I've reverted whole pulseaudio package back to version 0.9.15-14.fc11 as version in rawhide is not usable at all.
Anyway this fc11 version takes over 10% of my C2D - which nearly equals to the time needed for mpeg4 decompression for some smaller movies.
I remember times when audio playback of mp3 was not visible in top - so I'd like to see same perfomance again.
If it's not possible with PA than its usage should be made only optional for those who like to waste CPU power....
I would suggest to reassign this bug to pulseaudio component.
Seems to be now duplicate of #514739
This is slightly different, players not using gstreamer don't use that much CPU, so I'd suspect gstreamer's pulsesink.
Created attachment 358322 [details]
PulseAudio message from LG LT20
I have similar on both desktop and notebook. Reverting to old version of PulseAudio fixes the issue on desktop but I found out sound module fom LG LT20 got bug that made volume-control erratic (stop working after suspend).
Passing on to Pulseaudio as per last comment.
*** Bug 514739 has been marked as a duplicate of this bug. ***
This is a problem with the pulsesink interaction with PulseAudio:
From the upstream discussion it seems like it should be / is being addressed in gstreamer, so re-assigning back to the appropriate gstreamer package for now. If there's an upstream bug for this, perhaps we should close this as it's being handled upstream?
Fedora Bugzappers volunteer triage team
bastien, you seem to be the one who actually works on gstreamer-plugins-good these days, but the default assignee is ajax...re-assigning to you, perhaps the default needs to be changed. Adam doesn't seem to have touched the package since August 2008.
Fedora Bugzappers volunteer triage team
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.