Audacious causes excessive cpu usage while playing on Intrepid Alpha 4

[Mochtroid-X]

Binary package hint: audacious

While running Hardy, normal things like web browsing with Firefox, music with Audacious, bittorrent with KTorrent, and messaging with Pidgin would make my cpu idle at anywhere from 1.8Ghz to 2.2Ghz, with 2.4Ghz and 2.6Ghz spikes being quite rare. After installing Intrepid Alpha 4 on my computer I've noticed rather intense cpu usage and lagging on the desktop even when Audacious is the only program running:

starts playing:

http://pichostonline.com/u/080826/346d1d4faf.png

stops playing:
http://pichostonline.com/u/080826/25bfd5895e.png

If I check Processes in System Monitor it shows Audacious with cpu usage in the 40's.

[Martin Emrich (emme)]

Same here (current intrepid amd64). While audacious plays MP3 webradio, it uses ca. 55% CPU (2.8GHz Athlon 64 X2), which is way too much for a music player.

[Martin Emrich (emme)]

This is still a problem in intrepid today, I tried it again both with OSS and ALSA output. No pulseaudio running. What could I do to help? The upstream bugtracker seems to be down.

[Martin Emrich (emme)]

Hi!

I just disabled all those audio-enhancing gizmos that are enabled by default, and now the CPU load is down to 4%:
(not I am running LANG=de_DE, so I backtranslated the names of the buttons, possibly inaccurate)

- Go to preferences (CTRL+P)
- Audio pane: disable "active resampling" (or whatever it is called in LANG=C)
- Playback amplification pane: disable playback amplification

Of course one loses these features, but now the high CPU usage is gone. So IMHO this is not a bug, but a set of CPU-hungry features, that actually might bring a benefit to some users.

I propose that at least the active resampling should be off by default for new installations, as PulseAudio is now standard, and it does it's own resampling anyways.

Ciao

Martin

[Daniel Letzeisen (dtl131)]

Ubuntu Lucid/10.04 Desktop will be going to End-Of-Life (EOL) status next week. When it does, audacious 2.x packages will no longer be officially supported. I have decided that this would be a good point to clean out older audacious bugs.

I could not reproduce this bug in modern audacious versions (and the pulseaudio output is now the default anyway). I am setting this bug to Incomplete until someone confirms that it affects the audacious 3.x series found in Ubuntu Precise/12.04 and later. If it does, please set the bug to 'Confirmed' status. If it is no longer reproducible in audacious 3.x, no action is required and this bug will automatically become 'Invalid' after 60 days of inactivity.

Thanks for reporting this bug and please feel free to report audacious bugs in the future.

[Launchpad Janitor (janitor)]

[Expired for audacious (Ubuntu) because there has been no activity for 60 days.]