since the pulseaudio topic is closed... [Co carrier]

[ethoxyethaan]

the last person posted this in the topic:

so please be patient (or try to disable your pulse audio) for a while.

Well i tried to disable pulseaudio (removing pulseaudio binaries / reconfiguring alsa) the same problem popped up, (Teamspeak using up 100%CPU).

the previous client version (ts2) diden't work on any linux install as well so i used the windows version in combination with wine from http://www.winehq.org/ everything on the client worked (atleast better than on the linux version, with exceptions of some graphical glitches and push to talk outside the wine environment). to my surprise the Windows version of teamspeak 3 works on linux perfectly (except the problem with "Push to talk" again), so i guess as a temporary solution linux users could use the windows binaries since those got tested and are confirmed working.

[Master_D]

i use "padsp" as a loader for Teamspeak3 for using with Pulseaudio. I've had no problems until now, so you can test it. Maybe it will help you.

so you change to your client-folder and use "padsp ./ts3client_linux_x86" if you use a 32bit Linux, else you have to change the name of the client-binary in this command.

[ethoxyethaan]

i use "padsp" as a loader for Teamspeak3 for using with Pulseaudio. I've had no problems until now, so you can test it. Maybe it will help you.

so you change to your client-folder and use "padsp ./ts3client_linux_x86" if you use a 32bit Linux, else you have to change the name of the client-binary in this command.

Yes ive tried that, on both TS2 and TS3 this won't solve the problem. (i have audio and it works flawless, but it uses 2x100 CPU on my computer.) but no diff between using padsp and just pulseaudio.

the only problems i had on linux with some was involving teamspeak and the old version of the Java plugin for the browser.

[Master_D]

ok, i've tested it another time, to see the CPU-usage.

With padsp both of my cores using about 40% of their maximum, maybe it is a configuration-problem in pulseaudio.

can you test it on another linux-system, to find out, if it is only on your special system?

[ethoxyethaan]

ok, i've tested it another time, to see the CPU-usage.

With padsp both of my cores using about 40% of their maximum, maybe it is a configuration-problem in pulseaudio.

can you test it on another linux-system, to find out, if it is only on your special system?

Nothing is very special about my system. Ubuntu 9.10 default installation, updated all the way from 6.04. Pulseaudio is pretty default on ubuntu / debian / Fedora. and those are the most used Distrobutions. i don't think its good practice that my system needs to change just to run something, i can understand dependencies but 'conflicts' are bad practice.

[Master_D]

I've tested it once more for a longer time, and now it would use also 100% of both cores. Maybe it is fixed in Beta5. Time to test

[R. Ludwig]

no, no fmod uptate yet

[WoFNuLL]

yesterday one alsa sound Update on Ubuntu Updater ... but no issue Fix ... just try another sound device

[brechdurchall]

Same Problem with beta5 ... would be nice to reopen the origin thread

[lord_phantom]

Did anyone report this bug to the Fmod community? Are they aware of this problem?

[Actium]

I posted this in another thread. This way I've been able to easily get rid of Pulseaudio on Karmic:

Unfortunately the approach of disabling Pulseaudio has some - if you're lucky only minor - adverse effects. For example the audio applet will stop working (you'll have to adjust your audio settings using alsamixer in a terminal), the sound settings won't open any more and additional applications, which rely on pulseaudio being present, might just stop working as expected or completely.

Disabling Pulseaudio in Ubuntu 9.10 is pretty straighforward:

echo "autospawn = no" > ~/.pulse/client.conf
pulseaudio -k

If you want to reenable it:

rm ~/.pulse/client.conf
pulseaudio -D

Make sure you're not overwriting any settings you might have made to your user's PA client.conf, using the commands above. I rely on it being empty/non-existent, which it should be on a vanilla karmic.

[roul04]

As i wrote in the other thread:
It makes no sense to disable PA if you want to use Apps that rely on it. This has to be fixed where the problem is and not at the symptoms!

[ethoxyethaan]

As i wrote in the other thread:
It makes no sense to disable PA if you want to use Apps that rely on it. This has to be fixed where the problem is and not at the symptoms!

Fedora, Ubuntu, Mandriva, Linux Mint, and openSUSE use PA (i thin since Debian Squeeze as well) but not for KDE installs.

what distro did the Devs test it on?